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:
fence_rhevm doesn't provide any option that would translate to addition of "filter: true" http header, that is required to access the VM as a regular RHEV user.

Version-Release number of selected component (if applicable):
fence-agents-rhevm-4.0.11-27.el7

How reproducible:
always

Steps to Reproduce:
1. have a user account in RHEV and a VM with UserVmManager permission on it for that user (this permissions gives full control of the VM to the user without having any rights on RHEV itself)
2. try to use fence_rhevm to query status of the VM
3.

Actual results:
"Failed: unable to obtain correct plug status or plug is not available" - because this user if banned from API unless "Filter: true" header is set

Expected results:
it's possible to tell fence_rhevm to log in as a user

Additional info:

Created attachment 1128181 [details]
Combined patches from upstream

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

New build with the following patch that solves the issue with RHEV4:
https://github.com/ClusterLabs/fence-agents/pull/71/commits/786f5e1d5af984a958dc5502a8d065a24cb66970

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

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://rhn.redhat.com/errata/RHBA-2016-2373.html