Re: [ovirt-users] 10Gb Networking with OVN

[Dan Kenigsberg]

Beau, have you solved your performance problem already?

Would you share what is the MTU you have set on the underlying network, and
in your VMs?


On Dec 13, 2017 17:41, "Dominik Holler"  wrote:

On Tue, 12 Dec 2017 23:12:12 +0200
Yaniv Kaul  wrote:

> On Mon, Dec 11, 2017 at 8:21 PM, Beau Sapach 
> wrote:
>
> > Yes, we've done some testing.  With an oVirt VM running on a host
> > using 10Gb ethernet copying data to a physical machine also using
> > 10Gb ethernet we don't see network utilization exceed 800Mbits or
> > so.  A bit of research online yields some experimentation done by
> > others who used SR-IOV to achieve 10Gb from a VM.
> >
>
> Are you using multiple TCP streams, jumbo frames, threads, etc.?

Please verify that the expected interface is used. The automatic
configuration uses ovirtmgmt to transport the data.
This can be changed manually by executing

vdsm-tool ovn-config IP_OF_OVN_CENTRAL IP_OF_LOCAL_INTERFACE

on the host.

Are you using NICs which supports GENEVE offloading?


> Y.
>
>
> > I'm not sure where the bottleneck is, possibly in the VirtIO driver.
> >
> > Beau
> >
> > On Mon, Dec 11, 2017 at 1:23 AM, Dominik Holler 
> > wrote:
> >
> >> Is there an indication that the VMs will not take advantage of
> >> 10Gb?
> >>
> >> On Thu, 7 Dec 2017 15:27:25 -0700
> >> Beau Sapach  wrote:
> >>
> >> > Hello everyone,
> >> >
> >> > I see here:
> >> > https://www.ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/ that
> >> > version 4.2 will have OVN support.  Does anyone know if this will
> >> > allow VMs to take advantage of 10Gb networking without needing
> >> > SR-IOV?
> >> >
> >> >
> >>
> >>
> >
> >
> > --
> > Beau Sapach
> > *System Administrator | Information Technology Services |
> > University of Alberta Libraries*
> > *Phone: 780.492.4181 <(780)%20492-4181> | Email:
> > beau.sap...@ualberta.ca *
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> >

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Some major problems after 4.2 upgrade, could really use some assistance

[Darrell Budic]

Were you running gluster under you shared storage? If so, you probably need to 
setup ganesha nfs yourself.

If not, check your ha-agent logs and make sure it’s mounting the storage 
properly and check for errors. Good luck!

> From: Jayme 
> Subject: Re: [ovirt-users] Some major problems after 4.2 upgrade, could 
> really use some assistance
> Date: January 11, 2018 at 12:28:32 PM CST
> To: Martin Sivak; users@ovirt.org
> 
> This is becoming critical for me, does anyone have any ideas or 
> recommendations on what I can do to recover access to hosted VM?  As of right 
> now I have three hosts that are fully updated, they have the 4.2  repo and a 
> full yum update was performed on them, there are no new updates to apply.  
> The hosted engine had updates as well as a full and complete engine-setup, 
> but did not return after being shut down.  There must be some way I can get 
> the engine running again?  Please
> 
> On Thu, Jan 11, 2018 at 8:24 AM, Jayme  > wrote:
> The hosts have all ready been fully updated with 4.2 packages though.
> 
> ex. 
> 
> ovirt-host.x86_64  
> 4.2.0-1.el7.centos   @ovirt-4.2
> ovirt-host-dependencies.x86_64 
> 4.2.0-1.el7.centos   @ovirt-4.2
> ovirt-host-deploy.noarch   
> 1.7.0-1.el7.centos   @ovirt-4.2
> ovirt-hosted-engine-ha.noarch  
> 2.2.2-1.el7.centos   @ovirt-4.2
> ovirt-hosted-engine-setup.noarch   
> 2.2.3-1.el7.centos   @ovirt-4.2
> 
> On Thu, Jan 11, 2018 at 8:16 AM, Martin Sivak  > wrote:
> Hi,
> 
> yes, you need to upgrade the hosts. Just take the
> ovirt-hosted-engine-ha and ovirt-hosted-engine-setup packages from
> ovirt 4.2 repositories.
> 
> Martin
> 
> On Thu, Jan 11, 2018 at 11:40 AM, Jayme  > wrote:
> > How do I upgrade the hosted engine packages when I can't reach it or do you
> > mean upgrade the hosts if so how exactly do I do that. As for the missing VM
> > it appears that the disk image is there but it's missing XML file I have no
> > idea why or how to recreate it.
> >
> > On Jan 11, 2018 4:43 AM, "Martin Sivak"  > > wrote:
> >>
> >> Hi,
> >>
> >> you hit one known issue we already have fixes for (4.1 hosts with 4.2
> >> engine):
> >> https://gerrit.ovirt.org/#/q/status:open+project:ovirt-hosted-engine-ha+branch:v2.1.z+topic:ovf_42_for_41
> >>  
> >> 
> >>
> >> You can try hotfixing it by upgrading hosted engine packages to 4.2 or
> >> applying the patches manually and installing python-lxml.
> >>
> >> I am not sure what happened to your other VM.
> >>
> >> Best regards
> >>
> >> Martin Sivak
> >>
> >> On Thu, Jan 11, 2018 at 6:15 AM, Jayme  >> > wrote:
> >> > I performed Ovirt 4.2 upgrade on a 3 host cluster with NFS shared
> >> > storage.
> >> > The shared storage is mounted from one of the hosts.
> >> >
> >> > I upgraded the hosted engine first, downloading the 4.2 rpm, doing a yum
> >> > update then engine setup which seemed to complete successfully, at the
> >> > end
> >> > it powered down the hosted VM but it never came back up.  I was unable
> >> > to
> >> > start it.
> >> >
> >> > I proceeded to upgrade the three hosts, ovirt 4.2 rpm and a full yum
> >> > update.
> >> > I also rebooted each of the three hosts.
> >> >
> >> > After some time the hosts did come back and almost all of the VMs are
> >> > running again and seem to be working ok with the exception of two:
> >> >
> >> > 1. The hosted VM still will not start, I've tried everything I can think
> >> > of.
> >> >
> >> > 2. A VM that I know existed is not running and does not appear to exist,
> >> > I
> >> > have no idea where it is or how to start it.
> >> >
> >> > 1. Hosted engine
> >> >
> >> > From one of the hosts I get a weird error trying to start it:
> >> >
> >> > # hosted-engine --vm-start
> >> > Command VM.getStats with args {'vmID':
> >> > '4013c829-c9d7-4b72-90d5-6fe58137504c'} failed:
> >> > (code=1, message=Virtual machine does not exist: {'vmId':
> >> > u'4013c829-c9d7-4b72-90d5-6fe58137504c'})
> >> >
> >> > From the two other hosts I do not get the same error as above, sometimes
> >> > it
> >> > appears to start but --vm-status shows errors such as:  Engine status
> >> > : {"reason": "failed liveliness check", "health": "bad", "vm": "up",
> >> > "detail": "Up"}
> >> >
> >> > Seeing these errors in syslog:
> >> >
> >> > Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+: 

Re: [ovirt-users] Some major problems after 4.2 upgrade, could really use some assistance

[Jayme]

This is becoming critical for me, does anyone have any ideas or
recommendations on what I can do to recover access to hosted VM?  As of
right now I have three hosts that are fully updated, they have the 4.2 repo
and a full yum update was performed on them, there are no new updates to
apply.  The hosted engine had updates as well as a full and complete
engine-setup, but did not return after being shut down.  There must be some
way I can get the engine running again?  Please

On Thu, Jan 11, 2018 at 8:24 AM, Jayme  wrote:

> The hosts have all ready been fully updated with 4.2 packages though.
>
> ex.
>
> ovirt-host.x86_64
> 4.2.0-1.el7.centos   @ovirt-4.2
> ovirt-host-dependencies.x86_64
>  4.2.0-1.el7.centos   @ovirt-4.2
> ovirt-host-deploy.noarch
>  1.7.0-1.el7.centos   @ovirt-4.2
> ovirt-hosted-engine-ha.noarch
> 2.2.2-1.el7.centos   @ovirt-4.2
> ovirt-hosted-engine-setup.noarch
>  2.2.3-1.el7.centos   @ovirt-4.2
>
> On Thu, Jan 11, 2018 at 8:16 AM, Martin Sivak  wrote:
>
>> Hi,
>>
>> yes, you need to upgrade the hosts. Just take the
>> ovirt-hosted-engine-ha and ovirt-hosted-engine-setup packages from
>> ovirt 4.2 repositories.
>>
>> Martin
>>
>> On Thu, Jan 11, 2018 at 11:40 AM, Jayme  wrote:
>> > How do I upgrade the hosted engine packages when I can't reach it or do
>> you
>> > mean upgrade the hosts if so how exactly do I do that. As for the
>> missing VM
>> > it appears that the disk image is there but it's missing XML file I
>> have no
>> > idea why or how to recreate it.
>> >
>> > On Jan 11, 2018 4:43 AM, "Martin Sivak"  wrote:
>> >>
>> >> Hi,
>> >>
>> >> you hit one known issue we already have fixes for (4.1 hosts with 4.2
>> >> engine):
>> >> https://gerrit.ovirt.org/#/q/status:open+project:ovirt-hoste
>> d-engine-ha+branch:v2.1.z+topic:ovf_42_for_41
>> >>
>> >> You can try hotfixing it by upgrading hosted engine packages to 4.2 or
>> >> applying the patches manually and installing python-lxml.
>> >>
>> >> I am not sure what happened to your other VM.
>> >>
>> >> Best regards
>> >>
>> >> Martin Sivak
>> >>
>> >> On Thu, Jan 11, 2018 at 6:15 AM, Jayme  wrote:
>> >> > I performed Ovirt 4.2 upgrade on a 3 host cluster with NFS shared
>> >> > storage.
>> >> > The shared storage is mounted from one of the hosts.
>> >> >
>> >> > I upgraded the hosted engine first, downloading the 4.2 rpm, doing a
>> yum
>> >> > update then engine setup which seemed to complete successfully, at
>> the
>> >> > end
>> >> > it powered down the hosted VM but it never came back up.  I was
>> unable
>> >> > to
>> >> > start it.
>> >> >
>> >> > I proceeded to upgrade the three hosts, ovirt 4.2 rpm and a full yum
>> >> > update.
>> >> > I also rebooted each of the three hosts.
>> >> >
>> >> > After some time the hosts did come back and almost all of the VMs are
>> >> > running again and seem to be working ok with the exception of two:
>> >> >
>> >> > 1. The hosted VM still will not start, I've tried everything I can
>> think
>> >> > of.
>> >> >
>> >> > 2. A VM that I know existed is not running and does not appear to
>> exist,
>> >> > I
>> >> > have no idea where it is or how to start it.
>> >> >
>> >> > 1. Hosted engine
>> >> >
>> >> > From one of the hosts I get a weird error trying to start it:
>> >> >
>> >> > # hosted-engine --vm-start
>> >> > Command VM.getStats with args {'vmID':
>> >> > '4013c829-c9d7-4b72-90d5-6fe58137504c'} failed:
>> >> > (code=1, message=Virtual machine does not exist: {'vmId':
>> >> > u'4013c829-c9d7-4b72-90d5-6fe58137504c'})
>> >> >
>> >> > From the two other hosts I do not get the same error as above,
>> sometimes
>> >> > it
>> >> > appears to start but --vm-status shows errors such as:  Engine status
>> >> > : {"reason": "failed liveliness check", "health": "bad", "vm": "up",
>> >> > "detail": "Up"}
>> >> >
>> >> > Seeing these errors in syslog:
>> >> >
>> >> > Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+: 1910:
>> >> > error :
>> >> > qemuOpenFileAs:3183 : Failed to open file
>> >> >
>> >> > '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/
>> c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-
>> 4967-a1e5-fbe47c0cd705':
>> >> > No such file or directory
>> >> >
>> >> > Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+: 1910:
>> >> > error :
>> >> > qemuDomainStorageOpenStat:11492 : cannot stat file
>> >> >
>> >> > '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/
>> c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-
>> 4967-a1e5-fbe47c0cd705':
>> >> > Bad file descriptor
>> >> >
>> >> > 2. Missing VM.  virsh -r list on each host does not show the VM at
>> all.
>> >> > I
>> >> > know it existed and is important.  The log on one of the hosts even
>> >> > shows
>> >> > that it started it recently then stopped in 10 

Re: [ovirt-users] wheel next to the up triangle in the UI

[Luca 'remix_tj' Lorenzetto]

I suppose is because they're started with  "run once".

Happens the same also when you deploy with ansible using cloud-init. I
think with vagrant is the same.

Luca

Il 11 gen 2018 7:24 PM, "Nathanaël Blanchet"  ha scritto:

> Hi all,
>
> I'm using vagrant ovirt4 plugin to provision some vms, and I noticed that
> a wheel is still present next to the up status of those vms. What does that
> mean?
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 
> 34193 MONTPELLIER CEDEX 5
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14
> blanc...@abes.fr
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] wheel next to the up triangle in the UI

[Nathanaël Blanchet]

Hi all,

I'm using vagrant ovirt4 plugin to provision some vms, and I noticed 
that a wheel is still present next to the up status of those vms. What 
does that mean?


--
Nathanaël Blanchet

Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Troubleshooting a self-hosted engine deployment

[Denis Chaplygin]

Hello!

On Thu, Jan 11, 2018 at 1:03 PM, Николаев Алексей <
alexeynikolaev.p...@yandex.ru> wrote:

> Denis, thx for your answer.
>
> [root@node-gluster203 ~]# gluster volume heal engine info
> Brick node-gluster205:/opt/gluster/engine
> Status: Connected
> Number of entries: 0
>
> Brick node-gluster203:/opt/gluster/engine
> Status: Connected
> Number of entries: 0
>
> Brick node-gluster201:/opt/gluster/engine
> Status: Connected
> Number of entries: 0
>
> *Gluster volume looks like OK. Adding aditional info about volume options.
> *
>
>
>

Right, gluster volume seems to be fine. May be you have a connections
issue? Could you please try to execute 'hosted-engine --connect-storage'?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Are Ovirt updates nessessary after CVE-2017-5754 CVE-2017-5753 CVE-2017-5715

[Yaniv Kaul]

On Thu, Jan 11, 2018 at 5:32 PM, Derek Atkins  wrote:

> Hi,
>
> On Thu, January 11, 2018 9:53 am, Yaniv Kaul wrote:
>
> > No one likes downtime but I suspect this is one of those serious
> > vulnerabilities that you really really must be protected against.
> > That being said, before planning downtime, check your HW vendor for
> > firmware or Intel for microcode for the host first.
> > Without it, there's not a lot of protection anyway.
> > Note that there are 4 steps you need to take to be fully protected: CPU,
> > hypervisor, guests and guest CPU type - plan ahead!
> > Y.
>
> Is there a HOW-To written up somewhere on this?  ;)
>

Not for oVirt specifically right now. We'll blog about it once we release
additional improvements to detect if you are protected - right from oVirt
UI (in 4.2.1).


>
> I built the hardware from scratch myself, so I can't go off to Dell or
> someone for this.  So which do I need, motherboard firmware or Intel
> microcode?  I suppose I need to go to the motherboard manufacturer
> (Supermicro) to look for updated firmware?  Do I also need to look at
> Intel?  Is this either-or or a "both" situation?  Of course I have no idea
> how to reflash new firmware onto this motherboard -- I don't have DOS.
>

You could get it from Intel, via their microcode_ctl package. When they
release for your CPU is a different manner.
See[1] for some good pointers.
Y.

[1]
https://wiki.gentoo.org/wiki/Project:Security/Vulnerabilities/Meltdown_and_Spectre


>
> As you can see, planning I can do.  Execution is more challenging ;)
>
> Thanks!
>
> >> > Y.
>
> -derek
>
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Are Ovirt updates nessessary after CVE-2017-5754 CVE-2017-5753 CVE-2017-5715

[Arman Khalatyan]

if you have recent supermicro you dont need to update the bios,
Some tests:
Crack test:
https://github.com/IAIK/meltdown

Check test:
https://github.com/speed47/spectre-meltdown-checker

the intel microcodes  you can find here:
https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File?product=41447
good luck.
Arman.



On Thu, Jan 11, 2018 at 4:32 PM, Derek Atkins  wrote:
> Hi,
>
> On Thu, January 11, 2018 9:53 am, Yaniv Kaul wrote:
>
>> No one likes downtime but I suspect this is one of those serious
>> vulnerabilities that you really really must be protected against.
>> That being said, before planning downtime, check your HW vendor for
>> firmware or Intel for microcode for the host first.
>> Without it, there's not a lot of protection anyway.
>> Note that there are 4 steps you need to take to be fully protected: CPU,
>> hypervisor, guests and guest CPU type - plan ahead!
>> Y.
>
> Is there a HOW-To written up somewhere on this?  ;)
>
> I built the hardware from scratch myself, so I can't go off to Dell or
> someone for this.  So which do I need, motherboard firmware or Intel
> microcode?  I suppose I need to go to the motherboard manufacturer
> (Supermicro) to look for updated firmware?  Do I also need to look at
> Intel?  Is this either-or or a "both" situation?  Of course I have no idea
> how to reflash new firmware onto this motherboard -- I don't have DOS.
>
> As you can see, planning I can do.  Execution is more challenging ;)
>
> Thanks!
>
>>> > Y.
>
> -derek
>
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Are Ovirt updates nessessary after CVE-2017-5754 CVE-2017-5753 CVE-2017-5715

[Derek Atkins]

Hi,

On Thu, January 11, 2018 9:53 am, Yaniv Kaul wrote:

> No one likes downtime but I suspect this is one of those serious
> vulnerabilities that you really really must be protected against.
> That being said, before planning downtime, check your HW vendor for
> firmware or Intel for microcode for the host first.
> Without it, there's not a lot of protection anyway.
> Note that there are 4 steps you need to take to be fully protected: CPU,
> hypervisor, guests and guest CPU type - plan ahead!
> Y.

Is there a HOW-To written up somewhere on this?  ;)

I built the hardware from scratch myself, so I can't go off to Dell or
someone for this.  So which do I need, motherboard firmware or Intel
microcode?  I suppose I need to go to the motherboard manufacturer
(Supermicro) to look for updated firmware?  Do I also need to look at
Intel?  Is this either-or or a "both" situation?  Of course I have no idea
how to reflash new firmware onto this motherboard -- I don't have DOS.

As you can see, planning I can do.  Execution is more challenging ;)

Thanks!

>> > Y.

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Are Ovirt updates nessessary after CVE-2017-5754 CVE-2017-5753 CVE-2017-5715

[Yaniv Kaul]

On Thu, Jan 11, 2018 at 4:33 PM, Derek Atkins  wrote:

> Yaniv Kaul  writes:
>
> > On Mon, Jan 8, 2018 at 7:32 PM, Derek Atkins  wrote:
> >
> > Michal Skrivanek  writes:
> >
> > > > If there are Patches nessessary will there also be
> updates
> > for
> > > ovirt 4.1 or
> > > > only 4.2?
> > >
> > > 4.1 will be covered
> >
> > What about 4.0?  Or will that not be covered because it depends on
> 7.3,
> > which also isn't covered??
> >
> > It will not be covered because we have 4.1 and 4.2 out, both of which we
> take
> > care of.
>
> I was afraid of that.  So I will need to upgrade to at least 7.4/4.1 to
> get this fixed.   I'll need to find some time to do that.  :(
>
> My users don't like having downtime..  and this is a single-host system.
>

No one likes downtime but I suspect this is one of those serious
vulnerabilities that you really really must be protected against.
That being said, before planning downtime, check your HW vendor for
firmware or Intel for microcode for the host first.
Without it, there's not a lot of protection anyway.
Note that there are 4 steps you need to take to be fully protected: CPU,
hypervisor, guests and guest CPU type - plan ahead!
Y.


> > Y.
>
> -derek
>
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Are Ovirt updates nessessary after CVE-2017-5754 CVE-2017-5753 CVE-2017-5715

[Derek Atkins]

Yaniv Kaul  writes:

> On Mon, Jan 8, 2018 at 7:32 PM, Derek Atkins  wrote:
>
> Michal Skrivanek  writes:
>
> >             > If there are Patches nessessary will there also be updates
> for
> >             ovirt 4.1 or
> >             > only 4.2?
> >
> > 4.1 will be covered
>
> What about 4.0?  Or will that not be covered because it depends on 7.3,
> which also isn't covered??
>
> It will not be covered because we have 4.1 and 4.2 out, both of which we take
> care of.

I was afraid of that.  So I will need to upgrade to at least 7.4/4.1 to
get this fixed.   I'll need to find some time to do that.  :(

My users don't like having downtime..  and this is a single-host system.

> Y.

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] snapshotting

[Erekle Magradze]

Hello,
Could you please share your experience with snapshotting the VMs in 
oVirt 4.1 with GlusterFS as a storage?

Thanks in advance
Erekle
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Persistence on oVirt-Nodes

[FERNANDO FREDIANI]

Quick questions about Nodes (in order to not hijack the other thread).

As they don't have much notion of persistence how can I:

- To have a simple configuration backup in order for, if the Operating 
System disk fails I reinstall the Node, restore the config and 
everything comes back up fine ? Backing up /var /etc and /root folders 
would be enough or anything else ?


- If I install something custom (e.g: A Zabbix Agent) it works until the 
host receives a new system/image Upgrade. Is there any way that can be 
made persistent ?


- As oVirt-Nodes are images, if I install them in a SD Card or USB Stick 
will be there much write to disk still ? Other than possibly the logs 
and configuration changes what else could be written to disk ?


If so a Feature Request to solve this would be to mount the logs 
partition in RAM as the Node boots and logrotate that. If someone needs 
to keep it more time can always use rsyslog


Thanks
Fernando

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Non-RHEL RPMs gone after RHV-H upgrade

[Ryan Barry]

Hey Colin -

You're correct -- they will persist. However, there's only a plugin for
yum, and not bare RPM. If the packages were installed with "rpm -Uvh ...",
they won't be 'sticky'. I believe this is also part of the documentation.

If you don't remember whether you used yum or not, you can check
/var/imgbased/persisted-rpms/ to see if anything is present.

On Tue, Jan 9, 2018 at 7:24 PM, Colin Coe  wrote:

> Hi all
>
> We're running RHV 4.1.6.  Yesterday I upgraded the RHV-H nodes in our DEV
> environment to 20180102 and found that all the non-RHEL RPMs are now gone.
> Their associated config files in /etc are still there.  The RPMs in
> question were from HPE SPP plus a monitoring system client (Xymon).
>
> I had thought that non-RHEL RPMs would persist after a host upgrade.
>
> Am I wrong on this?
>
> Thanks
>
> CC
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA 

rba...@redhat.comM: +1-651-815-9306 IM: rbarry

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Node 4.1 question, writing files to /root and RPMs

[Ryan Barry]

Next-gen node (since 4.0) doesn't have any strong notion of "persistence",
unlike previous versions of oVirt Node.

My guess would be that /exports was not moved across to the new system.

The update process for Node is essentially:

* create a new lv
* unpack the squashfs in the new RPM and put it on the LV
* Go through /var, /etc, and /root to see if any files were modified/added,
and copy those to the new layer
* Add a new bootloader entry
* Re-install any persistent RPMs

I would guess that /exports as not on its own partition, so it didn't carry
across. Mounting the LV for the old image somewhere (/tmp/...) will make
them visible again,


On Tue, Dec 19, 2017 at 9:26 AM, Kasturi Narra  wrote:

> Hello Matt,
>
>All the partitions will be persisted when gluster is installed on
> the ovirt node since gluster recommends user not to create bricks in root
> directory. If the gluster bricks are created in root partition then once
> the update of the node is done, you will not be able to see any of the
> bricks.
>
> Hope this helps !!!
>
> Thanks
> kasturi.
>
> On Tue, Dec 19, 2017 at 4:28 AM, Matt Simonsen  wrote:
>
>> On 12/15/2017 03:06 AM, Simone Tiraboschi wrote:
>>
>> On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis 
>> wrote:
>>
>>> have you gotten an image update yet?
>>>
>>> On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  wrote:
>>>
 Hello all,

 I read at https://www.ovirt.org/develop/projects/node/troubleshooting/
 that "Changes made from the command line are done at your own risk. Making
 changes has the potential to leave your system in an unusable state." It
 seems clear that RPMs should not be installed.

>>>
>> That document mainly refers to vintage node.
>> In Next Generation Node now we have rpm persistence; please check
>> https://www.ovirt.org/develop/release-management/features/no
>> de/node-next-persistence/
>>
>>
>>
>>
>> I'm sure glad we tested!
>>
>> On one Node image we had images locally stored in /exports and shared out
>> via NFS. After an upgrade & reboot, images are gone.
>>
>> If we "Convert to local storage" will the data persist?  I am planning to
>> test, but want to be sure how this is designed.
>>
>> I assume during a Gluster installation something is also updated in oVirt
>> Node to allow for the Gluster partition to persist?
>>
>> At this point I'm thinking I should manually install via CentOS7 to
>> ensure folders and partitions are persistent. Is there any downside to
>> installing over CentOS7?
>>
>> Thanks
>> Matt
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA 

rba...@redhat.comM: +1-651-815-9306 IM: rbarry

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt NGN image customization troubles

[Ryan Barry]

I haven't tried to build on EL for a long time, but the easiest way to
modify may simply be to unpack the squashfs, chroot inside of it, and
repack it. Have you tried this?

On Wed, Dec 27, 2017 at 11:33 AM, Giuseppe Ragusa <
giuseppe.rag...@hotmail.com> wrote:

> Hi all,
>
> I'm trying to modify the oVirt NGN image (to add RPMs, since imgbased
> rpmpersistence currently seems to have a bug: https://bugzilla.redhat.com/
> show_bug.cgi?id=1528468 ) but I'm unfortunately stuck at the very
> beginning: it seems that I'm unable to recreate even the standard 4.1
> squashfs image.
>
> I'm following the instructions at https://gerrit.ovirt.org/
> gitweb?p=ovirt-node-ng.git;a=blob;f=README
>
> I'm working inside a CentOS7 fully-updated vm (hosted inside VMware, with
> nested virtualization enabled).
>
> I'm trying to work on the 4.1 branch, so I issued a:
>
> ./autogen.sh --with-ovirt-release-rpm-url=http://resources.ovirt.org/pub/
> yum-repo/ovirt-release41.rpm
>
> And after that I'm stuck in the "make squashfs" step: it never ends (keeps
> printing dots forever with no errors/warnings in log messages nor any
> apparent activity on the virtual disk image).
>
> Invoking it in debug mode and connecting to the VNC console shows the
> detailed Plymouth startup listing stuck (latest messages displayed:
> "Starting udev Wait for Complete Device Initialization..." and "Starting
> Device-Mapper Multipath Device Controller...")
>
> I wonder if it's actually supposed to be run only from a recent Fedora
> (the "dnf" reference seems a good indicator): if so, which version?
>
> I kindly ask for advice: has anyone succeeded in modifying/reproducing NGN
> squash images recently? If so, how? :-)
>
> Many thanks in advance,
>
> Giuseppe
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA 

rba...@redhat.comM: +1-651-815-9306 IM: rbarry

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

[Ryan Barry]

Note that, in the case of Node, the ovirt-release RPM should not be
installed. Mostly because it automatically enables a number of per-package
updates (such as vdsm) instead of installing a single image.

Trimming the repo files so they look like what is shipped in Node
(IgnorePkgs and OnlyPkgs) will pull ovirt-node-ng-image-update.rpm, which
is the only package needing an update.

On Fri, Dec 29, 2017 at 4:45 AM, Ed Stout  wrote:

> On 29 December 2017 at 09:11, Michal Skrivanek
>  wrote:
> >
> >
> >> On 29 Dec 2017, at 10:03, Ed Stout  wrote:
> >>
> >> On 29 December 2017 at 08:42, Michal Skrivanek
> >>  wrote:
> >>>
> >>>
>  On 29 Dec 2017, at 09:34, Ed Stout  wrote:
> 
>  Good Morning,
> 
>  Perhaps someone could clarify for me, please - to update oVirt Nodes
>  from 4.1.8 -> 4.2, should I just be able to yum install the 4.2
>  release file, then yum update?
> >>>
> >>> Hi,
> >>> yes, that should be the right one
> >>>
>  Or, do I have to start with the 4.2
>  ISO then update from there?
> 
>  When I try the former it fails with dependency issues for the nodes, I
>  did however manage to update a self hosted appliance engine to 4.2.  I
>  had a read through the mailing list archive and couldn't find similar
>  issues, so perhaps I'm doing something wrong.
> 
>  --> Processing Dependency: lshw for package:
> vdsm-4.20.9.3-1.el7.centos.x86_64
>  --> Finished Dependency Resolution
>  Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch
> (ovirt-4.2)
>   Requires: libvirt-daemon-config-network
>  Error: Package: ovirt-hosted-engine-setup-2.2.3-1.el7.centos.noarch
> (ovirt-4.2)
>   Requires: virt-install
>  Error: Package: glusterfs-geo-replication-3.12.3-1.el7.x86_64
>  (ovirt-4.2-centos-gluster312)
>   Requires: python-prettytable
>  Error: Package: vdsm-4.20.9.3-1.el7.centos.x86_64 (ovirt-4.2)
>   Requires: lshw
>  Error: Package: glusterfs-events-3.12.3-1.el7.x86_64
>  (ovirt-4.2-centos-gluster312)
>   Requires: python-prettytable
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles —nodigest
> >>>
> >>> can you list all your enabled repos? Seems you're missing the base
> CentOS
> >>>
> >>> Thanks,
> >>> michal
> >>
> >> Sure, thanks for the reply - I have 3 nodes, installed from the 4.1.x
> >> oVirt node ISOs, no custom packages/repos, that see the same (minus
> >> the 4.2 added here).
> >>
> >> [root@onode3 ~]# yum repolist enabled
> >> Loaded plugins: fastestmirror, imgbased-persist
> >> Loading mirror speeds from cached hostfile
> >> * ovirt-4.1-epel: mirrors.ukfast.co.uk
> >> * ovirt-4.2: ftp.snt.utwente.nl
> >> * ovirt-4.2-epel: mirrors.ukfast.co.uk
> >> repo id
> >> repo name
> >>
> >>   status
> >> centos-opstools-release/x86_64
> >> CentOS-7 - OpsTools - release
> >>
> >>  421
> >> centos-sclo-rh-release/x86_64
> >> CentOS-7 - SCLo rh
> >>
> >>6,534
> >> ovirt-4.1/7
> >> Latest oVirt 4.1 Release
> >>
> >>2,101
> >> ovirt-4.1-centos-gluster38/x86_64
> >> CentOS-7 - Gluster 3.8
> >>
> >>   31
> >> ovirt-4.1-epel/x86_64
> >> Extra Packages for Enterprise Linux 7
> >> - x86_64
> >>   12,184
> >> ovirt-4.1-patternfly1-noarch-epel/x86_64
> >> Copr repo for patternfly1 owned by
> >> patternfly
> >>   2
> >> ovirt-4.2/7
> >> Latest oVirt 4.2 Release
> >>
> >>  179
> >> ovirt-4.2-centos-gluster312/x86_64
> >> CentOS-7 - Gluster 3.12
> >>
> >>   93
> >> ovirt-4.2-centos-opstools/x86_64
> >> CentOS-7 - OpsTools - release
> >>
> >>  421
> >> ovirt-4.2-centos-ovirt42/x86_64
> >> CentOS-7 - oVirt 4.2
> >>
> >>  201
> >> ovirt-4.2-centos-qemu-ev/x86_64
> >> CentOS-7 - QEMU EV
> >>
> >>   39
> >> ovirt-4.2-epel/x86_64
> >> Extra Packages for Enterprise Linux 7
> >> - x86_64
> >>   12,184
> >> ovirt-4.2-virtio-win-latest
> >> virtio-win builds roughly matching
> >> what will be shipped in upcoming RHEL
> >>  35
> >> ovirt-centos-ovirt41/x86_64
> >> 

Re: [ovirt-users] Ovirt 4.2 Bug with Permissons on the Vm Portal?

[Latchezar Filtchev]

Hi Guys,

The same here. Upgrade 4.1.8 to 4.2. oVirt connected to Active Directory. User 
cannot see machines in VM portal. Still playing with permissions.
Any ideas?

Thank you!
Best,
Latcho




From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of 
Thomas Fecke
Sent: Monday, January 08, 2018 3:17 PM
To: users@ovirt.org
Subject: [ovirt-users] Ovirt 4.2 Bug with Permissons on the Vm Portal?

Hello Guys,

i recently upgrade to 4.2

We used the User Portal before. Every User could see his VM´s, every Admin just 
could see his VM´s ( User View ).

After the Update:

Admin´s can see every VM in VM Portal

The Users can´t see Vm´s anymore. The Portal is Empty. Role "UserVMManager" is 
set.

We tested some Scenarios: If the User create a new Virtual Machine, it is shown 
in the VM Portal. When he log out and in again -> VM is gone in his View

Admin View: The VM was created, Permission where set. Everything seems to be 
good.

Any Ideas? Thanks Guys
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Troubleshooting a self-hosted engine deployment

[Николаев Алексей]

Denis, thx for your answer. [root@node-gluster203 ~]# gluster volume heal engine infoBrick node-gluster205:/opt/gluster/engineStatus: ConnectedNumber of entries: 0 Brick node-gluster203:/opt/gluster/engineStatus: ConnectedNumber of entries: 0 Brick node-gluster201:/opt/gluster/engineStatus: ConnectedNumber of entries: 0 Gluster volume looks like OK. Adding aditional info about volume options.  [root@node-gluster203 ~]# gluster volume info engine Volume Name: engineType: ReplicateVolume ID: aece5318-4126-41f9-977c-9b39300bd0c8Status: StartedSnapshot Count: 0Number of Bricks: 1 x (2 + 1) = 3Transport-type: tcpBricks:Brick1: node-gluster205:/opt/gluster/engineBrick2: node-gluster203:/opt/gluster/engineBrick3: node-gluster201:/opt/gluster/engine (arbiter)Options Reconfigured:auth.allow: *network.ping-timeout: 10server.allow-insecure: onnfs.disable: ontransport.address-family: inetstorage.owner-uid: 36storage.owner-gid: 36performance.quick-read: offperformance.read-ahead: offperformance.io-cache: offperformance.stat-prefetch: offperformance.low-prio-threads: 32network.remote-dio: enablecluster.eager-lock: enablecluster.quorum-type: autocluster.server-quorum-type: servercluster.data-self-heal-algorithm: fullcluster.locking-scheme: granularcluster.shd-max-threads: 8cluster.shd-wait-qlength: 1features.shard: onuser.cifs: offgeo-replication.indexing: ongeo-replication.ignore-pid-check: onchangelog.changelog: oncluster.enable-shared-storage: enable 11.01.2018, 12:34, "Denis Chaplygin" :Hello! On Thu, Jan 11, 2018 at 9:56 AM, Николаев Алексей  wrote: We have a self-hosted engine test infra with gluster storage replica 3 arbiter 1 (oVirt 4.1).  Why would not you try 4.2? :-) There is a lot of good changes in that area.  RuntimeError: Volume does not exist: (u'13b5a4d0-dd26-491c-b5c0-5628b56bc3a5',)  I assume you may have an issue with your gluster volume. Could you please share output of the command 'gluster volume heal engine info'? Thanks in advance.___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Shutdown all VM's command line

[Giorgio Biacchi]

On 01/11/2018 11:44 AM, Kapetanakis Giannis wrote:

On 10/01/18 22:11, Wesley Stewart wrote:

Marcelo,

I would greatly appreciate seeing a script!  It would be an excellent chance 
for me to learn a bit about using ovirt from the command line as well!


I'm using something like this with ovirt-shell

vm_shutdown:
#!/bin/sh
LOG=/root/ovirt/vm_shutdown_log
echo `date` >> $LOG
/usr/bin/ovirt-shell -f /root/ovirt/vm_shutdown_script >> $LOG
echo "" >> $LOG

vm_shutdown_script:
list vms --kwargs status-state=up|grep name | sed s/'name   :'/'action vm'/ | 
sed -e 's/$/ shutdown/' > /root/ovirt/new_vm_shutdown_script
file /root/ovirt/new_vm_shutdown_script

new_vm_shutdown_script now lists entries like this:
action vm vm1 shutdown
action vm vm2 shutdown
etc.

G


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



You can use python SDK.

Somthing like this should work

#!/usr/bin/env python

import ovirtsdk4 as sdk

ovaddress = ""
username="admin@internal"
password="*"

connection = sdk.Connection(
  url=ovaddress,
  username=username,
  password=password,
  ca_file='ca.crt',
  insecure=True
)

system_service = connection.system_service()
vms_service = system_service.vms_service()
vms = vms_service.list()

for vm in vms:
vm_service = vms_service.vm_service(vm.id)
vm_service.shutdown()

connection.close()

--
gb

PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Shutdown all VM's command line

[Kapetanakis Giannis]

On 10/01/18 22:11, Wesley Stewart wrote:
> Marcelo,
> 
> I would greatly appreciate seeing a script!  It would be an excellent chance 
> for me to learn a bit about using ovirt from the command line as well!

I'm using something like this with ovirt-shell

vm_shutdown:
#!/bin/sh
LOG=/root/ovirt/vm_shutdown_log
echo `date` >> $LOG
/usr/bin/ovirt-shell -f /root/ovirt/vm_shutdown_script >> $LOG
echo "" >> $LOG

vm_shutdown_script:
list vms --kwargs status-state=up|grep name | sed s/'name   :'/'action vm'/ 
| sed -e 's/$/ shutdown/' > /root/ovirt/new_vm_shutdown_script
file /root/ovirt/new_vm_shutdown_script

new_vm_shutdown_script now lists entries like this:
action vm vm1 shutdown
action vm vm2 shutdown
etc.

G


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] [ANN] oVirt 4.1.9 First Release Candidate is now available

[Lev Veyde]

The oVirt Project is pleased to announce the availability of the oVirt
4.1.9 First
Release Candidate, as of January 11th, 2017

This update is the nineth in a series of stabilization updates to the 4.1
series.

This release is available now for:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.4 or later
* CentOS Linux (or similar) 7.4 or later
* oVirt Node 4.1

See the release notes [1] for installation / upgrade instructions and
a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Live is already available [2]
- oVirt Node will be available soon [2]

Additional Resources:
* Read more about the oVirt 4.1.9 release highlights:
http://www.ovirt.org/release/4.1. 9
/ 
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.1. 9
/ 
[2] http://resources.ovirt.org/pub/ovirt-4.1/iso/

-- 

Lev Veyde

Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Troubleshooting a self-hosted engine deployment

[Denis Chaplygin]

Hello!

On Thu, Jan 11, 2018 at 9:56 AM, Николаев Алексей <
alexeynikolaev.p...@yandex.ru> wrote:

>
> We have a self-hosted engine test infra with gluster storage replica 3
> arbiter 1 (oVirt 4.1).
>

Why would not you try 4.2? :-) There is a lot of good changes in that area.


>
> RuntimeError: Volume does not exist: (u'13b5a4d0-dd26-491c-b5c0-
> 5628b56bc3a5',)
>
>

I assume you may have an issue with your gluster volume. Could you please
share output of the command 'gluster volume heal engine info'?

Thanks in advance.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Troubleshooting a self-hosted engine deployment

[Николаев Алексей]

Hi community! We have a self-hosted engine test infra with gluster storage replica 3 arbiter 1 (oVirt 4.1). Shared storage for engine VM has a dns name "gluster-facility:/engine".DNS "gluster-facility" resolf's into 3 A records:"node-gluster205 10.77.253.205""node-gluster203 10.77.253.203""node-gluster201 10.77.253.201" (arbiter) Self-hosted engine fresh install was succesfull with path gluster-facility:/engine.But ovirt-ha-broker and ovirt-ha-agent services cant work normally. They can't manage manager VM.After manager VM down it can not be started. [root@node-gluster204 ~]# hosted-engine --vm-status --== Host 1 status ==-- conf_on_shared_storage             : TrueStatus up-to-date                  : FalseHostname                           : node-msk-gluster202.ipt.fsin.uisHost ID                            : 1Engine status                      : unknown stale-dataScore                              : 0stopped                            : TrueLocal maintenance                  : Falsecrc32                              : 3ac98fe3local_conf_timestamp               : 342471Host timestamp                     : 342470Extra metadata (valid at timestamp):        metadata_parse_version=1        metadata_feature_version=1        timestamp=342470 (Mon Dec  4 15:03:57 2017)        host-id=1        score=0        vm_conf_refresh_time=342471 (Mon Dec  4 15:03:57 2017)        conf_on_shared_storage=True        maintenance=False        state=AgentStopped        stopped=True broker.log says Thread-712::INFO::2018-01-11 11:29:30,629::listener::134::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(setup) Connection establishedThread-712::INFO::2018-01-11 11:29:30,630::listener::186::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle) Connection closedThread-700::INFO::2018-01-11 11:29:30,634::mem_free::50::mem_free.MemFree::(action) memFree: 30999Thread-697::ERROR::2018-01-11 11:29:33,270::listener::192::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle) Error handling request, data: 'set-storage-domain VdsmBackend hosted-engine.lockspace=7B22696D6167655F75756964223A202239323836376633652D373366312D346264382D393536332D35393661656566356461663C202270617468223A206E756C6C2C2022766F6C756D655F75756964223A202231336235613464302D646432362D343931632D623563302D353632386235366263336135227D sp_uuid=---- dom_type=glusterfs hosted-engine.metadata=7B22696D6167655F75756964223A202233643034323833362D663935332D346662372D626634322D35643534663262333835222C202270617468223A206E756C6C2C2022766F6C756D655F75756964223A202231313134633364642D303236342D343035392D393664312D623635633034623533396165227D sd_uuid=03da57d7-c5a2-4998-916a-f4f71baa4831'Traceback (most recent call last):  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", line 166, in handle    data)  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py", line 299, in _dispatch    .set_storage_domain(client, sd_type, **options)  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 66, in set_storage_domain    self._backends[client].connect()  File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 409, in connect    raise RuntimeError(response.message)RuntimeError: Volume does not exist: (u'13b5a4d0-dd26-491c-b5c0-5628b56bc3a5',) vdsm.log says a4d0-dd26-491c-b5c0-5628b56bc3a5', allowIllegal=False) from=::1,44266, task_id=fab6382f-8337-45e4-8eb8-1dbf79fe8c1d (api:46)2018-01-11 11:31:53,050+0300 INFO  (jsonrpc/6) [vdsm.api] START repoStats(options=None) from=::1,44262, task_id=68a37242-a84d-4372-804e-57e416d4c3de (api:46)2018-01-11 11:31:53,050+0300 INFO  (jsonrpc/6) [vdsm.api] FINISH repoStats return={} from=::1,44262, task_id=68a37242-a84d-4372-804e-57e416d4c3de (api:52)2018-01-11 11:31:53,065+0300 INFO  (jsonrpc/4) [vdsm.api] FINISH prepareImage error=Volume does not exist: (u'13b5a4d0-dd26-491c-b5c0-5628b56bc3a5',) from=::1,44266, task_id=fab6382f-8337-45e4-8eb8-1dbf79fe8c1d (api:50)2018-01-11 11:31:53,066+0300 ERROR (jsonrpc/4) [storage.TaskManager.Task] (Task='fab6382f-8337-45e4-8eb8-1dbf79fe8c1d') Unexpected error (task:872)Traceback (most recent call last):  File "/usr/share/vdsm/storage/task.py", line 879, in _run    return fn(*args, **kargs)  File "", line 2, in prepareImage  File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method    ret = func(*args, **kwargs)  File "/usr/share/vdsm/storage/hsm.py", line 3135, in prepareImage    raise se.VolumeDoesNotExist(leafUUID)VolumeDoesNotExist: Volume does not exist: (u'13b5a4d0-dd26-491c-b5c0-5628b56bc3a5',)2018-01-11 11:31:53,066+0300 INFO  (jsonrpc/4) [storage.TaskManager.Task] (Task='fab6382f-8337-45e4-8eb8-1dbf79fe8c1d') aborting: Task is aborted: "Volume does not exist: (u'13b5a4d0-dd26-491c-b5c0-5628b56bc3a5',)" - code 201 (task:1177)2018-01-11 11:31:53,066+0300 ERROR (jsonrpc/4) [storage.Dispatcher] 

Re: [ovirt-users] Some major problems after 4.2 upgrade, could really use some assistance

[Martin Sivak]

Hi,

you hit one known issue we already have fixes for (4.1 hosts with 4.2
engine): 
https://gerrit.ovirt.org/#/q/status:open+project:ovirt-hosted-engine-ha+branch:v2.1.z+topic:ovf_42_for_41

You can try hotfixing it by upgrading hosted engine packages to 4.2 or
applying the patches manually and installing python-lxml.

I am not sure what happened to your other VM.

Best regards

Martin Sivak

On Thu, Jan 11, 2018 at 6:15 AM, Jayme  wrote:
> I performed Ovirt 4.2 upgrade on a 3 host cluster with NFS shared storage.
> The shared storage is mounted from one of the hosts.
>
> I upgraded the hosted engine first, downloading the 4.2 rpm, doing a yum
> update then engine setup which seemed to complete successfully, at the end
> it powered down the hosted VM but it never came back up.  I was unable to
> start it.
>
> I proceeded to upgrade the three hosts, ovirt 4.2 rpm and a full yum update.
> I also rebooted each of the three hosts.
>
> After some time the hosts did come back and almost all of the VMs are
> running again and seem to be working ok with the exception of two:
>
> 1. The hosted VM still will not start, I've tried everything I can think of.
>
> 2. A VM that I know existed is not running and does not appear to exist, I
> have no idea where it is or how to start it.
>
> 1. Hosted engine
>
> From one of the hosts I get a weird error trying to start it:
>
> # hosted-engine --vm-start
> Command VM.getStats with args {'vmID':
> '4013c829-c9d7-4b72-90d5-6fe58137504c'} failed:
> (code=1, message=Virtual machine does not exist: {'vmId':
> u'4013c829-c9d7-4b72-90d5-6fe58137504c'})
>
> From the two other hosts I do not get the same error as above, sometimes it
> appears to start but --vm-status shows errors such as:  Engine status
> : {"reason": "failed liveliness check", "health": "bad", "vm": "up",
> "detail": "Up"}
>
> Seeing these errors in syslog:
>
> Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+: 1910: error :
> qemuOpenFileAs:3183 : Failed to open file
> '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705':
> No such file or directory
>
> Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+: 1910: error :
> qemuDomainStorageOpenStat:11492 : cannot stat file
> '/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705':
> Bad file descriptor
>
> 2. Missing VM.  virsh -r list on each host does not show the VM at all.  I
> know it existed and is important.  The log on one of the hosts even shows
> that it started it recently then stopped in 10 or so minutes later:
>
> Jan 10 18:47:17 host3 systemd-machined: New machine qemu-9-Berna.
> Jan 10 18:47:17 host3 systemd: Started Virtual Machine qemu-9-Berna.
> Jan 10 18:47:17 host3 systemd: Starting Virtual Machine qemu-9-Berna.
> Jan 10 18:54:45 host3 systemd-machined: Machine qemu-9-Berna terminated.
>
> How can I find out the status of the "Berna" VM and get it running again?
>
> Thanks so much!
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Some major problems after 4.2 upgrade, could really use some assistance

[Jayme]

I performed Ovirt 4.2 upgrade on a 3 host cluster with NFS shared storage.
The shared storage is mounted from one of the hosts.

I upgraded the hosted engine first, downloading the 4.2 rpm, doing a yum
update then engine setup which seemed to complete successfully, at the end
it powered down the hosted VM but it never came back up.  I was unable to
start it.

I proceeded to upgrade the three hosts, ovirt 4.2 rpm and a full yum
update.  I also rebooted each of the three hosts.

After some time the hosts did come back and almost all of the VMs are
running again and seem to be working ok with the exception of two:

1. The hosted VM still will not start, I've tried everything I can think of.

2. A VM that I know existed is not running and does not appear to exist, I
have no idea where it is or how to start it.

1. Hosted engine

>From one of the hosts I get a weird error trying to start it:

# hosted-engine --vm-start
Command VM.getStats with args {'vmID':
'4013c829-c9d7-4b72-90d5-6fe58137504c'} failed:
(code=1, message=Virtual machine does not exist: {'vmId':
u'4013c829-c9d7-4b72-90d5-6fe58137504c'})

>From the two other hosts I do not get the same error as above, sometimes it
appears to start but --vm-status shows errors such as:  Engine status
: {"reason": "failed liveliness check", "health": "bad",
"vm": "up", "detail": "Up"}

Seeing these errors in syslog:

Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+: 1910: error :
qemuOpenFileAs:3183 : Failed to open file
'/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705':
No such file or directory

Jan 11 01:06:30 host0 libvirtd: 2018-01-11 05:06:30.473+: 1910: error :
qemuDomainStorageOpenStat:11492 : cannot stat file
'/var/run/vdsm/storage/248f46f0-d793-4581-9810-c9d965e2f286/c2dde892-f978-4dfc-a421-c8e04cf387f9/23aa0a66-fa6c-4967-a1e5-fbe47c0cd705':
Bad file descriptor

2. Missing VM.  virsh -r list on each host does not show the VM at all.  I
know it existed and is important.  The log on one of the hosts even shows
that it started it recently then stopped in 10 or so minutes later:

Jan 10 18:47:17 host3 systemd-machined: New machine qemu-9-Berna.
Jan 10 18:47:17 host3 systemd: Started Virtual Machine qemu-9-Berna.
Jan 10 18:47:17 host3 systemd: Starting Virtual Machine qemu-9-Berna.
Jan 10 18:54:45 host3 systemd-machined: Machine qemu-9-Berna terminated.

How can I find out the status of the "Berna" VM and get it running again?

Thanks so much!
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users