Bug 1802478 - hosted-engine deploy does not configure a serial console in the engine vm
Summary: hosted-engine deploy does not configure a serial console in the engine vm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-appliance
Classification: oVirt
Component: General
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ovirt-4.4.0
: 4.4.0
Assignee: Yedidyah Bar David
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-13 09:36 UTC by Yedidyah Bar David
Modified: 2020-05-20 20:00 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-appliance-4.4-20200402205634.1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-20 20:00:33 UTC
oVirt Team: Integration
Embargoed:
sbonazzo: ovirt-4.4?
pelauter: planning_ack+
sbonazzo: devel_ack?
mavital: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 106943 0 master MERGED Add serial console 2020-04-16 08:50:56 UTC

Description Yedidyah Bar David 2020-02-13 09:36:08 UTC
Description of problem:

'hosted-engine --console' does not work.

The VM does have a serial console, but no getty is running there.

Running 'systemctl start getty@ttyS0' solves this.

This should normally happen automatically if grub is configured to tell the kernel to use a serial console.

Version-Release number of selected component (if applicable):
Current master

How reproducible:
Not sure, I think always

Steps to Reproduce:
1. Deploy hosted-engine
2. hosted-engine --console
3.

Actual results:

Starts, but does not show a login prompt. 'ps auxww | grep getty' in the engine vm does not show one on ttyS0.

Expected results:

Shows a login prompt.

Additional info:

I am not sure what the root cause is. Asked Simone, he says it might be in the appliance, but I am not sure, because I do not see there any mention of serial console, and this did work there in previous version.

Comment 1 Simone Tiraboschi 2020-02-13 10:16:42 UTC
If we check https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_64/294/consoleFull#L6,728 (the logs of the job that built the oVirt engine appliance for 4.3.7 GA )
10:21:04 09:21:04,068 INFO anaconda:bootloader.py: used boot args: crashkernel=auto rd.lvm.lv=ovirt/root rd.lvm.lv=ovirt/swap console=ttyS0
and console=ttyS0 is enough to configure it.

while in https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el8-x86_64/110/consoleFull#L6,912 (4.4.0 alpha5) we have only:
18:57:35 17:57:35,148 INFO anaconda:bootloader.py: used boot args: crashkernel=auto rd.lvm.lv=ovirt/root rd.lvm.lv=ovirt/swap rhgb quiet

So the issue is where/when we lost it on appliance side.

Comment 2 Yedidyah Bar David 2020-03-16 10:29:32 UTC
Didn't investigate too much how/where we lost it, but I am pretty certain it was just a changed default somewhere, not an explicit change specific to the appliance. The patch simply adds to the 'bootloader' command in the kickstart suitable options for the kernel, which were never passed so far, and this works.

Comment 3 Nikolai Sednev 2020-04-16 09:14:30 UTC
Tested on:
ovirt-engine-setup-4.4.0-0.31.master.el8ev.noarch
ovirt-hosted-engine-ha-2.4.2-1.el8ev.noarch
rhvm-appliance.x86_64 2:4.4-20200403.0.el8ev
ovirt-hosted-engine-setup-2.4.4-1.el8ev.noarch

Linux 4.18.0-193.el8.x86_64 #1 SMP Fri Mar 27 14:35:58 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Service is running on engine just fine.

nsednev-he-4 ~]# systemctl status ovirt-vmconsole*
● ovirt-vmconsole-proxy-sshd.service - oVirt VM Console SSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/ovirt-vmconsole-proxy-sshd.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-04-06 21:57:34 IDT; 1 weeks 2 days ago
 Main PID: 1306 (sshd)
    Tasks: 1 (limit: 101293)
   Memory: 1.3M
   CGroup: /system.slice/ovirt-vmconsole-proxy-sshd.service
           └─1306 /usr/sbin/sshd -f /usr/share/ovirt-vmconsole/ovirt-vmconsole-proxy/ovirt-vmconsole-proxy-sshd/sshd_>

Apr 06 21:57:34 nsednev-he-4.scl.lab.tlv.redhat.com systemd[1]: Started oVirt VM Console SSH server daemon.
Apr 06 21:57:35 nsednev-he-4.scl.lab.tlv.redhat.com sshd[1306]: Server listening on 0.0.0.0 port 2222.
Apr 06 21:57:35 nsednev-he-4.scl.lab.tlv.redhat.com sshd[1306]: Server listening on :: port 2222.

Service running on ha-host:
puma19 ~]# systemctl status ovirt-vmconsole*
● ovirt-vmconsole-host-sshd.service - oVirt VM Console SSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/ovirt-vmconsole-host-sshd.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-04-06 21:27:10 IDT; 1 weeks 2 days ago
 Main PID: 63652 (sshd)
    Tasks: 1 (limit: 178310)
   Memory: 1.1M
   CGroup: /system.slice/ovirt-vmconsole-host-sshd.service
           └─63652 /usr/sbin/sshd -f /usr/share/ovirt-vmconsole/ovirt-vmconsole-host/ovirt-vmconsole-host-sshd/sshd_c>

Apr 06 21:27:10 puma19.scl.lab.tlv.redhat.com systemd[1]: Started oVirt VM Console SSH server daemon.
Apr 06 21:27:10 puma19.scl.lab.tlv.redhat.com sshd[63652]: Server listening on 0.0.0.0 port 2223.
Apr 06 21:27:10 puma19.scl.lab.tlv.redhat.com sshd[63652]: Server listening on :: port 2223.


puma19 ~]# hosted-engine --console
The engine VM is running on this host
Escape character is ^]


Red Hat Enterprise Linux 8.2 (Ootpa)
Kernel 4.18.0-193.el8.x86_64 on an x86_64

Web console: https://nsednev-he-4.scl.lab.tlv.redhat.com:9090/ or https://10.35.163.167:9090/

nsednev-he-4 login:

Comment 4 Sandro Bonazzola 2020-05-20 20:00:33 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.