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:
nova-compute-wait resource agent used in Openstack Instance HA setup (for resource of nova evacuate) uses openstack-config tool for querying nova conf file. The openstack-config tool is part of openstack-utils package and is not anymore installed in default in RHOS10. It was decided that openstack-config|status|service tools should not be a requirement of anything. That's why It would be good to change resource agent and not to use that tool but rather another way how to query conf file or If It's really neccessary then we need to update the guide and ask users to install the package which is still available (not sure how long though).

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Configure pacemaker resource which uses nova-compute-wait resource agent.

Actual results:
The configured resource will be in failed status because resource agent will throw an error of missing dependency of openstack-config

Expected results:
The best would be if agent can work without openstack-config dependency.

Additional info:

Oyvind, the upstream agent already has the change to use crudini instead.

If you don't want the whole thing, you can literally just s/openstack-config/crudini/ in the existing patch.

The patch in bz#1320783 updates the agent to use crudini instead of openstack-config.

*** This bug has been marked as a duplicate of bug 1320783 ***