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.
How to test.
1. Export VirtualDomain environment variables. Replace my config path with yours.
# export OCF_ROOT=/usr/lib/ocf
# export OCF_RESKEY_config=/home/dvossel/virtual_machines/rhel7-dev.xml
2. start the vm and monitor it.
# ./VirtualDomain start
# ./VirtualDomain monitor
# echo $?
# 0
3. stop libvirtd and make sure you can still monitor, you'll see errors about virsh not being able to connect, but the return code should still be 0
# service libvirtd stop
# ./VirtualDomain monitor
# echo $?
# 0
It seems not to work as described
duck-03# rpm -q resource-agents
resource-agents-3.9.5-26.el7.x86_64
duck-03# export OCF_RESKEY_config=/var/lib/libvirt/lxc/duck-03-node01.xml
duck-03# export OCF_RESKEY_hypervisor=lxc:///
duck-03# virsh -c lxc:/// list
Id Name State
----------------------------------------------------
31089 duck-03-node01 running
duck-03# /usr/lib/ocf/resource.d/heartbeat/VirtualDomain monitor
DEBUG: Virtual domain duck-03-node01 is currently running.
WARNING: crm_resource failed to set utilization attribute cpu: Resource 'default' not found: No such device or address
Error performing operation: No such device or address
WARNING: crm_resource failed to set utilization attribute hv_memory: Resource 'default' not found: No such device or address
Error performing operation: No such device or address
duck-03# echo $?
0
duck-03# systemctl stop libvirtd
duck-03# /usr/lib/ocf/resource.d/heartbeat/VirtualDomain monitor
<never returns>
..not hang but keeps waiting forever
(In reply to michal novacek from comment #5)
> It seems not to work as described
>
> duck-03# rpm -q resource-agents
> resource-agents-3.9.5-26.el7.x86_64
>
> duck-03# export OCF_RESKEY_config=/var/lib/libvirt/lxc/duck-03-node01.xml
> duck-03# export OCF_RESKEY_hypervisor=lxc:///
>
> duck-03# virsh -c lxc:/// list
> Id Name State
> ----------------------------------------------------
> 31089 duck-03-node01 running
>
> duck-03# /usr/lib/ocf/resource.d/heartbeat/VirtualDomain monitor
> DEBUG: Virtual domain duck-03-node01 is currently running.
> WARNING: crm_resource failed to set utilization attribute cpu: Resource
> 'default' not found: No such device or address
> Error performing operation: No such device or address
> WARNING: crm_resource failed to set utilization attribute hv_memory:
> Resource 'default' not found: No such device or address
> Error performing operation: No such device or address
>
> duck-03# echo $?
> 0
>
> duck-03# systemctl stop libvirtd
>
> duck-03# /usr/lib/ocf/resource.d/heartbeat/VirtualDomain monitor
>
> <never returns>
> ..not hang but keeps waiting forever
Can you please attach the .xml file for the vm
-- Vossel
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.