Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Linux Virtual Machines deployed (with ppcle architecture), using IBM PowerVM Hypervisor on IBM Power System hosts, need an additional component (referred to as RMC - Resource Monitoring and Control subsystem) to be installed and successfully running on the VM. This requires special configuration on these ppcle VMs. This RMC module/service must be installed and functioning on a ppcle VM, for the PowerVM Hypervisor to be able to communicate / manage these Virtual Machines. When a VM boots, there are some basic set of steps(generation of unique RMC node id; subsequent restart of the RMC service etc), that must be performed on a ppcle VM, to ensure that the communication of the VM and PowerVM Hypervisor is intact. RMC has to be active on the VM for the hypervisor to be able to perform many operations (specifically DLPAR related operations) successfully. Thus a healthy RMC is a prerequisite for a PowerVM hypervisor based VM.
More details about RMC and RSCT can be found at:
https://www.ibm.com/support/knowledgecenter/en/SGVKBA_3.2/admin/bl503_ovrv.htmhttps://www.ibm.com/support/knowledgecenter/SGVKBA_3.2/admin/admin_pdf.pdf
To enable the healthy functioning of RMC services on ppcle Linux based VMs, there are couple of cloud-init config modules that we have been maintaining downstream. As part of the LP bug [1], these changes are being upstreamed.
[1]https://bugs.launchpad.net/cloud-init/+bug/1895979
This feature request is being opened to enable support for these PowerVM specific modules in community, to be included as part of Red Hat cloud-init.
The changes that were made for RHEL 8.3.z:
1894014 - Support for cloud-init config modules for PowerVM Hypervisor in Red Hat cloud-init [rhel-8.3.0.z]
1894015 - Add support for ipv6_autoconf on cloud-init-20.3 [rhel-8.3.0.z]
need to be back-ported for RHEL 8.2 and 8.1 (for SAP).
Thanks Rick for moving forward on this. I think it is better to use the original 8.4 ystream bug 1886430. I have done the clone from it, 8.1.z: bz 1908322, 8.2.z: bz 1908321.
Hi Divya, FYI about our zstream request process, we need to request in related ystream bug, and zstream bug have to be cloned from the ystream bug. So let's close this bz as duplicate of the new bug.