Description of problem:
On creating a new organization via `manage organizations` page, the title of the Context-switching menu changes to 'Any Context' (however, according to the behavior, the context has changed to the newly created organization).
Version-Release number of selected component (if applicable):
sat 6.2.0 Beta (GA11)
Steps to Reproduce:
1. create a new organization using WebUI
2. Notice the Organization dropdown stays at/changes to 'Any Context'
3. navigating to some other resource, e.g. Activation Keys shows, we actually use the context of the new org (no 'select organization' dialog appears)
navbar menu says: "Any Context"
navbar menu changes to the name of the newly created Org
marking this as a blocker as almost every user using multiple organizations will see this as 1 of the first things in Satellite
Created redmine issue http://projects.theforeman.org/issues/17681 from this bug
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17681 has been resolved.
Setting as triaged as there's a fix already upstream
The context now changes to the new organization, after leaving the wizard 'the correct' way.
However, there is a case, after user creates an org, there is the 'assign host dialog' on this dialog, the context is still set to 'any context'...if user exits teh wizard by navigating to some other page (e.g. infrastructure->subnets), the context will stay at 'any' with the behavior of the newly created org.
I was able to reproduce the behaviour in comment #9, I think you can fail this.
Failing due to behaviour described in comment #9
Connecting redmine issue http://projects.theforeman.org/issues/21867 from this bug
the context is now correctly switched even on exiting the wizard prematurely
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