Bug 1896799
| Summary: | Add provides for previous oVirt Ansible roles packages to ovirt-ansible-collection to minimize issues during upgrade to 4.4.3 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-ansible-collection | Reporter: | Gianluca Cecchi <gianluca.cecchi> | ||||
| Component: | General | Assignee: | Martin Necas <mnecas> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matyáš <pmatyas> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 1.2.1 | CC: | arusakov, bugs, dfodor, didi, gilboad, lleistne, lsvaty, michal.skrivanek, mperina, sbonazzo | ||||
| Target Milestone: | ovirt-4.4.3-1 | Flags: | pm-rhel:
ovirt-4.4+
mperina: blocker? |
||||
| Target Release: | 1.2.2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-ansible-collection-1.2.2 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-11-27 15:50:15 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: | |||||||
| Attachments: |
|
||||||
|
Description
Gianluca Cecchi
2020-11-11 15:01:47 UTC
I think we should remove the "Obsoletes:" lines. Did we add them to fix a specific bug? Can't find a 'Bug-Url:' in the commit message, so not sure. We can't remove the old packages before upgrading the engine itself. If we want to remove them when/after upgrading the engine, we can check if making the new engine "Conflicts:" with the old packages will do that, or perhaps add an engine-setup plugin to manually remove them. Need to think separately about what to do on hosts - including: 1. upgrading a host before adding it to an engine 2. upgrading a host after adding it to an engine 3. upgrading a host before deploying hosted-engine 4. upgrading a host after deploying hosted-engine Probably other. Could you please try to upgrade using below steps: # dnf update ovirt\*setup\* rh\*vm-setup-plugins --nobest # engine-setup # dnf update --nobest # reboot (In reply to Martin Perina from comment #3) > Could you please try to upgrade using below steps: > > # dnf update ovirt\*setup\* rh\*vm-setup-plugins --nobest Correction: # dnf update ovirt\*setup\* --nobest > # engine-setup > # dnf update --nobest > # reboot Hi,
with the commands proposed the workflow was successful. I'm going to attach all standard output logs (I used the "script" command and then I did a "clean" of the generated file).
After the command:
dnf update --nobest
I executed
dnf update
(without the --nobest)
and I was given
Dependencies resolved.
======================================================================================================================
Package Arch Version Repository Size
======================================================================================================================
Upgrading:
NetworkManager
x86_64 1:1.26.2-1.el8 ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.26 2.4 M
NetworkManager-config-server
noarch 1:1.26.2-1.el8 ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.26 117 k
NetworkManager-libnm
x86_64 1:1.26.2-1.el8 ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.26 1.7 M
NetworkManager-team
x86_64 1:1.26.2-1.el8 ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.26 134 k
NetworkManager-tui
x86_64 1:1.26.2-1.el8 ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.26 312 k
Transaction Summary
======================================================================================================================
Upgrade 5 Packages
No conflict anymore and I accepted it.
See full log also for that in attached logfile
Then reboot.
After that engine web admin ui accessible and for example I see the "Clone VM" button enabled also for a running VM, that should be a new feature in 4.4.3, so it seems ok.
and
[root@ovmgr1 ~]# dnf update
Last metadata expiration check: 0:03:51 ago on Wed 11 Nov 2020 09:05:20 PM CET.
Dependencies resolved.
Nothing to do.
Complete!
[root@ovmgr1 ~]#
Any comment about the NetworkManager further update?
Created attachment 1728495 [details]
standard output generated during the suggested workflow for update
Verified on ovirt-ansible-collection-1.2.2-1.el8ev.noarch |