Petrosian to Quinteros Upgrade Issues

[bfilion87]

We are trying to upgrade our Vcenter installed MIQ environment and am running into issues following the steps on the upgrade doc found here: https://www.manageiq.org/docs/reference/latest/appliances/upgrading.html

First issue, is we get an error on the first dnf update, it appears to have conflicting updates and the only way we got it to run is by adding the --allowerasing. However I believe the allowerasing is what is possibly leading to our next issue, after the dnf install completes, we try to execute the bundle exec rake db:migrate (from /var/www/miq/vmdb) and it comes back with

/var/www/miq/vmdb/Gemfile not found

It feels like I am missing a step that may not be included in the documentation, but any help would be greatly appreciated. I kind of assumed the upgrade would be fairly straightforward since we arent doing any major updates like ruby version or postgresql version.

[Fryguy]

@bdunne Can you help out here?

[Fryguy]

@bdunne I thought we needed --no-best for this ansible thing? Or I thought there was a way to give priority to our repos over the epel repos.

Either that or I wonder if the ansible team removed ansible-core older version from epel and now we need to carry it in our repos?

[Fryguy]

@bdunne I did notice quinteros repo has the ansible-core (ref), but not petrosian (ref)

[natemontgomery]

Went ahead and tried dnf update --nobest. That ran by skipping two ansible packages:

ansible       noarch              9.2.0-1.el8
ansible-core  x86_64              2.16.3-2.el8

After running I was able to install the release RPM for Quinteros using:
dnf install https://rpm.manageiq.org/release/17-quinteros/el8/noarch/manageiq-release-17.0-1.el8.noarch.rpm

Then stopping the evm service and updating I got again the same conflict with ansible and the manageiq-ansible-venv-16.1.0-1.el8.x86_64 package.

Running with --nobest did not install anything.
Running with --allowerasing loads the updates for ansible and python packages but nothing for manageiq-release-17.0-1.

After rebooting the appliance it did not result in an update of the running ManageIQ version, which would be expected as the update has not really occurred yet for the rest of the manageiq packages.

TL;DR It appears that only the release RPM was pulled for 17-quinteros and none of the other ManageIQ packages were pulled, so the running server is still Petrosian. No update options seem to help pull down the rest of the Quinteros packages.

I believe we could install the individual RPMs for Quinteros but is not something that will likely be allowable for the instance @bfilion87 and I are trying to upgrade. Thanks for your help so far!

[bdunne]

I found an issue with the RPM repo generation, so I opened ManageIQ/manageiq-rpm_build#482 to fix it. The correct RPMs are in the repo now, so dnf update --nobest should take care of it now.

[bfilion87]

@bdunne it appears the dnf update--nobest still fails with the same error message as just the dnf update:

[root@miq-dev-test2 ~]# dnf update --nobest
Last metadata expiration check: 23:02:04 ago on Mon 19 Aug 2024 09:56:54 AM PDT.
Dependencies resolved.

Problem 1: package manageiq-ansible-venv-16.1.0-1.el8.x86_64 from @System requires ansible < 6, but none of the providers can be installed

• cannot install both ansible-9.2.0-1.el8.noarch from epel and ansible-5.4.0-3.el8.noarch from @System
• cannot install both ansible-5.4.0-3.el8.noarch from manageiq-17-quinteros-noarch and ansible-9.2.0-1.el8.noarch from epel
• cannot install the best update candidate for package ansible-5.4.0-3.el8.noarch
• problem with installed package manageiq-ansible-venv-16.1.0-1.el8.x86_64
  Problem 2: package manageiq-ansible-venv-16.1.0-1.el8.x86_64 from @System requires ansible < 6, but none of the providers can be installed
• package ansible-5.4.0-3.el8.noarch from @System requires (ansible-core >= 2.12.2 with ansible-core < 2.13), but none of the providers can be installed
• package ansible-5.4.0-3.el8.noarch from manageiq-17-quinteros-noarch requires (ansible-core >= 2.12.2 with ansible-core < 2.13), but none of the providers can be installed
• cannot install both ansible-core-2.16.3-2.el8.x86_64 from appstream and ansible-core-2.12.7-1.el8.x86_64 from @System
• cannot install both ansible-core-2.12.7-1.el8.x86_64 from manageiq-17-quinteros and ansible-core-2.16.3-2.el8.x86_64 from appstream
• package manageiq-core-16.1.0-1.el8.x86_64 from @System requires manageiq-ansible-venv = 16.1.0-1.el8, but none of the providers can be installed
• cannot install the best update candidate for package ansible-core-2.12.7-1.el8.x86_64
• problem with installed package manageiq-core-16.1.0-1.el8.x86_64
  =========================================================================================================================================================================================================
  Package Architecture Version Repository Size
  =========================================================================================================================================================================================================
  Skipping packages with conflicts:
  (add '--best --allowerasing' to command line to force their upgrade):
  ansible noarch 9.2.0-1.el8 epel 46 M
  ansible-core x86_64 2.16.3-2.el8 appstream 4.1 M

Transaction Summary

Skip 2 Packages

Nothing to do.
Complete!

[bdunne]

You may need to dnf clean all first. It looks like it still thinks that the latest available manageiq-* packages are v16.1.0, not 17.

[natemontgomery]

@bdunne That got it working, thanks a ton!