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.

Bug 1365229

Summary: BMC Configuration steps need updating
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: Docs Host Configuration GuideAssignee: Zac Dover <zdover>
Status: CLOSED CURRENTRELEASE QA Contact: Charles Wood <chwood>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: adahms, chhudson
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-01 23:25:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike McCune 2016-08-08 16:48:41 UTC
Document URL: 

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/host-configuration-guide/94-configuring-an-additional-network-interface#proc-Red_Hat_Satellite-Host_Configuration_Guide-Enabling_BMC_Power_Management-To_Enable_BMC_Power_Management_on_an_Existing_Capsule

Section Number and Name: 

Procedure 9.14. To Enable BMC Power Management on an Existing Capsule Server:

Describe the issue: 

we can now drive that configuration of the BMC feature entirely from the satellite-installer routine. This should instruct users to enable it via the following flags:

    --foreman-proxy-bmc           Enable BMC feature (default: false)
    --foreman-proxy-bmc-default-provider  BMC default provider. (default: "ipmitool")

eg:

# satellite-installer    --foreman-proxy-bmc=true --foreman-proxy-bmc-default-provider=ipmitool



Suggestions for improvement: 

Additional information:

Comment 2 Andrew Dahms 2017-01-27 01:56:20 UTC
Assigning to Zac for review.

Zac - looks like we need to update the procedure to replace Step 1. and Step 2. with a single step that tells users to use the 'satellite-installer' command with the above two options.

Comment 5 Andrew Dahms 2017-02-01 23:25:04 UTC
This content is live on the Customer Portal.

Closing.