Created attachment 355854 [details] The highlighted text refers to an Organizations tab above (that is not there) Steps to Reproduce: 1. create two orgs orgA orgB with a trust between them 2. log into orgA and create a public channel 3. log into orgB and register a system setting its base channel to the shared channel from orgA 4. log into to orgA and change the public base channel to protected... Just before hitting the "Deny Access and Confirm", you will see a screen with the message: You may choose to grant the organizations below access to this channel, or you may deny them access. You can modify access to this channel at any time using the 'Organizations' tab above. Actual results: There is no "'Organizations' tab above." (see the screen shot attached) Expected results: Because the 'Organizations' tab is only accessible once the channel is actually protected, the message should say: At this time, you may choose to grant all the organizations below access to this channel, or you may deny all of them access. Once this channel is protected, it can be selectively shared with any of the following organizations on the 'Organizations' tab.
I agree the message is confusing. Changing just: [-You-]{+Once the channel is protected, you+} can modify access to this channel at any time using the 'Organizations' [-tab above.-]{+tab.+} spacewalk.git: 48a377d93b9d972e62082256df2f10c3d7d3f007
VERIFIED on Satellite-5.6.0-RHEL6-re20130917.0 Steps to reproduce in comment 0. You may choose to grant the organizations below access to this channel, or you may deny them access. Once the channel is protected, you can modify access to this channel at any time using the 'Organizations' tab.
Satellite 5.6 has been released. This bug was tracked under the release. This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly before release). Moving to CLOSED CURRENT_RELEASE. Text from Upgrade Erratum follows: 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. http://rhn.redhat.com/errata/RHEA-2013-1395.html