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.
The following subcommands are no longer available in 6.2.9-1 compose. Looks like they still exist in nightly, so I believe it might be a packaging bug.
Description of problem:
E AssertionError:
E hammer host create
E Removed options:
E * lifecycle-environment
E * release-version
E * autoheal
E * lifecycle-environment-id
E * content-view-id
E * service-level
E * kickstart-repository-id
E * hypervisor-guest-uuids
E * content-view
E
E hammer host update
E Removed options:
E * lifecycle-environment
E * release-version
E * autoheal
E * lifecycle-environment-id
E * content-view-id
E * service-level
E * kickstart-repository-id
E * hypervisor-guest-uuids
E * content-view
# rpm -qa *hammer*
tfm-rubygem-hammer_cli_import-0.11.2-1.el7sat.noarch
tfm-rubygem-hammer_cli_katello-0.0.22.28-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman-0.5.1.10-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.6-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_admin-0.0.5-1.el7sat.noarch
tfm-rubygem-hammer_cli-0.5.1.13-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3.3-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.5.3-1.el7sat.noarch
tfm-rubygem-hammer_cli_csv-2.2.1.1-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.10.3-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-0.0.2.3-1.el7sat.noarch
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. hammer host create --help
2. hammer host update --help
Actual results:
above options not available
Expected results:
above options available
Additional info:
Comment 7Daniel Lobato Garcia
2017-04-12 08:04:37 UTC
I'm not sure what causes the problem but I can confirm there's probably some issue with order of loading plugins and generating apipie cache during installation.
Docs for host create action in apidoc index file "v2.json" lack all attributes that come from facets. Apidoc file "create.json" with action details that should serve as a source for "v2.json" is correct. When I trigger foreman-rake apipie:cache on the server, facet related attributes disappear even from "create.json".
See attached v2.json and create.json apidoc exports from a clean 6.2.9 installation (before foreman-rake apipie:cache was run).
Comment 14Satellite Program
2017-04-23 21:38:53 UTC
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, 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/RHBA-2017:1191
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, 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/RHBA-2017:1191