The last ovirt-engine package ran on Jan 11th and this failure happened on the 14th so the appliance package is suppose to be newer then the engine and should be running fine. if this is not the case, then I suggest that the maintainers of the project see what is needed to be updated and trigger a new package build (which is why I was alerting to the failure)
Thanks, Dafna On Tue, Jan 15, 2019 at 6:51 AM Yedidyah Bar David <d...@redhat.com> wrote: > On Mon, Jan 14, 2019 at 2:15 PM Dafna Ron <d...@redhat.com> wrote: > > > > Hi, > > > > we are failing test 001_upgrade_engine.test_initialize_engine on ovirt > 4.2 for project ovirt-ansible-hosted-engine-setup. > > > > Patch reported by CQ: > > > > > https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d38719de663cb8ade13eb8bdff2d1e6f > - Rename the role - replacing '-' with '_' > > > > Ido, can you please check this issue? > > > > failed build: > > > > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/ > > > > error: > > > > [ INFO ] Checking for an update for Setup... > > An update for the Setup packages ovirt-engine-setup > ovirt-engine-setup-plugin-websocket-proxy ovirt-engine-dwh-setup was found. > Please update that package by running: > > "yum update ovirt-engine-setup > ovirt-engine-setup-plugin-websocket-proxy ovirt-engine-dwh-setup" > > and then execute Setup again. > > [ ERROR ] Failed to execute stage 'Environment customization': Please > update the Setup packages > > [ INFO ] Stage: Clean up > > Log file is located at > /var/log/ovirt-engine/setup/ovirt-engine-setup-20190114053840-4ysu6y.log > > [ INFO ] Generating answer file > '/var/lib/ovirt-engine/setup/answers/20190114053855-setup.conf' > > [ INFO ] Stage: Pre-termination > > [ INFO ] Stage: Termination > > [ ERROR ] Execution of setup failed > > ('FATAL Internal error (main): Please update the Setup packages',) > > > > lago.ssh: DEBUG: Command 8e6b18d0 on > lago-upgrade-from-release-suite-4-2-engine errors: > > Traceback (most recent call last): > > File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in > main > > installer.execute() > > File "/usr/lib/python2.7/site-packages/otopi/main.py", line 157, in > execute > > self.context.runSequence() > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 771, in > runSequence > > util.raiseExceptionInformation(infos[0]) > > File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in > raiseExceptionInformation > > exec('raise info[1], None, info[2]') > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in > _executeMethod > > method['method']() > > File > "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py", > line 410, in _customization > > raise RuntimeError(_('Please update the Setup packages')) > > RuntimeError: Please update the Setup packages > > I think this is self-explanatory, no? > > Most likely this happens because we have a new engine and the appliance > is not updated. If it's just a timing issue, should be solved without > intervention on next appliance build. You (CI) might consider, though, > forcing an appliance build and using it in each CQ batch that updates > the engine. > > If it's something else, need to check appliance build status. > > Best regards, > -- > Didi >
_______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KTBPK7GH6UV244RYRBRTFMP5GQVHULXB/
