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 1734522

Summary: [RFE] - Use IPMI system facts to automatically create BMC interface.
Product: Red Hat Satellite Reporter: Anand Jambhulkar <ajambhul>
Component: Power & BMCAssignee: Lukas Zapletal <lzap>
Status: CLOSED CURRENTRELEASE QA Contact: Roman Plevka <rplevka>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: bkearney, lzap, riehecky, wpinheir
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-15 15:44:39 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 Anand Jambhulkar 2019-07-30 18:43:56 UTC
Description of problem:


The customer wants to use the IPMI system facts to automatically generate the BMC interfaces.


Business Case:

When adding the BMC proxy to Sat6, it would be helpful if hosts could 
automatically create their IPMI interfaces via system facts.

Technical Requirements:

Add BMC interfaces in a similar manner to how other network interfaces 
are added from system facts.
Add a "default" BMC user/pass to the admin config.

Comment 4 Lukas Zapletal 2019-08-01 05:38:36 UTC
Is this for Puppet, RHSM or Ansible facts?

Comment 5 Pat Riehecky 2019-08-01 13:17:47 UTC
In my environment, these are puppet provided facts.

Comment 7 Anand Jambhulkar 2019-08-01 17:52:19 UTC
Lzap,

The customer has confirmed that these are Puppet facts.


Thanks,
Anand Jambhulkar

Comment 8 Lukas Zapletal 2019-08-02 08:54:07 UTC
For puppet we might already have this feature, there is a "hidden" setting contributed by our community: Administer - Settings - Discovery - Create bond interfaces and it is turned off by default. If you flip this on, discovery process should attempt to create bond interfaces. This feature has no QA coverage, please ask the customer to test it and if this works for them we can start testing this every release. Or we can take this further and probably remove the settingg and start detecting LLDP-bond interfaces for all customers.

Comment 9 Anand Jambhulkar 2019-08-02 20:17:16 UTC
Lzap,

I don't know whether the customer has tested what you have asked in the previous comment or not which I had conveyed to him.

However, he has asked the following - "these are IPMI interfaces rather than bond interfaces....would that make a difference?"


Thanks,
Anand Jambhulkar

Comment 10 Lukas Zapletal 2019-08-05 07:04:15 UTC
Anand, please do not remove NEEDINFO until you figure out with your customer if this is what they need. They need to test this, there is no other way to tell.

Yes, it creates bond interfaces from IPMI information.

Comment 11 Anand Jambhulkar 2019-08-06 18:02:50 UTC
Lukas,

The customer has tested this and have found out that it creates bond interfaces from IPMI facts.

However, they want BMC interfaces to be created from those IPMI facts.


Warm Regards,
Anand Jambhulkar

Comment 13 Bryan Kearney 2019-11-15 15:44:39 UTC
Based on comment 8, this feature exists already. If the customer sees issues, they should raise a BZ.

Comment 14 Lukas Zapletal 2019-11-20 15:39:02 UTC
Hello, apologies for the delay. I was on PTO.

It is still a valid RFE, however implementation of BMC in Satellite is a bit weak - all we can do is currently do a call via ipmitool/freeipmi to power on, off and few more commands.

Can customer give an example of facter output (facter --json) and expected BMC interface with all the data which should be created?

Comment 15 Pat Riehecky 2019-11-20 15:57:25 UTC
# facter --json --puppet |grep ipmi | sort
  "ipmi1_gateway": "192.168.1.1",
  "ipmi1_ipaddress": "192.168.145.31",
  "ipmi1_ipaddress_source": "Static Address",
  "ipmi1_macaddress": "1c:c4:7a:e4:eb:b2",
  "ipmi1_subnet_mask": "255.255.255.0",
  "ipmi_gateway": "192.168.1.1",
  "ipmi_ipaddress": "192.168.145.31",
  "ipmi_ipaddress_source": "Static Address",
  "ipmi_macaddress": "1c:c4:7a:e4:eb:b2",
  "ipmi_subnet_mask": "255.255.255.0",

Comment 16 Anand Jambhulkar 2019-11-20 17:19:24 UTC
Hello Lukas,

I will ask that to the customer now.


Thanks and Regards,
Anand Jambhulkar

Comment 17 Anand Jambhulkar 2019-11-21 09:50:29 UTC

Hello Lukas,

The customer has provided the following data - 

# facter --json --puppet |grep ipmi | sort
  "ipmi1_gateway": "192.168.1.1",
  "ipmi1_ipaddress": "192.168.145.31",
  "ipmi1_ipaddress_source": "Static Address",
  "ipmi1_macaddress": "1c:c4:7a:e4:eb:b2",
  "ipmi1_subnet_mask": "255.255.255.0",
  "ipmi_gateway": "192.168.1.1",
  "ipmi_ipaddress": "192.168.145.31",
  "ipmi_ipaddress_source": "Static Address",
  "ipmi_macaddress": "1c:c4:7a:e4:eb:b2",
  "ipmi_subnet_mask": "255.255.255.0",


Thanks and Regards,
Anand Jambhulkar

Comment 18 Lukas Zapletal 2019-11-22 08:57:25 UTC
Thank you, I've researched that Satellite already performs this from at least version 6.3. When "ipmi_ipaddress" and "ipmi_macaddress" facts are found, new interface is created automatically. However there is one drawback - the interface always has username/password set to nil value (nothing). Unless this is edited in Satellite UI/CLI this is a bit useless.

Please confirm you see this behavior.

We could probably implement some default password and username fallback. While we are against adding more and more Administer - Settings (we have too many) the default value could be taken from host parameters. So as long as you have set some parameters in host or hostgroup, Satellite could utilize this as the default value. If you like this behavior, please file new RFE BZ with this description on this BZ component and I will pick it up later.

Comment 19 Anand Jambhulkar 2019-12-04 09:25:25 UTC
Hello Lukas,

The customer has confirmed that he is not observing the behavior that you have stated in Comment-18.


Warm Regards,
Anand Jambhulkar

Comment 20 Anand Jambhulkar 2021-06-27 00:17:34 UTC
Hello Lukas,

It looks like there already is an RFE that has been filed as per your suggestion in the Comment-18.


Following is a link to that RFE -

https://bugzilla.redhat.com/show_bug.cgi?id=1746072


Following is a link to that RFE in upstream -

https://projects.theforeman.org/issues/8523



Thanks and Regards,
Anand Jambhulkar