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:
- During content view publish if we specify --minor value as 038 039 or 048 049 or 080 090 command fails with Error: Option '--minor': Numeric value is required whereas same command works with --minor value set between 031-037,041-047.
Version-Release number of selected component (if applicable):
- 6.12.0
How reproducible:
- Publish content view with specifying --minor value to 038,039,048,049,058,059
# hammer content-view publish --id 6 --major 4 --minor 038 --description 'The 07-Feb-2023 (Day 038) version'
Could not publish the content view:
Error: Option '--minor': Numeric value is required..
# hammer content-view publish --id 6 --major 4 --minor 039 --description 'The 07-Feb-2023 (Day 038) version'
Could not publish the content view:
Error: Option '--minor': Numeric value is required..
# hammer content-view publish --id 6 --major 4 --minor 048 --description 'The 07-Feb-2023 (Day 038) version'
Could not publish the content view:
Error: Option '--minor': Numeric value is required..
# hammer content-view publish --id 6 --major 4 --minor 049 --description 'The 07-Feb-2023 (Day 038) version'
Could not publish the content view:
Error: Option '--minor': Numeric value is required..
- Same command will work if we specify --minor value range between 031-037,041-047 or if we specify only 38,39,48,49
# hammer content-view publish --id 6 --major 4 --minor 031 --description 'The 07-Feb-2023 (Day 038) version'
[..........................................................................................................................................................................................................] [100%]
# hammer content-view publish --id 6 --major 4 --minor 037 --description 'The 07-Feb-2023 (Day 038) version'
[..........................................................................................................................................................................................................] [100%]
Steps to Reproduce:
1. Publish content view with hammer command specifying --minor value to 038,039 or 048 049 or 058 059
Actual results:
- Command fail with below error.
# hammer content-view publish --id 6 --major 4 --minor 049 --description 'The 07-Feb-2023 (Day 038) version'
Could not publish the content view:
Error: Option '--minor': Numeric value is required
Expected results:
- Publish command should be successful
Additional info:
- NA
The numbers with 0 in the front are being treated as octal numbers by Hammer. Resulting in all numbers with 0 in the front and values outside 0-7 being rejected. I'd advise people to avoid the preceding 0 in numbers passed to hammer. This would need to be fixed in hammer.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.