Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 986413

Summary: Updating user info with option --no_default_environment fails
Product: Red Hat Satellite Reporter: Tazim Kolhar <tkolhar>
Component: HammerAssignee: Tom McKay <tomckay>
Status: CLOSED NOTABUG QA Contact: Tazim Kolhar <tkolhar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: cwelton, mmccune, omaciel, tomckay
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-22 16:32:26 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:
Bug Depends On:    
Bug Blocks: 833466    

Description Tazim Kolhar 2013-07-19 17:26:51 UTC 
Description of problem:
Updating user info with option --no_default_environment fails

Version-Release number of selected component (if applicable):
# rpm -qa | grep katello
katello-selinux-1.4.3-1.git.4.99dc194.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-all-1.4.2-1.git.852.fc1c56a.el6.noarch
signo-katello-0.0.9-1.el6.noarch
katello-glue-elasticsearch-1.4.2-1.git.852.fc1c56a.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-1.4.2-1.git.128.53e0dde.el6.noarch
katello-configure-1.4.3-1.git.67.f71e590.el6.noarch
katello-common-1.4.2-1.git.852.fc1c56a.el6.noarch
katello-glue-pulp-1.4.2-1.git.852.fc1c56a.el6.noarch
katello-certs-tools-1.4.2-1.el6.noarch
katello-1.4.2-1.git.852.fc1c56a.el6.noarch
katello-repos-1.4.2-1.el6.noarch
katello-cli-common-1.4.2-1.git.128.53e0dde.el6.noarch
katello-glue-candlepin-1.4.2-1.git.852.fc1c56a.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch


How reproducible:
# yum install -y katello-all
# katello-configure --user-pass=***

Steps to Reproduce:
1.# katello --username "admin" --password "admin" user update --no_default_environment --username "usr-1374253642173" --default_organization "org-1374253319143" 
Usage:  katello <options> user update <options>

katello: errors:
1) Option --default_environment is required; please see --help
2) Option --no_default_environment is colliding with --default_organization, --default_environment; please see --help

2.please refer
http://hudson.rhq.lab.eng.bos.redhat.com:8080/hudson/job/katello-api/171/TestNG_Report/
3.

Actual results:
the cli command fails

Expected results:
the command should be successful

Additional info:
Comment 1 Tom McKay 2013-07-22 16:32:26 UTC 
This is working as intended:

The confusion,  I think, is with the default org: There is no such thing as a default org, only a default environment which exists in an org. Thus it does not make sense to specify --no_default_environment along with --default_organization; they are mutually exclusive as the message indicates.