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.
DescriptionGarik Khachikyan
2011-08-25 10:04:46 UTC
Description of problem:
in the katello-cli "user create" method the parameter disabled takes the value "true" for preparing disabled user. The "True" case just does not work.
but intuitively (as the tool is in Python itself) it was expected to accept True (as well).
I would suggest to make disabled.lower() :)
Version-Release number of selected component (if applicable):
recent katello rpm build: katello-0.1.70-1.git.7.ca8d03c.fc15.noarch
How reproducible:
always
Steps to Reproduce:
1. katello shell
2. user create --name test --password <pass> --disabled True
3. user list
note, that your user is created with Disabled "False" there.
Actual results:
"--disabled True" does not work,
Expected results:
Would be better to have both: true and True working as --disabled values.
Additional info:
Fixed in 2e48d51dd0e7291dbba8cc04d1b425dc6a653747
Also added checking for the correct value so that this option won't accept anything else except "true" or "false" ignoring case.
# VERIFIED
fixed - now the true|false with its ignorecase(s) are accepted,anything else gives:katello: error: option --disabled: invalid boolean value: <value>
Checked against: katello-cli-0.1.10-1.git.278.85760dc.el6.noarch