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.

Bug 1520574

Summary:	when upgrading from 7.2 to 7.4 some resource agents will have NODENAME set empty
Product:	Red Hat Enterprise Linux 7	Reporter:	Michael Bayer <mbayer>
Component:	resource-agents	Assignee:	Oyvind Albrigtsen <oalbrigt>
Status:	CLOSED ERRATA	QA Contact:	Marian Krcmarik <mkrcmari>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.4	CC:	agk, aherr, arkady_kanevsky, chjones, cluster-maint, dciabrin, fdinitto, jruemker, mschuppe, msufiyan, rcernin, ssigwald, toneata, ushkalim, whayutin
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	7.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	resource-agents-3.9.5-117.el7	Doc Type:	If docs needed, set a value
Doc Text:	Previously, the galera, redis, and rabbitmq-cluster resource agents were unable to start non-containerized resources when a recent version of the resource agent ran on a Pacemaker version that did not support bundles. With this update, a fallback path for non-containerized resources has been added, and, as a result, the described problem no longer occurs.	Story Points:	---
Clone Of:
Clones:	1524454 (view as bug list)		Environment:
Last Closed:	2018-04-10 12:11:25 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:
Bug Depends On:
Bug Blocks:	1524454

Description Michael Bayer 2017-12-04 17:59:40 UTC

Description of problem:

ocf_attribute_target()  does not consider the case where meta_on_node is not set.

more details forthcoming

Comment 2 Damien Ciabrini 2017-12-05 10:32:26 UTC

Additional details for the original description:

For containerized resources (bundles), various resource agents now use
a helper function ocf_attribute_target to
get the name of the pacemaker node to store attributes on.

If a recent version of the resource agent is being run on a pacemaker
version which does not support bundles, ocf_attribute_target will
return an empty string as hostname.

Comment 3 Damien Ciabrini 2017-12-05 10:33:55 UTC

More specifically, we saw the problem happening when upgrading from RHEL
7.2 to RHEL 7.4, and skipping intermediate RHEL 7.3.

Comment 16 errata-xmlrpc 2018-04-10 12:11:25 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/RHBA-2018:0757

Comment 17 Damien Ciabrini 2018-07-23 08:11:21 UTC

*** Bug 1585457 has been marked as a duplicate of this bug. ***