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.

Description of problem:

Pacemaker needs the ability to manage remote-nodes with dynamic ip addresses.

For example, docker containers are assigned a random IP every time they start. For a docker container to become a remote-node, pacemaker needs to be made aware of what the IP address is for the container after the container starts. Currently there is no mechanism to allow this.

To resolve this, the resource-agent associated with the remote-node container must have the ability to update Pacemaker with the container's IP during the agent's 'start' operation.  This IP should be communicated with pacemaker via a transient attribute. From there pacemaker will use the address provided to it by this transient attribute to connect to the container's pacemaker_remote instance rather than a statically allocated address in the resource's configuration entry.

This option feature is no longer necessary. The use case this feature was meant to solve has already been solved by another means. It is possible to port forward pacemaker remote within a docker container to the host, which completely removes the need for pacemaker-remote to need to process dynamic IPs.