Created attachment 922074 [details]
Description of problem:
When running downstream setup the --offline doesn't work as expected, since it uses yum to check if setup package is available in any repo. This means that only way to install packages from private build is adding local repo. Also no way to run setup and not use yum.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. build rhevm with minimead
2. install on el6
3. run engine-setup --offline
fails on setup package not found via yum
Should not use yum if --offline is chosen
Not sure what's the best way to solve this - '--offline' does not set any specific flag, it just disables yum packager and enables "offlinepackager".
offlinepackager is a trivial packager that reports just an installed version of vdsm '999.9.9' if queried about vdsm, otherwise an empty list. Not sure what we need this 'vdsm' thing for.
Possible solutions I can think of:
1. Just check if offlinepackager is true or false
2. Add to the fixed list of offlinepackager also the setup package
3. Make '--offline' an independent new env key and check it (and convert existing code in the shell wrapper to python code that will set other env based on this new key)
4. Make offlinepackager extensible (allow other code add stuff to it in addition to 'vdsm').
A possible workaround is to pass to env: 'OVESETUP_RPMDISTRO/engineSetupPackages=str:'. Didn't verify that.
Sandro - please comment...
As far as I can remember, offline-packager was supposed to install all required dependencies and tell setup that required package is in and no updates are available.
Adding Alon to the discussion.
in case of --offline we should not access miniyum, so we need also to disable the ovirt-engine-common/distro-rpm/packages.py explicit access to yum.
Actually distro-rpm/packages.py checks OFFLINE_PACKAGER . I'll do that too.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.