Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1483078

Summary: [ovirt-ansible-roles] ovirt-cluster-upgrade: Run 'check for upgrade' action
Product: Red Hat Enterprise Virtualization Manager Reporter: Petr Kubica <pkubica>
Component: ovirt-ansible-rolesAssignee: Ondra Machacek <omachace>
Status: CLOSED ERRATA QA Contact: Petr Kubica <pkubica>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.5CC: mperina, pstehlik, ylavi
Target Milestone: ovirt-4.2.0Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1487144 (view as bug list) Environment:
Last Closed: 2018-05-15 17:59:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1486573, 1487144    

Description Petr Kubica 2017-08-18 17:38:51 UTC
Description of problem:
Checking for upgrade seems doesn't work in role ovirt-cluster-upgrade.
Manual check in webadmin will solve this issue and after that is possible to upgrade checked host via this role. Other hosts are still remain old. 

Version-Release number of selected component (if applicable):
ovirt-ansible-roles-1.0.1-1.el7ev.noarch
python-ovirt-engine-sdk4-4.1.6-1.el7ev.x86_64
ovirt-engine-restapi-4.1.5.2-0.1.el7.noarch
ovirt-engine-4.1.5.2-0.1.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. add hosts to engine
2. add repositories with newer packages
3. run playbook with role ovirt-cluster-upgrade

Comment 1 Ondra Machacek 2017-08-18 18:34:03 UTC
Yeah, we currently upgrade only hosts which reports that they have update available.

Comment 2 Oved Ourfali 2017-08-22 05:37:29 UTC
I don't consider that as urgent.
As far as I know, this is due to the behavior in the engine.
I don't expect the role to now trigger upgrade check on all hosts.
We can maybe add a note clarifying that.

Comment 3 Petr Kubica 2017-08-25 08:54:34 UTC
I think this role should help users to upgrade their huge environment without clicking on every single host and upgrade it. Role should check and upgrade every host in cluster in a simple way. 

Now user must click on every host and trigger upgrade check. After that user can use this role for upgrade. So from my perspective, the objective of upgrading hosts in cluster without difficult clicking (per host) isn't now available.

Comment 4 Martin Perina 2017-08-25 09:01:04 UTC
(In reply to Petr Kubica from comment #3)
> I think this role should help users to upgrade their huge environment
> without clicking on every single host and upgrade it. Role should check and
> upgrade every host in cluster in a simple way. 
> 
> Now user must click on every host and trigger upgrade check. After that user
> can use this role for upgrade. So from my perspective, the objective of
> upgrading hosts in cluster without difficult clicking (per host) isn't now
> available.

Check for upgrade is executed automatically each day (can be changed using engine-config -s HostPackagesUpdateTimeInHours) for all hosts in Up or NonOperational, so in real setups each host in a cluster should have some available updates (especially when cluster upgrade should be a manually scheduled process).

Adding check for upgrade execution for each host prior to its upgrade can increase the time needed for upgrade, so we are still discussing what would be the best solution for that.

Comment 7 Petr Kubica 2017-09-06 10:20:47 UTC
Verified in 
ovirt-ansible-roles-1.0.2-1.el7ev.noarch
ansible-2.3.1.0-3.el7.noarch

there is new variable "check_upgrade"

Comment 12 errata-xmlrpc 2018-05-15 17:59:47 UTC
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/RHEA-2018:1534

Comment 13 Franta Kust 2019-05-16 13:07:34 UTC
BZ<2>Jira Resync