-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Galaxy install missing files #11706
Comments
Ouch, this really emphasizes that our CI does not cover wholly the collection usage :/ |
8700495 is only in 2.26 though so I'm not sure how you have this on 2.25 ? Could you check if the linked PR fix your issue ? |
The 2.25 was a silly mistake on my part. The rest of the details do reference 2.26 and that is what I was using. |
Referencing version 2.25 was a mental error on my part. I was actually using 2.26 and my steps to reproduce use that version. The PR shoud fix the immediate issue I had, but does not appear to me to entirely fix the issue. This is a list I put together of the files that are missing (not including tests, OWNERS files, one README.md and one .gitkeep file). Note that several of the files do not have an extension:
I got this list by running a find command on the roles directory that was designed to return only files not matching the extensions that the Galaxy manifest process includes by default. |
Hum, maybe a better way to fix this is actually to do something like
- recursive-include roles files/*
Since regardless of the extension, anythings we put in files/ should be needed
|
What happened?
Using Kubespray v2.25.0 using a galaxy install from github (as part of a larger ansible process)
During installing Calico with the API server enabled, got error containing:
Could not find or access 'openssl.conf'
Investigating showed that even though the file existed in the Git repository in the
files
directory of thenetwork_plugins/calico
role, it did not exist in the installed collection.What did you expect to happen?
Successful install of Calico including API Server and the rest of Kubernetes
How can we reproduce it (as minimally and precisely as possible)?
Set up a one node inventory, with
calico_apiserver_enabled
set to true and run the followingThe text was updated successfully, but these errors were encountered: