Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
if I upload to repository more puppet modules with the same name (but different authors)
for example
http://forge.puppetlabs.com/puppetlabs/rubyhttp://forge.puppetlabs.com/ecbypi/ruby
then I cannot publish that repo
> content definition publish --org org --name def --view_name view
Selected puppet repository has 1 name conflict(s) and cannot be published.
but I think it should not be problem to have more puppet modules with the same name in repository
Version-Release number of selected component (if applicable):
ruby193-rubygem-katello-foreman-engine-0.0.12-7.el6sat.noarch
ruby193-rubygem-katello_api-0.0.3-4.el6sat.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-certs-tools-1.4.4-1.el6sat.noarch
katello-common-1.4.6-63.el6sat.noarch
katello-glue-elasticsearch-1.4.6-63.el6sat.noarch
katello-cli-1.4.3-29.el6sat.noarch
katello-all-1.4.6-63.el6sat.noarch
ruby193-rubygem-foreman-katello-engine-0.0.17-7.el6sat.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-agent-1.4.4-3.el6sat.noarch
katello-glue-candlepin-1.4.6-63.el6sat.noarch
katello-cli-common-1.4.3-29.el6sat.noarch
katello-1.4.6-63.el6sat.noarch
pulp-katello-plugins-0.2-1.el6sat.noarch
katello-configure-foreman-1.4.7-7.el6sat.noarch
katello-glue-pulp-1.4.6-63.el6sat.noarch
katello-selinux-1.4.4-4.el6sat.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-foreman-all-1.4.6-63.el6sat.noarch
katello-configure-1.4.7-7.el6sat.noarch
signo-katello-0.0.23-2.el6sat.noarch
How reproducible:
always
Steps to Reproduce:
1. repo content_upload --repo puppy --product product --org org --content_type puppet --filepath /tmp/ecbypi-ruby-0.0.3.tar.gz
2. repo content_upload --repo puppy --product product --org org --content_type puppet --filepath /tmp/puppetlabs-ruby-0.1.0.tar.gz
3. content definition add_repo --org org --name def --repo puppy --product product
4. content definition publish --org org --name def --view_name view
Actual results:
Selected puppet repository has 1 name conflict(s) and cannot be published.
Expected results:
Content view published successfully
Additional info:
note that it is also not possible to publish repository which contains more versions of one puppet module
Comment 1RHEL Program Management
2013-11-08 11:25:39 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
This is by design, though we could certainly make it easier + clearer. Puppet can't distinguish between two classes with the same name - the author and version metadata are removed when installing these modules, so they look identical. It only makes sense to have a single module per name within a published content view.