- Users - oVirt List Archives

Simple API call to start VM
by Kirin van der Veer 30 May '18

30 May '18

Hi oVirt users, I have (what I hope) is a simple problem. I want to make an https request to start a VM via the oVirt REST API. Here is the command that I think should work: curl --user "admin:SECRETPASSWORD" --request POST --header "Content-Type: application/xml" --header "Accept: application/xml" --data '</action>' https://ovirtengine.localnet:443/api/vms/69c47a91-bbv1-4eda-b71d-7bddf82ee8… However I get a 404 in response (see below): <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /api/vms/60c47a91-bca1-4eda-b71d-7bddf82ee8ab/start was not found on this server.</p> </body></html> Where have I made a mistake here? -- *IMPORTANT NOTE. *If you are NOT AN AUTHORISED RECIPIENT of this e-mail, please contact Planet Innovation Pty Ltd by return e-mail or by telephone on +613 9945 7510. In this case, you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. This e-mail and any attachments are confidential and may contain legally privileged information and/or copyright material of Planet Innovation Pty Ltd or third parties. You should only re-transmit, distribute or commercialise the material if you are authorised to do so. Although we use virus scanning software, we deny all liability for viruses or alike in any message or attachment. This notice should not be removed. **

7 7

Re: Fwd: FreeBSD after 10.3 could not boot (Freeze)
by Karli Sjöberg 30 May '18

30 May '18

1 0

Re: ovirt-node: freshly installed node: network interfaces not visible
by Ales Musil 30 May '18

30 May '18

On Wed, May 30, 2018 at 10:14 AM, Etienne Charlier < Etienne.Charlier(a)reduspaceservices.eu> wrote: > Hello, Thanks for the support > > > log are only sent to you , not to the list !!! > > > Kind Regards, > > Etienne > > Can you also please send the engine log? Regards, Ales > > ------------------------------ > *De :* Ales Musil <amusil(a)redhat.com> > *Envoyé :* mercredi 30 mai 2018 09:02 > *À :* Etienne Charlier > *Cc :* users > *Objet :* Re: [ovirt-users] Re: ovirt-node: freshly installed node: > network interfaces not visible > > > > On Tue, May 29, 2018 at 8:40 AM, <etienne.charlier(a)reduspaceservices.eu> > wrote: > >> Hello Ales, >> >> Thanks for the answer ! >> >> I tried multiple time to refresh capabilities... without success >> >> For the record, the tab named "Host Devices" is also empty >> >> Have a nice Day >> Etienne >> > > Can you please send us the vdsm and supervdsm log from the host? > > > > >> _______________________________________________ >> 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/communit >> y/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archiv >> es/list/users(a)ovirt.org/message/ISBFSCIX7J6INUIKJXUSI6J4DWKA326Q/ >> > > > > -- > > ALES MUSIL > INTERN - rhv network > > Red Hat EMEA <https://www.redhat.com/> > > > amusil(a)redhat.com IM: amusil > <https://red.ht/sig> > -- ALES MUSIL INTERN - rhv network Red Hat EMEA <https://www.redhat.com/> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

1 0

Use an oVirt-VM as a VDSM server
by James Michels 30 May '18

30 May '18

Greetings. In terms of teaching our students how to create and configure an oVirt infrastructure, we're planning to provide each of them a VM that will act as a Manager server, which has no issues so far. The problem is that we don't have enough physical machines to use as virtualization servers (VDSM), therefore we have been trying to use a CentOS7 based oVirt guest to run as a VDSM server. However, when trying to add it as a host, a (logical) error message shows up saying that the VM doesn't allow virtualization. The question is simple: Is there a way to enable virtualization on an oVirt VM, so we can deploy them as VDSM servers? This is oVirt 4.2.2 FWIW. Thanks James

4 3

Re: Simple API call to start VM
by Karli Sjöberg 30 May '18

30 May '18

1 0

FreeBSD after 10.3 could not boot (Freeze)
by Paul.LKW 30 May '18

30 May '18

HI All: Any one have tried to boot up FreeBSD 10.4, I tried 10.3 is all working fine but no lucky in 10.4 at all even boot from DVD !!! Attached is the point freezes. BR, Paul.LKW

3 5

Re: Fwd: FreeBSD after 10.3 could not boot (Freeze)
by Karli Sjöberg 30 May '18

30 May '18

2 1

Re: Gluster quorum
by Sahina Bose 30 May '18

30 May '18

[+users] Can you provide the engine.log to see why the monitoring is not working here. thanks! On Wed, May 16, 2018 at 2:08 PM, Demeter Tibor <tdemeter(a)itsmart.hu> wrote: > Hi, > > Meanwhile, I did the upgrade engine, but the gluster state is same on my > first node. > I've attached some screenshot of my problem. > > Thanks > > Tibor > > > > ----- 2018. máj.. 16., 10:16, Demeter Tibor <tdemeter(a)itsmart.hu> írtaHi, > > > If 4.3.4 will release, i just have to remove the nightly repo and update > to stable? > > I'm sorry for my terrible English, I try to explain what was my problem > with update. > I'm upgraded from 4.1.8. > > I followed up the official hosted-engine update documentation, that was > not clear me, because it has referenced to a lot of old thing (i think). > https://www.ovirt.org/documentation/upgrade-guide/upgrade-guide/ > https://www.ovirt.org/documentation/how-to/hosted- > engine/#upgrade-hosted-engine > > Maybe it need to update, because I had a lot of question under upgrade and > I was not sure in all of necessary steps. For example, If I need to > installing the new, 4.2 repo on the hosts, then need to remove the old repo > from that? > Why I need to do a" yum update -y" on hosts, meanwhile there is an > "Updatehost" menu in the GUI? So, maybe it outdated. > Since upgrade hosted engine, and the first node, I have problems with > gluster. It seems to working fine if you check it from console "gluster > volume status, etc" but not on the Gui, because now it yellow, and the > brick reds in the first node. > > Previously I did a mistake with glusterfs, my gluster config was wrong. I > have corrected them, but it did not helped to me,gluster bricks are reds on > my first node yet.... > > > Now I try to upgrade to nightly, but I'm affraid, because it a living, > productive system, and I don't have downtime. I hope it will help me. > > Thanks for all, > > Regards, > Tibor Demeter > > > > ----- 2018. máj.. 16., 9:58, Sahina Bose <sabose(a)redhat.com> írta: > > > > On Wed, May 16, 2018 at 1:19 PM, Demeter Tibor <tdemeter(a)itsmart.hu> > wrote: > >> Hi, >> >> is it a different, unstable repo? I have a productive cluster, how is >> safe that? >> I don't have any experience with nightly build. How can I use this? It >> have to install to the engine VM or all of my hosts? >> Thanks in advance for help me.. >> > > Only on the engine VM. > > Regarding stability - it passes CI so relatively stable, beyond that there > are no guarantees. > > What's the specific problem you're facing with update? Can you elaborate? > > >> Regards, >> >> Tibor >> >> ----- 2018. máj.. 15., 9:58, Demeter Tibor <tdemeter(a)itsmart.hu> írta: >> >> Hi, >> >> Could you explain how can I use this patch? >> >> R, >> Tibor >> >> >> ----- 2018. máj.. 14., 11:18, Demeter Tibor <tdemeter(a)itsmart.hu> írta: >> >> Hi, >> >> Sorry for my question, but can you tell me please how can I use this >> patch? >> >> Thanks, >> Regards, >> Tibor >> ----- 2018. máj.. 14., 10:47, Sahina Bose <sabose(a)redhat.com> írta: >> >> >> >> On Sat, May 12, 2018 at 1:14 PM, Demeter Tibor <tdemeter(a)itsmart.hu> >> wrote: >> >>> Hi, >>> >>> Could someone help me please ? I can't finish my upgrade process. >>> >> >> https://gerrit.ovirt.org/91164 should fix the error you're facing. >> >> Can you elaborate why this is affecting the upgrade process? >> >> >>> Thanks >>> R >>> Tibor >>> >>> >>> >>> ----- 2018. máj.. 10., 12:51, Demeter Tibor <tdemeter(a)itsmart.hu> írta: >>> >>> Hi, >>> >>> I've attached the vdsm and supervdsm logs. But I don't have engine.log >>> here, because that is on hosted engine vm. Should I send that ? >>> >>> Thank you >>> >>> Regards, >>> >>> Tibor >>> ----- 2018. máj.. 10., 12:30, Sahina Bose <sabose(a)redhat.com> írta: >>> >>> There's a bug here. Can you log one attaching this engine.log and also >>> vdsm.log & supervdsm.log from n3.itsmart.cloud >>> >>> On Thu, May 10, 2018 at 3:35 PM, Demeter Tibor <tdemeter(a)itsmart.hu> >>> wrote: >>> >>>> Hi, >>>> >>>> I found this: >>>> >>>> >>>> 2018-05-10 03:24:19,096+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, >>>> return: org.ovirt.engine.core.common.businessentities.gluster. >>>> GlusterVolumeAdvancedDetails@ca97448e, log id: 347435ae >>>> 2018-05-10 03:24:19,097+02 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] >>>> (DefaultQuartzScheduler7) [43f4eaec] Error while refreshing brick statuses >>>> for volume 'volume2' of cluster 'C6220': null >>>> 2018-05-10 03:24:19,097+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler8) [7715ceda] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 03:24:19,104+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n4.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='3ddef95f-158d-407c-a7d8-49641e012755'}), log id: 6908121d >>>> 2018-05-10 03:24:19,106+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n4.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='3ddef95f-158d-407c-a7d8-49641e012755'})' execution failed: >>>> null >>>> 2018-05-10 03:24:19,106+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 6908121d >>>> 2018-05-10 03:24:19,107+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n1.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='8e737bab-e0bb-4f16-ab85-e24e91882f57'}), log id: 735c6a5f >>>> 2018-05-10 03:24:19,109+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n1.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='8e737bab-e0bb-4f16-ab85-e24e91882f57'})' execution failed: >>>> null >>>> 2018-05-10 03:24:19,109+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 735c6a5f >>>> 2018-05-10 03:24:19,110+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 6f9e9f58 >>>> 2018-05-10 03:24:19,112+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'})' execution failed: >>>> null >>>> 2018-05-10 03:24:19,112+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 6f9e9f58 >>>> 2018-05-10 03:24:19,113+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n3.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='fd2ee743-f5d4-403b-ba18-377e309169ec'}), log id: 2ee46967 >>>> 2018-05-10 03:24:19,115+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n3.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='fd2ee743-f5d4-403b-ba18-377e309169ec'})' execution failed: >>>> null >>>> 2018-05-10 03:24:19,116+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 2ee46967 >>>> 2018-05-10 03:24:19,117+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] START, GetGlusterVolumeAdvancedDetailsVDSCommand(HostName >>>> = n1.itsmart.cloud, GlusterVolumeAdvancedDetailsVD >>>> SParameters:{hostId='8e737bab-e0bb-4f16-ab85-e24e91882f57', >>>> volumeName='volume1'}), log id: 7550e5c >>>> 2018-05-10 03:24:20,748+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler7) [43f4eaec] FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, >>>> return: org.ovirt.engine.core.common.businessentities.gluster. >>>> GlusterVolumeAdvancedDetails@4a46066f, log id: 7550e5c >>>> 2018-05-10 03:24:20,749+02 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] >>>> (DefaultQuartzScheduler7) [43f4eaec] Error while refreshing brick statuses >>>> for volume 'volume1' of cluster 'C6220': null >>>> 2018-05-10 03:24:20,750+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterServersListVDSCommand] >>>> (DefaultQuartzScheduler8) [7715ceda] START, GlusterServersListVDSCommand(HostName >>>> = n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 120cc68d >>>> 2018-05-10 03:24:20,930+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterServersListVDSCommand] >>>> (DefaultQuartzScheduler8) [7715ceda] FINISH, GlusterServersListVDSCommand, >>>> return: [10.101.0.2/24:CONNECTED, n1.cloudata.local:CONNECTED, >>>> 10.104.0.3:CONNECTED, 10.104.0.4:CONNECTED], log id: 120cc68d >>>> 2018-05-10 03:24:20,949+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListVDSCommand] >>>> (DefaultQuartzScheduler8) [7715ceda] START, GlusterVolumesListVDSCommand(HostName >>>> = n2.itsmart.cloud, GlusterVolumesListVDSParameter >>>> s:{hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 118aa264 >>>> 2018-05-10 03:24:21,048+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster/brick/brick1' >>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,055+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster/brick/brick2' >>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,061+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster/brick/brick3' >>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,067+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster2/brick/brick1' >>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,074+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster2/brick/brick2' >>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,080+02 WARN [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler8) >>>> [7715ceda] Could not associate brick '10.104.0.1:/gluster2/brick/brick3' >>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>> 000000000339' >>>> 2018-05-10 03:24:21,081+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GlusterVolumesListVDSCommand] >>>> (DefaultQuartzScheduler8) [7715ceda] FINISH, GlusterVolumesListVDSCommand, >>>> return: {68cfb061-1320-4042-abcd-9228da23c0c8=org.ovirt.engine. >>>> core.common.businessentities.gluster.GlusterVolumeEntity@7a6720d, >>>> e0f568fa-987c-4f5c-b853-01bce718ee27=org.ovirt.engine. >>>> core.common.businessentities.g >>>> luster.GlusterVolumeEntity@f88c521b}, log id: 118aa264 >>>> >>>> >>>> >>>> 2018-05-10 11:59:26,047+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n1.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='8e737bab-e0bb-4f16-ab85-e24e91882f57'})' execution failed: >>>> null >>>> 2018-05-10 11:59:26,047+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 14a71ef0 >>>> 2018-05-10 11:59:26,048+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n4.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='3ddef95f-158d-407c-a7d8-49641e012755'}), log id: 28d9e255 >>>> 2018-05-10 11:59:26,051+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n4.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='3ddef95f-158d-407c-a7d8-49641e012755'})' execution failed: >>>> null >>>> 2018-05-10 11:59:26,051+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 28d9e255 >>>> 2018-05-10 11:59:26,052+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 4a7b280e >>>> 2018-05-10 11:59:26,054+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'})' execution failed: >>>> null >>>> 2018-05-10 11:59:26,054+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 4a7b280e >>>> 2018-05-10 11:59:26,055+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] START, GetGlusterLocalLogicalVolumeListVDSCommand(HostName >>>> = n3.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='fd2ee743-f5d4-403b-ba18-377e309169ec'}), log id: 18adc534 >>>> 2018-05-10 11:59:26,057+02 ERROR [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] Command ' >>>> GetGlusterLocalLogicalVolumeListVDSCommand(HostName = >>>> n3.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>> {hostId='fd2ee743-f5d4-403b-ba18-377e309169ec'})' execution failed: >>>> null >>>> 2018-05-10 11:59:26,057+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterLocalLogicalVolumeListVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterLocalLogicalVolumeListVDSCommand, >>>> log id: 18adc534 >>>> 2018-05-10 11:59:26,058+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] START, GetGlusterVolumeAdvancedDetailsVDSCommand(HostName >>>> = n3.itsmart.cloud, GlusterVolumeAdvancedDetailsVD >>>> SParameters:{hostId='fd2ee743-f5d4-403b-ba18-377e309169ec', >>>> volumeName='volume1'}), log id: 3451084f >>>> 2018-05-10 11:59:28,050+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:28,060+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:28,062+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,054+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,054+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,062+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,064+02 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] >>>> (DefaultQuartzScheduler3) [2eb1c389] Failed to acquire lock and wait lock >>>> 'EngineLock:{exclusiveLocks='[59c10db3-0324-0320-0120-000000000339=GLUSTER]', >>>> sharedLocks=''}' >>>> 2018-05-10 11:59:31,465+02 INFO [org.ovirt.engine.core. >>>> vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] >>>> (DefaultQuartzScheduler4) [400fa486] FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, >>>> return: org.ovirt.engine.core.common.businessentities.gluster. >>>> GlusterVolumeAdvancedDetails@3f1b7f43, log id: 3451084f >>>> 2018-05-10 11:59:31,466+02 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] >>>> (DefaultQuartzScheduler4) [400fa486] Error while refreshing brick statuses >>>> for volume 'volume1' of cluster 'C6220': null >>>> >>>> >>>> R >>>> Tibor >>>> >>>> ----- 2018. máj.. 10., 11:43, Sahina Bose <sabose(a)redhat.com> írta: >>>> >>>> This doesn't affect the monitoring of state. >>>> Any errors in vdsm.log? >>>> Or errors in engine.log of the form "Error while refreshing brick >>>> statuses for volume" >>>> >>>> On Thu, May 10, 2018 at 2:33 PM, Demeter Tibor <tdemeter(a)itsmart.hu> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> Thank you for your fast reply :) >>>>> >>>>> >>>>> 2018-05-10 11:01:51,574+02 INFO [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterServersListVDSCommand] >>>>> (DefaultQuartzScheduler6) [7f01fc2d] START, GlusterServersListVDSCommand(HostName >>>>> = n2.itsmart.cloud, VdsIdVDSCommandParametersBase: >>>>> {hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 39adbbb8 >>>>> 2018-05-10 11:01:51,768+02 INFO [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterServersListVDSCommand] >>>>> (DefaultQuartzScheduler6) [7f01fc2d] FINISH, GlusterServersListVDSCommand, >>>>> return: [10.101.0.2/24:CONNECTED, n1.cloudata.local:CONNECTED, >>>>> 10.104.0.3:CONNECTED, 10.104.0.4:CONNECTED], log id: 39adbbb8 >>>>> 2018-05-10 11:01:51,788+02 INFO [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListVDSCommand] >>>>> (DefaultQuartzScheduler6) [7f01fc2d] START, GlusterVolumesListVDSCommand(HostName >>>>> = n2.itsmart.cloud, GlusterVolumesListVDSParameter >>>>> s:{hostId='06e361ef-3361-4eaa-9923-27fa1a0187a4'}), log id: 738a7261 >>>>> 2018-05-10 11:01:51,892+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster/brick/brick1' >>>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,898+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster/brick/brick2' >>>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,905+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster/brick/brick3' >>>>> of volume 'e0f568fa-987c-4f5c-b853-01bce718ee27' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,911+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster2/brick/brick1' >>>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,917+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster2/brick/brick2' >>>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,924+02 WARN [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler6) >>>>> [7f01fc2d] Could not associate brick '10.104.0.1:/gluster2/brick/brick3' >>>>> of volume '68cfb061-1320-4042-abcd-9228da23c0c8' with correct network >>>>> as no gluster network found in cluster '59c10db3-0324-0320-0120- >>>>> 000000000339' >>>>> 2018-05-10 11:01:51,925+02 INFO [org.ovirt.engine.core. >>>>> vdsbroker.gluster.GlusterVolumesListVDSCommand] >>>>> (DefaultQuartzScheduler6) [7f01fc2d] FINISH, GlusterVolumesListVDSCommand, >>>>> return: {68cfb061-1320-4042-abcd-9228da23c0c8=org.ovirt.engine. >>>>> core.common.businessentities.gluster.GlusterVolumeEntity@7a6720d, >>>>> e0f568fa-987c-4f5c-b853-01bce718ee27=org.ovirt.engine. >>>>> core.common.businessentities.gluster.GlusterVolumeEntity@f88c521b}, >>>>> log id: 738a7261 >>>>> >>>>> >>>>> This happening continuously. >>>>> >>>>> Thanks! >>>>> Tibor >>>>> >>>>> >>>>> >>>>> ----- 2018. máj.. 10., 10:56, Sahina Bose <sabose(a)redhat.com> írta: >>>>> >>>>> Could you check the engine.log if there are errors related to getting >>>>> GlusterVolumeAdvancedDetails ? >>>>> >>>>> On Thu, May 10, 2018 at 2:02 PM, Demeter Tibor <tdemeter(a)itsmart.hu> >>>>> wrote: >>>>> >>>>>> Dear Ovirt Users, >>>>>> I've followed up the self-hosted-engine upgrade documentation, I >>>>>> upgraded my 4.1 system to 4.2.3. >>>>>> I upgaded the first node with yum upgrade, it seems working now fine. >>>>>> But since upgrade, the gluster informations seems to displayed incorrect on >>>>>> the admin panel. The volume yellow, and there are red bricks from that node. >>>>>> I've checked in console, I think my gluster is not degraded: >>>>>> >>>>>> root@n1 ~]# gluster volume list >>>>>> volume1 >>>>>> volume2 >>>>>> [root@n1 ~]# gluster volume info >>>>>> >>>>>> Volume Name: volume1 >>>>>> Type: Distributed-Replicate >>>>>> Volume ID: e0f568fa-987c-4f5c-b853-01bce718ee27 >>>>>> Status: Started >>>>>> Snapshot Count: 0 >>>>>> Number of Bricks: 3 x 3 = 9 >>>>>> Transport-type: tcp >>>>>> Bricks: >>>>>> Brick1: 10.104.0.1:/gluster/brick/brick1 >>>>>> Brick2: 10.104.0.2:/gluster/brick/brick1 >>>>>> Brick3: 10.104.0.3:/gluster/brick/brick1 >>>>>> Brick4: 10.104.0.1:/gluster/brick/brick2 >>>>>> Brick5: 10.104.0.2:/gluster/brick/brick2 >>>>>> Brick6: 10.104.0.3:/gluster/brick/brick2 >>>>>> Brick7: 10.104.0.1:/gluster/brick/brick3 >>>>>> Brick8: 10.104.0.2:/gluster/brick/brick3 >>>>>> Brick9: 10.104.0.3:/gluster/brick/brick3 >>>>>> Options Reconfigured: >>>>>> transport.address-family: inet >>>>>> performance.readdir-ahead: on >>>>>> nfs.disable: on >>>>>> storage.owner-uid: 36 >>>>>> storage.owner-gid: 36 >>>>>> performance.quick-read: off >>>>>> performance.read-ahead: off >>>>>> performance.io-cache: off >>>>>> performance.stat-prefetch: off >>>>>> performance.low-prio-threads: 32 >>>>>> network.remote-dio: enable >>>>>> cluster.eager-lock: enable >>>>>> cluster.quorum-type: auto >>>>>> cluster.server-quorum-type: server >>>>>> cluster.data-self-heal-algorithm: full >>>>>> cluster.locking-scheme: granular >>>>>> cluster.shd-max-threads: 8 >>>>>> cluster.shd-wait-qlength: 10000 >>>>>> features.shard: on >>>>>> user.cifs: off >>>>>> server.allow-insecure: on >>>>>> >>>>>> Volume Name: volume2 >>>>>> Type: Distributed-Replicate >>>>>> Volume ID: 68cfb061-1320-4042-abcd-9228da23c0c8 >>>>>> Status: Started >>>>>> Snapshot Count: 0 >>>>>> Number of Bricks: 3 x 3 = 9 >>>>>> Transport-type: tcp >>>>>> Bricks: >>>>>> Brick1: 10.104.0.1:/gluster2/brick/brick1 >>>>>> Brick2: 10.104.0.2:/gluster2/brick/brick1 >>>>>> Brick3: 10.104.0.3:/gluster2/brick/brick1 >>>>>> Brick4: 10.104.0.1:/gluster2/brick/brick2 >>>>>> Brick5: 10.104.0.2:/gluster2/brick/brick2 >>>>>> Brick6: 10.104.0.3:/gluster2/brick/brick2 >>>>>> Brick7: 10.104.0.1:/gluster2/brick/brick3 >>>>>> Brick8: 10.104.0.2:/gluster2/brick/brick3 >>>>>> Brick9: 10.104.0.3:/gluster2/brick/brick3 >>>>>> Options Reconfigured: >>>>>> nfs.disable: on >>>>>> performance.readdir-ahead: on >>>>>> transport.address-family: inet >>>>>> cluster.quorum-type: auto >>>>>> network.ping-timeout: 10 >>>>>> auth.allow: * >>>>>> performance.quick-read: off >>>>>> performance.read-ahead: off >>>>>> performance.io-cache: off >>>>>> performance.stat-prefetch: off >>>>>> performance.low-prio-threads: 32 >>>>>> network.remote-dio: enable >>>>>> cluster.eager-lock: enable >>>>>> cluster.server-quorum-type: server >>>>>> cluster.data-self-heal-algorithm: full >>>>>> cluster.locking-scheme: granular >>>>>> cluster.shd-max-threads: 8 >>>>>> cluster.shd-wait-qlength: 10000 >>>>>> features.shard: on >>>>>> user.cifs: off >>>>>> storage.owner-uid: 36 >>>>>> storage.owner-gid: 36 >>>>>> server.allow-insecure: on >>>>>> [root@n1 ~]# gluster volume status >>>>>> Status of volume: volume1 >>>>>> Gluster process TCP Port RDMA Port >>>>>> Online Pid >>>>>> ------------------------------------------------------------ >>>>>> ------------------ >>>>>> Brick 10.104.0.1:/gluster/brick/brick1 49152 0 Y >>>>>> 3464 >>>>>> Brick 10.104.0.2:/gluster/brick/brick1 49152 0 Y >>>>>> 68937 >>>>>> Brick 10.104.0.3:/gluster/brick/brick1 49161 0 Y >>>>>> 94506 >>>>>> Brick 10.104.0.1:/gluster/brick/brick2 49153 0 Y >>>>>> 3457 >>>>>> Brick 10.104.0.2:/gluster/brick/brick2 49153 0 Y >>>>>> 68943 >>>>>> Brick 10.104.0.3:/gluster/brick/brick2 49162 0 Y >>>>>> 94514 >>>>>> Brick 10.104.0.1:/gluster/brick/brick3 49154 0 Y >>>>>> 3465 >>>>>> Brick 10.104.0.2:/gluster/brick/brick3 49154 0 Y >>>>>> 68949 >>>>>> Brick 10.104.0.3:/gluster/brick/brick3 49163 0 Y >>>>>> 94520 >>>>>> Self-heal Daemon on localhost N/A N/A Y >>>>>> 54356 >>>>>> Self-heal Daemon on 10.104.0.2 N/A N/A Y >>>>>> 962 >>>>>> Self-heal Daemon on 10.104.0.3 N/A N/A Y >>>>>> 108977 >>>>>> Self-heal Daemon on 10.104.0.4 N/A N/A Y >>>>>> 61603 >>>>>> >>>>>> Task Status of Volume volume1 >>>>>> ------------------------------------------------------------ >>>>>> ------------------ >>>>>> There are no active volume tasks >>>>>> >>>>>> Status of volume: volume2 >>>>>> Gluster process TCP Port RDMA Port >>>>>> Online Pid >>>>>> ------------------------------------------------------------ >>>>>> ------------------ >>>>>> Brick 10.104.0.1:/gluster2/brick/brick1 49155 0 Y >>>>>> 3852 >>>>>> Brick 10.104.0.2:/gluster2/brick/brick1 49158 0 Y >>>>>> 68955 >>>>>> Brick 10.104.0.3:/gluster2/brick/brick1 49164 0 Y >>>>>> 94527 >>>>>> Brick 10.104.0.1:/gluster2/brick/brick2 49156 0 Y >>>>>> 3851 >>>>>> Brick 10.104.0.2:/gluster2/brick/brick2 49159 0 Y >>>>>> 68961 >>>>>> Brick 10.104.0.3:/gluster2/brick/brick2 49165 0 Y >>>>>> 94533 >>>>>> Brick 10.104.0.1:/gluster2/brick/brick3 49157 0 Y >>>>>> 3883 >>>>>> Brick 10.104.0.2:/gluster2/brick/brick3 49160 0 Y >>>>>> 68968 >>>>>> Brick 10.104.0.3:/gluster2/brick/brick3 49166 0 Y >>>>>> 94541 >>>>>> Self-heal Daemon on localhost N/A N/A Y >>>>>> 54356 >>>>>> Self-heal Daemon on 10.104.0.2 N/A N/A Y >>>>>> 962 >>>>>> Self-heal Daemon on 10.104.0.3 N/A N/A Y >>>>>> 108977 >>>>>> Self-heal Daemon on 10.104.0.4 N/A N/A Y >>>>>> 61603 >>>>>> >>>>>> Task Status of Volume volume2 >>>>>> ------------------------------------------------------------ >>>>>> ------------------ >>>>>> There are no active volume tasks >>>>>> >>>>>> I think ovirt can't read valid informations about gluster. >>>>>> I can't contiune upgrade of other hosts until this problem exist. >>>>>> >>>>>> Please help me:) >>>>>> >>>>>> >>>>>> Thanks >>>>>> >>>>>> Regards, >>>>>> >>>>>> Tibor >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Users mailing list -- users(a)ovirt.org >>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>> >>>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> >>> >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> >> >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community- >> guidelines/ >> List Archives: >> >> >

4 16

Does ovirt engine itself support high scalability (such as Load Balancing)?
by simiam 30 May '18

30 May '18

Hi, Does ovirt engine itself support high scalability (such as Load Balancing)? It means that i can add one or many engine servers to balance the load easily. Thanks.

1 1

start vm without engine
by David David 29 May '18

29 May '18

hi. How to start VM directly in hypervisor? ovirt-engine was crashed. VM's id is known. vdsclient VM, hasn't argumets for starting vm. Thanks.

3 2

Updated ovirt-engine packages were released for oVirt 4.2
by Lev Veyde 29 May '18

29 May '18

Hi, We have added an updated oVirt engine (4.2.3.8) to the oVirt 4.2 stable yum repo. It fixes BZ#1582483 [1]. [1] https://bugzilla.redhat.com/1582483 Thanks in advance, -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Ovirt 4.2.4 - Trouble installing additional self hosted engine hosts
by Maton, Brett 29 May '18

29 May '18

Adding regular, non SHE hosts works fine, however I can't seem to add Self Hosted Engine to additional physical hosts. I think this is the problem, but I don't know what the solution is: 2018-05-29 08:00:52,502+0100 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Misc configuration': Cannot resolve ovirt_hosted_engine_ha module Deploy log attached.

3 4

CVE-2018-3639 - Important - oVirt - Speculative Store Bypass
by Sandro Bonazzola 29 May '18

29 May '18

As you may have already heard, an industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions. This issue is well described by CVE-2018-3639 announce available at https://access.redhat.com/security/cve/cve-2018-3639. oVirt team has released right now an update of ovirt-engine to version 4.2.3.7 which add support for SSBD CPUs in order to mitigate the security issue. If you are running oVirt on Red Hat Enterprise Linux, please apply updates described in https://access.redhat.com/security/cve/cve-2018-3639. If you are running oVirt on CentOS Linux please apply updated described by: CESA-2018:1629 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html> CESA-2018:1632 Important CentOS 7 libvirt Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022840.html> CESA-2018:1649 Important CentOS 7 java-1.8.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022839.html> CESA-2018:1648 Important CentOS 7 java-1.7.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022838.html> An update for qemu-kvm-ev has been also tagged for release and announced with CESA-2018:1655 Important: qemu-kvm-ev security update <https://lists.centos.org/pipermail/centos-virt/2018-May/005804.html> but due to some issues in CentOS release process for Virt SIG content, it is not yet available on mirrors. We are working with CentOS community to get the packages signed and published as soon as possible. In the meanwhile you can still get the update package by enabling the test repository https://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ on your systems or manually installing the package from the repository. If you're running oVirt on a different Linux distribution, please check with your vendor for available updates. Please note that to fully mitigate this vulnerability, system administrators must apply both hardware “microcode” updates and software patches that enable new functionality. At this time, microprocessor microcode will be delivered by the individual manufacturers. The oVirt team recommends end users and systems administrator to apply any available updates as soon as practical. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

6 10

SSH into guest VM
by 03ce007＠gmail.com 29 May '18

29 May '18

I have self-hosted-engine (4.2) deployed successfully on cento (7.4) server. The physical server has 'ovirt' as hostname and the self-hosted engineVM deployed and running on it has 'engine.ovirt' as fdqn. I can successfully create new VM using the oVirt.vm-infra example playbook. But what other config/var i need to add in them so that I can ssh into this new VM. Some example, tips, hints would be helpful. Thank you.

3 4

cache and viodiskcache parameters in documentation
by stefanos＠prismatelecomtesting.com 28 May '18

28 May '18

Hi, on chapter 6.13.1 "Live Migration Prerequisites" [1] of the RHV 4.2 Virtual Machine Management Guide, there is written: ____________ At a minimum, for successful live migration of virtual machines to be possible: [...] The migrating virtual machine must not have the cache!=none custom property set. ____________ However I can't find any custom property called "cache" under Edit Virtual Machine --> Custom Properties but only "viodiskcache". As a matter of fact, Appendix A of the same guide [2] reports the following statement: "If viodiskcache is enabled, the virtual machine cannot be live migrated" that suggest viodiskcache as the correct parameter. Are the two statements contradictory? Thank you. Stefano Stagnaro [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… [2] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht…

2 2

Bad volume specification
by Bryan Sockel 28 May '18

28 May '18

Hi, I am having to rebuild my ovirt instance for a couple of reasons. I have setup a temporary ovirt portal to migrate my setup to while i rebuild my production portal. I have run int a couple of VM's that will no longer start. Everything that i am seeing is identical to this article - https://access.redhat.com/solutions/2423391 VM devel-build is down with error. Exit message: Bad volume specification {'serial': 'ec7a3258-7a99-4813-aa7d-dceb727a1975', 'index': 0, 'iface': 'virtio', 'apparentsize': '1835008', 'specParams': {}, 'cache': 'none', 'imageID': 'ec7a3258-7a99-4813-aa7d-dceb727a1975', 'truesize': '1777664', 'type': 'disk', 'domainID': '2b79768f-a329-4eab-81e0-120a81ac8906', 'reqsize': '0', 'format': 'cow', 'poolID': '9e7d643c-592d-11e8-82eb-005056b41d15', 'device': 'disk', 'path': '/rhev/data-center/9e7d643c-592d-11e8-82eb-005056b41d15/2b79768f-a329-4eab-81e0-120a81ac8906/images/ec7a3258-7a99-4813-aa7d-dceb727a1975/8f4ddee4-68b3-48e9-be27-0231557f5218', 'propagateErrors': 'off', 'name': 'vda', 'bootOrder': '1', 'volumeID': '8f4ddee4-68b3-48e9-be27-0231557f5218', 'diskType': 'file', 'alias': 'ua-ec7a3258-7a99-4813-aa7d-dceb727a1975', 'discard': False}. Currently running version 4.2.3.5-1 Is there anyway to recover the image, or even just be able to mount the drive to another vm to extract data. Thank You

2 2

second deploy hosted engine, engine VM is shut dwon
by dhy336＠sina.com 28 May '18

28 May '18

HiI first deploy hosted engine is failed， then deploy hosted engine, after ansible run "name: Add host ovirt_hosts:"(bootstrap_local_vm.yml), engine VM is shut dwon, why to shutown engine VM?

1 0

Reference architecture for oVirt Gluster HCI
by Karli Sjöberg 28 May '18

28 May '18

1 0

ovirt guest agent epel 6 and rhevm in the name
by Gianluca Cecchi 28 May '18

28 May '18

Hello, I have updated one test environment to 4.2 (it was in 4.1.9) I have a guest in Oracle Linux 6 and epel 6 repo enabled. After powering down and start the VM, I saw the exclamation mark regarding ovirt-guest-agent latest version needed. On the VM the process was dead and I took the time of updatng it from ovirt-guest-agent-1.0.12-4.el6.noarch to ovirt-guest-agent-1.0.13-2.el6.noarch and start the agent. All seems ok; no exclamation mark now and I see the ip addresses of the guest in 4.2 web admin gui. But in log of ovirt-guest-agent I see: MainThread::ERROR::2018-05-28 14:34:55,711::ovirt-guest-agent::140::root::Unhandled exception in oVirt guest agent! Traceback (most recent call last): File "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 134, in <module> agent.run(daemon, pidfile) File "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 65, in run self.agent = LinuxVdsAgent(config) File "/usr/share/ovirt-guest-agent/GuestAgentLinux2.py", line 466, in __init__ AgentLogicBase.__init__(self, config) File "/usr/share/ovirt-guest-agent/OVirtAgentLogic.py", line 188, in __init__ self.vio = VirtIoChannel(config.get("virtio", "device")) File "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 151, in __init__ self._stream = VirtIoStream(vport_name) File "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 132, in __init__ self._vport = os.open(vport_name, os.O_RDWR) OSError: [Errno 2] No such file or directory: '/dev/virtio-ports/com.redhat.rhevm.vdsm' MainThread::INFO::2018-05-28 14:42:45,535::ovirt-guest-agent::59::root::Starting oVirt guest agent The status of files under the indicated directory is: # ll /dev/virtio-ports/ total 0 lrwxrwxrwx 1 root root 11 May 28 14:34 com.redhat.spice.0 -> ../vport0p3 lrwxrwxrwx 1 root root 11 May 28 14:34 org.qemu.guest_agent.0 -> ../vport0p2 lrwxrwxrwx 1 root root 11 May 28 14:42 ovirt-guest-agent.0 -> ../vport0p1 # Anything to be done at my side at guest/host configuration level? Thanks, Gianluca

1 1

Does ovirt engine itself support high scalability
by simiam 28 May '18

28 May '18

Does ovirt engine itself support high scalability?

1 0

CentOS7 Install Failure to Shutdown
by Matthew Wimpelberg 28 May '18

28 May '18

I have ovirt 4.2.3.5-1.el7.centos installed and am unable to cleanly reboot the host machine. The only way I can reboot is to press and hold the power button which causes an unclean shutdown of the engine vm. I can upload logs if necessary I'm just not sure where to upload them to.

2 1

Fwd: External ceph storage
by Leo David 27 May '18

27 May '18

---------- Forwarded message --------- From: Leo David <leoalex(a)gmail.com> Date: Sun, May 27, 2018, 20:01 Subject: Re: [ovirt-users] External ceph storage To: Luca 'remix_tj' Lorenzetto <lorenzetto.luca(a)gmail.com> Indeed, you right. Will setup the gws while waiting for a maybe future native ceph connection, which in my oppinion would bring a lot of power to oVirt. On Sun, May 27, 2018, 19:48 Luca 'remix_tj' Lorenzetto < lorenzetto.luca(a)gmail.com> wrote: > I think is the best option. Setting up a sma openstack setup only for it > is not worth the hassle. > > Luca > > Il dom 27 mag 2018, 18:44 Leo David <leoalex(a)gmail.com> ha scritto: > >> Ok, so since i dont have openstack installed (which would put cinder >> between ceph and ovirt ), the only option remains the iscsi gw... >> Thank you very much ! >> >> On Sun, May 27, 2018, 18:14 Luca 'remix_tj' Lorenzetto < >> lorenzetto.luca(a)gmail.com> wrote: >> >>> No, >>> >>> The only way you have is to configure cinder to manage ceph pool or in >>> alternative you have to deploy an iscsi gateway, no other ways are >>> available at the moment. >>> >>> So you can't use rbd directly. >>> >>> Luca >>> >>> Il dom 27 mag 2018, 16:54 Leo David <leoalex(a)gmail.com> ha scritto: >>> >>>> Thank you Luca, >>>> At the moment i would try the cinder storage provider, since we already >>>> have a proxmox cluster directly connecting to ceph. The problem is that I >>>> just could not find a straight way to do this. >>>> ie: Specify the ceph monitors and ceph pool to connect to. Can oVirt >>>> directly connect to ceph monitors ? How the configuration should be done if >>>> so ? >>>> Thank you very much ! >>>> >>>> >>>> On Sun, May 27, 2018, 17:20 Luca 'remix_tj' Lorenzetto < >>>> lorenzetto.luca(a)gmail.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> Yes, using cinder or through iscsi gateway. >>>>> >>>>> For a simpler setup i suggest the second option. >>>>> >>>>> Luca >>>>> >>>>> Il dom 27 mag 2018, 16:08 Leo David <leoalex(a)gmail.com> ha scritto: >>>>> >>>>>> Hello everyone, >>>>>> I am new to ovirt and very impressed of its features. I would like to >>>>>> levereage on our existing ceph cluster to provide rbd images for vm hdds, >>>>>> is this possible to achieve ? >>>>>> Thank you very much ! >>>>>> Regards, >>>>>> Leo >>>>>> _______________________________________________ >>>>>> Users mailing list -- users(a)ovirt.org >>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>> >>>>>

1 0

Failed to complete VM name creation fills the log every minute
by acavasiljevic＠gmail.com 27 May '18

27 May '18

Hi, Could you please help. Every 30 seconds I get an error "Failed to complete VM name creation" The task was started but stopped after a while. I have killed all tasks : $ su - postgres $ psql -d engine -U postgres > select * from job order by start_time desc; > select DeleteJob('702e9f6a-e2a3-4113-bd7d-3757ba6bc4ef'); I run: oVirt Engine Version: 4.1.9.1-1.el7.centos Thank you very much. Best regards,

1 0

Re: External ceph storage
by Luca 'remix_tj' Lorenzetto 27 May '18

27 May '18

Remember always to reply to the list, youur feedback will return back to the devs! Il dom 27 mag 2018, 19:01 Leo David <leoalex(a)gmail.com> ha scritto: > Indeed, you right. Will setup the gws while waiting for a maybe future > native ceph connection, which in my oppinion would bring a lot of power to > oVirt. > > On Sun, May 27, 2018, 19:48 Luca 'remix_tj' Lorenzetto < > lorenzetto.luca(a)gmail.com> wrote: > >> I think is the best option. Setting up a sma openstack setup only for it >> is not worth the hassle. >> >> Luca >> >> Il dom 27 mag 2018, 18:44 Leo David <leoalex(a)gmail.com> ha scritto: >> >>> Ok, so since i dont have openstack installed (which would put cinder >>> between ceph and ovirt ), the only option remains the iscsi gw... >>> Thank you very much ! >>> >>> On Sun, May 27, 2018, 18:14 Luca 'remix_tj' Lorenzetto < >>> lorenzetto.luca(a)gmail.com> wrote: >>> >>>> No, >>>> >>>> The only way you have is to configure cinder to manage ceph pool or in >>>> alternative you have to deploy an iscsi gateway, no other ways are >>>> available at the moment. >>>> >>>> So you can't use rbd directly. >>>> >>>> Luca >>>> >>>> Il dom 27 mag 2018, 16:54 Leo David <leoalex(a)gmail.com> ha scritto: >>>> >>>>> Thank you Luca, >>>>> At the moment i would try the cinder storage provider, since we >>>>> already have a proxmox cluster directly connecting to ceph. The problem is >>>>> that I just could not find a straight way to do this. >>>>> ie: Specify the ceph monitors and ceph pool to connect to. Can oVirt >>>>> directly connect to ceph monitors ? How the configuration should be done if >>>>> so ? >>>>> Thank you very much ! >>>>> >>>>> >>>>> On Sun, May 27, 2018, 17:20 Luca 'remix_tj' Lorenzetto < >>>>> lorenzetto.luca(a)gmail.com> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> Yes, using cinder or through iscsi gateway. >>>>>> >>>>>> For a simpler setup i suggest the second option. >>>>>> >>>>>> Luca >>>>>> >>>>>> Il dom 27 mag 2018, 16:08 Leo David <leoalex(a)gmail.com> ha scritto: >>>>>> >>>>>>> Hello everyone, >>>>>>> I am new to ovirt and very impressed of its features. I would like >>>>>>> to levereage on our existing ceph cluster to provide rbd images for vm >>>>>>> hdds, is this possible to achieve ? >>>>>>> Thank you very much ! >>>>>>> Regards, >>>>>>> Leo >>>>>>> _______________________________________________ >>>>>>> Users mailing list -- users(a)ovirt.org >>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>>> >>>>>>

1 0

Re: External ceph storage
by Luca 'remix_tj' Lorenzetto 27 May '18

27 May '18

I think is the best option. Setting up a sma openstack setup only for it is not worth the hassle. Luca Il dom 27 mag 2018, 18:44 Leo David <leoalex(a)gmail.com> ha scritto: > Ok, so since i dont have openstack installed (which would put cinder > between ceph and ovirt ), the only option remains the iscsi gw... > Thank you very much ! > > On Sun, May 27, 2018, 18:14 Luca 'remix_tj' Lorenzetto < > lorenzetto.luca(a)gmail.com> wrote: > >> No, >> >> The only way you have is to configure cinder to manage ceph pool or in >> alternative you have to deploy an iscsi gateway, no other ways are >> available at the moment. >> >> So you can't use rbd directly. >> >> Luca >> >> Il dom 27 mag 2018, 16:54 Leo David <leoalex(a)gmail.com> ha scritto: >> >>> Thank you Luca, >>> At the moment i would try the cinder storage provider, since we already >>> have a proxmox cluster directly connecting to ceph. The problem is that I >>> just could not find a straight way to do this. >>> ie: Specify the ceph monitors and ceph pool to connect to. Can oVirt >>> directly connect to ceph monitors ? How the configuration should be done if >>> so ? >>> Thank you very much ! >>> >>> >>> On Sun, May 27, 2018, 17:20 Luca 'remix_tj' Lorenzetto < >>> lorenzetto.luca(a)gmail.com> wrote: >>> >>>> Hello, >>>> >>>> Yes, using cinder or through iscsi gateway. >>>> >>>> For a simpler setup i suggest the second option. >>>> >>>> Luca >>>> >>>> Il dom 27 mag 2018, 16:08 Leo David <leoalex(a)gmail.com> ha scritto: >>>> >>>>> Hello everyone, >>>>> I am new to ovirt and very impressed of its features. I would like to >>>>> levereage on our existing ceph cluster to provide rbd images for vm hdds, >>>>> is this possible to achieve ? >>>>> Thank you very much ! >>>>> Regards, >>>>> Leo >>>>> _______________________________________________ >>>>> Users mailing list -- users(a)ovirt.org >>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>> >>>>

1 0