Description of problem: On a Satellite with many test organizations created, I created an org "proxy-test", I tried a few times to select that org, but the web UI context menu keeps showing Any Organization Version-Release number of selected component (if applicable): Sat7 snap 6 7.0.0-6.0 How reproducible: not sure Steps to Reproduce: 1. On a Satellite with many orgs created by test automation 2. Create one org and try to select it in the web UI context menu Actual results: web UI context menu keeps showing Any Organization Expected results: web UI context menu shows org you select Additional info: I only created a proxy and loaded a manifest in the test org Will attach production logs
Hello further testing shows that selecting any organization apart from the Default Org takes you to Any Organization. Selecting Default Org works as expected.
Created redmine issue https://projects.theforeman.org/issues/34416 from this bug
Guys, this bug is causing a discovery regression in 7.0: https://bugzilla.redhat.com/show_bug.cgi?id=2058879 The current build of 7.0 is foreman-3.1.1.6 while the fix was fixed upstream in 3.1.2. So we need to backport this into 7.0
The context is, in our case for some reason an organization was created without any title: irb(main):004:0> Organization.unscoped.pluck(:id, :name, :label, :title) => [[1, "RedHat", "RedHat", "RedHat"], [3, "SCA", "SCA", nil]] Editing the organization in the UI saving it again restores the title. I believe this has something to do with this patch.
Hi Lukas, I have a couple of quick questions on comment 13. Based upon the feedback, should this bugzilla be in the failedQA state? For Satellite 7, we now in cherry-pick mode; therefore, we update to 3.1.2. Do you happen to know what commit (or commits) needed to be cherry-picked to address the issue? If so, can you associate the appropriate redmines to this bugzilla? Thanks!
I don't think there is anything wrong, from what we know (or think) the other BZ was tested on a snap that did not have this patch, then it was updates and organization was already created incorrectly (without title), then tests were performed and there was a misbehavior. Sayan is currently trying again now with the latest snap, so there is nothing to do in here. Sorry for the confusion, I commented before we actually figured it out.
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 (Moderate: Satellite 6.11 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:5498