Bug 1725250

Summary: Mismatches for organization and location on production environment and domain
Product: Red Hat Satellite Reporter: Nikhil Kathole <nkathole>
Component: Organizations and LocationsAssignee: Tomer Brisker <tbrisker>
Status: CLOSED ERRATA QA Contact: Nikhil Kathole <nkathole>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: mhulan, mmccune, pcreech, sajha, tbrisker
Target Milestone: 6.6.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-1.22.0.9-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 12:47:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of UI none

Description Nikhil Kathole 2019-06-28 20:28:43 UTC 
Created attachment 1585738 [details]
screenshot of UI

Description of problem:

Mismatches report shows production environment and domain on satellite 6.6 fresh install.

Version-Release number of selected component (if applicable):
Satellite 6.6 snap 9


How reproducible: always


Steps to Reproduce:
1. Install 6.6 satellite
2. Check mismatches on organization/location


Actual results:
Puppet environment and domain is shown under mismatches report.



Expected results: No mismatches on fresh install

Additional info: Similar issue for smart proxy is recently fixed in snap 9 https://bugzilla.redhat.com/show_bug.cgi?id=1709695.

Regression.
Comment 5 Marek Hulan 2019-07-04 07:38:39 UTC 
Created redmine issue https://projects.theforeman.org/issues/27233 from this bug
Comment 10 Nikhil Kathole 2019-07-15 12:30:10 UTC 
VERIFIED

Version tested:
Satellite 6.6 snap 11

No mismatch found on fresh installed satellite 6.6.
Comment 12 errata-xmlrpc 2019-10-22 12:47:50 UTC 
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, 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-2019:3172