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.
Bug 1349174 - Default organization deleted from Satellite 6.1.9 but it's still referenced
Summary: Default organization deleted from Satellite 6.1.9 but it's still referenced
Keywords:
Status: CLOSED DUPLICATE of bug 1226273
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Organizations and Locations
Version: 6.1.9
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-22 21:23 UTC by janglin@ciena.com
Modified: 2018-06-26 15:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-21 10:49:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot of one reference to non-existent Default Organization (183.48 KB, image/png)
2016-06-22 21:23 UTC, janglin@ciena.com 		no flags Details
no default organization (24.73 KB, image/png)
2016-06-30 14:37 UTC, janglin@ciena.com 		no flags Details
screenshot of another reference to non-existent Default Organization (116.97 KB, image/png)
2016-07-04 18:56 UTC, janglin@ciena.com 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12773 0 Normal New deleting an organization does not refresh UI page 2020-04-16 18:23:12 UTC

Description janglin@ciena.com 2016-06-22 21:23:20 UTC 
Created attachment 1171080 [details]
screenshot of one reference to non-existent Default Organization

Description of problem:

Satellite organizations have a mutable name and immutable associated label.  We could have renamed Default Organization to our own org name but figured the label field should match and since RedHat documenation said it would be ok, we deleted Default Organization.  However, we now see that Satellite continues to reference Default Organization in some places and since there's a lot of filtering done based on what current org and location are set to, we are wondering whether it is possible to recreate the Default Organization.


Version-Release number of selected component (if applicable):
Satellite 6.1.9

How reproducible:
(well, it's not like we can delete the default organization more than once)

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Deleting an organization should delete that organization.  It should not live on in obscure places.  Deleting "Default Organization" should mean the default, if one needs to exist, shifts to another defined organization.

Additional info:
Comment 3 janglin@ciena.com 2016-06-30 14:37:07 UTC 
Created attachment 1174623 [details]
no default organization
Comment 4 janglin@ciena.com 2016-06-30 15:01:09 UTC 
We deleted Default Organization very early on in our installation.  I did find (see 2nd attachment) one subscribed host that apparently did not belong to any organization but that may have been defunct duplicate instance.  I unregistered and deleted that host completely from Satellite, then re-registered it to clear that.  We still see references to Default_Organization under Operating Systems and I think other places but I'd have to look for other examples.  I suspect Satellite needs a Default Organization regardless though as a holding place for hypervisors, etc.  I'm concerned that if I just try to recreate it, I'll end up with a new user-defined org with the same name (ie: new db record) instead of actually recreating Default Organization.
Comment 5 janglin@ciena.com 2016-07-04 18:56:14 UTC 
Created attachment 1176166 [details]
screenshot of another reference to non-existent Default Organization

ESXi servers detected by virt-who show up in non-existent Default Organization
Comment 6 janglin@ciena.com 2016-07-14 15:43:14 UTC 
I am not sure what other info you need.  The only organization that exists in our Satellite 6.1.9 installation is one we defined ourselves ("Ciena") but Satellite  still references to "Default Organization" in various places.  It's like a long program in which someone has changed a variable name but not everywhere ... it still works but could be buggy.  Is it possible to recreate the original "Default Organization" without re-installing Satellite completely from scratch and without just ending up with another user-defined org with the same name?  Either way, I suggest Red Hat's documentation should be updated to advise against deleting "Default Organization".
Comment 7 janglin@ciena.com 2016-08-15 21:04:33 UTC 
I don't know what other info you need.  Please stop flagging this as info needed without providing an idea what you need.

I will mention that I upgraded from Satellite 6.1.9 to 6.2.1 today but as far as I can see that has not made any difference to this issue.
Comment 8 Bryan Kearney 2017-01-05 16:09:25 UTC 
janglin the needinfo is on an internal person to get more information.

Partha, please see comment 1.
Comment 9 Sebastian Gräßl 2017-11-21 10:49:25 UTC 

*** This bug has been marked as a duplicate of bug 1226273 ***
Note You need to log in before you can comment on or make changes to this bug.