Created attachment 1510098 [details] screenshot, ks file and log related Description of problem: 1.RHVH 4.2.8 installed in local machine, the status of service sshd : activating(auto-restart),Failed to start OpenSSH server daemon. 2.RHVH 4.2.8 installed in vm, the status of service sshd: inactive(dead). 2.RHVH4.2.7 installed, the status of service sshd : active(running) Version-Release number of selected component (if applicable): redhat-virtualization-host-4.2.8-20181128.0.el7_6 How reproducible: 100% Regression bug Keywords: sshd Steps to Reproduce: 1. install redhat-virtualization-host-4.2.8-20181128.0 via ks. 2. enter command "service sshd status" Actual results: 1.local machine:Active:activating(auto-restart) Nov 30 07:10:58 systemctl[1]:Failed to start OpenSSH server daemon. 2. VM (see attachment ) Expected results: active(running)
The bug still exists. Version: 1.Red Hat Virtualization Host 4.3.0(el7.6) 2.imgbase layout:rhvh-4.3.0.2-0.20190109 Steps to Reproduce: 1. install redhat-virtualization-host-4.2.8-20181128.0 via ks. 2. enter command "service sshd status"
(In reply to chyan from comment #8) > The bug still exists. > > Version: > 1.Red Hat Virtualization Host 4.3.0(el7.6) > 2.imgbase layout:rhvh-4.3.0.2-0.20190109 > > Steps to Reproduce: > 1. install redhat-virtualization-host-4.2.8-20181128.0 via ks. > 2. enter command "service sshd status" 4.2.8 or 4.3 ?
(In reply to Yuval Turgeman from comment #9) > (In reply to chyan from comment #8) > > The bug still exists. > > > > Version: > > 1.Red Hat Virtualization Host 4.3.0(el7.6) > > 2.imgbase layout:rhvh-4.3.0.2-0.20190109 > > > > Steps to Reproduce: > > 1. install redhat-virtualization-host-4.2.8-20181128.0 via ks. > > 2. enter command "service sshd status" > > 4.2.8 or 4.3 ? RHVH 4.3 (redhat-virtualization-host-4.3-20190109.0.el7_6) imgbased-1.1.2-0.1.el7ev
Sorry I commented wrong, the steps to reproduce should be: 1. install redhat-virtualization-host-4.3-20190109.0.el7_6 via ks. 2. enter command "service sshd status"
According to Martin, this may be caused by system running out of entropy. Are you testing in a VM? If so can you run rngd on the host to ensure some more entropy is generated?
does it work with selinux disabled?
vdsm-tool configure during installation (in anaconda) changes the context for some essential files. In imgbased-1.1.3 we relabel those files after vdsm-tool.
(In reply to Sandro Bonazzola from comment #12) > According to Martin, this may be caused by system running out of entropy. > Are you testing in a VM? If so can you run rngd on the host to ensure some > more entropy is generated? I am testing in physical machine and the probability to be reproduced is about 33%. Machine version: 1.hp-dl385pg8(active) 2.dell-per730(active) 3.dell-OPTIPLEX-790(activating) (In reply to Sandro Bonazzola from comment #13) > does it work with selinux disabled? No, it doesn't.
Verified this bug: 1. install redhat-virtualization-host-4.3-20190115.0.el7_6 via ks or iso. 2. enter command "service sshd status" Result:active(running) The physical machine (dell-OPTIPLEX-790) and vm encountered this problem beforealso work fine now.
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://access.redhat.com/errata/RHBA-2019:1053