- Users - oVirt List Archives

oVirt failing to make a template of Centos 7 VM using seal
by damien.altman＠gmail.com 20 Jan '20

20 Jan '20

Hi there, My oVirt engine is failing to create a template from a Centos 7 VM, the /var/log/vdsm/vdsm.log is as follows: ) 2020-01-20 19:39:07,332+1100 ERROR (virt/875f8036) [root] Job u'875f8036-e28a-4741-b3a3-046cc711d252' failed (jobs:221) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/jobs.py", line 157, in run self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/jobs/seal.py", line 74, in _run virtsysprep.sysprep(vol_paths) File "/usr/lib/python2.7/site-packages/vdsm/virtsysprep.py", line 39, in sysprep commands.run(cmd) File "/usr/lib/python2.7/site-packages/vdsm/common/commands.py", line 110, in run raise cmdutils.Error(args, p.returncode, out, err) Error: Command ['/usr/bin/virt-sysprep', '-a', u'/rhev/data-center/mnt/xxxxx.xxxxx.net:_storage_host__storage/eb8ba7f9-27d5 -44c0-a744-9027be39a756/images/3ac44e69-ae82-4d79-8b58-0f3ef4cf60db/f4631212 -4b1e-4c65-b19b-47215e9aca55'] failed with rc=1 out='[ 0.0] Examining the guest ...\n' err="libvirt: XML-RPC error : Cannot create user runtime directory '//.cache/libvirt': Permission denied\nvirt-sysprep: error: libguestfs error: could not connect to libvirt (URI = \nqemu:///session): Cannot create user runtime directory '//.cache/libvirt': \nPermission denied [code=38 int1=13]\n\nIf reporting bugs, run virt-sysprep with debugging enabled and include the \ncomplete output:\n\n virt-sysprep -v -x [...]\n" The template saves fine if I do not have 'Seal Template' selected.

2 1

VM Failover Scenario - automatically shutting down Test VM when failover for Prod VM is required
by Martin Decker 19 Jan '20

19 Jan '20

Hello List, I have a simple setup with 2 Compute Nodes to host 2 VMs: a PROD VM and a TEST VM. The requirement is that if the compute node with the Prod VM fails, the Prod VM should automatically migrate to the second compute node. In order to maximize performance for the Prod VM, there should be no other VMs running on the same compute node. This means that the Test VM should be stopped before the Prod VM is started on the failover compute node. I want to use 80-90% of the physical memory of the compute node for Prod VM, therefore Prod VM can not be started due to lack of memory if Test VM is not stopped up front. Can this be implemented? Best regards, Martin

1 0

ISO Upload
by Christian Reiss 17 Jan '20

17 Jan '20

Hey folks, I have a cluster setup as follows (among others) /vms for vm storage. Attached as data domain. /isos for, well, isos. Attached as iso domain. When I try to upload a(ny) iso via the ovirt engine, I can only select the vms storage path, not the iso storage path. Both are green and active across the board. Is my understanding correct that I can only upload and ISO to a data domain, then (once uploaded), move the iso file to the iso domain via the web-ui? -Chris. -- with kind regards, mit freundlichen Gruessen, Christian Reiss

6 10

Re: [moVirt] Expanding oVirt
by Michal Skrivanek 17 Jan '20

17 Jan '20

[fwding to the right list] > On 15 Jan 2020, at 22:57, mweber(a)maetrix.tech wrote: > > I am planning a basic 3-host hyperconverged oVirt cluster and am very happy with tests I have conducted regarding the deployment. > > I have a question regarding expanding the cluster and cant seem to find a direct answer. My hosts have a limited number of HDD slots and am curious about expanding the gluster volumes. Is this a simple process of adding another host or hosts as I go and adding the gluster bricks to the volume and rebalancing? I also recall seeing a hard limit of nine hosts in a cluster. Is this correct? > Thank you, > _______________________________________________ > moVirt mailing list -- movirt(a)ovirt.org > To unsubscribe send an email to movirt-leave(a)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/movirt@ovirt.org/message/YSSYKBGN6HMU…

1 0

Re: Ovirt OVN help needed
by Strahil 17 Jan '20

17 Jan '20

Hi Miguel, It seems the Cluster's switch is of type 'Linux Bridge'. Best Regards, Strahil NikolovOn Jan 10, 2020 12:37, Miguel Duarte de Mora Barroso <mdbarroso(a)redhat.com> wrote: > > On Mon, Jan 6, 2020 at 9:21 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > > > Hi Miguel, > > > > I had read some blogs about OVN and I tried to collect some data that might hint where the issue is. > > > > I still struggle to "decode" that , but it may be easier for you or anyone on the list. > > > > I am eager to receive your reply. > > Thanks in advance and Happy New Year ! > > Hi, > > Sorry for not noticing your email before. Hope late is better than never .. > > > > > > > Best Regards, > > Strahil Nikolov > > > > В сряда, 18 декември 2019 г., 21:10:31 ч. Гринуич+2, Strahil Nikolov <hunter86_bg(a)yahoo.com> написа: > > > > > > That's a good question. > > ovirtmgmt is using linux bridge, but I'm not so sure about the br-int. > > 'brctl show' is not understanding what type is br-int , so I guess openvswitch. > > > > This is still a guess, so you can give me the command to verify that :) > > You can use the GUI for that; access "Compute > clusters" , choose the > cluster in question, hit 'edit', then look for the 'Swtich type' > entry. > > > > > > As the system was first build on 4.2.7 , most probably it never used anything except openvswitch. > > > > Thanks in advance for your help. I really appreciate that. > > > > Best Regards, > > Strahil Nikolov > > > > > > В сряда, 18 декември 2019 г., 17:53:31 ч. Гринуич+2, Miguel Duarte de Mora Barroso <mdbarroso(a)redhat.com> написа: > > > > > > On Wed, Dec 18, 2019 at 6:35 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > > > > > Hi Dominik, > > > > > > sadly reinstall of all hosts is not helping. > > > > > > @ Miguel, > > > > > > I have 2 clusters > > > 1. Default (amd-based one) -> ovirt1 (192.168.1.90) & ovirt2 (192.168.1.64) > > > 2. Intel (intel-based one and a gluster arbiter) -> ovirt3 (192.168.1.41) > > > > But what are the switch types used on the clusters: openvswitch *or* > > legacy / linux bridges ? > > > > > > > > > > > > The output of the 2 commands (after I run reinstall on all hosts ): > > > > > > [root@engine ~]# ovn-sbctl list encap > > > _uuid : d4d98c65-11da-4dc8-9da3-780e7738176f > > > chassis_name : "baa0199e-d1a4-484c-af13-a41bcad19dbc" > > > ip : "192.168.1.90" > > > options : {csum="true"} > > > type : geneve > > > > > > _uuid : ed8744a5-a302-493b-8c3b-19a4d2e170de > > > chassis_name : "25cc77b3-046f-45c5-af0c-ffb2f77d73f1" > > > ip : "192.168.1.64" > > > options : {csum="true"} > > > type : geneve > > > > > > _uuid : b72ff0ab-92fc-450c-a6eb-ab2869dee217 > > > chassis_name : "5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3" > > > ip : "192.168.1.41" > > > options : {csum="true"} > > > type : geneve > > > > > > > > > [root@engine ~]# ovn-sbctl list chassis > > > _uuid : b1da5110-f477-4c60-9963-b464ab96c644 > > > encaps : [ed8744a5-a302-493b-8c3b-19a4d2e170de] > > > external_ids : {datapath-type="", iface-types="erspan,geneve,gre,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan", ovn-bridge-mappings=""} > > > hostname : "ovirt2.localdomain" > > > name : "25cc77b3-046f-45c5-af0c-ffb2f77d73f1" > > > nb_cfg : 0 > > > transport_zones : [] > > > vtep_logical_switches: [] > > > > > > _uuid : dcc94e1c-bf44-46a3-b9d1-45360c307b26 > > > encaps : [b72ff0ab-92fc-450c-a6eb-ab2869dee217] > > > external_ids : {datapath-type="", iface-types="erspan,geneve,gre,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan", ovn-bridge-mappings=""} > > > hostname : "ovirt3.localdomain" > > > name : "5668499c-7dd0-41ee-bc5d-2e6ee9cd61c3" > > > nb_cfg : 0 > > > transport_zones : [] > > > vtep_logical_switches: [] > > > > > > _uuid : 897b34c5-d1d1-41a7-b2fd-5f1fa203c1da > > > encaps : [d4d98c65-11da-4dc8-9da3-780e7738176f] > > > external_ids : {datapath-type="", iface-types="erspan,geneve,gre,internal,ip6erspan,ip6gre,lisp,patch,stt,system,tap,vxlan", ovn-bridge-mappings=""} > > > hostname : "ovirt1.localdomain" > > > name : "baa0199e-d1a4-484c-af13-a41bcad19dbc" > > > nb_cfg : 0 > > > transport_zones : [] > > > vtep_logical_switches: [] > > > > > > > > > If you know an easy method to reach default settings will be best, as I'm currently not using OVN in production (just for tests and to learn more about how it works) and I can afford any kind of downtime. > > > > > > Best Regards, > > > Strahil Nikolov > > > > > > В вторник, 17 декември 2019 г., 11:28:25 ч. Гринуич+2, Miguel Duarte

3 2

ovirt_disk Ansible module creating disks of wrong size but why?
by m.skrzetuski＠gmail.com 16 Jan '20

16 Jan '20

Hello everyone, I just saw the list of modules at https://github.com/ansible/ansible/tree/663f8464ee7ab2cb086857f04393e643407…. Does this mean you (oVirt devs) did not update ovirt Ansible modules since 2 years? Anyhow, the following tasks create a VM with a 8GB instead of 500GB disk (confirmed with lsblk and fdisk). Why is that and how do I get around it? - name: download centos image get_url: url: https://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 dest: /data/isos/CentOS-7-x86_64-GenericCloud.qcow2 - name: create disk for vm ovirt_disk: name: centos upload_image_path: /data/isos/CentOS-7-x86_64-GenericCloud.qcow2 storage_domain: vmdata2 size: 500GiB wait: true bootable: true format: cow when: register_centos_disks.ovirt_disks|length == 0 - name: create vm ovirt_vm: name: dumbo type: server state: "running" cluster: dumbo high_availability: yes disks: - name: centos graphical_console: protocol: vnc operating_system: Linux nics: - name: nic1 profile_name: ovirtmgmt memory: 8GiB cpu_sockets: 1 cpu_cores: 1 cpu_threads: 2 If I use sparse: false with the ovirt_disk module I am getting following errors. An exception occurred during task execution. To see the full traceback, use -vvv. The error was: Error: Fault reason is "Operation Failed". Fault detail is "[Cannot add Virtual Disk. Disk configuration (COW Preallocated) is incompatible with the storage domain type.]". HTTP response code is 409. fatal: [dumbo]: FAILED! => changed=false msg: Fault reason is "Operation Failed". Fault detail is "[Cannot add Virtual Disk. Disk configuration (COW Preallocated) is incompatible with the storage domain type.]". HTTP response code is 409. The storage domain type is data. So what is wrong with that? Frustrated regards Skrzetuski

4 7

Re: Can we please migrate to 2020 and get a user friendly issues/support tool?
by Strahil 16 Jan '20

16 Jan '20

I can admit that I also struggle with the search. Anything like the CentOS forum will be far better than now. P.S.: when you have several thousand e-mails, searching in the client is the same ... Best Regards, Strahil NikolovOn Jan 13, 2020 16:54, Torsten Stolpmann <torsten.stolpmann(a)verit.de> wrote: > > To throw in my 2cents worth - I am totally happy with a mailing list and > see absolutely no need for a change. > > I heard that Google is very good at indexing btw. as is my mailreader. > > > On 13.01.2020 15:37, m.skrzetuski(a)gmail.com wrote: > > Well, yes... in my opinion it should be a discussion forum, with a well designed search. A place where you can see the question and answers and maybe a "marked" solution. Not everything is a bug and Bugzilla is as modern as Internet Explorer 4. Did you try to search for solutions, for some oVirt problems? It's a nightmare to go through this list here. > > > > The comparison with Jira was probably wrong, although you don't have to use Jira like a ticketing system. I just wanted to express that I would like some kind of a modern tool. Something like StackOverflow maybe. Or a simple forum software. > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)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/LAHRPTZCDZQEO… > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/ZQPK2LGGAJFNP…

4 4

Re: upgrade issue
by Jingjie Jiang 16 Jan '20

16 Jan '20

Hi Paul, I got it now. Thanks a lot, Jingjie On 1/16/20 5:02 AM, Staniforth, Paul wrote: > Hi Jingjie, > It sounds like you are using linux hosts try yum > check-update and yum update. The ovirt-node-ng-image-update is for > when you have installed oVirt Node, you can't change from an > enterprise linux host to a node without deleting the host and > reinstalling using the oVirt node iso as it installs to a bare-metal > system. > > https://www.ovirt.org/documentation/install-guide/chap-Introduction_to_Host… > Introduction to Hosts | oVirt > <https://www.ovirt.org/documentation/install-guide/chap-Introduction_to_Host…> > Host Type Other Names Description; oVirt Node: Thin host: This is a > minimal operating system based on Enterprise Linux. It is distributed > as an ISO file and contains only the packages required for the machine > to act as a host. > www.ovirt.org > > Regards, > Paul S. > ------------------------------------------------------------------------ > *From:* Jingjie Jiang <jingjie.jiang(a)oracle.com> > *Sent:* 15 January 2020 18:25 > *To:* Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk>; Parth > Dhanjal <dparth(a)redhat.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [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 Paul, > > Thanks for your reply. > > I did install ovirt-release43 before I install the > ovirt-node-ng-image-update package. > > > Here is the brief procedure: > > 1. Install the 4.2.8 ovirt host on CentOS7.6 by adding the node from > AdminPortal. > > 2. Upgrade ovirt 4.2.8 engine to 4.3.6. > > 3. Set the host to maintainence from AdminPortal. > > 4. Yum install ovirt-release43 rpm > > # yum install > http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm > <https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.…> > > 5.Yum install node update package > > # yum install > https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-imag… > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresources…> > > 6. reboot > > > vdsm did not get update. > > > -Jingjie > > > On 1/15/20 6:14 AM, Staniforth, Paul wrote: >> Hel# yum install >> https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-imag… >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresources…> >> Jingjie, >> I think you need to install >> https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresources…> >> so yum updates to the 4.3 release otherwise it will stay on the 4.2 >> release (4.2.8 being the last version). >> >> >> Regards, >> Paul S. >> ------------------------------------------------------------------------ >> *From:* Jingjie Jiang <jingjie.jiang(a)oracle.com> >> <mailto:jingjie.jiang@oracle.com> >> *Sent:* 14 January 2020 15:30 >> *To:* Parth Dhanjal <dparth(a)redhat.com> <mailto:dparth@redhat.com> >> *Cc:* users <users(a)ovirt.org> <mailto: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_t… >>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> >> >> 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 >>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresources…> >>> You can use >>> https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm >>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresources…> >>> >>> Regards >>> Parth Dhanjal >>> >>> On Mon, Jan 13, 2020 at 11:44 PM <jingjie.jiang(a)oracle.com >>> <mailto:jingjie.jiang@oracle.com>> wrote: >>> >>> Hello, >>> >>> By following the instruction at >>> https://www.ovirt.org/documentation/upgrade-guide/appe-Manually_Updating_Ho… >>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…>, >>> 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(a)ovirt.org <mailto:users@ovirt.org> >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> <mailto:users-leave@ovirt.org> >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BLE3M55EMIDEC… >>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> >>> >> To view the terms under which this email is distributed, please go to:- >> http://leedsbeckett.ac.uk/disclaimer/email/ > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/KERM3W5G5OI3H…

1 0

dhw-error after HE restore
by Christoph Köhler 16 Jan '20

16 Jan '20

1 0

Re: upgrade issue
by Jingjie Jiang 16 Jan '20

16 Jan '20

Hi Paul, Thanks for your reply. I did install ovirt-release43 before I install the ovirt-node-ng-image-update package. Here is the brief procedure: 1. Install the 4.2.8 ovirt host on CentOS7.6 by adding the node from AdminPortal. 2. Upgrade ovirt 4.2.8 engine to 4.3.6. 3. Set the host to maintainence from AdminPortal. 4. Yum install ovirt-release43 rpm # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm 5.Yum install node update package # yum install https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-imag… 6. reboot vdsm did not get update. -Jingjie On 1/15/20 6:14 AM, Staniforth, Paul wrote: > Hel# yum install > https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-imag… > Jingjie, > I think you need to install > https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm > <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresources…> > so yum updates to the 4.3 release otherwise it will stay on the 4.2 > release (4.2.8 being the last version). > > > Regards, > Paul S. > ------------------------------------------------------------------------ > *From:* Jingjie Jiang <jingjie.jiang(a)oracle.com> > *Sent:* 14 January 2020 15:30 > *To:* Parth Dhanjal <dparth(a)redhat.com> > *Cc:* users <users(a)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_t… >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > > 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 >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresources…> >> You can use >> https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresources…> >> >> Regards >> Parth Dhanjal >> >> On Mon, Jan 13, 2020 at 11:44 PM <jingjie.jiang(a)oracle.com >> <mailto:jingjie.jiang@oracle.com>> wrote: >> >> Hello, >> >> By following the instruction at >> https://www.ovirt.org/documentation/upgrade-guide/appe-Manually_Updating_Ho… >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…>, >> 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(a)ovirt.org <mailto:users@ovirt.org> >> To unsubscribe send an email to users-leave(a)ovirt.org >> <mailto:users-leave@ovirt.org> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BLE3M55EMIDEC… >> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> >> > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/

3 2