Bug 760635

Summary:	Creating new user with "No Default Organization" is awkward/broken.
Product:	Red Hat Satellite	Reporter:	Corey Welton <cwelton>
Component:	WebUI	Assignee:	Tom McKay <tomckay>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	mmccune, sghai
Target Milestone:	Unspecified	Keywords:	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:	2012-08-22 18:10:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	747354

Description Corey Welton 2011-12-06 16:51:46 UTC

Description of problem:
When creating a new user and providing "No Default Organization", and subsequently going in to assign it to ACME, user is told "The default you supplied was the same as the old default."

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


How reproducible:


Steps to Reproduce:
1.  Create a new org, "Test_org".
2.  Create a new user, "fibble". Do NOT assign it a default org - instead, keep the option, "No Default Organization". Save.
3.  Users > fibble > Environments
4.  Modify New Default Organization to be "ACME_Corporation"
5. View results
  
Actual results:
A confusing message:  The default you supplied was the same as the old default.

Expected results:
Not sure, because I'm not sure exactly what the bug is?  Are users getting assigned to ACME_Corporation even though 'no default org' has explicitly been selected? Is there something else going on?

Additional info:

Also, just clicking through the options in your orgs list seems to trigger the above error message w/o rhyme or reason. At first I thought it might be from, say, choosing an org you have already selected. But I don't think that's the case either, I can try to switch from "Test_org" to "ACME_Corporation" and still get that message.

Comment 1 Tom McKay 2011-12-08 15:14:55 UTC

commit 49be4366793ccd49fc30bafb8b02c87064cef2b9
Author: Tom McKay <thomasmckay>
Date:   Thu Dec 8 10:09:25 2011 -0500

    + Bug 754526 - Cannot unset a user's default env
      https://bugzilla.redhat.com/show_bug.cgi?id=754526
      Choosing "No Default Organization" works now
    + Bug 754855 - User cannot change default system environment on their own
      https://bugzilla.redhat.com/show_bug.cgi?id=754855
      User editing own account now allows editing of default env
    + Bug 760563 - User cannot see their roles & permissions
      https://bugzilla.redhat.com/show_bug.cgi?id=760563
      User editing their own account can see (but not modify) their roles
    + Bug 760635 - Creating new user with "No Default Organization" is awkward/broken.
      https://bugzilla.redhat.com/show_bug.cgi?id=760635
      Save button on Environments tab now properly enables/disables based upon
      current choice vs. current default.

Comment 2 Sachin Ghai 2011-12-22 08:17:10 UTC

verified with following katello build:

[root@dhcp201-162 ~]# rpm -qa | grep katello
katello-0.1.154-1.el6.noarch
katello-trusted-ssl-cert-1.0-1.noarch
katello-cli-common-0.1.30-1.el6.noarch
katello-glue-pulp-0.1.154-1.el6.noarch
katello-configure-0.1.46-1.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-glue-candlepin-0.1.154-1.el6.noarch
katello-all-0.1.154-1.el6.noarch
katello-repos-0.1.4-1.el6.noarch
katello-cli-0.1.30-1.el6.noarch
katello-glue-foreman-0.1.154-1.el6.noarch
katello-common-0.1.154-1.el6.noarch
katello-certs-tools-1.0.1-1.el6.noarch
katello-httpd-ssl-key-pair-1.0-1.noarch
[root@dhcp201-162 ~]# rpm -qa | grep katello-cli
katello-cli-common-0.1.30-1.el6.noarch
katello-cli-0.1.30-1.el6.noarch
[root@dhcp201-162 ~]# 


I created a user keeping the option "No  default organization" and then modified the "No default organization"  to 'ACME_Corporation".

The organization changed with the notification:

User environment updated successfully.

Moving this to verified state.