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.
Description of problem:
Running the following command directly against fence_ipmilan succeeded :
/usr/sbin/fence_ipmilan -a modi04-mgmt.eng.lab.tlv.redhat.com -l XXX -p YYY -o status -T 4 -P
Getting status of IPMI:modi04-mgmt.eng.lab.tlv.redhat.com...Chassis power = On
Done
But running the same command from vdsClient fails:
vdsClient 0 fenceNode modi04-mgmt.eng.lab.tlv.redhat.com "" ipmilan XXX YYY status "false" "P\nT=4"
unknown
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.Run status directly against an iLO3 machine using /usr/sbin/fence_ipmilan
2.Run status with the same parameters via vdsClient
3.
Actual results:
Running command directly succeeded while running with vdsClient fails
Expected results:
vdsClient should succeed to run the command
Additional info:
Please note that XXX is masked user login and YYY is masked password.
Please contact me to get the actual connection info for that machine if you want to use it.
vdsm log on command :
---------------------
Thread-22077::DEBUG::2011-08-28 17:10:19,275::clientIF::1180::vds::(fenceNode) fenceNode(addr=modi04-mgmt.eng.lab.tlv.redhat.com,port=,agent=ipmilan,user=root,passwd=XXXX,action=status,secure=false,options=P\nT=4)
Thread-22077::DEBUG::2011-08-28 17:10:20,329::clientIF::1206::vds::(fenceNode) rc 1 in agent=fence_ipmilan
ipaddr=modi04-mgmt.eng.lab.tlv.redhat.com
login=root
option=status
passwd=XXXX
P\nT=4 out Getting status of IPMI:modi04-mgmt.eng.lab.tlv.redhat.com...Chassis power = Unknown
Failed
err