Description of problem:
BZ#1365451 raised a question - why did the 'ovirt-imageio-proxy-setup' issues occurred on the 2nd engine-setup run but not the first one?
The reason for that is that the 'ovirt-imageio-proxy-setup' package was not installed the 1st time engine-setup was run.
Following the logic of the "ovirt-engine-dwh-setup" package, it may be tha case that we need to have engine-setup refuse to run now if 'ovirt-imageio-proxy-setup' is not installed and up to date.
Version-Release number of selected component (if applicable):
The following flow should theoretically reproduce the issue:
Steps to Reproduce:
0. start with a blank host with ovirt repos configured
1. 'yum install ovirt-engine-\*setup\*'
2. run 'engine-setup'
3. run 'engine-setup'
The 1st engine-setup will also install 'ovirt-imageio-proxy-setup'
The 2nd engine-setup will actually try to setup 'ovirt-imageio-proxy'
The 1st engine-setup should require 'ovirt-imageio-proxy-setup' so it could setup 'ovirt-imageio-proxy'
The reason this is not failing the ovirt-system-tests ATM is because ovirt-system-tests currently does 'yum install ovirt-engine' rather then 'yum install ovirt-engine-setup'.
Please open a bug against it if this should be changed.
No sure ATM if this also made the upgrade jobs fail, those are, alas, too fragile ATM.
If you need to have ovirt-imageio-proxy-setup installed before running engine-setup (which does the upgrade), you need to add "Requires: ovirt-imageio-proxy-setup" into setup-plugin-ovirt-engine RPM (same way as we enforced installation of ovirt-engine-extension-aaa-jdbc in 3.6)
the whole imageio stuff are handled by Amit, moving to him.
I think we can add a Known Issue on ovirt 4.0.2 release notes about it.
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
# repoquery ovirt-engine-setup-plugin-ovirt-engine.noarch --requires --resolve
(In reply to Barak Korren from comment #0)
> Description of problem:
> BZ#1365451 raised a question - why did the 'ovirt-imageio-proxy-setup'
> issues occurred on the 2nd engine-setup run but not the first one?
General note: Bugs, and especially verifications, should be described functionally. In current case the bug should have had summary line:
imageio-proxy is not asked about, thus not configured, on upgrade from 3.6 to 4.0, but only on the next run of engine-setup after upgrade.
(or something shorter, but you get my point).
'this requires that', or 'this does not require that' is hardly a bug in itself. It can be a root cause for a bug, as in current case.
Also verification, obviously, should have been:
1. Installed and set up 3.6 engine
2. Added 4.0 repos and ran 'yum update ovirt-engine\*setup\*'
3. Ran engine-setup - was asked about imageio-proxy, replied yes
4. imageio-proxy was successfully configured