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:
Fence drac5 fails to log in with no obvious error when oCiphers is specified, it doesn't work either without the cipher specification as ciphers on the machine are outdated (even though it has latest drivers)
Version-Release number of selected component (if applicable):
fence-agents-drac5-4.0.11-66.el7_4.3.x86_64
How reproducible:
always
Steps to Reproduce:
1.fence_drac5 -a $address -l $username -p $password -n $slot_number --ssh-options="-oCiphers=+3des-cbc" -o status -x -vvv
Actual results:
Running command: /usr/bin/ssh $username@$addresss -p 22 -o PubkeyAuthentication=no -oCiphers=+3des-cbc
Timeout exceeded in read_nonblocking().
<fencing.fspawn object at 0x7f1782d2e4d0>
version: 2.3 ($Revision: 399 $)
command: /usr/bin/ssh
args: ['/usr/bin/ssh', '$username@$address', '-p', '22', '-o', 'PubkeyAuthentication=no', '-oCiphers=+3des-cbc']
searcher: searcher_re:
0: re.compile("ssword:")
1: re.compile("Are you sure you want to continue connecting (yes/no)?")
buffer (last 100 chars):
before (last 100 chars):
after: <class 'pexpect.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 32647
child_fd: 4
closed: False
timeout: 30
delimiter: <class 'pexpect.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
Unable to connect/login to fencing device
Expected results:
status of machine
Additional info:
From /var/log/messages:
Dec 7 17:42:52 $machine fence_drac5: Running command: /usr/bin/ssh $username@$address -p 22 -o PubkeyAuthentication=no -oCiphers=+3des-cbc
Dec 7 17:42:57 $machine fence_drac5: Unable to connect/login to fencing device
Comment 2Oyvind Albrigtsen
2017-12-08 09:08:15 UTC
I just tested and you just need to increase login-timeout. I tested with --login-timeout=40, but it might be worth doing a lot of requests over time to see if it gets higher sometimes.
We have verified and closed dependent BZ1484404 with following result:
1. Adding "ssh_options=-oCiphers=+3des-cbc" into Options field withing oVirt/RHV engine is required for all drac5 fence agents
2. Adding "login_timeout=30" was required for the specific machine, but it might not be needed for other machines
So from RHV point of view this bug can be closed.
Comment 7RHEL Program Management
2021-02-15 07:33:52 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: Fence drac5 fails to log in with no obvious error when oCiphers is specified, it doesn't work either without the cipher specification as ciphers on the machine are outdated (even though it has latest drivers) Version-Release number of selected component (if applicable): fence-agents-drac5-4.0.11-66.el7_4.3.x86_64 How reproducible: always Steps to Reproduce: 1.fence_drac5 -a $address -l $username -p $password -n $slot_number --ssh-options="-oCiphers=+3des-cbc" -o status -x -vvv Actual results: Running command: /usr/bin/ssh $username@$addresss -p 22 -o PubkeyAuthentication=no -oCiphers=+3des-cbc Timeout exceeded in read_nonblocking(). <fencing.fspawn object at 0x7f1782d2e4d0> version: 2.3 ($Revision: 399 $) command: /usr/bin/ssh args: ['/usr/bin/ssh', '$username@$address', '-p', '22', '-o', 'PubkeyAuthentication=no', '-oCiphers=+3des-cbc'] searcher: searcher_re: 0: re.compile("ssword:") 1: re.compile("Are you sure you want to continue connecting (yes/no)?") buffer (last 100 chars): before (last 100 chars): after: <class 'pexpect.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 32647 child_fd: 4 closed: False timeout: 30 delimiter: <class 'pexpect.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 Unable to connect/login to fencing device Expected results: status of machine Additional info: From /var/log/messages: Dec 7 17:42:52 $machine fence_drac5: Running command: /usr/bin/ssh $username@$address -p 22 -o PubkeyAuthentication=no -oCiphers=+3des-cbc Dec 7 17:42:57 $machine fence_drac5: Unable to connect/login to fencing device