Description of problem: (Originally as comment at https://bugzilla.redhat.com/show_bug.cgi?id=1381419#c5) when no repo has a rpm with has in rpm metadata 'provides: ovirt-node-ng-image-update' the upgradecheck fails with: ~~~ Failed to check for available updates on host dell-r210ii-03 with message 'Command returned failure code 1 during SSH session 'root.63.222''. ~~~ IMO isn't the issue here? ~~~ Yum: queue package ovirt-node-ng-image-update for install ~~~ Wouldn't be better to get 'yum list updates' equivalent via python module and parse output? This way it won't fail with rc 1. Just guessing loudly... 2017-01-27 12:28:51 DEBUG otopi.context context._executeMethod:128 Stage packages METHOD otopi.plugins.ovirt_host_mgmt.packages.update.Plugin._packagesCheck 2017-01-27 12:28:51 DEBUG otopi.plugins.ovirt_host_mgmt.packages.update update.verbose:94 Yum: queue package ovirt-node-ng-image-update for install 2017-01-27 12:28:51 ERROR otopi.plugins.ovirt_host_mgmt.packages.update update.error:102 Yum: Cannot queue package ovirt-node-ng-image-update: Package ovirt-node-ng-image-update cannot be found 2017-01-27 12:28:51 INFO otopi.plugins.ovirt_host_mgmt.packages.update update.info:98 Yum: Performing yum transaction rollback 2017-01-27 12:28:51 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/tmp/ovirt-7pEBIyFC1u/pythonlib/otopi/context.py", line 132, in _executeMethod method['method']() File "/tmp/ovirt-7pEBIyFC1u/otopi-plugins/ovirt-host-mgmt/packages/update.py", line 110, in _packagesCheck packages=self.environment[omgmt.PackagesEnv.PACKAGES], File "/tmp/ovirt-7pEBIyFC1u/pythonlib/otopi/miniyum.py", line 851, in install **kwargs File "/tmp/ovirt-7pEBIyFC1u/pythonlib/otopi/miniyum.py", line 500, in _queue package=package, RuntimeError: Package ovirt-node-ng-image-update cannot be found 2017-01-27 12:28:51 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Package installation': Package ovirt-node-ng-image-update cannot be found 2017-01-27 12:28:51 DEBUG otopi.transaction transaction.abort:119 aborting 'Yum Transaction' 2017-01-27 12:28:51 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Performing yum transaction rollback Loaded plugins: product-id 2017-01-27 12:28:51 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN 2017-01-27 12:28:51 DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/error=bool:'True' 2017-01-27 12:28:51 DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError('Package ovirt-node-ng-image-update cannot be found',), <traceback object at 0x1c3b1b8>)]' 2017-01-27 12:28:51 DEBUG otopi.context context.dumpEnvironment:774 ENVIRONMENT DUMP - END Version-Release number of selected component (if applicable): ovirt-engine-4.1.0.2-0.2.el7.noarch How reproducible: 100% Steps to Reproduce: 1. install hypervisor (ngn) 2. do not have defined repos for ovirt-node-ng-image-update package 3. run upgrade check of host Actual results: Failed to check for available updates on host dell-r210ii-03 with message 'Command returned failure code 1 during SSH session 'root.63.222''. Expected results: something more understandable Additional info:
Moving to Moti since he's the owner of the upgrade management feature.
So we could ignore errors that package doesn't exists during check for upgrade, but I don't want to do that for following reasons: 1. This warns admin that something is wrong with his setup, because all repositories should be available (there might be network/mirrors issues, but generally you shouldn't get into the package unknown issue). 2. This is the only way for admin how to find out that he entered wrong package name into UserPackageNamesForCheckUpdate option via engine-config I'd probably close it as WONTFIX if there are no strong opinions otherwise ...
Closing as WONTFIX, feel free to reopen and provide new reasons why this should be fixed