Bug 1537796

Summary: Missing repo in content view if "Publish via HTTP" is changed
Product: Red Hat Satellite Reporter: Partha Aji <paji>
Component: Content ViewsAssignee: Partha Aji <paji>
Status: CLOSED ERRATA QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0Keywords: Triaged
Target Milestone: 6.4.0   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:01:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Partha Aji 2018-01-23 22:03:00 UTC
- Product P exists with Yum Repository R. Publish via HTTP is turned off!
- Content View CV exists with Repository R. Version 1 was published an promoted to Development.

We want to publish the CV and its Repository via HTTP. Therefore, we do:
- Change Publish via HTTP to on for Repository R.
- Publish a new Version of CV (Version 2) and promote it to Development

Result: The Repository in CV for environment Development is still not fully available via HTTP. 
Expected: Repository is reachable via HTTP in CV for environment Development. 

Issue found with Katello 3.4.5

Comment 1 Partha Aji 2018-01-23 22:03:08 UTC
Created from redmine issue http://projects.theforeman.org/issues/21612

Comment 2 Partha Aji 2018-01-23 22:03:17 UTC
Upstream bug assigned to paji

Comment 4 Satellite Program 2018-01-29 15:24:56 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21612 has been resolved.

Comment 5 Chris Brown 2018-06-27 15:45:44 UTC
Verified in Satellite 6.4

Comment 7 Bryan Kearney 2018-10-16 19:01:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.