Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
How to reproduce:
1. assign puppet environment to organization
2. go to organization details, in environments check "All environments" button
3. go to environment details: the organization is unassigned from the organization.
With this behavior, checking the "all environments" lead to loosing the whole information about the originally assigned organization. Unchecking "all environments" later would end up with organization without environments.
Expected behaviour:
The organization assignments is preserved when the "all environments" is checked.
See https://bugzilla.redhat.com/show_bug.cgi?id=1474249 for consequences.
This will be probably fixed by BZ 1321543, we should retest when it's merged. We won't keep the history of what was assigned before but all environments will be associated. The issue described in 1474249 should not occur anymore.