Bug 1381419

That the suggestion to update is shown is probably caused by bug 1364040.

But this bug is about the "<UNKNOWN>" string, which shoul dnot be shown but rather the nam eof the to be updated package.

The described bug indicates that ovirt-host-deploy has detected an update available, but the package name is reported as an empty string.

The event logging mechanism replaces the empty string with the <UNKNOWN> string.

I assume that the mentioned host is the NGN, therefore could you provide the following information:

1. /var/log/ovirt-engine/engine.log
2. The relevant file named: /var/log/ovirt-engine/host-deploy/ovirt-host-mgmt*
3. The output of 'dnf check update ovirt-node-ng-image-update' as executed on the node.

Hi,

  I have put /var/log/ovirt-engine/engine.log, /var/log/ovirt-engine/host-deploy/ovirt-host-mgmt* in the link below.

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/HC/1381419/

output of yum check update ovirt-node-ng-image-update:
============================================================

[root@rhsqa-grafton1 ~]# yum check update ovirt-node-ng-image-update
Loaded plugins: imgbased-warning, product-id, search-disabled-repos, subscription-manager
Warning: yum operations are not persisted across upgrades!
check ['update', 'ovirt-node-ng-image-update']

The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

not good enough with ovirt-engine-backend-4.1.0.2-0.2.el7.noarch

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

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

1. This bug is about displaying "<UNKNOWN>" string instead of an empty list when no package upgrades found

2. It's known limitation that list of packages which we check for upgrade have to contain only existing packages. So if you want this limitation removed, please create RFE to track that

Because of the above moving back to ON_QA

ok, ovirt-engine-4.1.0.2-0.2.el7.noarch & redhat-release-virtualization-host-4.1-0.6.el7.x86_64

Check for available updates on host dell-r210ii-03 was completed successfully with message 'no updates found.'.