Bug 1480353

Summary: Content sync/promotion fails to all capsules if one capsule is down
Product: Red Hat Satellite Reporter: Satellite Program <pm-sat>
Component: Capsule - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Patrik Segedy <psegedy>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.8CC: aagrawal, bbuckingham, bkearney, cdonnell, cpatters, jcallaha, jsherril, kbidarka, kdixon, mjahangi, mmccune, nitthoma, oshtaier, pmoravec, psegedy, xdmoon
Target Milestone: UnspecifiedKeywords: PrioBumpField, PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1448777 Environment:
Last Closed: 2018-02-21 17:00:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Patrik Segedy 2017-10-24 11:30:03 UTC
Steps to verify @satellite-6.3.0-20.0.beta.el7sat.noarch:
1. Have 2 capsules registered to Satellite and Library CV
2. Enable new repository
2. Start repo sync and make one capsule unavailable by allowing only ssh and dhcp in firewall during the sync
3. Sync on unavailable capsule failed and succeeded on the other capsule

VERIFIED

Comment 3 Bryan Kearney 2018-02-21 17:00:30 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.

https://access.redhat.com/errata/RHSA-2018:0336