Created attachment 997408 [details] login-error.png Description of problem: Can't login RHEV-H with correct password after uptime more than 2 days. Version-Release number of selected component (if applicable): rhev-hypervisor7-7.1-20150226.0.el7ev ovirt-node-3.2.1-7.el7.noarch How reproducible: Only met once, and not sure whether cause by long time running rhevh! Steps to Reproduce: 1. Install rhev-hypervisor7-7.1-20150226.0.el7ev. 2. Configure network with dhcp. 3. keep host uptime more than 2 days. 4. Try to login the host with correct password. Actual results: Can't login RHEV-H with correct password after uptime more than 2 days. Expected results: Can login RHEV-H with correct password even uptime more than 2 days. Additional info:
Created attachment 997409 [details] login-failed.tar.gz
This bug is medium because it is hard to reproduce so far, but it happened once.
qe are not sure whether running 2 days will cause this issue. so I updated the bug summary to avoid more misunderstanding. this only happened once during rhevh 7.1 testing. We didn't do other work after rhevh 7.1 installation, after installation, rhevh 7.1 can be login, experienced at least 4 times rhevh itself restart manually, then running 2 days, this issue happened once.
Does this bug also happen in SELinux permissive mode?
The screenshot shows that it does not look like an SELinux issue.
Hi shaochen, A vdsm issue affected the communication between ovirt-node-plugin-vdsm and vdsm. I recommend open a different bug into vdsm component. I will add a clause of exception in the plugin to avoid the non login screen in such case. messages ========== Mar 3 05:46:24 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:27 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:30 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:30 localhost journal: Forwarding to syslog missed 42 messages. Mar 3 05:46:33 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:36 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:39 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:42 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:45 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:48 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:51 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:54 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:46:57 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:47:00 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:47:00 localhost journal: Forwarding to syslog missed 10 messages. Mar 3 05:47:03 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:47:06 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:47:09 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:47:12 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: '' Mar 3 05:47:13 localhost python: Error in communication with subscription manager, trying to recover: Mar 3 05:47:13 localhost python: Unable to recover, retry in 60 seconds. vdsm.log ============= storageRefresh::DEBUG::2015-02-27 08:28:03,047::lvm::416::Storage.OperationMutex::(_reloadvgs) Operation 'lvm reload operation' released the operation mutex storageRefresh::DEBUG::2015-02-27 08:28:03,047::hsm::410::Storage.HSM::(storageRefresh) HSM is ready Detector thread::DEBUG::2015-02-27 08:28:03,348::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) Adding connection from 10.66.109.77:44889 Detector thread::DEBUG::2015-02-27 08:28:03,378::protocoldetector::207::vds.MultiProtocolAcceptor::(_process_handshake) Error during handshake: sslv3 alert certificate unknown Detector thread::DEBUG::2015-02-27 08:28:03,378::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection) Connection removed from 10.66.109.77:44889 Detector thread::WARNING::2015-02-27 08:28:03,379::protocoldetector::241::vds.MultiProtocolAcceptor::(_handle_connection_read) Unrecognized protocol: '' Detector thread::DEBUG::2015-02-27 08:28:06,402::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) Adding connection from 10.66.109.77:58982 Detector thread::DEBUG::2015-02-27 08:28:06,406::protocoldetector::207::vds.MultiProtocolAcceptor::(_process_handshake) Error during handshake: sslv3 alert certificate unknown Detector thread::DEBUG::2015-02-27 08:28:06,407::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection) Connection removed from 10.66.109.77:58982 Detector thread::WARNING::2015-02-27 08:28:06,407::protocoldetector::241::vds.MultiProtocolAcceptor::(_handle_connection_read) Unrecognized protocol: '' Detector thread::DEBUG::2015-02-27 08:28:09,428::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) Adding connection from 10.66.109.77:47584 Detector thread::DEBUG::2015-02-27 08:28:09,431::protocoldetector::207::vds.MultiProtocolAcceptor::(_process_handshake) Error during handshake: sslv3 alert certificate unknown Detector thread::DEBUG::2015-02-27 08:28:09,431::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection) Connection removed from 10.66.109.77:47584 Detector thread::WARNING::2015-02-27 08:28:09,432::protocoldetector::241::vds.MultiProtocolAcceptor::(_handle_connection_read) Unrecognized protocol: '' Detector thread::DEBUG::2015-02-27 08:28:12,457::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) Adding connection from 10.66.109.77:33782 Detector thread::DEBUG::2015-02-27 08:28:12,460::protocoldetector::207::vds.MultiProtocolAcceptor::(_process_handshake) Error during handshake: sslv3 alert certificate unknown
(In reply to Ying Cui from comment #7) > (In reply to Douglas Schilling Landgraf from comment #6) > > Hi shaochen, > > > > A vdsm issue affected the communication between ovirt-node-plugin-vdsm and > > vdsm. I recommend open a different bug into vdsm component. I will add a > > clause of exception in the plugin to avoid the non login screen in such > > case. > > Hi Douglas, could you please help to open the vdsm bug directly for better > description the cause instead of chen? > > Thanks > Ying done.
(In reply to Douglas Schilling Landgraf from comment #8) > (In reply to Ying Cui from comment #7) > > (In reply to Douglas Schilling Landgraf from comment #6) > > > Hi shaochen, > > > > > > A vdsm issue affected the communication between ovirt-node-plugin-vdsm and > > > vdsm. I recommend open a different bug into vdsm component. I will add a > > > clause of exception in the plugin to avoid the non login screen in such > > > case. > > > > Hi Douglas, could you please help to open the vdsm bug directly for better > > description the cause instead of chen? > > > > Thanks > > Ying > > done. Just for the record, opened the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1199133
Test version: rhev-hypervisor7-7.2-20151025.0.el7ev ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch ovirt-node-plugin-vdsm-0.6.1-1.el7ev.noarch Test steps: 1. Install rhev-hypervisor7.2 2. Configure network with dhcp. 3. keep host uptime more than 2 days. 4. Try to login the host with correct password. 5. Repeat above step on different machines. Test result: All machine can login RHEV-H with correct password even uptime more than 2 days. So the bug is fixed, change bug status to VERIFIED.
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-0378.html