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.
Description of problem:
When creating an organization with hammer, we have the following option:
# hammer organization create
--name "My_Organization"
--label "My_Organization_Label"
--simple-content-access true/false
This does not show up in the organization update command.
Version-Release number of selected component (if applicable):
Sat 6.13
How reproducible:
Steps to Reproduce:
1. hammer organization update -h
Actual results:
--simple-content-access true/false is missing from org update command
Expected results:
--simple-content-access true/false to be an option
Additional info:
This was found during the new SCA Candlepin docs review with myself and Adam
Verified on 6.15 - Snap 5
Steps to Verify:
1. Check that hammer organization update -h has --simple-content-access as an option
2. Create an organization
3. Run hammer organization update --id <org_id> --simple-content-access true/false
4. Validate that the sca flag has been set properly using hammer organization info --id <org_id>
Expected Results:
The sca option is present, and after using it in a hammer organization update, sets the sca flag on the org properly.
Actual Results:
The sca option is present, and after using it in a hammer organization update, sets the sca flag on the org properly.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2024:2010
Comment 13Red Hat Bugzilla
2024-08-22 04:25:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days