Hi Jingjie,
                
                  If you have a node installed using ovirt-node-ng it created a thin LVM pool and ovirt-node-ng-image-update creates a new LVM layer so you have 2 versions of the node that you can switch between.
                    

Regards,
                  Paul S.

From: Jingjie Jiang <jingjie.jiang@oracle.com>
Sent: 14 January 2020 15:30
To: Parth Dhanjal <dparth@redhat.com>
Cc: users <users@ovirt.org>
Subject: [ovirt-users] Re: upgrade issue
 

Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.

Hi Path,

Thanks for your rely.

Please check my inline comments

-Jingjie

On 1/14/20 2:28 AM, Parth Dhanjal wrote:
Hello Jingjie!

You can follow https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_to_oVirt_4.2.html

I tried the above link before and it worked.

But, I'd like to know how  the upgrade with ovirt-node-ng-image-update package works.

Any suggestion about the issue I reported in previous email?

Also, about the link you pointed, "imgbase check" command crashed when I ran from the ovirt host based on CentOS:

# imgbase check
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/lib/python2.7/site-packages/imgbased/__main__.py", line 53, in <module>
    CliApplication()
  File "/usr/lib/python2.7/site-packages/imgbased/__init__.py", line 82, in CliApplication
    app.hooks.emit("post-arg-parse", args)
  File "/usr/lib/python2.7/site-packages/imgbased/hooks.py", line 120, in emit
    cb(self.context, *args)
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 185, in post_argparse
    run_check(app)
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 225, in run_check
    status = Health(app).status()
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 358, in status
    status.results.append(group().run())
  File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line 385, in check_thin
    pool = self.app.imgbase._thinpool()
  File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 120, in _thinpool
    return LVM.Thinpool.from_tag(self.thinpool_tag)
  File "/usr/lib/python2.7/site-packages/imgbased/lvm.py", line 227, in from_tag
    assert len(lvs) == 1
AssertionError



Under this link you can find a tab to upgrade the hosts. Instead of 
https://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm You can use https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm

Regards
Parth Dhanjal

On Mon, Jan 13, 2020 at 11:44 PM <jingjie.jiang@oracle.com> wrote:
Hello,

By following the instruction at https://www.ovirt.org/documentation/upgrade-guide/appe-Manually_Updating_Hosts.html, I tried to upgrade host from 4.2.8(CentOS 7.6) to 4.3.7.
After the reboot, the host still running 4.2.8 vdsm.
 # rpm -qa | grep vdsm
vdsm-common-4.20.46-1.el7.noarch
vdsm-yajsonrpc-4.20.46-1.el7.noarch
vdsm-hook-vhostmd-4.20.46-1.el7.noarch
vdsm-4.20.46-1.el7.x86_64
vdsm-client-4.20.46-1.el7.noarch
vdsm-python-4.20.46-1.el7.noarch
vdsm-hook-fcoe-4.20.46-1.el7.noarch
vdsm-network-4.20.46-1.el7.x86_64
vdsm-jsonrpc-4.20.46-1.el7.noarch
vdsm-hook-vmfex-dev-4.20.46-1.el7.noarch
vdsm-http-4.20.46-1.el7.noarch
vdsm-api-4.20.46-1.el7.noarch
vdsm-hook-ethtool-options-4.20.46-1.el7.noarch
vdsm-hook-openstacknet-4.20.46-1.el7.noarch
[root@ovs260 ~]#


Looks like the upgrade did not take place as expected.
Any clue?

Thanks in advance,
Jingjie
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/BLE3M55EMIDECUEZ6XWIFYNRHGDYO7RA/
To view the terms under which this email is distributed, please go to:-
http://leedsbeckett.ac.uk/disclaimer/email/