[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-14 Thread Nardus Geldenhuys 
This is fixed. Was a table in db that was truncated, we fixed it by restoring 
backup
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KFDWSRJGBRJGXKY6RT2HEHTCZWMOTYYC/

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-11 Thread Ales Musil 
Hello,

On Wed, Apr 10, 2019 at 2:26 PM Nardus Geldenhuys  wrote:

> Hi Milan
>
> Nothing special. We did the upgrade on two clusters. One is fine and this
> one is broken. Is there a way to rescan the cluster with all its VM's to
> pull information
>
> I did notice also that there is no NIC showing under the VM's network.
> When you trying to add one it complains that it exists but it is not
> showing.
>

That would mean that there is probably some corrupted information in the db
about the VM interface. Which might be the reason why there is NPE
in the libvirt XML process.

To which network was the VM interface connected?
Did something happened with the related network during upgrade?


>
> Thanks
>
> Nardus
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/PDCCB5C2YXSEBXDFJNFD6EKUVJATXUOT/
>


-- 

ALES MUSIL
Associate Software Engineer - rhv network

Red Hat EMEA 


amu...@redhat.com   IM: amusil

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ERNGYE2JHXHSKX2YCZPUH3FWENJGXTWH/

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-10 Thread Nardus Geldenhuys 
Hi Milan

Nothing special. We did the upgrade on two clusters. One is fine and this one 
is broken. Is there a way to rescan the cluster with all its VM's to pull 
information

I did notice also that there is no NIC showing under the VM's network. When you 
trying to add one it complains that it exists but it is not showing.

Thanks

Nardus
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PDCCB5C2YXSEBXDFJNFD6EKUVJATXUOT/

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-10 Thread Milan Zamazal 
Nardus Geldenhuys  writes:

> attached is the engine.log

> Can't find any logs containing the VM name on the host it was supposed
> to start. Seems that it does not even get to the host and that it
> fails in the ovirt engine

Thank you for the info.  The problem looks completely unrelated to the
cited bug.

The VM fails to start already in Engine due to a NullPointerException
when putting network interfaces into the VM domain XML.  So it's
probably unrelated to storage as well.  Something probably broke during
the upgrade regarding network interfaces attached to the VM.

Is there anything special about your network interfaces or is there
anything suspicious about them in Engine when the VM fails to start?

> On Wed, 10 Apr 2019 at 10:39, Milan Zamazal  wrote:
>
>> nard...@gmail.com writes:
>>
>> > Wonder if this issue is related to our problem and if there is a way
>> > around it. We upgraded from 4.2.8. to 4.3.2. Now when we start some of
>> > the VM's fail to start. You need to deattach the disks, create new VM,
>> > reattach the disks to the new VM and then the new VM starts.
>>
>> Hi, were those VMs previously migrated from a 4.2.8 to a 4.3.2 host or
>> to a 4.3.[01] host (which have the given bug)?
>>
>> Would it be possible to provide Vdsm logs from some of the failed and
>> successful (with the new VM) starts with the same storage and also from
>> the destination host of the preceding migration of the VM to a 4.3 host
>> (if the VM was migrated)?
>>
>> Thanks,
>> Milan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YS7IUTJKLYEG3EHFGT64MMHNL7R5AI6L/

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-10 Thread Nardus Geldenhuys 
It seems that ovirt-engine thinks that the storage is attached to a running VM. 
But it is not. Is there away to refresh these stats ?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RAD6THJISCDZBQHIBCVBUHYACXRJB7LS/

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-10 Thread Nardus Geldenhuys 
Can't find any logs containing the VM name on the host it was supposed to 
start. Seems that it does not even get to the host and that it fails in the 
ovirt engine
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TYTJ7SLSJTZH54AERIWEMYKUDM7PLW2F/

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-10 Thread Nardus Geldenhuys 
Can a moderator delete this post please. Can't find the option to delete it. 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SOLZQMJPFU6G3QY3BVLCCYREB3O3F2QQ/

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-10 Thread Nardus Geldenhuys 
attached is the engine.log

On Wed, 10 Apr 2019 at 10:39, Milan Zamazal  wrote:

> nard...@gmail.com writes:
>
> > Wonder if this issue is related to our problem and if there is a way
> > around it. We upgraded from 4.2.8. to 4.3.2. Now when we start some of
> > the VM's fail to start. You need to deattach the disks, create new VM,
> > reattach the disks to the new VM and then the new VM starts.
>
> Hi, were those VMs previously migrated from a 4.2.8 to a 4.3.2 host or
> to a 4.3.[01] host (which have the given bug)?
>
> Would it be possible to provide Vdsm logs from some of the failed and
> successful (with the new VM) starts with the same storage and also from
> the destination host of the preceding migration of the VM to a 4.3 host
> (if the VM was migrated)?
>
> Thanks,
> Milan
>
2019-04-10 10:09:46,786+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (default task-331) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Lock Acquired to object 'EngineLock:{exclusiveLocks='[81a82c39-4786-46db-b719-2808f736e359=VM]', sharedLocks=''}'
2019-04-10 10:09:46,831+02 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-331) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='81a82c39-4786-46db-b719-2808f736e359'}), log id: 2cbbd903
2019-04-10 10:09:46,832+02 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-331) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 2cbbd903
2019-04-10 10:09:46,922+02 INFO  [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-331) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Candidate host 's4-cluster-05.abc.co.za' ('e2e277d0-1fcb-4c39-8b43-f7931c18abf5') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: null)
2019-04-10 10:09:47,125+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Running command: RunVmCommand internal: false. Entities affected :  ID: 81a82c39-4786-46db-b719-2808f736e359 Type: VMAction group RUN_VM with role type USER
2019-04-10 10:09:47,196+02 INFO  [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Candidate host 's4-cluster-05.abc.co.za' ('e2e277d0-1fcb-4c39-8b43-f7931c18abf5') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: bcc741ae-2fc3-4c21-8fcd-e5d69c48946b)
2019-04-10 10:09:47,366+02 INFO  [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] START, UpdateVmDynamicDataVDSCommand( UpdateVmDynamicDataVDSCommandParameters:{hostId='null', vmId='81a82c39-4786-46db-b719-2808f736e359', vmDynamic='org.ovirt.engine.core.common.businessentities.VmDynamic@7b441365'}), log id: 1387e426
2019-04-10 10:09:47,394+02 INFO  [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] FINISH, UpdateVmDynamicDataVDSCommand, return: , log id: 1387e426
2019-04-10 10:09:47,397+02 INFO  [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] START, CreateVDSCommand( CreateVDSCommandParameters:{hostId='69e69c67-49a5-4af6-a754-ddbed3e11f03', vmId='81a82c39-4786-46db-b719-2808f736e359', vm='VM [s4-grandmama-db-01]'}), log id: 1935c97c
2019-04-10 10:09:47,398+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] START, CreateBrokerVDSCommand(HostName = s4-cluster-06.abc.co.za, CreateVDSCommandParameters:{hostId='69e69c67-49a5-4af6-a754-ddbed3e11f03', vmId='81a82c39-4786-46db-b719-2808f736e359', vm='VM [s4-grandmama-db-01]'}), log id: 18e44d16
2019-04-10 10:09:47,415+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Failed in 'CreateBrokerVDS' method, for vds: 's4-cluster-06.abc.co.za'; host: 's4-cluster-06.abc.co.za': null
2019-04-10 10:09:47,416+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Command 'CreateBrokerVDSCommand(HostName = s4-cluster-06.abc.co.za, CreateVDSCommandParameters:{hostId='69e69c67-49a5-4af6-a754-ddbed3e11f03', vmId='81a82c39-4786-46db-b719-2808f736e359', vm='VM [s4-grandmama-db-01]'})' execution failed: null
2019-04-10 10:09:47,416+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] FINISH, CreateBrokerVDSCommand, return: , log id: 18e44d16
2019-04-10 10:09:47,416+02

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-10 Thread Nardus Geldenhuys 
attaching ovirt engine.log
2019-04-10 10:09:46,786+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (default task-331) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Lock Acquired to object 'EngineLock:{exclusiveLocks='[81a82c39-4786-46db-b719-2808f736e359=VM]', sharedLocks=''}'
2019-04-10 10:09:46,831+02 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-331) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='81a82c39-4786-46db-b719-2808f736e359'}), log id: 2cbbd903
2019-04-10 10:09:46,832+02 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-331) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 2cbbd903
2019-04-10 10:09:46,922+02 INFO  [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-331) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Candidate host 's4-cluster-05.abc.co.za' ('e2e277d0-1fcb-4c39-8b43-f7931c18abf5') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: null)
2019-04-10 10:09:47,125+02 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Running command: RunVmCommand internal: false. Entities affected :  ID: 81a82c39-4786-46db-b719-2808f736e359 Type: VMAction group RUN_VM with role type USER
2019-04-10 10:09:47,196+02 INFO  [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Candidate host 's4-cluster-05.abc.co.za' ('e2e277d0-1fcb-4c39-8b43-f7931c18abf5') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: bcc741ae-2fc3-4c21-8fcd-e5d69c48946b)
2019-04-10 10:09:47,366+02 INFO  [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] START, UpdateVmDynamicDataVDSCommand( UpdateVmDynamicDataVDSCommandParameters:{hostId='null', vmId='81a82c39-4786-46db-b719-2808f736e359', vmDynamic='org.ovirt.engine.core.common.businessentities.VmDynamic@7b441365'}), log id: 1387e426
2019-04-10 10:09:47,394+02 INFO  [org.ovirt.engine.core.vdsbroker.UpdateVmDynamicDataVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] FINISH, UpdateVmDynamicDataVDSCommand, return: , log id: 1387e426
2019-04-10 10:09:47,397+02 INFO  [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] START, CreateVDSCommand( CreateVDSCommandParameters:{hostId='69e69c67-49a5-4af6-a754-ddbed3e11f03', vmId='81a82c39-4786-46db-b719-2808f736e359', vm='VM [s4-grandmama-db-01]'}), log id: 1935c97c
2019-04-10 10:09:47,398+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] START, CreateBrokerVDSCommand(HostName = s4-cluster-06.abc.co.za, CreateVDSCommandParameters:{hostId='69e69c67-49a5-4af6-a754-ddbed3e11f03', vmId='81a82c39-4786-46db-b719-2808f736e359', vm='VM [s4-grandmama-db-01]'}), log id: 18e44d16
2019-04-10 10:09:47,415+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Failed in 'CreateBrokerVDS' method, for vds: 's4-cluster-06.abc.co.za'; host: 's4-cluster-06.abc.co.za': null
2019-04-10 10:09:47,416+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Command 'CreateBrokerVDSCommand(HostName = s4-cluster-06.abc.co.za, CreateVDSCommandParameters:{hostId='69e69c67-49a5-4af6-a754-ddbed3e11f03', vmId='81a82c39-4786-46db-b719-2808f736e359', vm='VM [s4-grandmama-db-01]'})' execution failed: null
2019-04-10 10:09:47,416+02 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] FINISH, CreateBrokerVDSCommand, return: , log id: 18e44d16
2019-04-10 10:09:47,416+02 ERROR [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-47) [bcc741ae-2fc3-4c21-8fcd-e5d69c48946b] Failed to create VM: java.lang.NullPointerException
at org.ovirt.engine.core.vdsbroker.builder.vminfo.LibvirtVmXmlBuilder.lambda$writeInterfaces$30(LibvirtVmXmlBuilder.java:1250) [vdsbroker.jar:]
at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469) [rt.jar:1.8.0_201]
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355) [rt.jar:1.8.0_201]
at java.util.TimSort.sort(TimSort.java:220) [rt.jar:1.8.0_201]
at java.util.Arrays.sort(Arrays.java:1512) [rt.jar:1.8.0_201]
at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:348)

[ovirt-users] Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP

2019-04-10 Thread Milan Zamazal 
nard...@gmail.com writes:

> Wonder if this issue is related to our problem and if there is a way
> around it. We upgraded from 4.2.8. to 4.3.2. Now when we start some of
> the VM's fail to start. You need to deattach the disks, create new VM,
> reattach the disks to the new VM and then the new VM starts.

Hi, were those VMs previously migrated from a 4.2.8 to a 4.3.2 host or
to a 4.3.[01] host (which have the given bug)?

Would it be possible to provide Vdsm logs from some of the failed and
successful (with the new VM) starts with the same storage and also from
the destination host of the preceding migration of the VM to a 4.3 host
(if the VM was migrated)?

Thanks,
Milan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YTD2JB33JHP4ENVUMWVAOVZQXVRPAKJX/