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 1671148 - hammer host update not showing --lifecycle-environment option
Summary: hammer host update not showing --lifecycle-environment option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.4.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: 6.5.0
Assignee: satellite6-bugs
QA Contact: Mirek Długosz
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-30 21:47 UTC by Ivan Windon
Modified: 2022-03-13 16:53 UTC (History)
21 users (show)

Fixed In Version: foreman-1.20.1.12-1,tfm-rubygem-katello-3.10.0.25-1,foreman_openscap-0.11.5.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-14 12:40:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25717 0 Normal Closed Bootdisk provision_method not available in API (docs) 2020-06-29 11:11:37 UTC
Foreman Issue Tracker 25820 0 Normal Closed Use string in `add_controller_action_scope` 2020-06-29 11:11:36 UTC
Foreman Issue Tracker 25821 0 Normal Closed Use string in `add_controller_action_scope` 2020-06-29 11:11:36 UTC
Red Hat Knowledge Base (Solution) 3164191 0 Supportability None [Satellite 6] hammer cli command does not recognise option --lifecycle-environment 2019-02-26 20:35:25 UTC
Red Hat Product Errata RHSA-2019:1222 0 None None None 2019-05-14 12:40:11 UTC

Comment 20 Justin Sherrill 2019-02-19 20:41:47 UTC
Uploading a patch that was tested with 6.4 for this issue.  Note, this is NOT a final solution.  The current issue is that only one plugin can add extensions to the host object within apipie.  This patch makes it so that katello is the one adding extensions at the expense of the openscap plugin.


After applying this patch, simply run "foreman-rake apipie:cache"


diff --git a/lib/katello/engine.rb b/lib/katello/engine.rb
index 260fc3d1d4..5ee5574417 100644
--- a/lib/katello/engine.rb
+++ b/lib/katello/engine.rb
@@ -55,7 +55,7 @@ module Katello
 
     # make sure the Katello plugin is initialized before `after_initialize`
     # hook so that the resumed Dynflow tasks can rely on everything ready.
-    initializer 'katello.register_plugin', :before => :finisher_hook do
+    initializer 'katello.register_plugin', :before => 'foreman_openscap.register_plugin' do
       require 'katello/plugin'
       # extend builtin permissions from core with new actions
       require 'katello/permissions'

Comment 21 Justin Sherrill 2019-02-20 14:10:06 UTC
It turns out this has been resolved upstream this past month.  Adding the 3 upstream issues.

Comment 40 errata-xmlrpc 2019-05-14 12:40:00 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/RHSA-2019:1222


Note You need to log in before you can comment on or make changes to this bug.