Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1689942 - Event Host upgrade was completed successfully should be when host come up after reboot, not in the same time as event Host was restared
Summary: Event Host upgrade was completed successfully should be when host come up aft...
Keywords:
Status: NEW
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ovirt-4.3.5
: ---
Assignee: Ondra Machacek
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-18 13:43 UTC by Petr Kubica
Modified: 2019-04-16 14:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Infra
pm-rhel: ovirt-4.3+


Attachments (Terms of Use)

Description Petr Kubica 2019-03-18 13:43:57 UTC
Description of problem:
It's a bit confusing, that there is event 'Host <host> upgrade was completed successfully' and then the host is rebooted in the same time. I think that 'the upgrade was completed' event should wait for the host to get back to state, from where the upgrade was started (in my case up). From my point of view, restarting is a part of upgrade process. What if rebooting will fail from any reason? (for example host will hang in PXE or in shutdown process)

Version-Release number of selected component (if applicable):
ovirt-ansible-cluster-upgrade-1.1.12-1.el7ev.noarch

How reproducible:
always

Steps to Reproduce:
1. run cluster upgrade (with reboot) and correlate events with states of the host

additional info:
please notice times of rebooting and upgrade:
2:32:04 PM Upgrade of cluster Default finished successfully.
2:31:44 PM Status of host host-03 was set to Up.
2:26:37 PM Host host-03 upgrade was completed successfully.
2:26:37 PM Host host-03 was restarted using SSH by the engine.
2:25:45 PM Host host-03 was switched to Maintenance Mode.
2:25:45 PM Host host-03 upgrade was started (User: admin@internal-authz).
2:25:43 PM check for available updates on host host-03 was completed successfully with message 'found updates for packages vim-common, vim-enhanced'.	
2:25:17 PM Started to check for available updates on host host-03.


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