Bug 1853906 - [RFE] Add the ability to reboot after install/ reinstall
Summary: [RFE] Add the ability to reboot after install/ reinstall
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: ovirt-host-deploy-ansible
Version: future
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.4.5
: 4.4.5
Assignee: Dana
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks: 1843882 1917821 1934407
TreeView+ depends on / blocked
 
Reported: 2020-07-05 12:50 UTC by Dana
Modified: 2021-03-18 15:13 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.4.5
Clone Of:
Environment:
Last Closed: 2021-03-18 15:13:57 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+
mtessun: planning_ack+
pm-rhel: devel_ack+
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 112339 0 master MERGED bll: host-deploy: add ability to reboot after install 2021-02-08 23:04:49 UTC

Description Dana 2020-07-05 12:50:15 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Martin Perina 2020-07-08 08:03:27 UTC 
Ability to reboot the host after installation or reinstallation will help in several flows:

1. When specifying new kernel parameters
2. When switching from iptables to firewalld (BZ1843882)

Host reboot will be enabled by default, but administrator can disable reboot manually (the same behavior as in host upgrade)
Comment 2 Petr Matyáš 2021-01-19 13:12:57 UTC 
Verified on ovirt-engine-4.4.5-0.11.el8ev.noarch

Although I opened another bug 1917821 as with reboot the host is never moved to state Rebooting and when adding it is actually moved to Non Operational.
However the actual act of reboot is executed (isn't if unmarked) and this IMO is enough to verify this RFE.
Comment 3 Sandro Bonazzola 2021-03-18 15:13:57 UTC 
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.5 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.