Skip to content
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

Ansible Galaxy Repo failed to synchronize case-sensitive role name #747

Closed
pulpbot opened this issue Nov 17, 2021 · 3 comments
Closed

Ansible Galaxy Repo failed to synchronize case-sensitive role name #747

pulpbot opened this issue Nov 17, 2021 · 3 comments

Comments

@pulpbot
Copy link
Member

pulpbot commented Nov 17, 2021

Author: stosem (stosem)

Redmine Issue: 9534, https://pulp.plan.io/issues/9534


The galaxy.ansible.com API uses case-insensitive fields for the owner username and role name. The Ansible Galaxy Hub source code: https://github.com/ansible/galaxy/blob/e0e4b909171ddc6ca40f0ef2f7d4dce5680777ce/galaxy/api/views/roles.py#L50

But pulp usesnamespace=namespace. It causes the error on case-sensitive repositories (404 not found, or empty set). An example:

Galaxy Ansible returns the same result. But pulp isn't.

So we can't install roles like this using regular ansible-galaxy install oefenweb.postfix command with the Pulp repo.

@pulpbot
Copy link
Member Author

pulpbot commented Nov 17, 2021

From: stosem (stosem)
Date: 2021-10-25T15:23:45Z


Pull request: #670

@pulpbot
Copy link
Member Author

pulpbot commented Nov 17, 2021

From: @mdellweg (mdellweg)
Date: 2021-10-26T08:46:57Z


This sounds like we would need appropriate uniqueness constraints in the database to prevent both "tEst" and "TeSt" to exist as namespaces.

@fao89
Copy link
Member

fao89 commented Dec 15, 2021

@fao89 fao89 closed this as completed Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants