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.
DescriptionKarim Boumedhel
2013-03-06 12:10:10 UTC
Description of problem:
fence_rhevm does not work because of a bad regex to detect vm s id
Version-Release number of selected component (if applicable):
fence-agents-3.1.5-17.el6.x86_64
tested on rhev3.1 and ovirt3.1
How reproducible:
fence_rhevm -a 192.168.17.1 -z -l admin@internal -p password -n node1 -o status
Steps to Reproduce:
1.run the following command
fence_rhevm -a 192.168.17.1 -z -l admin@internal -p password -n node1 -o status
Actual results:
Failed: Unable to obtain correct plug status or plug is not available
Expected results:
Status: ON
Additional info:
the script fails on retrieving the id of the vm.
for that matter, it uses the following regex from line 15
re_get_id = re.compile("<vm id=\"(.*?)\"", re.IGNORECASE);
but since the result actually reads this way
<vm href="/api/vms/XXXXX" id="XXXXX">
a better regex would be the following one
re_get_id = re.compile("<vm .* id=\"(.*?)\"", re.IGNORECASE);
Description of problem: fence_rhevm does not work because of a bad regex to detect vm s id Version-Release number of selected component (if applicable): fence-agents-3.1.5-17.el6.x86_64 tested on rhev3.1 and ovirt3.1 How reproducible: fence_rhevm -a 192.168.17.1 -z -l admin@internal -p password -n node1 -o status Steps to Reproduce: 1.run the following command fence_rhevm -a 192.168.17.1 -z -l admin@internal -p password -n node1 -o status Actual results: Failed: Unable to obtain correct plug status or plug is not available Expected results: Status: ON Additional info: the script fails on retrieving the id of the vm. for that matter, it uses the following regex from line 15 re_get_id = re.compile("<vm id=\"(.*?)\"", re.IGNORECASE); but since the result actually reads this way <vm href="/api/vms/XXXXX" id="XXXXX"> a better regex would be the following one re_get_id = re.compile("<vm .* id=\"(.*?)\"", re.IGNORECASE);