Description of problem: user is looking at a host within new_org, going for lunch, the sat will automatically sign him out from satellite, when he gets back and log in, the new host page details is showing an empty host. In this case user is required to notice that he was logged in to default taxonomy and is not possible to load such a host. The expected result, we tell the user that his request is wrong. Version-Release number of selected component (if applicable): sat 6.11 snap 14 How reproducible: Always Steps to Reproduce: Apply on the description above but without waiting. 1. Create a host with a different organization as default 2. Make sure that your user will open with default taxonomies on login (I think it is by default) 3. copy URL https://<sat-fqdn>/new/hosts/<host-fqdn>#/Overview 4. log out 5. paste URL 6. use credentials to log in Actual results: host page is empty trying and it seems it's trying to load as shown on attached screen 1. Expected results: Old UI is resolving this with an Error, "Host not found Please try to update your request" attachment 2 [details].
Upstream bug assigned to afeferku
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33862 has been resolved.
Easier reproducer: create two hosts in two different org, open the host details, change the organization actual and expected results are same in this scenario as in the description
it is getting unpredictable when in one browser tab the host details is opened, and then in the other tab organization is changed get back to the first browser tab and click between tabs, things are not loaded, but user is not aware of that, because on his tab the organization is still shown the same, just data are not loaded anymore, of course until reload
Verified on Sat 6.12 snap 6
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 (Important: Satellite 6.12 Release), 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-2022:8506
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days