[ovirt-users] Re: Storage domain in maintenance

2020-04-10 Thread Strahil Nikolov
The issue was found.

We are not looking for a directory with the exact name of the Storage Domain 
UUID, but we look for ALL directories that contain the Storage Domain UUID.

For example:
[root@ovirt3 gluster1:_data__fast4]# ll
общо 1
drwxrwxr-x. 5 vdsm kvm 48 10 ное 13,42 578bca3d-6540-41cd-8e0e-9e3047026484
drwxrwxr-x. 5 vdsm kvm 48 10 ное 13,42 578bca3d-6540-41cd-8e0e-9e3047026484-NEW

[root@ovirt3 gluster1:_data__fast]# ll
общо 1
drwxrwxrwx. 6 vdsm kvm 59 11 апр  6,30 396604d9-2a9e-49cd-9563-fdc79981f67b
drwxr-xr-x. 5 vdsm kvm 48 19 ное 21,32 396604d9-2a9e-49cd-9563-fdc79981f67b-OLD

As 578bca3d-6540-41cd-8e0e-9e3047026484-NEW & 
396604d9-2a9e-49cd-9563-fdc79981f67b-OLD are not valid SDuuids - the activation 
fails.

I have opened a bug for it (not sure on the correct Product/Component) :
https://bugzilla.redhat.com/show_bug.cgi?id=1823033

Hey Sandro,

is this expected, as I never saw it as a requirement ?
If it is expected (already in the docs), please mark 1823033 "notabug".

Best Regards,
Strahil Nikolov






В вторник, 7 април 2020 г., 23:13:43 Гринуич+3, Strahil Nikolov 
 написа: 





Hi Shani,

thanks for the asitance.
First atempt to activate storage domain "data_fast" (for today) which is ontop 
gluster volume "data_fast":


So Far I see the following when I filter "INFO" on the engine:
2020-04-07 22:44:55,760+03 ERROR 
[org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-100115) 
[7de0d120-fde0-4471-9032-f10e69d2e54
0] Failed in 'ActivateStorageDomainVDS' method
2020-04-07 22:44:55,781+03 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engine-Thread-100115) 
[7de0d120-fde0-4471-9032-f10e69d2e540] EV
ENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command 
ActivateStorageDomainVDS failed: Storage domain does not exist: 
(u'396604d9-2a9e-49cd-9563-fdc79981f67b',)
2020-04-07 22:44:55,781+03 ERROR 
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] 
(EE-ManagedThreadFactory-engine-Thread-100115) 
[7de0d120-fde0-4471-9032-f10e69d2e540] IrsBroker::F
ailed::ActivateStorageDomainVDS: IRSGenericException: IRSErrorException: Failed 
to ActivateStorageDomainVDS, error = Storage domain does not exist: 
(u'396604d9-2a9e-49cd-9563-fdc79981f67b',),
code = 358
2020-04-07 22:44:56,223+03 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engine-Thread-100115) [174bb3e2] EVENT_ID: 
SYSTEM_CHANGE_STORAG
E_POOL_STATUS_PROBLEMATIC_SEARCHING_NEW_SPM(986), Data Center is being 
initialized, please wait for initialization to complete.
2020-04-07 22:44:58,086+03 ERROR 
[org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-100115) [174bb3e2] Failed in 
'ActivateStorag
eDomainVDS' method
2020-04-07 22:44:58,106+03 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engine-Thread-100115) [174bb3e2] EVENT_ID: 
IRS_BROKER_COMMAND_F
AILURE(10,803), VDSM command ActivateStorageDomainVDS failed: Storage domain 
does not exist: (u'396604d9-2a9e-49cd-9563-fdc79981f67b',)
2020-04-07 22:44:58,106+03 ERROR 
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] 
(EE-ManagedThreadFactory-engine-Thread-100115) [174bb3e2] 
IrsBroker::Failed::ActivateStorageDomain
VDS: IRSGenericException: IRSErrorException: Failed to 
ActivateStorageDomainVDS, error = Storage domain does not exist: 
(u'396604d9-2a9e-49cd-9563-fdc79981f67b',), code = 358
2020-04-07 22:44:58,345+03 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engine-Thread-100115) [3ac80a6] EVENT_ID: 
SYSTEM_CHANGE_STORAGE
_POOL_STATUS_PROBLEMATIC_SEARCHING_NEW_SPM(986), Data Center is being 
initialized, please wait for initialization to complete.
2020-04-07 22:45:00,222+03 ERROR 
[org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-100115) [3ac80a6] Failed in 
'ActivateStorage
DomainVDS' method
2020-04-07 22:45:00,240+03 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engine-Thread-100115) [3ac80a6] EVENT_ID: 
IRS_BROKER_COMMAND_FA
ILURE(10,803), VDSM command ActivateStorageDomainVDS failed: Storage domain 
does not exist: (u'396604d9-2a9e-49cd-9563-fdc79981f67b',)
2020-04-07 22:45:00,241+03 ERROR 
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] 
(EE-ManagedThreadFactory-engine-Thread-100115) [3ac80a6] 
IrsBroker::Failed::ActivateStorageDomainV
DS: IRSGenericException: IRSErrorException: Failed to ActivateStorageDomainVDS, 
error = Storage domain does not exist: 
(u'396604d9-2a9e-49cd-9563-fdc79981f67b',), code = 358
2020-04-07 22:45:00,241+03 ERROR 
[org.ovirt.engine.core.bll.storage.domain.ActivateStorageDomainCommand] 
(EE-ManagedThreadFactory-engine-Thread-100115) [3ac80a6] Command 

[ovirt-users] Re: Can't migrate over migration network

2020-04-10 Thread Brian Dumont
Evan,

Thanx for your help.  I think I've got the Networks setup correctly on the
Setup Hosts Network section, but obviously I've got something fundamentally
wrong.

Just can't figure it out.

Thanx again

On Fri, Apr 10, 2020 at 5:14 PM Brian Dumont  wrote:

> Thanx for the note.  Still not working.  I made the change on the hosts
> and manager and then added the custom ip addresses to the ovirtmgmt
> network.   The attached screenshot shows the custom IP address added to
> ovirtmgmt.
>
> Same issue.
>
> 2020-04-10 21:05:13.882+: 5801: error : virNetSocketNewConnectTCP:591
> : unable to connect to server at '192.168.25.5:49152': No route to host.
>
> I can ping the 192.168.25.x address on the host - but I can't ping the
> .25.x address on the other host.
>
> I also can't ping either 192.168.25.x address from the manager.
>
> One question I had is does the migration network need to be a VM Network?
> I've tried it several ways - but just wanted to know the right
> configuration.
>
> Thanx!!!
>
> On Fri, Apr 10, 2020 at 3:55 PM  wrote:
>
>> Thanx for the suggestion.  Changed my networks to the following and still
>> got the same error:
>>
>> 5801: error : virNetSocketNewConnectTCP:591 : unable to connect to server
>> at '192.168.25.5:49152': No route to host
>>
>> Here is my updated configuration:
>> - 2 Hosts
>> - Host 1
>> - nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1
>> - nic 2 - migration network - 192.168.25.5/24 VLAN 25
>> - Host 2
>> - nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1
>> - nic 2 - migration network - 192.168.25.6/24 - VLAN 25
>>
>> Migration network is setup as follows:
>> - Assign - Yes
>> - Required - Yes
>> - VM Network - No (tried it with VM Nework = Yes with same results)
>> - Migration Network - Yes
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLS2EVPDQDHIKMWLLQVMHOPL22CQVQB2/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SOIMP6M5O7JIJB2WKMIIJZ6OLCPSXWHL/


[ovirt-users] Re: Can't migrate over migration network

2020-04-10 Thread eevans
I migrate over the vm network. 

You need to ask someone more familiar with Ovirt about the migration vs. the vm 
network. I have had issue getting different subnets for the vm’s to function 
properly. My understanding is that if the engine host knows and can use the 
network, you should be able to use it. However, the migration network has to be 
setup on the hosts and attached to a nic in order to use it. In the host 
properties and setup networks, is the migration network attached to a nic with 
the proper subnets or vlans? 

I’m not sure if that’s helpful or not. I just don’t know enough about Ovirt to 
give a definitive answer.

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Brian Dumont  
Sent: Friday, April 10, 2020 5:15 PM
To: users@ovirt.org
Subject: [ovirt-users] Re: Can't migrate over migration network

 

Thanx for the note.  Still not working.  I made the change on the hosts and 
manager and then added the custom ip addresses to the ovirtmgmt network.   The 
attached screenshot shows the custom IP address added to ovirtmgmt.

Same issue.

2020-04-10 21:05:13.882+: 5801: error : virNetSocketNewConnectTCP:591 : 
unable to connect to server at '192.168.25.5:49152  
': No route to host.

 

I can ping the 192.168.25.x address on the host - but I can't ping the .25.x 
address on the other host.

 

I also can't ping either 192.168.25.x address from the manager.

One question I had is does the migration network need to be a VM Network?  I've 
tried it several ways - but just wanted to know the right configuration.

 

Thanx!!!

 

On Fri, Apr 10, 2020 at 3:55 PM mailto:briandum...@gmail.com> > wrote:

Thanx for the suggestion.  Changed my networks to the following and still got 
the same error:

5801: error : virNetSocketNewConnectTCP:591 : unable to connect to server at 
'192.168.25.5:49152  ': No route to host

Here is my updated configuration:
- 2 Hosts
- Host 1
- nic 1 - ovirtmgmt - 192.168.1.24/24   - VLAN 1
- nic 2 - migration network - 192.168.25.5/24   VLAN 25
- Host 2
- nic 1 - ovirtmgmnt - 192.168.1.24/24   - VLAN 1
- nic 2 - migration network - 192.168.25.6/24   - VLAN 
25

Migration network is setup as follows:
- Assign - Yes
- Required - Yes
- VM Network - No (tried it with VM Nework = Yes with same results)
- Migration Network - Yes
___
Users mailing list -- users@ovirt.org  
To unsubscribe send an email to users-le...@ovirt.org 
 
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLS2EVPDQDHIKMWLLQVMHOPL22CQVQB2/


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


[ovirt-users] Re: Windows 10 Pro 64 (1909) crashes when migrating

2020-04-10 Thread eevans
I found this thread on Stack overflow:

https://stackoverflow.com/questions/9077457/how-to-trace-tcmalloc-large-alloc

 

See  

 
http://code.google.com/p/gperftools/source/browse/trunk/src/tcmalloc.cc?r=80=1
 line 843

Depending on your application - the large allocation may or may not be a bug.

In any case - the part after the @ mark is a stack trace and can be used to 
locate the source of the message

The repeating number (4294488064 which seems to be equal to 4G-479232 or 
0x1-0x75000) makes me suspect the original allocation call got a 
negative signed value and used it as an unsigned value.

It also had this to trace the memory leak:

to trace the mem address to a line in your code, use addr2line commandline 
tool.. use it as addr2line -e  then press enter and then paste 
an address and press enter

 

I’m not sure if this is helpful but it does sound like a memory leak.

 

In a related Microsoft doc it stated:

 

1073741824 Allocations larger than this value cause a stack trace to be 
dumped to stderr. The threshold for dumping stack traces is increased by a 
factor of 1.125 every time we print a message so that the threshold 
automatically goes up by a factor of ~1000 every 60 messages. This bounds the 
amount of extra logging generated by this flag. Default value of this flag is 
very large and therefore you should see no extra logging unless the flag is 
overridden.

 

The default in Windows is 1 GB. I’m not sure about Linux.

 

I hope this is helpful.

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Maton, Brett  
Sent: Friday, April 10, 2020 4:53 PM
To: eev...@digitaldatatechs.com
Cc: Ovirt Users 
Subject: [ovirt-users] Re: Windows 10 Pro 64 (1909) crashes when migrating

 

The hosts are identical, and yes I'm sure about the 563 terrabytes, which is 
obviously wrong, and why I mentioned it. Possibly an overflow?

 

On Fri, 10 Apr 2020, 21:31 , mailto:eev...@digitaldatatechs.com> > wrote:

I have a Windows 10 guest and a Server 2016 guest that migrate without an issue.
Are your CPU architectures comparable between the hosts? 
BTW,  56294995342131 bytes is 562 terabytes. Are you sure that's correct?
___
Users mailing list -- users@ovirt.org  
To unsubscribe send an email to users-le...@ovirt.org 
 
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7JDAC6SVJIPJRMLDHHZIREUGC3EDR6FP/


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


[ovirt-users] Re: Can't migrate over migration network

2020-04-10 Thread Brian Dumont
Thanx for the note.  Still not working.  I made the change on the hosts and
manager and then added the custom ip addresses to the ovirtmgmt network.
The attached screenshot shows the custom IP address added to ovirtmgmt.

Same issue.

2020-04-10 21:05:13.882+: 5801: error : virNetSocketNewConnectTCP:591 :
unable to connect to server at '192.168.25.5:49152': No route to host.

I can ping the 192.168.25.x address on the host - but I can't ping the
.25.x address on the other host.

I also can't ping either 192.168.25.x address from the manager.

One question I had is does the migration network need to be a VM Network?
I've tried it several ways - but just wanted to know the right
configuration.

Thanx!!!

On Fri, Apr 10, 2020 at 3:55 PM  wrote:

> Thanx for the suggestion.  Changed my networks to the following and still
> got the same error:
>
> 5801: error : virNetSocketNewConnectTCP:591 : unable to connect to server
> at '192.168.25.5:49152': No route to host
>
> Here is my updated configuration:
> - 2 Hosts
> - Host 1
> - nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1
> - nic 2 - migration network - 192.168.25.5/24 VLAN 25
> - Host 2
> - nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1
> - nic 2 - migration network - 192.168.25.6/24 - VLAN 25
>
> Migration network is setup as follows:
> - Assign - Yes
> - Required - Yes
> - VM Network - No (tried it with VM Nework = Yes with same results)
> - Migration Network - Yes
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLS2EVPDQDHIKMWLLQVMHOPL22CQVQB2/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4ORHNDKBCINPTARNE76N7FGJICM4DCBS/


[ovirt-users] Re: Windows 10 Pro 64 (1909) crashes when migrating

2020-04-10 Thread Maton, Brett
The hosts are identical, and yes I'm sure about the 563 terrabytes, which
is obviously wrong, and why I mentioned it. Possibly an overflow?

On Fri, 10 Apr 2020, 21:31 ,  wrote:

> I have a Windows 10 guest and a Server 2016 guest that migrate without an
> issue.
> Are your CPU architectures comparable between the hosts?
> BTW,  56294995342131 bytes is 562 terabytes. Are you sure that's correct?
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7JDAC6SVJIPJRMLDHHZIREUGC3EDR6FP/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YRJ2QS4NXAKISWRMPOFHDO74V63ARPBN/


[ovirt-users] Re: Windows 10 Pro 64 (1909) crashes when migrating

2020-04-10 Thread eevans
I have a Windows 10 guest and a Server 2016 guest that migrate without an issue.
Are your CPU architectures comparable between the hosts? 
BTW,  56294995342131 bytes is 562 terabytes. Are you sure that's correct?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7JDAC6SVJIPJRMLDHHZIREUGC3EDR6FP/


[ovirt-users] Re: Firewall GARP not reachable to VM

2020-04-10 Thread eevans
Just an educated guess but you are missing a route to the GARP firewall. Are 
the firewalls on the same subnet? 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6U6KLEF76TOPNEPVZXMMZFE5QH73XONJ/


[ovirt-users] multiple subnets on hosts for vm's

2020-04-10 Thread eevans
This is not critical but some functionality I think should be in Ovirt and 
maybe I am going about it the wrong way. 
I have several subnets on my physical network. My engine host is separate from 
the clustered hosts that house  the vm's. In order for the vm's on the other 
subnets (vlans) to get Internet access, I have to add the extra ip addrs on the 
ovirtmgmt network interface. 
I have read and tried every solution I could find trying to add teh subnets 
without using the extra ip addrs option but the machine either becomes isolated 
or will not start at all.
Can someone tell me how to add the vlans so the engine host sees and utilizes 
them? 
The engine host can get to resources on the vlans because of the router config 
but will not let any subnet except ovirtmgmt outside the cluster.
This is not critical but something I would like to get working for future 
deployments.
Thank you for your help.
Eric
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q6HSXIGWABX2KB5ZPHD4CDNJQ6MIMPSJ/


[ovirt-users] Re: Can't migrate over migration network

2020-04-10 Thread eevans
Follow this article to add the extra addrs. On the ovirtmgmt interface on the 
hosts, go to custom  and add the IP's you need. See the attached screenshot.
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/sect-Hosts_and_Networking#Editing-VLAN-Settings
That should take care of the problem for you.


Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: briandum...@gmail.com  
Sent: Friday, April 10, 2020 3:55 PM
To: users@ovirt.org
Subject: [ovirt-users] Re: Can't migrate over migration network

Thanx for the suggestion.  Changed my networks to the following and still got 
the same error:

5801: error : virNetSocketNewConnectTCP:591 : unable to connect to server at 
'192.168.25.5:49152': No route to host

Here is my updated configuration:
- 2 Hosts
- Host 1
- nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.25.5/24 VLAN 25
- Host 2
- nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.25.6/24 - VLAN 25

Migration network is setup as follows:
- Assign - Yes
- Required - Yes
- VM Network - No (tried it with VM Nework = Yes with same results)
- Migration Network - Yes
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: 
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLS2EVPDQDHIKMWLLQVMHOPL22CQVQB2/

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


[ovirt-users] Re: Can't migrate over migration network

2020-04-10 Thread briandumont
Thanx for the suggestion.  Changed my networks to the following and still got 
the same error:

5801: error : virNetSocketNewConnectTCP:591 : unable to connect to server at 
'192.168.25.5:49152': No route to host

Here is my updated configuration:
- 2 Hosts
- Host 1
- nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.25.5/24 VLAN 25
- Host 2
- nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.25.6/24 - VLAN 25

Migration network is setup as follows:
- Assign - Yes
- Required - Yes
- VM Network - No (tried it with VM Nework = Yes with same results)
- Migration Network - Yes
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLS2EVPDQDHIKMWLLQVMHOPL22CQVQB2/


[ovirt-users] Re: Data domain down due to space crunch

2020-04-10 Thread eevans
What is filling the drive up? Logs? Temp files? Find out what is using the 
space and either delete it or compress it. 

 

Eric Evans

Digital Data Services LLC.

304.660.9080



 

From: Crazy Ayansh  
Sent: Friday, April 10, 2020 12:56 PM
To: users 
Subject: [ovirt-users] Re: Data domain down due to space crunch

 

Any help or suggestions would be appreciated.

 

On Wed, Apr 8, 2020, 6:25 PM Crazy Ayansh mailto:shashank123rast...@gmail.com> > wrote:

Hi Guys,

 

I am using Ovirt 4.3.7 in my environment.I am using servers local storage for 
data domains. Today one of the servers data domain got full and due to this my 
VMs paused.



 

Now i am unable to export my VM as the storage in ovirt is down.What should 
i do now.any suggestions.?

 

Thanks


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


[ovirt-users] Re: Can't migrate over migration network

2020-04-10 Thread eevans
Apologies, vlans 1 and 25. They should be separate subnets.

Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: briandum...@gmail.com  
Sent: Friday, April 10, 2020 1:48 PM
To: users@ovirt.org
Subject: [ovirt-users] Can't migrate over migration network

Hello,

I am trying to configure a dedicated migration network and am unable to get it 
to work.  It is failing with a no route to host error in the cockpit logs, 
specifically  a libvirtd error virNetSocketNewConnectTCP:591 : unable to 
connect to server at '192.168.1.50:49152': No route to host.  Trying to migrate 
from Host 1 to Host 2.  192.168.1.50 is the ip address on the source host for 
the migration.  

If I try to migrate in the other direction I get the same error with tthat 
hosts migration network ip.

My migration network is setup on a different VLAN than my ovirtmgmt network.

Here is my configuration:
- 2 Hosts
  - Host 1 
- nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.1.50/24 VLAN 25
  - Host 2
- nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.1.51/24 - VLAN 25

Migration network is setup as follows:
  - Assign - Yes
  - Required - Yes
  - VM Network - No (tried it with VM Nework = Yes with same results)
  - Migration Network - Yes

I think I've got something fundamentally wrong with my host networking but I 
can't figure it out.

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


[ovirt-users] Re: Can't migrate over migration network

2020-04-10 Thread eevans
Just pointing out the obvious, but you have vlan 1 and 50 on the same subnet 
unless it's a mistype.

Eric Evans
Digital Data Services LLC.
304.660.9080


-Original Message-
From: briandum...@gmail.com  
Sent: Friday, April 10, 2020 1:48 PM
To: users@ovirt.org
Subject: [ovirt-users] Can't migrate over migration network

Hello,

I am trying to configure a dedicated migration network and am unable to get it 
to work.  It is failing with a no route to host error in the cockpit logs, 
specifically  a libvirtd error virNetSocketNewConnectTCP:591 : unable to 
connect to server at '192.168.1.50:49152': No route to host.  Trying to migrate 
from Host 1 to Host 2.  192.168.1.50 is the ip address on the source host for 
the migration.  

If I try to migrate in the other direction I get the same error with tthat 
hosts migration network ip.

My migration network is setup on a different VLAN than my ovirtmgmt network.

Here is my configuration:
- 2 Hosts
  - Host 1 
- nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.1.50/24 VLAN 25
  - Host 2
- nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.1.51/24 - VLAN 25

Migration network is setup as follows:
  - Assign - Yes
  - Required - Yes
  - VM Network - No (tried it with VM Nework = Yes with same results)
  - Migration Network - Yes

I think I've got something fundamentally wrong with my host networking but I 
can't figure it out.

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


[ovirt-users] Can't migrate over migration network

2020-04-10 Thread briandumont
Hello,

I am trying to configure a dedicated migration network and am unable to get it 
to work.  It is failing with a no route to host error in the cockpit logs, 
specifically  a libvirtd error virNetSocketNewConnectTCP:591 : unable to 
connect to server at '192.168.1.50:49152': No route to host.  Trying to migrate 
from Host 1 to Host 2.  192.168.1.50 is the ip address on the source host for 
the migration.  

If I try to migrate in the other direction I get the same error with tthat 
hosts migration network ip.

My migration network is setup on a different VLAN than my ovirtmgmt network.

Here is my configuration:
- 2 Hosts
  - Host 1 
- nic 1 - ovirtmgmt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.1.50/24 VLAN 25
  - Host 2
- nic 1 - ovirtmgmnt - 192.168.1.24/24 - VLAN 1
- nic 2 - migration network - 192.168.1.51/24 - VLAN 25

Migration network is setup as follows:
  - Assign - Yes
  - Required - Yes
  - VM Network - No (tried it with VM Nework = Yes with same results)
  - Migration Network - Yes

I think I've got something fundamentally wrong with my host networking but I 
can't figure it out.

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


[ovirt-users] Re: Data domain down due to space crunch

2020-04-10 Thread Crazy Ayansh
Any help or suggestions would be appreciated.

On Wed, Apr 8, 2020, 6:25 PM Crazy Ayansh 
wrote:

> Hi Guys,
>
> I am using Ovirt 4.3.7 in my environment.I am using servers local storage
> for data domains. Today one of the servers data domain got full and due to
> this my VMs paused.
> [image: image.png]
>
> Now i am unable to export my VM as the storage in ovirt is down.What
> should i do now.any suggestions.?
>
> Thanks
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IABUENU562JWUOMK6P5AUZWXP2SGCRP2/


[ovirt-users] Re: Ovirt and Dell Compellent in ISCSI

2020-04-10 Thread dalmasso

Hi, 

thank you. 
Effecttivly , It's really a lack of not having good support for ISCSI. 

Sylvain 


De: "Vinícius Ferrão"  
À: dalma...@cines.fr 
Cc: "Shani Leviim" , "users"  
Envoyé: Jeudi 9 Avril 2020 16:06:19 
Objet: Re: [ovirt-users] Re: Ovirt and Dell Compellent in ISCSI 

It’s the same problem all over again. 

iSCSI in oVirt/RHV is broken. For years. 

Reported this a while: [ https://bugzilla.redhat.com/show_bug.cgi?id=1474904 | 
https://bugzilla.redhat.com/show_bug.cgi?id=1474904 ] 

iSCSI Multipath in the engine does not means a thing. It’s broken. 

I don’t know why the oVirt team does not acknowledge this. I’m being an idiot 
always answering and inquiring about this, but I can’t understand why anyone 
doesn’t take this seriously. It’s real, it’s affects everyone and simply does 
not makes sense. 


Sent from my iPhone 



On 9 Apr 2020, at 10:39, "dalma...@cines.fr"  wrote: 





BQ_BEGIN

Hi Shani, 
thank's for the reply. 
In this case, the bounding, I think, is inapropriate. 
The dell compellent has 2 "fault domain" with différent IP network 
This is a iSCSI array with 8 front-end ports (4 per controller). The iSCSI 
network is simple: two independant switches with a single VLAN, front-end ports 
are split equally between the two switches. 
And for each serveur one Ethernet controller is connected on each switch. So, 
bonding seems inappropriate. 
(see this dell documentation : [ 
https://downloads.dell.com/manuals/common/scv30x0iscsi-setup_en.pdf | 
https://downloads.dell.com/manuals/common/scv30x0iscsi-setup_en.pdf ] ) 
Maybe I misunderstood how iscsi bonding work in ovirt ? 

Regards, 
Sylvain 


De: "Shani Leviim"  
À: dalma...@cines.fr 
Cc: "users"  
Envoyé: Mardi 7 Avril 2020 15:41:16 
Objet: Re: [ovirt-users] Ovirt and Dell Compellent in ISCSI 

Hi Sylvain, 
Not sure that's exactly what you're looking for, but you can define an iscsi 
bond (iscsi multipath) using the UI and REST API: 
[ 
https://www.ovirt.org/develop/release-management/features/storage/iscsi-multipath.html
 | 
https://www.ovirt.org/develop/release-management/features/storage/iscsi-multipath.html
 ] 

Note that this is a character of the DC. 

Hope it helps. 

Regards, 
Shani Leviim 


On Wed, Apr 1, 2020 at 12:35 PM < [ mailto:dalma...@cines.fr | 
dalma...@cines.fr ] > wrote: 

BQ_BEGIN
hi all, 
we use ovirt 4.3 on dell server r640 runing centos 7.7 and a storage bay Dell 
Compellent SCv3020 in ISCSI. 
We use two 10gb interfaces for iSCSI connection on each dell server. 
If we configure ISCSI connection directly from web IU, we can’t specify the two 
physical ethernet interface , and there are missing path . (only 4 path on 8) 
So, on the shell of hypervisor we use this commands for configure the 
connections : 
iscsiadm -m iface -I em1 --op=new # 1st ethernet interface 
iscsiadm -m iface -I p3p1 --op=new # 2d ethernet interface 
iscsiadm -m discovery -t sendtargets -p xx.xx.xx.xx 
iscsiadm -m node -o show 
iscsiadm -m node --login 
after this, on the web IU we can connect our LUN with all path. 

Also, I don’t understand how to configure multipath in the web UI . By defaut 
the configuration is in failover : 
multipath -ll : 
36000d3100457e405 dm-3 COMPELNT,Compellent Vol 
size=500G features='1 queue_if_no_path' hwhandler='0' wp=rw 
`-+- policy='service-time 0' prio=1 status=active 
|- 23:0:0:1 sdb 8:16 active ready running 
|- 24:0:0:1 sdd 8:48 active ready running 
|- 25:0:0:1 sdc 8:32 active ready running 
|- 26:0:0:1 sde 8:64 active ready running 
|- 31:0:0:1 sdf 8:80 active ready running 
|- 32:0:0:1 sdg 8:96 active ready running 
|- 33:0:0:1 sdh 8:112 active ready running 
|- 34:0:0:1 sdi 8:128 active ready running 

I think round robind or another configuration will be more performent. 

So can we made this configuration , select physical interface and configure 
multipath in web UI ? for easyly maintenance and adding other server ? 

Thank you. 

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

BQ_END


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

[ovirt-users] Re: ovirt-engine unresponsive - how to rescue?

2020-04-10 Thread Shareef Jalloq
Where should I be checking if there are any files/folder not owned by
vdsm:kvm?  I checked on the mount the HA sits on and it's fine.

How would I go about checking vdsm can access those images?  If I run
virsh, it lists them and they were running yesterday even though the HA was
down.  I've since restarted both hosts but the broker is still spitting out
the same error (copied below).  How do I find the reason the broker can't
connect to the storage?  The conf file is already at DEBUG verbosity:

[handler_logfile]

class=logging.handlers.TimedRotatingFileHandler

args=('/var/log/ovirt-hosted-engine-ha/broker.log', 'd', 1, 7)

level=DEBUG

formatter=long

And what are all these .prob- files that are being created?  There are
over 250K of them now on the mount I'm using for the Data domain.  They're
all of 0 size and of the form, /rhev/data-center/mnt/nas-01.phoelex.com:
_volume2_vmstore/.prob-ffa867da-93db-4211-82df-b1b04a625ab9

@eevans:  The volume I have the Data Domain on has TB's free.  The HA is
dead so I can't ssh in.  No idea what started these errors and the other
VMs were still running happily although they're on a different Data Domain.

Shareef.

MainThread::INFO::2020-04-10
07:45:00,408::storage_backends::373::ovirt_hosted_engine_ha.lib.storage_backends::(connect)
Connecting the storage

MainThread::INFO::2020-04-10
07:45:00,408::storage_server::349::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server)
Connecting storage server

MainThread::INFO::2020-04-10
07:45:01,577::storage_server::356::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server)
Connecting storage server

MainThread::INFO::2020-04-10
07:45:02,692::storage_server::413::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server)
Refreshing the storage domain

MainThread::WARNING::2020-04-10
07:45:05,175::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__)
Can't connect vdsm storage: Command StorageDomain.getInfo with args
{'storagedomainID': 'a6cea67d-dbfb-45cf-a775-b4d0d47b26f2'} failed:

(code=350, message=Error in storage domain action:
(u'sdUUID=a6cea67d-dbfb-45cf-a775-b4d0d47b26f2',))

On Thu, Apr 9, 2020 at 5:58 PM Strahil Nikolov 
wrote:

> On April 9, 2020 11:12:30 AM GMT+03:00, Shareef Jalloq <
> shar...@jalloq.co.uk> wrote:
> >OK, let's go through this.  I'm looking at the node that at least still
> >has
> >some VMs running.  virsh also tells me that the HostedEngine VM is
> >running
> >but it's unresponsive and I can't shut it down.
> >
> >1. All storage domains exist and are mounted.
> >2. The ha_agent exists:
> >
> >[root@ovirt-node-01 ovirt-hosted-engine-ha]# ls /rhev/data-center/mnt/
> >nas-01.phoelex.com
> \:_volume2_vmstore/a6cea67d-dbfb-45cf-a775-b4d0d47b26f2/
> >
> >dom_md  ha_agent  images  master
> >
> >3.  There are two links
> >
> >[root@ovirt-node-01 ovirt-hosted-engine-ha]# ll /rhev/data-center/mnt/
> >nas-01.phoelex.com
> >\:_volume2_vmstore/a6cea67d-dbfb-45cf-a775-b4d0d47b26f2/ha_agent/
> >
> >total 8
> >
> >lrwxrwxrwx. 1 vdsm kvm 132 Apr  2 14:50 hosted-engine.lockspace ->
>
> >/var/run/vdsm/storage/a6cea67d-dbfb-45cf-a775-b4d0d47b26f2/ffb90b82-42fe-4253-85d5-aaec8c280aaf/90e68791-0c6f-406a-89ac-e0d86c631604
> >
> >lrwxrwxrwx. 1 vdsm kvm 132 Apr  2 14:50 hosted-engine.metadata ->
>
> >/var/run/vdsm/storage/a6cea67d-dbfb-45cf-a775-b4d0d47b26f2/2161aed0-7250-4c1d-b667-ac94f60af17e/6b818e33-f80a-48cc-a59c-bba641e027d4
> >
> >4. The services exist but all seem to have some sort of warning:
> >
> >a) Apr 08 18:10:55 ovirt-node-01.phoelex.com sanlock[1728]: *2020-04-08
> >18:10:55 1744152 [36796]: s16 delta_renew long write time 10 sec*
> >
> >b) Mar 23 18:02:59 ovirt-node-01.phoelex.com supervdsmd[29409]: *failed
> >to
> >load module nvdimm: libbd_nvdimm.so.2: cannot open shared object file:
> >No
> >such file or directory*
> >
> >c) Apr 09 08:05:13 ovirt-node-01.phoelex.com vdsm[4801]: *ERROR failed
> >to
> >retrieve Hosted Engine HA score '[Errno 2] No such file or directory'Is
> >the
> >Hosted Engine setup finished?*
> >
> >d)Apr 08 22:48:27 ovirt-node-01.phoelex.com libvirtd[29307]: 2020-04-08
> >22:48:27.134+: 29309: warning : qemuGetProcessInfo:1404 : cannot
> >parse
> >process status data
> >
> >Apr 08 22:48:27 ovirt-node-01.phoelex.com libvirtd[29307]: 2020-04-08
> >22:48:27.134+: 29309: error : virNetDevTapInterfaceStats:764 :
> >internal
> >error: /proc/net/dev: Interface not found
> >
> >Apr 08 23:09:39 ovirt-node-01.phoelex.com libvirtd[29307]: 2020-04-08
> >23:09:39.844+: 29307: error : virNetSocketReadWire:1806 : End of
> >file
> >while reading data: Input/output error
> >
> >Apr 09 01:05:26 ovirt-node-01.phoelex.com libvirtd[29307]: 2020-04-09
> >01:05:26.660+: 29307: error : virNetSocketReadWire:1806 : End of
> >file
> >while reading data: Input/output error
> >
> >5 & 6.  The broker log is continually printing this error:
> >
> >MainThread::INFO::2020-04-09
>