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 1468556 - "Filter:true" hard coded in fence_rhevm prevents oVirt 3 connection
Summary: "Filter:true" hard coded in fence_rhevm prevents oVirt 3 connection
Keywords:
Status: CLOSED DUPLICATE of bug 1422499
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: fence-agents
Version: 7.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Marek Grac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-07 12:05 UTC by Nicolas Ecarnot
Modified: 2017-07-07 13:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-07 13:18:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Nicolas Ecarnot 2017-07-07 12:05:22 UTC 
Description of problem:
Using fence_rhevm with an oVirt 3.6 engine is failing with the error "Failed: Unable to obtain correct plug status or plug is not available".

Version-Release number of selected component (if applicable):
- RHEL 7.3 client (fence_rhevm source)
- oVirt 3.6.7 on RHEL 7.2 (fence_rhevm target)
- fence-agents-rhevm-4.0.11-47.el7_3.5.x86_64 is failing
- fence-agents-rhevm-4.0.11-27.el7_2.7.x86_64 was working

How reproducible:
Always

Steps to Reproduce:
1. Run :
fence_rhevm -a ovirt-engine -o status -l 'admin@internal' -p 'xxx' --ssl -n vm01 --ssl-insecure

Actual results:
Failed: Unable to obtain correct plug status or plug is not available

Expected results:
With fence-agents-rhevm-4.0.11-27, the result is "Status: ON".

Additional info:
This patch (https://github.com/ClusterLabs/fence-agents/pull/71/commits) added the hard-coded "Filter:true" into the HTTPHEADER connection options.
I tried with the admin@internal of with a dedicated user (with superuser rights).
In every cases, I get a connection in my engine logs, but the failing replies (see above).

When manually removing this Filter:true option, every command are working successfully.

This patch came after this BZ : https://bugzilla.redhat.com/show_bug.cgi?id=1287059

AFAIR, this Filter header was made mandatory on oVirt 4.x generation.
It is a blocker for us people who are still maintaining oVirt 3.x stable DCs.
This would be nice to make this header optional (or better auto-detect).

Best regards.
Comment 2 Marek Grac 2017-07-07 13:18:41 UTC 
Hi,

We are aware of this issue and you can use 'disable_http_filter' (or --disable-http-filter from the command line). 

The patch is available in upstream and should be part of the next minor release. If you need to have an official package sooner, feel free to open customer's ticket.

*** This bug has been marked as a duplicate of bug 1422499 ***
Note You need to log in before you can comment on or make changes to this bug.