Initially reported as https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/issues/280
One note, it would be beneficial for QE to be able to inject also repositories (or packages) so we would have something to update to.
With regular manual deployment I see these in engine setup's log: nsednev-he-1 ~]# cat /var/log/ovirt-engine/setup/ovirt-engine-setup-20200420163013-g3ffsj.log | grep packagesUpgradeList 2020-04-20 16:30:15,747+0300 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_RPMDISTRO/packagesUpgradeList=list:'[]' 2020-04-20 16:30:17,704+0300 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_RPMDISTRO/packagesUpgradeList=list:'[{'packages': ['ovirt-engine-extension-aaa-jdbc']}]' 2020-04-20 16:30:17,771+0300 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_RPMDISTRO/packagesUpgradeList=list:'[{'packages': ['ovirt-engine-extension-aaa-jdbc']}, {'packages': ['ovirt-engine', 'ovirt-engine-ui-extensions', 'ovirt-web-ui', 'rhvm-branding-rhv', 'ovirt-log-collector']}]' 2020-04-20 16:30:17,791+0300 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_RPMDISTRO/packagesUpgradeList=list:'[{'packages': ['ovirt-engine-extension-aaa-jdbc']}, {'packages': ['ovirt-engine', 'ovirt-engine-ui-extensions', 'ovirt-web-ui', 'rhvm-branding-rhv', 'ovirt-log-collector']}, {'packages': ['ovirt-engine-websocket-proxy']}]' 2020-04-20 16:30:17,802+0300 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_RPMDISTRO/packagesUpgradeList=list:'[{'packages': ['ovirt-engine-extension-aaa-jdbc']}, {'packages': ['ovirt-engine', 'ovirt-engine-ui-extensions', 'ovirt-web-ui', 'rhvm-branding-rhv', 'ovirt-log-collector']}, {'packages': ['ovirt-engine-websocket-proxy']}, {'packages': ['ovirt-engine-dwh']}]' 2020-04-20 16:30:19,296+0300 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_RPMDISTRO/packagesUpgradeList=list:'[{'packages': ['ovirt-engine-extension-aaa-jdbc']}, {'packages': ['ovirt-engine', 'ovirt-engine-ui-extensions', 'ovirt-web-ui', 'rhvm-branding-rhv', 'ovirt-log-collector']}, {'packages': ['ovirt-engine-websocket-proxy']}, {'packages': ['ovirt-engine-dwh']}]' 2020-04-20 16:35:19,147+0300 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_RPMDISTRO/packagesUpgradeList=list:'[{'packages': ['ovirt-engine-extension-aaa-jdbc']}, {'packages': ['ovirt-engine', 'ovirt-engine-ui-extensions', 'ovirt-web-ui', 'rhvm-branding-rhv', 'ovirt-log-collector']}, {'packages': ['ovirt-engine-websocket-proxy']}, {'packages': ['ovirt-engine-dwh']}]' Tested on: ovirt-ansible-hosted-engine-setup-1.1.2-1.el8ev.noarch ovirt-hosted-engine-ha-2.4.2-1.el8ev.noarch ovirt-hosted-engine-setup-2.4.4-1.el8ev.noarch Linux 4.18.0-193.el8.x86_64 #1 SMP Fri Mar 27 14:35:58 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 8.2 (Ootpa)
Please provide clear reproduction steps for verification and proper documentation.
(In reply to Nikolai Sednev from comment #3) > Please provide clear reproduction steps for verification and proper > documentation. Write Ansible playbooks that will run on the engine VM before engine-setup https://github.com/oVirt/ovirt-ansible-hosted-engine-setup#make-changes-in-the-engine-vm-during-the-deployment You can use these references in order to create the Ansible playbooks: For subscription: https://docs.ansible.com/ansible/latest/modules/redhat_subscription_module.html For repo enable: https://docs.ansible.com/ansible/latest/modules/rhsm_repository_module.html After HE installation finishes, look for `--== PACKAGES ==--` in engine setup log on the engine VM.
Works for me on these components: Software Version:4.4.1.2-0.10.el8ev rhvm-appliance-4.4-20200604.0.el8ev.x86_64 ovirt-hosted-engine-setup-2.4.4-1.el8ev.noarch ovirt-hosted-engine-ha-2.4.3-1.el8ev.noarch Linux 4.18.0-193.9.1.el8_2.x86_64 #1 SMP Sun Jun 14 15:03:05 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 8.2 (Ootpa)
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.