Bug 1011528

Summary: Default Environment selection for user doesn't let you select a content view
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: Content ManagementAssignee: Eric Helms <ehelms>
Status: CLOSED CURRENTRELEASE QA Contact: Corey Welton <cwelton>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.2CC: cwelton, ehelms, jmontleo, mmccune, omaciel
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Mike McCune 2013-09-24 13:34:58 UTC
Our current widget on the User's "Defaults" setting only allows you to specify an Environment.

Now that we require Content Views this needs to also expand to include a CV as a selection option.

Comment 3 Mike McCune 2013-11-06 03:05:05 UTC
https://github.com/Katello/katello/pull/3293

Comment 4 Mike McCune 2013-11-06 14:37:44 UTC
https://github.com/Katello/katello-cli/pull/119

Comment 7 Corey Welton 2013-11-07 06:44:24 UTC
This bug is confusing me.

The subject line of the bug indicates that I should be looking for a way to select a content view in the  user defaults

Unless I'm missing something, I don't see this in Satellite-6.0.2-RHEL-6-20131106.0  It's not 100% clear where exactly I am looking for this, but I have looked in the following locations:

$user > My Account > Defaults
Administer > Users > $user > Defaults
Administer > Users > +New User > System Registration Defaults (note - this is after choosing an org and environment)

That said...

The text of the pull request reads:
"When content views were added, the default environment functionality
broke from the UI perspective since a user would need to select both
an environment and a content view. To simplify this interaction the
default environment selection was removed and replaced by choosing
just a default organization."

I take this to mean that (something??) was scrapped, whereupon we now only select a Default Org. In this specific scenario, we're good when editing the defaults for a user.

When we are _creating_ a user,  however, we're still given the option for selecting a default environment (after choosing an org).

TBH I'm not sure if
a) we're supposed to be able to choose a content view
b) we're supposed to only be able to select a default org
c) whether the imposed limitation of being only able to select a default org should apply to when users are being created.


Please clarify, QE will test when we're sure of what the expected behavior should be.

Comment 8 Mike McCune 2013-11-07 14:24:53 UTC
You *just* select a default org which simplifies org faving in the drop list and dumps systems in the Default Environment View.

The bug is a bit confusing because we changed it up during implementation somewhat to only selecting an org but *not* a content view, you just get the Default.

Comment 9 Corey Welton 2013-11-07 15:04:17 UTC
QA Verified for questions a) and b) above.  Per mmccune, c) is being written up as a new BZ - no reason to allow selection of an environment at user creation if it can't be changed later with this new workflow.

Satellite-6.0.2-RHEL-6-20131106.0

Comment 10 Bryan Kearney 2014-04-24 17:10:54 UTC
This was verified and delivered with MDP2. Closing it out.

Comment 11 Bryan Kearney 2014-04-24 17:11:58 UTC
This was delivered and verified with MDP2. Closing the bug.