-
Notifications
You must be signed in to change notification settings - Fork 169
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
repository_set
cannot find the repository
#1736
Comments
Can you show us the output of |
|
"Good" (for some values of good, at least). This says that your Katello thinks there are no repositories available. That can have multiple reasons: connection problems reaching |
requesting https://xxx/katello/api/repository_sets/7416/available_repositories?organization_id=1 gives the following error in the production.log
I must have made some error, when I converted the manifest to be ansible controlled, removing access to them. However, it is confusing that the web ui shows them as available on https://xxx/redhat_repositories with the selector set to
returns 12 results, among others the When making the above query the production.log does not contain |
I think the UI just assumes enabled repos to be available, and thus "tricks" you in the view. |
Yes, the syncs were also failing. I clicked the It does not seem like anything needs to be changed in the foreman-ansible-modules, unless you want to suggest refreshing the manifest in the error message. |
I don't think changing the error message makes sense (there are many different reasons why repos can't be found, this is just one of them) But I pinged @jeremylenz whether Katello could more prominently expose the need for a refresh in the UI. |
SUMMARY
repository_set
cannot find the repositoryHammer can find it and see that it is enabled
ISSUE TYPE
ANSIBLE VERSION
COLLECTION VERSION
KATELLO/FOREMAN VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
The repository_set is already enabled, so it should just be
ok
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: