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.
Steps to reproduce
#################
0) Create a custom puppet module
1) Go to a content View
2) Go to puppet-modules
3) Select a puppet module
4) Choose the repository
Inhouse_puppet_repository
5) Upload the module.
This is where the issue was reproduced during the 10:34 timestamp.
/orgx-Inhouse_puppet_modules-Inhouse_puppet_repository/?details=true HTTP/1.1" 200 791 "-" "Ruby"
- - [04/Apr/2016:10:33:34 +1000] "GET /katello/api/v2/repositories/73?organization_id=3 HTTP/1.1" 304 - "https://satfqdn/products/39/repositories/73" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0"
6) However no errors appears on the Satellite, its like somehow the name has been corrupted.
if we choose a different name, the module uploads fine.
7) We resolved this issue, by creating a new repository, with the same name.
Uploading a different module first.
Then uploading the module having issues.
8) Then removing the repository, recreating and it works.
9) Seems there was a corruption in the database.
foreman-debug attached.
I was not able to reproduce this on Satellite 6.2. Would it be possible for you to retry it there? If not, could you share the puppet module (tar.gz) that was causing the error? Thanks!