There is no new lv, I can remove rpm and reinstall manually to reproduce with
any debug options, if you want.
I left host in maintenance mode.
should I also remove ovirt-node-ng-image ? I found something strange:
# rpm -q ovirt-node-ng-image
ovirt-node-ng-image-4.1.0-1.el7.centos.noarch
# rpm
Hey Sergey -
If you check "lvs" and ensure that there's not actually a new LV from the
update, you can cleanly 'rpm -e ovirt-node-ng-image-update', and be ok
without redeploying.
Unfortunately, it's hard to tell from the logs (and '--justdb' hanging)
what's happening here, but I'll try to reprodu
Adding Douglas and Ryan
Il 06/Feb/2017 13:32, "Sergey Kulikov" ha scritto:
>
> 1) I've updated from 4.0.6 to 4.1.0 (on Feb 01 node-ng was at version
> 4.1.0-0)
> After some time engine alerted, that this node have updates to
> ovirt-node-ng-image-4.1.0-1,
> but update from engine timed out, ther
1) I've updated from 4.0.6 to 4.1.0 (on Feb 01 node-ng was at version 4.1.0-0)
After some time engine alerted, that this node have updates to
ovirt-node-ng-image-4.1.0-1,
but update from engine timed out, there were hanging processes in ps on this
node:
root 36309 0.0 0.0 113120 1564 ?
4 matches
Mail list logo