Bug 1625302 - Not possible to import default environment production
Summary: Not possible to import default environment production
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-04 15:17 UTC by Jan Jansky
Modified: 2018-09-07 12:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-07 12:36:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Jansky 2018-09-04 15:17:48 UTC
Description of problem:
Freshly installed Satellite 6.4, WebUI -> Configure -> Puppet -> Environments -> Import environments from satellite.example.com

Check all environment, by default production, common, development.

Imported are only common and development.


How reproducible:
Always

Steps to Reproduce:
1. WebUI -> Configure -> Puppet -> Environments -> Import environments from satellite.example.com
2. Check production

Actual results:
production not imported


Expected results:
production imported

Comment 1 Brad Buckingham 2018-09-06 20:33:07 UTC
Hi, 

If you:
- go to Configure -> Environments
- set organization switcher to 'Any Organization'
- set location switcher to 'Any Location'

Do you see 'production' listed?
If so, the production environment may have existed during install time and been imported without an organization.

Comment 2 Jan Jansky 2018-09-07 07:00:38 UTC
Hi Brad, 
you are correct, my mistake. I probably never get used to imported components without organization, when for example for CV you need to select Organization.

Sorry, you can close this BZ.

Comment 3 Brad Buckingham 2018-09-07 12:36:36 UTC
Hi Jan,

No worries at all. The org/loc context is often misleading.  Thanks for the quick reply.  I am going to close; however, feel free to re-open if there are further concerns.  Thanks!


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