Bug 1323553

Summary: Puppet modules not uploading
Product: Red Hat Satellite Reporter: jnikolak
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.8CC: bbuckingham, jnikolak
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-26 00:54:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description jnikolak 2016-04-04 04:31:49 UTC 
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.
Comment 2 Bryan Kearney 2016-07-26 19:00:33 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 3 Brad Buckingham 2016-08-26 00:48:32 UTC 
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!
Comment 4 jnikolak 2016-08-26 00:54:50 UTC 
I think close off the bug, if the issue occurs again, will reopen