Hide Forgot
Description of problem: I installed satellite with an external capsule that was registered to the server. The capsule was not connected to any org/loc so I wanted to add them. I clicked on the capsule to display it and then clicked on Edit. After choosing an org, loc and lifecycle environment I hit save. There was a message displayed that the capsule was updated successfully but I was still on the Edit page. I hit cancel and then checked, the capsule was updated as expected but there was no way to know from the UI response. Version-Release number of selected component (if applicable): Snap 8.2 How reproducible: Tried twice on new registered capsule, happened both times. Steps to Reproduce: 1. Install new capsule and register it to the Satellite server 2. Choose Any Organization/Any Location 3. Go to Infrastructure -> Capsules 4. Click on the capsule to display it 5. Click Edit 6. Update org/loc/lifecycle environment 7. Click Save Actual results: There is a message about successful update but you stay on the same page. Expected results: The capsule is saved and you are redirected to the capsules index page. Additional info: The capsule was registered to satellite with only foreman-installer. The capsule subscription-manager is not registered to the Satellite server.
Created redmine issue http://projects.theforeman.org/issues/14838 from this bug
Upstream bug assigned to oprazak
1. Selected Any Organization/Any Location 2. Went to Infrastructure -> Capsules 3. Clicked on the capsule to display it 4. Clicked Edit 5. Updated org 6. Clicked Save 7. UI gave a success message and lands us back on the show capsule page. 1. Selected Any Organization/Any Location 2. Went to Infrastructure -> Capsules 4. Clicked on the Edit button of the Capsule. 5. Updated org 6. Clicked Save 7. UI gave a success message and lands us back on the capsule index page. I am unable to reproduce this issue, anymore if this issue is seen again please feel free to re-open this bug. VERIFIED with sat62-snap(GA)-14.1
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/RHBA-2016:1501