Bug 1479736 - Checking "all environments" on Organization edit page resets the assignment of the organization to the environment
Summary: Checking "all environments" on Organization edit page resets the assignment o...
Keywords:
Status: CLOSED DUPLICATE of bug 1321543
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Organizations and Locations
Version: 6.2.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
: 1474249 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-09 10:00 UTC by Ivan Necas
Modified: 2022-03-13 14:23 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1474249
Environment:
Last Closed: 2017-09-21 17:56:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1321543 1 None None None 2022-09-10 08:27:16 UTC

Internal Links: 1321543

Description Ivan Necas 2017-08-09 10:00:17 UTC
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.

Comment 3 Ivan Necas 2017-08-22 13:58:07 UTC
*** Bug 1474249 has been marked as a duplicate of this bug. ***

Comment 4 Marek Hulan 2017-09-18 12:12:37 UTC
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.

Comment 5 Andrew Kofink 2017-09-21 17:56:09 UTC
I can confirm this is fixed with BZ 1321543.

*** This bug has been marked as a duplicate of bug 1321543 ***

Comment 7 Andrii Balakhtar 2018-12-05 15:33:52 UTC
Test coverage removed as BZ 1321543 was closed with WONTFIX resolution


Note You need to log in before you can comment on or make changes to this bug.