Executed: openstack overcloud upgrade run --yes --stack overcloud --tags system_upgrade --limit controller0 and the output error is: ============================================================", " ERRORS ", "============================================================", "", "2023-10-22 09:12:39.943799 [ERROR] Actor: dnf_transaction_check", "Message: DNF execution failed with non zero exit code.", "STDOUT:", "Last metadata expiration check: 0:03:06 ago on Sun Oct 22 09:09:15 2023.", "Package container-selinux-2:2.167.0-1.module+el8.4.0+14908+81312c48.noarch is already installed.", "Package os-net-config-14.2.1-1.20230412014753.el8ost.noarch is already installed.", "Package python3-iso8601-0.1.12-8.el8ost.1.noarch is already installed.", "Package python3-pyOpenSSL-19.0.0-1.el8.noarch is already installed.", "", "STDERR:", "warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.", "warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.", "Warning: Package marked by Leapp to install not found in repositories metadata: ovn2.15 openvswitch2.15", "Warning: Package marked by Leapp to upgrade not found in repositories metadata: python3-leapp leapp-upgrade-el8toel9 gpg-pubkey leapp", "Transaction check: ", "", " Problem 1: conflicting requests", " Problem 2: package os-net-config-14.2.1-1.20230412014753.el8ost.noarch requires python(abi) = 3.6, but none of the providers can be installed", " - conflicting requests", "", "", "============================================================", " END OF ERRORS ", "============================================================"
There are one patch missing already attached to the BZ, the patch only set the default parameters for upgrading... besides other little things (but it does not apply here) Configuring those parameters with the correct ones did not fix the issue. The parameters were not properly configured due to the fact that the upgrade prepare command was using and answer file to add the parameters. $ openstack overcloud upgrade prepare --answers-file answer-upgrade.yaml -r roles-data.yaml -n networking-data.yaml When the operator execute the os upgrade command, the default parameters were still on the configuration. To configure properly the parameters, the system_upgrade.yaml and the upgrade_environment.yaml were removed from the answer-upgrade.yaml file and append to the end of the "openstack overcloud upgrade prepare" command as: $ openstack overcloud upgrade prepare --answers-file answer-upgrade.yaml -r roles-data.yaml -n networking-data.yaml -e system_upgrade.yaml -e upgrade_environment.yaml Once that the parameters were properly configured, the operator could do the system upgrade.