Re: [ovirt-users] Cloning VM on NFS Leads to Locked Disks

[Charles Tassell]

Sure, it's pretty big so I've put it online for download at 
http://krissy.islandadmin.ca/public/engine.log.txt


On 2017-05-11 04:08 PM, Fred Rolland wrote:
The locking is on the engine side and restarting the vdsm will not 
affect it .

Can you send the whole engine log ?
Which exact version are you using ?


On Thu, May 11, 2017 at 9:30 PM, Charles Tassell 
> wrote:


Just as an update, I created a new VM and had the same issue: the
disk remains locked.  So I then added a new data store (this one
iSCSI not NFS) and create a new VM on that.  Again, the disk
remains locked.  So the problem seems to be that any action that
sets to modify a disk image on my cluster locks the disk and keeps
it locked permanently.

I tried restarting the vdsm daemon, but that didn't make a
difference.  I'm seeing this in my sanlock.log file though, which
worries me:


017-05-07 07:51:41-0300 1738538 [13575]: s2 renewal error -202
delta_length 10 last_success 1738508
2017-05-07 07:51:41-0300 1738538 [11513]: s1 renewal error -202
delta_length 10 last_success 1738508

Here's the last 20 lines:
2017-05-07 07:51:41-0300 1738538 [13580]: s3 renewal error -202
delta_length 10 last_success 1738508
2017-05-07 07:51:41-0300 1738538 [13575]: 20423d5e aio timeout RD
0x7fe1440008c0:0x7fe1440008d0:0x7fe160255000 ioto 10 to_count 67
2017-05-07 07:51:41-0300 1738538 [13575]: s2 delta_renew read
timeout 10 sec offset 0

/rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-4e10-9893-588ceb81b354/dom_md/ids
2017-05-07 07:51:41-0300 1738538 [13575]: s2 renewal error -202
delta_length 10 last_success 1738508
2017-05-07 07:51:41-0300 1738538 [11513]: hosted-e aio timeout RD
0x7fe1480008c0:0x7fe1480008d0:0x7fe14e6fc000 ioto 10 to_count 65
2017-05-07 07:51:41-0300 1738538 [11513]: s1 delta_renew read
timeout 10 sec offset 0

/var/run/vdsm/storage/5dccd07d-a923-4d4b-9cb1-3b51ebfdca4d/5a9c284f-0faa-4a25-94ce-c9efdae07484/ab2443f1-95ed-475d-886c-c1653257cf04
2017-05-07 07:51:41-0300 1738538 [11513]: s1 renewal error -202
delta_length 10 last_success 1738508
2017-05-07 07:51:47-0300 1738544 [13575]: 20423d5e aio collect RD
0x7fe1440008c0:0x7fe1440008d0:0x7fe160255000 result 1048576:0
match reap
2017-05-07 07:51:47-0300 1738544 [13580]: 5dccd07d aio collect RD
0x7fe13c0008c0:0x7fe13c0008d0:0x7fe14e5fa000 result 1048576:0
match reap
2017-05-07 07:51:47-0300 1738544 [11513]: hosted-e aio collect RD
0x7fe1480008c0:0x7fe1480008d0:0x7fe14e6fc000 result 1048576:0
match reap
2017-05-07 07:53:57-0300 1738674 [13590]: s2:r15 resource

20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-4e10-9893-588ceb81b354/dom_md/leases:1048576
for 7,21,78395
2017-05-07 07:59:49-0300 1739027 [13575]: s2 delta_renew long
write time 10 sec
2017-05-09 08:38:34-0300 1914151 [13590]: s2:r16 resource

20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-4e10-9893-588ceb81b354/dom_md/leases:1048576
for 7,21,78395
2017-05-11 15:07:45-0300 2110302 [13590]: s2:r17 resource

20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-4e10-9893-588ceb81b354/dom_md/leases:1048576
for 7,21,112346
2017-05-11 15:17:24-0300 2110881 [13590]: s4 lockspace

b010093e-1924-46e1-bd57-2cf2b2445087:1:/dev/b010093e-1924-46e1-bd57-2cf2b2445087/ids:0
2017-05-11 15:17:45-0300 2110902 [1395]: s4 host 1 1 2110881
44ae07eb-3371-4750-8728-ab3b049dbae2.ovirt730-0
2017-05-11 15:17:45-0300 2110902 [1400]: s4:r18 resource

b010093e-1924-46e1-bd57-2cf2b2445087:SDM:/dev/b010093e-1924-46e1-bd57-2cf2b2445087/leases:1048576
for 7,21,112346
2017-05-11 15:17:52-0300 2110909 [1399]: s5 lockspace

b010093e-1924-46e1-bd57-2cf2b2445087:1:/dev/b010093e-1924-46e1-bd57-2cf2b2445087/ids:0
2017-05-11 15:18:13-0300 2110930 [1395]: s5 host 1 2 2110909
44ae07eb-3371-4750-8728-ab3b049dbae2.ovirt730-0
2017-05-11 15:18:13-0300 2110930 [1395]: s5 host 2 1 2110065
4d31313f-b2dd-4368-bf31-d39835e10afb.ovirt730-0


On 2017-05-11 10:09 AM, Charles Tassell wrote:


Hi Freddy,

  Sure, thanks for looking into this.  Here you go:

2017-05-10 11:35:30,249-03 INFO
[org.ovirt.engine.core.bll.aaa.SessionDataContainer]
(DefaultQuartzScheduler8) [1c84abac] Not removing session

'vZyqrcCljPC7hQtcILsk4uDug3QsiinZBOyoGDiQKkYYT2znGyWe4fasrPbjYxdjbfyR3DBnp+UZ9/k20dGsMA==',
session has running commands for user 'admin@internal-authz'.[snip]

On 2017-05-11 04:30 AM, Fred Rolland wrote:

Hi,

Can you provide the engine log ?

Thanks,

Freddy

On Wed, May 10, 2017 at 5:57 PM, Charles Tassell

Re: [ovirt-users] Cloning VM on NFS Leads to Locked Disks

[Fred Rolland]

The locking is on the engine side and restarting the vdsm will not affect
it .
Can you send the whole engine log ?
Which exact version are you using ?


On Thu, May 11, 2017 at 9:30 PM, Charles Tassell 
wrote:

> Just as an update, I created a new VM and had the same issue: the disk
> remains locked.  So I then added a new data store (this one iSCSI not NFS)
> and create a new VM on that.  Again, the disk remains locked.  So the
> problem seems to be that any action that sets to modify a disk image on my
> cluster locks the disk and keeps it locked permanently.
>
> I tried restarting the vdsm daemon, but that didn't make a difference.
> I'm seeing this in my sanlock.log file though, which worries me:
>
>
> 017-05-07 07:51:41-0300 1738538 [13575]: s2 renewal error -202
> delta_length 10 last_success 1738508
> 2017-05-07 07:51:41-0300 1738538 [11513]: s1 renewal error -202
> delta_length 10 last_success 1738508
>
> Here's the last 20 lines:
> 2017-05-07 07:51:41-0300 1738538 [13580]: s3 renewal error -202
> delta_length 10 last_success 1738508
> 2017-05-07 07:51:41-0300 1738538 [13575]: 20423d5e aio timeout RD
> 0x7fe1440008c0:0x7fe1440008d0:0x7fe160255000 ioto 10 to_count 67
> 2017-05-07 07:51:41-0300 1738538 [13575]: s2 delta_renew read timeout 10
> sec offset 0 /rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-
> 188c-4e10-9893-588ceb81b354/dom_md/ids
> 2017-05-07 07:51:41-0300 1738538 [13575]: s2 renewal error -202
> delta_length 10 last_success 1738508
> 2017-05-07 07:51:41-0300 1738538 [11513]: hosted-e aio timeout RD
> 0x7fe1480008c0:0x7fe1480008d0:0x7fe14e6fc000 ioto 10 to_count 65
> 2017-05-07 07:51:41-0300 1738538 [11513]: s1 delta_renew read timeout 10
> sec offset 0 /var/run/vdsm/storage/5dccd07d-a923-4d4b-9cb1-
> 3b51ebfdca4d/5a9c284f-0faa-4a25-94ce-c9efdae07484/ab2443f1-95ed-475d-886c-
> c1653257cf04
> 2017-05-07 07:51:41-0300 1738538 [11513]: s1 renewal error -202
> delta_length 10 last_success 1738508
> 2017-05-07 07:51:47-0300 1738544 [13575]: 20423d5e aio collect RD
> 0x7fe1440008c0:0x7fe1440008d0:0x7fe160255000 result 1048576:0 match reap
> 2017-05-07 07:51:47-0300 1738544 [13580]: 5dccd07d aio collect RD
> 0x7fe13c0008c0:0x7fe13c0008d0:0x7fe14e5fa000 result 1048576:0 match reap
> 2017-05-07 07:51:47-0300 1738544 [11513]: hosted-e aio collect RD
> 0x7fe1480008c0:0x7fe1480008d0:0x7fe14e6fc000 result 1048576:0 match reap
> 2017-05-07 07:53:57-0300 1738674 [13590]: s2:r15 resource
> 20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-
> center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-
> 4e10-9893-588ceb81b354/dom_md/leases:1048576 for 7,21,78395
> 2017-05-07 07:59:49-0300 1739027 [13575]: s2 delta_renew long write time
> 10 sec
> 2017-05-09 08:38:34-0300 1914151 [13590]: s2:r16 resource
> 20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-
> center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-
> 4e10-9893-588ceb81b354/dom_md/leases:1048576 for 7,21,78395
> 2017-05-11 15:07:45-0300 2110302 [13590]: s2:r17 resource
> 20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-
> center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-
> 4e10-9893-588ceb81b354/dom_md/leases:1048576 for 7,21,112346
> 2017-05-11 15:17:24-0300 2110881 [13590]: s4 lockspace
> b010093e-1924-46e1-bd57-2cf2b2445087:1:/dev/b010093e-
> 1924-46e1-bd57-2cf2b2445087/ids:0
> 2017-05-11 15:17:45-0300 2110902 [1395]: s4 host 1 1 2110881
> 44ae07eb-3371-4750-8728-ab3b049dbae2.ovirt730-0
> 2017-05-11 15:17:45-0300 2110902 [1400]: s4:r18 resource
> b010093e-1924-46e1-bd57-2cf2b2445087:SDM:/dev/b010093e-1924-46e1-bd57-2cf2b2445087/leases:1048576
> for 7,21,112346
> 2017-05-11 15:17:52-0300 2110909 [1399]: s5 lockspace
> b010093e-1924-46e1-bd57-2cf2b2445087:1:/dev/b010093e-
> 1924-46e1-bd57-2cf2b2445087/ids:0
> 2017-05-11 15:18:13-0300 2110930 [1395]: s5 host 1 2 2110909
> 44ae07eb-3371-4750-8728-ab3b049dbae2.ovirt730-0
> 2017-05-11 15:18:13-0300 2110930 [1395]: s5 host 2 1 2110065
> 4d31313f-b2dd-4368-bf31-d39835e10afb.ovirt730-0
>
>
> On 2017-05-11 10:09 AM, Charles Tassell wrote:
>
> Hi Freddy,
>
>   Sure, thanks for looking into this.  Here you go:
>
> 2017-05-10 11:35:30,249-03 INFO  
> [org.ovirt.engine.core.bll.aaa.SessionDataContainer]
> (DefaultQuartzScheduler8) [1c84abac] Not removing session '
> vZyqrcCljPC7hQtcILsk4uDug3QsiinZBOyoGDiQKkYYT2znGyWe4fasrPbjYxdjbfyR3DBnp+UZ9/k20dGsMA==',
> session has running commands for user 'admin@internal-authz'.[snip]
> On 2017-05-11 04:30 AM, Fred Rolland wrote:
>
> Hi,
>
> Can you provide the engine log ?
>
> Thanks,
>
> Freddy
>
> On Wed, May 10, 2017 at 5:57 PM, Charles Tassell 
> wrote:
>
>> Hi Everyone,
>>
>>   I'm having some issues with my oVirt 4.1 (fully updated to latest
>> release as of yesterday) cluster.  When I clone a VM the disks of both the
>> original and the clone stay in the locked state, and the only way I can
>> resolve it is to go into the database on the engine and run "update images
>> set imagestatus=1 

Re: [ovirt-users] Cloning VM on NFS Leads to Locked Disks

[Charles Tassell]

Just as an update, I created a new VM and had the same issue: the disk 
remains locked.  So I then added a new data store (this one iSCSI not 
NFS) and create a new VM on that.  Again, the disk remains locked.  So 
the problem seems to be that any action that sets to modify a disk image 
on my cluster locks the disk and keeps it locked permanently.


I tried restarting the vdsm daemon, but that didn't make a difference.  
I'm seeing this in my sanlock.log file though, which worries me:



017-05-07 07:51:41-0300 1738538 [13575]: s2 renewal error -202 
delta_length 10 last_success 1738508
2017-05-07 07:51:41-0300 1738538 [11513]: s1 renewal error -202 
delta_length 10 last_success 1738508


Here's the last 20 lines:
2017-05-07 07:51:41-0300 1738538 [13580]: s3 renewal error -202 
delta_length 10 last_success 1738508
2017-05-07 07:51:41-0300 1738538 [13575]: 20423d5e aio timeout RD 
0x7fe1440008c0:0x7fe1440008d0:0x7fe160255000 ioto 10 to_count 67
2017-05-07 07:51:41-0300 1738538 [13575]: s2 delta_renew read timeout 10 
sec offset 0 
/rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-4e10-9893-588ceb81b354/dom_md/ids
2017-05-07 07:51:41-0300 1738538 [13575]: s2 renewal error -202 
delta_length 10 last_success 1738508
2017-05-07 07:51:41-0300 1738538 [11513]: hosted-e aio timeout RD 
0x7fe1480008c0:0x7fe1480008d0:0x7fe14e6fc000 ioto 10 to_count 65
2017-05-07 07:51:41-0300 1738538 [11513]: s1 delta_renew read timeout 10 
sec offset 0 
/var/run/vdsm/storage/5dccd07d-a923-4d4b-9cb1-3b51ebfdca4d/5a9c284f-0faa-4a25-94ce-c9efdae07484/ab2443f1-95ed-475d-886c-c1653257cf04
2017-05-07 07:51:41-0300 1738538 [11513]: s1 renewal error -202 
delta_length 10 last_success 1738508
2017-05-07 07:51:47-0300 1738544 [13575]: 20423d5e aio collect RD 
0x7fe1440008c0:0x7fe1440008d0:0x7fe160255000 result 1048576:0 match reap
2017-05-07 07:51:47-0300 1738544 [13580]: 5dccd07d aio collect RD 
0x7fe13c0008c0:0x7fe13c0008d0:0x7fe14e5fa000 result 1048576:0 match reap
2017-05-07 07:51:47-0300 1738544 [11513]: hosted-e aio collect RD 
0x7fe1480008c0:0x7fe1480008d0:0x7fe14e6fc000 result 1048576:0 match reap
2017-05-07 07:53:57-0300 1738674 [13590]: s2:r15 resource 
20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-4e10-9893-588ceb81b354/dom_md/leases:1048576 
for 7,21,78395
2017-05-07 07:59:49-0300 1739027 [13575]: s2 delta_renew long write time 
10 sec
2017-05-09 08:38:34-0300 1914151 [13590]: s2:r16 resource 
20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-4e10-9893-588ceb81b354/dom_md/leases:1048576 
for 7,21,78395
2017-05-11 15:07:45-0300 2110302 [13590]: s2:r17 resource 
20423d5e-188c-4e10-9893-588ceb81b354:SDM:/rhev/data-center/mnt/192.168.130.217:_media_ovirt/20423d5e-188c-4e10-9893-588ceb81b354/dom_md/leases:1048576 
for 7,21,112346
2017-05-11 15:17:24-0300 2110881 [13590]: s4 lockspace 
b010093e-1924-46e1-bd57-2cf2b2445087:1:/dev/b010093e-1924-46e1-bd57-2cf2b2445087/ids:0
2017-05-11 15:17:45-0300 2110902 [1395]: s4 host 1 1 2110881 
44ae07eb-3371-4750-8728-ab3b049dbae2.ovirt730-0
2017-05-11 15:17:45-0300 2110902 [1400]: s4:r18 resource 
b010093e-1924-46e1-bd57-2cf2b2445087:SDM:/dev/b010093e-1924-46e1-bd57-2cf2b2445087/leases:1048576 
for 7,21,112346
2017-05-11 15:17:52-0300 2110909 [1399]: s5 lockspace 
b010093e-1924-46e1-bd57-2cf2b2445087:1:/dev/b010093e-1924-46e1-bd57-2cf2b2445087/ids:0
2017-05-11 15:18:13-0300 2110930 [1395]: s5 host 1 2 2110909 
44ae07eb-3371-4750-8728-ab3b049dbae2.ovirt730-0
2017-05-11 15:18:13-0300 2110930 [1395]: s5 host 2 1 2110065 
4d31313f-b2dd-4368-bf31-d39835e10afb.ovirt730-0



On 2017-05-11 10:09 AM, Charles Tassell wrote:


Hi Freddy,

  Sure, thanks for looking into this.  Here you go:

2017-05-10 11:35:30,249-03 INFO 
[org.ovirt.engine.core.bll.aaa.SessionDataContainer] 
(DefaultQuartzScheduler8) [1c84abac] Not removing session 
'vZyqrcCljPC7hQtcILsk4uDug3QsiinZBOyoGDiQKkYYT2znGyWe4fasrPbjYxdjbfyR3DBnp+UZ9/k20dGsMA==', 
session has running commands for user 'admin@internal-authz'.[snip]


On 2017-05-11 04:30 AM, Fred Rolland wrote:

Hi,

Can you provide the engine log ?

Thanks,

Freddy

On Wed, May 10, 2017 at 5:57 PM, Charles Tassell 
> wrote:


Hi Everyone,

  I'm having some issues with my oVirt 4.1 (fully updated to
latest release as of yesterday) cluster.  When I clone a VM the
disks of both the original and the clone stay in the locked
state, and the only way I can resolve it is to go into the
database on the engine and run "update images set imagestatus=1
where imagestatus=2;"

  I'm using NFS4 as a datastore and the disks seem to copy fine
(file sizes match and everything), but the locking worries me. 
To clone the VM I just shut the source VM down and then right

click on it and select "Clone"

  I've attached the full VDSM log from my last attempt, but here

Re: [ovirt-users] ansible and list of vms

[Ondra Machacek]

I am not Ansible expert, this maybe worth asking on Ansible users list,
but one thing which you can do is following:

in tasks/main.yml

- include: "{{ item }}"
  with_items: "{{ resources | default('vms') }}.yml"

then have following files:
 - tasks/vms.yml
 - tasks/clusters.yml
 - tasks/disks.yml
 - ...

then run it as:

 $ ansible-playbook -e "resources: [vms,disks]" play.yml
 $ ansible-playbook -e "resources: [clusters] clusters_pattern=name=x*"
play.yml


On Thu, May 11, 2017 at 6:34 PM, Nathanaël Blanchet 
wrote:

> Thanks, all works as expected.
>
> Now, I try make roles.
>
> here it is :
>
> *cat /etc/ansible/roles/ovirt_vm_facts/tasks/main.yml*
>
>   - name: get vm facts
> ovirt_vms_facts:
>   auth:
> url: https://{{ engine }}.v100.abes.fr/ovirt-engine/api
> username: "{{ username }}"
> password: "{{ password }}"
> insecure: "{{ insecure }}"
>   pattern: "{{ pattern }}"
>   - debug:
>   msg: "{{ ovirt_vms | map(attribute='name') | join(' ') }}"
>
> *cat /etc/ansible/roles/ovirt_vm_facts/vars/main.yml*
>
> pattern: "os=rhel_5x64 or os=rhel_5"
> engine: air
> username: admin@internal
> password: ovirt123
> insecure: true
>
> and I call those files with */tmp/ovirt_vm_facts.yml* with extra
> variables if needed
>
> - hosts: localhost
>   connection: local
>   roles:
> - ovirt_vm_fact
>
> running ansible-playbook /tmp/ovirt_vm_facts.ym -e 'pattern="name=acier*
> and cluster=Dev"'
>
> *But..*
>
> I don't want to do the same for each ansible module shipped with 2.3.
>
> Knowing that each *facts module has the same structure auth/pattern, is
> there a way to play a generic playbook independant from the role, like:
>
> - hosts: localhost
>   connection: local
>   roles:
> - ovirt_facts (with somewhere a variable "myfact")
>
> which would play an unique role */etc/ansible/roles/ovirt_facts/tasks/main.yml
> with*
>
>
> - name: get vm facts
> myfact
>   auth:
> 
>
> Hope to be clear enough, thank your for your help.
>
> Le 10/05/2017 à 13:14, Ondra Machacek a écrit :
>
>
>
> On Wed, May 10, 2017 at 12:38 PM, Nathanaël Blanchet 
> wrote:
>
>> Le 10/05/2017 à 10:29, Ondra Machacek a écrit :
>>
>> Not sure I understand. You can use Ansible module to list VMs, you
>> can use ovirt_vms _facts[1] module.
>>
>> For example to get only stopped VMs, you can use following:
>>
>> - name: Get stopped VMs
>>   ovirt_vms_facts:
>> auth:
>>   url: https://ovirt.example.com/ovirt-engine/api
>>   username: admin@internal
>>   password: password
>>   ca_file: /etc/pki/ovirt-engine/ca.pem
>> pattern: "status = down"
>>
>> I want a list of vms sorted by any possible attributes, i.e. sorted by
>> datacenter or cluster, not only by status.
>>
>>- For example, ovirt_vms_facts doesn't allow to get the datacenter
>>the vm belongs to , and the pattern filter doesn't return a list of vms as
>>expected:
>>
>>
>> - hosts: localhost
>>   connection: local
>>   tasks:
>>   - name: Get stopped VMs
>> ovirt_vms_facts:
>>   auth:
>> url: https://acore.v100.abes.fr/ovirt-engine/api
>> username: admin@internal
>> password: ovirt123
>> insecure: true
>> pattern: name=centos* and cluster=west
>>   - debug:
>>   var: ovirt_vms
>>   - shell: echo "{{ ovirt_vms.name }}"
>>
>
>
> Ok, I understand, now.
> You have few options here.
> If you want for example only VMs from datacenter 'X', you can use
> following:
>
> - hosts: localhost
>   connection: local
>   tasks:
>   - name: Get VMs from datacenter X
> ovirt_vms_facts:
>   pattern: datacenter=X
>   auth:
> url: https://acore.v100.abes.fr/ovirt-engine/api
> username: admin@internal
> password: ovirt123
> insecure: true
>   - debug:
>   msg: "{{ ovirt_vms | map(attribute='name') | list }}"
>
>
>>
>> How can I successfully display this list of vms like described here :
>> name description returned type sample
>> ovirt_vms List of dictionaries describing the VMs. VM attribues are
>> mapped to dictionary keys, all VMs attributes can be found at following
>> url: https://ovirt.example.com/ovirt-engine/api/model#types/vm. On
>> success. list
>>
>>
>>- About the python SDK:
>>
>> list_vms.py could be what I expect, but vm.datacenter_name doesn't exist
>>
>
> Yes, because the 'data_center' parameter isn't part of the VM type. Take a
> look here[1],
> you will find there all attributes the VM has. As you can see there is no
> 'datacenter', but
> there is a 'cluster', but as said in documentation, it's just a reference
> to the cluster. That
> means that it contains the ID of the cluster and the 'href' to the
> cluster, so you can get
> the cluster object by following that reference using this code:
>
>  vm_cluster = connection.follow_link(vm.cluster)
>  print vm_cluster.name
>
>  # Same for datacenter:
>  vm_dc = connection.follow_link(vm_cluster.data_center)

[ovirt-users] Ovirt nested in VMware

[Mark Duggan]

Hi everyone,

>From reading through the mailing list, it does appear that it's possible to
have the ovirt nodes/hosts be VMware virtual machines, once I enable the
appropriate settings on the VMware side. All seems to have gone well, I can
see the hosts in the ovirt interface, but when I attempt to create and
start a VM it never gets past printing the SeaBios version and the machine
UUID to the screen/console. It doesn't appear to try to boot from the hard
disk or an ISO that I've attached.

Has anyone else encountered similar behaviour?

Are there additional debug logs I can look at or enable to help further
diagnose what is happening?

Thanks

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

[ovirt-users] slow kerberos authentication

[Fabrice Bacchella]

I'm using kerberos authentication in ovirt for the URL 
/sso/oauth/token-http-auth, but kerberos is done in Apache using 
auth_gssapi_module and it's quite slow, about 6s for a request.

I'm trying to understand if it's apache or ovirt-engine that are slow. Is there 
a way to get response time metered for http requests inside ovirt instead of 
seen from apache ?

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

Re: [ovirt-users] 4.0 : hosts connecting/non responsive and data domains inactive

[Piotr Kliczewski]

>From provided log snippets I see that engine was unable to connect to both
of your hosts. Is the network OK?

In vdsm log it seems that there is an issue with you storage domain.

I am not able to say anything about the issue you are facing without having
more complete logs.

On Thu, May 11, 2017 at 6:28 PM, Oved Ourfali  wrote:

> What 4.0 version do you use?
> Can you attach complete engine and vdsm logs?
> CC-ing Piotr as well.
>
>
> On May 11, 2017 6:44 PM, "Alexis HAUSER" 
> wrote:
>
>> After rebooting the manager VM,  hosts are connecting/non responsive and
>> data domains inactive. Here are the engine and vdsmd logs. Any ideas ?
>>
>>
>>
>>
>> Engine logs :
>>
>>
>>
>> 2017-05-11 17:28:09,302 WARN  [org.ovirt.engine.core.dal.dbb
>> roker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler5)
>> [55f1aab5] Correlation ID: null, Call Stack: null, Custom Event ID: -1,
>> Message: Failed to verify Power Management configuration for Host
>> rhvserv-05.
>> 2017-05-11 17:28:09,346 INFO  
>> [org.ovirt.engine.core.bll.HandleVdsVersionCommand]
>> (DefaultQuartzScheduler5) [48bc69cd] Running command:
>> HandleVdsVersionCommand internal: true. Entities affected :  ID:
>> 04565f10-9abf-4709-9445-9dc6ed97e136 Type: VDS
>> 2017-05-11 17:28:09,349 WARN  [org.ovirt.engine.core.vdsbroker.VdsManager]
>> (org.ovirt.thread.pool-6-thread-27) [639977e4] Host 'rhvserv-05' is not
>> responding.
>> 2017-05-11 17:28:09,364 WARN  [org.ovirt.engine.core.dal.dbb
>> roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-27)
>> [639977e4] Correlation ID: null, Call Stack: null, Custom Event ID: -1,
>> Message: Host rhvserv-05 is not responding. Host cannot be fenced
>> automatically because power management for the host is disabled.
>> 2017-05-11 17:28:11,299 ERROR [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler3)
>> [c0e6a2e] Command 'GetCapabilitiesVDSCommand(HostName = rhvserv-03,
>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>> hostId='4036f027-8e90-49c0-8ca5-3ddb8d586916',
>> vds='Host[rhvserv-03,4036f027-8e90-49c0-8ca5-3ddb8d586916]'})' execution
>> failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
>> Connection failed
>> 2017-05-11 17:28:11,299 ERROR 
>> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
>> (DefaultQuartzScheduler3) [c0e6a2e] Failure to refresh host 'rhvserv-03'
>> runtime info: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
>> Connection failed
>> 2017-05-11 17:28:11,327 INFO  
>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
>> (SSL Stomp Reactor) [] Connecting to rhvserv-04.mydomain.com/192.16
>> 8.93.214
>> 2017-05-11 17:28:12,484 INFO  [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler3)
>> [c0e6a2e] START, GetHardwareInfoVDSCommand(HostName = rhvserv-05,
>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
>> hostId='04565f10-9abf-4709-9445-9dc6ed97e136',
>> vds='Host[rhvserv-05,04565f10-9abf-4709-9445-9dc6ed97e136]'}), log id:
>> f807ece
>> 2017-05-11 17:28:12,487 INFO  [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler3)
>> [c0e6a2e] FINISH, GetHardwareInfoVDSCommand, log id: f807ece
>> 2017-05-11 17:28:12,532 INFO  [org.ovirt.engine.core.bll.Han
>> dleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler3)
>> [4e882ea0] Running command: HandleVdsCpuFlagsOrClusterChangedCommand
>> internal: true. Entities affected :  ID: 04565f10-9abf-4709-9445-9dc6ed97e136
>> Type: VDS
>> 2017-05-11 17:28:12,539 INFO  [org.ovirt.engine.core.bll.InitVdsOnUpCommand]
>> (DefaultQuartzScheduler3) [75f25b35] Running command: InitVdsOnUpCommand
>> internal: true. Entities affected :  ID: 58f8df36-019f-02bc-00e7-0023
>> Type: StoragePool
>> 2017-05-11 17:28:12,545 INFO  [org.ovirt.engine.core.bll.sto
>> rage.pool.ConnectHostToStoragePoolServersCommand]
>> (DefaultQuartzScheduler3) [46cc3f58] Running command:
>> ConnectHostToStoragePoolServersCommand internal: true. Entities affected
>> :  ID: 58f8df36-019f-02bc-00e7-0023 Type: StoragePool
>> 2017-05-11 17:28:12,556 INFO  [org.ovirt.engine.core.vdsbrok
>> er.vdsbroker.ConnectStorageServerVDSCommand] (DefaultQuartzScheduler3)
>> [46cc3f58] START, ConnectStorageServerVDSCommand(HostName = rhvserv-05,
>> StorageServerConnectionManagementVDSParameters:{runAsync='true',
>> hostId='04565f10-9abf-4709-9445-9dc6ed97e136',
>> storagePoolId='58f8df36-019f-02bc-00e7-0023',
>> storageType='ISCSI', connectionList='[StorageServer
>> Connections:{id='10c0528b-f08d-4d1d-8c63-8a05fd9d58b9',
>> connection='10.35.21.1', iqn='iqn.1984-05.com.dell:powe
>> rvault.md3200i.6782bcb00073e3324edde164', vfsType='null',
>> mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null',
>> iface='null', netIfaceName='null'}]'}), log id: 1beb27b6
>> 2017-05-11 17:28:13,031 

Re: [ovirt-users] hosted engine unattended install

[Ramachandra Reddy Ankireddypalle]

Thank you all. That worked.

On Thu, May 11, 2017 at 11:49 AM, Simone Tiraboschi 
wrote:

>
>
> On Thu, May 11, 2017 at 5:47 PM, Sandro Bonazzola 
> wrote:
>
>>
>>
>> On Thu, May 11, 2017 at 4:30 PM, Ramachandra Reddy Ankireddypalle <
>> rcreddy.ankireddypa...@gmail.com> wrote:
>>
>>> Hi,
>>>  I am trying to do an unattended install of hosted engine through a
>>> script. All the required parameters are being read from answer file and
>>> that works fine. Is there a way to provide passwords for the ovirt engine
>>> linux box and admin console through answer file.
>>>
>>>
>> Hi,
>> welcome to oVirt community!
>>
>> Yes, you can pass admin password using the answer file.
>> The environment key is: OVEHOSTED_ENGINE/adminPassword
>>
>
> And OVEHOSTED_VM/cloudinitRootPwd for the root password of the engine VM.
>
>
>>
>>
>>
>>
>>> Thanks and Regards,
>>> Ram
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
>>
>> Red Hat EMEA 
>> 
>> TRIED. TESTED. TRUSTED. 
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ansible and list of vms

[Nathanaël Blanchet]

Thanks, all works as expected.

Now, I try make roles.

here it is :

*cat /etc/ansible/roles/ovirt_vm_facts/tasks/main.yml*

  - name: get vm facts
ovirt_vms_facts:
  auth:
url: https://{{ engine }}.v100.abes.fr/ovirt-engine/api
username: "{{ username }}"
password: "{{ password }}"
insecure: "{{ insecure }}"
  pattern: "{{ pattern }}"
  - debug:
  msg: "{{ ovirt_vms | map(attribute='name') | join(' ') }}"

*cat /etc/ansible/roles/ovirt_vm_facts/vars/main.yml*

pattern: "os=rhel_5x64 or os=rhel_5"
engine: air
username: admin@internal
password: ovirt123
insecure: true

and I call those files with */tmp/ovirt_vm_facts.yml* with extra 
variables if needed


- hosts: localhost
  connection: local
  roles:
- ovirt_vm_fact

running ansible-playbook /tmp/ovirt_vm_facts.ym -e 'pattern="name=acier* 
and cluster=Dev"'


*But..*

I don't want to do the same for each ansible module shipped with 2.3.

Knowing that each *facts module has the same structure auth/pattern, is 
there a way to play a generic playbook independant from the role, like:


- hosts: localhost
  connection: local
  roles:
- ovirt_facts (with somewhere a variable "myfact")

which would play an unique role 
*/etc/ansible/roles/ovirt_facts/tasks/main.yml with*



- name: get vm facts
myfact
  auth:


Hope to be clear enough, thank your for your help.


Le 10/05/2017 à 13:14, Ondra Machacek a écrit :



On Wed, May 10, 2017 at 12:38 PM, Nathanaël Blanchet > wrote:


Le 10/05/2017 à 10:29, Ondra Machacek a écrit :

Not sure I understand. You can use Ansible module to list VMs, you
can use ovirt_vms _facts[1] module.

For example to get only stopped VMs, you can use following:

- name: Get stopped VMs
  ovirt_vms_facts:
auth:
  url: https://ovirt.example.com/ovirt-engine/api

  username: admin@internal
  password: password
  ca_file: /etc/pki/ovirt-engine/ca.pem
pattern: "status = down"

I want a list of vms sorted by any possible attributes, i.e.
sorted by datacenter or cluster, not only by status.

  * For example, ovirt_vms_facts doesn't allow to get the
datacenter the vm belongs to , and the pattern filter doesn't
return a list of vms as expected:


- hosts: localhost
  connection: local
  tasks:
  - name: Get stopped VMs
ovirt_vms_facts:
  auth:
url: https://acore.v100.abes.fr/ovirt-engine/api

username: admin@internal
password: ovirt123
insecure: true
pattern: name=centos* and cluster=west
  - debug:
  var: ovirt_vms
  - shell: echo "{{ ovirt_vms.name  }}"



Ok, I understand, now.
You have few options here.
If you want for example only VMs from datacenter 'X', you can use 
following:


- hosts: localhost
  connection: local
  tasks:
  - name: Get VMs from datacenter X
ovirt_vms_facts:
  pattern: datacenter=X
  auth:
url: https://acore.v100.abes.fr/ovirt-engine/api 


username: admin@internal
password: ovirt123
insecure: true
  - debug:
  msg: "{{ ovirt_vms | map(attribute='name') | list }}"


How can I successfully display this list of vms like described here :
namedescription returnedtypesample
ovirt_vms   List of dictionaries describing the VMs. VM attribues
are mapped to dictionary keys, all VMs attributes can be found at
following url:
https://ovirt.example.com/ovirt-engine/api/model#types/vm
.  On
success.list


  * About the python SDK:

list_vms.py could be what I expect, but vm.datacenter_name doesn't
exist


Yes, because the 'data_center' parameter isn't part of the VM type. 
Take a look here[1],
you will find there all attributes the VM has. As you can see there is 
no 'datacenter', but
there is a 'cluster', but as said in documentation, it's just a 
reference to the cluster. That
means that it contains the ID of the cluster and the 'href' to the 
cluster, so you can get

the cluster object by following that reference using this code:

 vm_cluster = connection.follow_link(vm.cluster)
 print vm_cluster.name 

 # Same for datacenter:
 vm_dc = connection.follow_link(vm_cluster.data_center)
 print vm_dc.name 

What you need to understand is, what is the difference between the 'full'
object and the reference to the object. It's good to take a look at 
the XML

output of the API and learn to read the API specification documentation,
when working with oVirt Ansible and Python SDK.

[1] 

Re: [ovirt-users] 4.0 : hosts connecting/non responsive and data domains inactive

[Oved Ourfali]

What 4.0 version do you use?
Can you attach complete engine and vdsm logs?
CC-ing Piotr as well.


On May 11, 2017 6:44 PM, "Alexis HAUSER" 
wrote:

> After rebooting the manager VM,  hosts are connecting/non responsive and
> data domains inactive. Here are the engine and vdsmd logs. Any ideas ?
>
>
>
>
> Engine logs :
>
>
>
> 2017-05-11 17:28:09,302 WARN  [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler5)
> [55f1aab5] Correlation ID: null, Call Stack: null, Custom Event ID: -1,
> Message: Failed to verify Power Management configuration for Host
> rhvserv-05.
> 2017-05-11 17:28:09,346 INFO  
> [org.ovirt.engine.core.bll.HandleVdsVersionCommand]
> (DefaultQuartzScheduler5) [48bc69cd] Running command:
> HandleVdsVersionCommand internal: true. Entities affected :  ID:
> 04565f10-9abf-4709-9445-9dc6ed97e136 Type: VDS
> 2017-05-11 17:28:09,349 WARN  [org.ovirt.engine.core.vdsbroker.VdsManager]
> (org.ovirt.thread.pool-6-thread-27) [639977e4] Host 'rhvserv-05' is not
> responding.
> 2017-05-11 17:28:09,364 WARN  [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (org.ovirt.thread.pool-6-thread-27)
> [639977e4] Correlation ID: null, Call Stack: null, Custom Event ID: -1,
> Message: Host rhvserv-05 is not responding. Host cannot be fenced
> automatically because power management for the host is disabled.
> 2017-05-11 17:28:11,299 ERROR 
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler3) [c0e6a2e] Command 
> 'GetCapabilitiesVDSCommand(HostName
> = rhvserv-03, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='4036f027-8e90-49c0-8ca5-3ddb8d586916',
> vds='Host[rhvserv-03,4036f027-8e90-49c0-8ca5-3ddb8d586916]'})' execution
> failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
> Connection failed
> 2017-05-11 17:28:11,299 ERROR 
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (DefaultQuartzScheduler3) [c0e6a2e] Failure to refresh host 'rhvserv-03'
> runtime info: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException:
> Connection failed
> 2017-05-11 17:28:11,327 INFO  
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
> (SSL Stomp Reactor) [] Connecting to rhvserv-04.mydomain.com/192.
> 168.93.214
> 2017-05-11 17:28:12,484 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
> (DefaultQuartzScheduler3) [c0e6a2e] START, GetHardwareInfoVDSCommand(HostName
> = rhvserv-05, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='04565f10-9abf-4709-9445-9dc6ed97e136',
> vds='Host[rhvserv-05,04565f10-9abf-4709-9445-9dc6ed97e136]'}), log id:
> f807ece
> 2017-05-11 17:28:12,487 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
> (DefaultQuartzScheduler3) [c0e6a2e] FINISH, GetHardwareInfoVDSCommand, log
> id: f807ece
> 2017-05-11 17:28:12,532 INFO  [org.ovirt.engine.core.bll.
> HandleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler3)
> [4e882ea0] Running command: HandleVdsCpuFlagsOrClusterChangedCommand
> internal: true. Entities affected :  ID: 04565f10-9abf-4709-9445-9dc6ed97e136
> Type: VDS
> 2017-05-11 17:28:12,539 INFO  [org.ovirt.engine.core.bll.InitVdsOnUpCommand]
> (DefaultQuartzScheduler3) [75f25b35] Running command: InitVdsOnUpCommand
> internal: true. Entities affected :  ID: 58f8df36-019f-02bc-00e7-0023
> Type: StoragePool
> 2017-05-11 17:28:12,545 INFO  [org.ovirt.engine.core.bll.storage.pool.
> ConnectHostToStoragePoolServersCommand] (DefaultQuartzScheduler3)
> [46cc3f58] Running command: ConnectHostToStoragePoolServersCommand
> internal: true. Entities affected :  ID: 58f8df36-019f-02bc-00e7-0023
> Type: StoragePool
> 2017-05-11 17:28:12,556 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.
> ConnectStorageServerVDSCommand] (DefaultQuartzScheduler3) [46cc3f58]
> START, ConnectStorageServerVDSCommand(HostName = rhvserv-05,
> StorageServerConnectionManagementVDSParameters:{runAsync='true',
> hostId='04565f10-9abf-4709-9445-9dc6ed97e136',
> storagePoolId='58f8df36-019f-02bc-00e7-0023',
> storageType='ISCSI', connectionList='[StorageServerConnections:{id='
> 10c0528b-f08d-4d1d-8c63-8a05fd9d58b9', connection='10.35.21.1',
> iqn='iqn.1984-05.com.dell:powervault.md3200i.
> 6782bcb00073e3324edde164', vfsType='null', mountOptions='null',
> nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null',
> netIfaceName='null'}]'}), log id: 1beb27b6
> 2017-05-11 17:28:13,031 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.
> ConnectStorageServerVDSCommand] (DefaultQuartzScheduler3) [46cc3f58]
> FINISH, ConnectStorageServerVDSCommand, return: 
> {10c0528b-f08d-4d1d-8c63-8a05fd9d58b9=0},
> log id: 1beb27b6
> 2017-05-11 17:28:13,032 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.
> ConnectStorageServerVDSCommand] (DefaultQuartzScheduler3) [46cc3f58]
> START, ConnectStorageServerVDSCommand(HostName = rhvserv-05,

[ovirt-users] Migrate VirtualBox Vm into

[Gajendra Ravichandran]

Hi,


I am running a ovirt engine and ovirt host on a single machine for testing 
purpose. I trying to convert and move Debian virtualbox vm which is created 
using vagrant into ovirt engine as template.


I tried to convert using virt-v2v as http://libguestfs.org/virt-v2v.1.html. 
However, I get error as (Debian/ Linux cannot be converted).


I have exported the vm from virtualbox and have the image as .ova. Is there any 
way to migrate?


Thanks

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

[ovirt-users] problem while updating oVirt from 3.6 to 4.0

[Nelson Lameiras]

Hello, 

Not sure if I should post here, or on the dev mailling list. 

I had a serious problem when upgrading an oVirt cluster from 3.6 to 4.0 (before 
updating to 4.1) 

The error on engine-setup log was : 
"schema.sh: FATAL: Cannot execute sql command: 
--file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0930_disallow_boot_protocol_to_be_null.sql"
 

After long hours of debuguing and analysing I found out the problem. On 
database, some entries on table network_attachements had a NULL value which 
were incompatible with the sql file above. 
I'm guessing this is an "exotic situation" which shouldn't exist... in theory 
;) 

Anyway, I'm fairly sure that the solution for this problem would be to patch 
the following file 
'ovirt-engine/packaging/dbscripts/upgrade/04_00_0910_do_not_allow_null_boot_protocol.sql'
 
by adding the following line " update network_attachments set boot_protocol = ' 
NONE ' where boot_protocol is null ;" 

If a dev want to discuss it further, I'll be happy to explain my thoughts on 
this matter. 

cordialement, regards, 


Nelson LAMEIRAS 
Ingénieur Systèmes et Réseaux / Systems and Networks engineer 
Tel: +33 5 32 09 09 70 
nelson.lamei...@lyra-network.com 

www.lyra-network.com | www.payzen.eu 





Lyra Network, 109 rue de l'innovation, 31670 Labège, FRANCE 

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

Re: [ovirt-users] hosted engine unattended install

[Simone Tiraboschi]

On Thu, May 11, 2017 at 5:47 PM, Sandro Bonazzola 
wrote:

>
>
> On Thu, May 11, 2017 at 4:30 PM, Ramachandra Reddy Ankireddypalle <
> rcreddy.ankireddypa...@gmail.com> wrote:
>
>> Hi,
>>  I am trying to do an unattended install of hosted engine through a
>> script. All the required parameters are being read from answer file and
>> that works fine. Is there a way to provide passwords for the ovirt engine
>> linux box and admin console through answer file.
>>
>>
> Hi,
> welcome to oVirt community!
>
> Yes, you can pass admin password using the answer file.
> The environment key is: OVEHOSTED_ENGINE/adminPassword
>

And OVEHOSTED_VM/cloudinitRootPwd for the root password of the engine VM.


>
>
>
>
>> Thanks and Regards,
>> Ram
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
>
> Red Hat EMEA 
> 
> TRIED. TESTED. TRUSTED. 
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] hosted engine unattended install

[Sandro Bonazzola]

On Thu, May 11, 2017 at 4:30 PM, Ramachandra Reddy Ankireddypalle <
rcreddy.ankireddypa...@gmail.com> wrote:

> Hi,
>  I am trying to do an unattended install of hosted engine through a
> script. All the required parameters are being read from answer file and
> that works fine. Is there a way to provide passwords for the ovirt engine
> linux box and admin console through answer file.
>
>
Hi,
welcome to oVirt community!

Yes, you can pass admin password using the answer file.
The environment key is: OVEHOSTED_ENGINE/adminPassword




> Thanks and Regards,
> Ram
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

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

[ovirt-users] 4.0 : hosts connecting/non responsive and data domains inactive

[Alexis HAUSER]

After rebooting the manager VM, hosts are connecting/non responsive and data 
domains inactive. Here are the engine and vdsmd logs. Any ideas ? 




Engine logs : 



2017-05-11 17:28:09,302 WARN 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler5) [55f1aab5] Correlation ID: null, Call Stack: null, 
Custom Event ID: -1, Message: Failed to verify Power Management configuration 
for Host rhvserv-05. 
2017-05-11 17:28:09,346 INFO 
[org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler5) 
[48bc69cd] Running command: HandleVdsVersionCommand internal: true. Entities 
affected : ID: 04565f10-9abf-4709-9445-9dc6ed97e136 Type: VDS 
2017-05-11 17:28:09,349 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] 
(org.ovirt.thread.pool-6-thread-27) [639977e4] Host 'rhvserv-05' is not 
responding. 
2017-05-11 17:28:09,364 WARN 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(org.ovirt.thread.pool-6-thread-27) [639977e4] Correlation ID: null, Call 
Stack: null, Custom Event ID: -1, Message: Host rhvserv-05 is not responding. 
Host cannot be fenced automatically because power management for the host is 
disabled. 
2017-05-11 17:28:11,299 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] 
(DefaultQuartzScheduler3) [c0e6a2e] Command 'GetCapabilitiesVDSCommand(HostName 
= rhvserv-03, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', 
hostId='4036f027-8e90-49c0-8ca5-3ddb8d586916', 
vds='Host[rhvserv-03,4036f027-8e90-49c0-8ca5-3ddb8d586916]'})' execution 
failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection 
failed 
2017-05-11 17:28:11,299 ERROR 
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(DefaultQuartzScheduler3) [c0e6a2e] Failure to refresh host 'rhvserv-03' 
runtime info: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: 
Connection failed 
2017-05-11 17:28:11,327 INFO 
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] 
Connecting to rhvserv-04.mydomain.com/192.168.93.214 
2017-05-11 17:28:12,484 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] 
(DefaultQuartzScheduler3) [c0e6a2e] START, GetHardwareInfoVDSCommand(HostName = 
rhvserv-05, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', 
hostId='04565f10-9abf-4709-9445-9dc6ed97e136', 
vds='Host[rhvserv-05,04565f10-9abf-4709-9445-9dc6ed97e136]'}), log id: f807ece 
2017-05-11 17:28:12,487 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] 
(DefaultQuartzScheduler3) [c0e6a2e] FINISH, GetHardwareInfoVDSCommand, log id: 
f807ece 
2017-05-11 17:28:12,532 INFO 
[org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] 
(DefaultQuartzScheduler3) [4e882ea0] Running command: 
HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : 
ID: 04565f10-9abf-4709-9445-9dc6ed97e136 Type: VDS 
2017-05-11 17:28:12,539 INFO [org.ovirt.engine.core.bll.InitVdsOnUpCommand] 
(DefaultQuartzScheduler3) [75f25b35] Running command: InitVdsOnUpCommand 
internal: true. Entities affected : ID: 58f8df36-019f-02bc-00e7-0023 
Type: StoragePool 
2017-05-11 17:28:12,545 INFO 
[org.ovirt.engine.core.bll.storage.pool.ConnectHostToStoragePoolServersCommand] 
(DefaultQuartzScheduler3) [46cc3f58] Running command: 
ConnectHostToStoragePoolServersCommand internal: true. Entities affected : ID: 
58f8df36-019f-02bc-00e7-0023 Type: StoragePool 
2017-05-11 17:28:12,556 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] 
(DefaultQuartzScheduler3) [46cc3f58] START, 
ConnectStorageServerVDSCommand(HostName = rhvserv-05, 
StorageServerConnectionManagementVDSParameters:{runAsync='true', 
hostId='04565f10-9abf-4709-9445-9dc6ed97e136', 
storagePoolId='58f8df36-019f-02bc-00e7-0023', storageType='ISCSI', 
connectionList='[StorageServerConnections:{id='10c0528b-f08d-4d1d-8c63-8a05fd9d58b9',
 connection='10.35.21.1', 
iqn='iqn.1984-05.com.dell:powervault.md3200i.6782bcb00073e3324edde164', 
vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', 
nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log id: 1beb27b6 
2017-05-11 17:28:13,031 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] 
(DefaultQuartzScheduler3) [46cc3f58] FINISH, ConnectStorageServerVDSCommand, 
return: {10c0528b-f08d-4d1d-8c63-8a05fd9d58b9=0}, log id: 1beb27b6 
2017-05-11 17:28:13,032 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] 
(DefaultQuartzScheduler3) [46cc3f58] START, 
ConnectStorageServerVDSCommand(HostName = rhvserv-05, 
StorageServerConnectionManagementVDSParameters:{runAsync='true', 
hostId='04565f10-9abf-4709-9445-9dc6ed97e136', 
storagePoolId='58f8df36-019f-02bc-00e7-0023', storageType='NFS', 
connectionList='[StorageServerConnections:{id='e604d0d2-0810-4c25-b9ed-610f9923cb1a',
 connection='nfsserv-01:/nfs/export', 

Re: [ovirt-users] Ovirt + Citrix Xenserver support?

[Sandro Bonazzola]

On Tue, May 9, 2017 at 12:29 PM, santosh bhabal  wrote:

> Hello Experts,
>
> I am new to Ovirt community.
>

Hi, welcome to the oVirt community!



> Apology if this question has asked earlier.
> I just wanted to know that does Ovirt support Citrix Xenserver or not?
>

Sadly oVirt doesn't support Xen. There was an attempt in the past to
support it, see http://www.ovirt.org/documentation/how-to/xen/ but it has
been abanoned.

However, we support conversion of VMs from Xen to oVirt (see
http://www.ovirt.org/develop/release-management/features/virt/virt-v2v-integration/
)  so you can setup an oVirt datacenter next to the Xen one and move VMs to
oVirt / KVM.



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


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

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

Re: [ovirt-users] ovirt 4.1: migrate vm to node 2 results in lost connectivity

[Sandro Bonazzola]

On Thu, May 11, 2017 at 2:13 PM, yayo (j)  wrote:

> Hi all,
>
> I have a simple 3 node ovirt 4.1 gluster.
>

Can you be a bit more specific? Is it a Hosted Engine deployment?
Hyperconverged? Using oVirt Node for nodes?



> All works fine but when I create or move a vm to node 2 the connection is
> lost, if I move the vm back to node 1 all works fine again.
>

Dan, can youhelp here?



> Looking to ovirt engine, network seems identical (for now I have only
> ovirtmng network). If I ping something from node 2, ping works fine
> (internet in general). Where can I check also? thank you
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

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

Re: [ovirt-users] install ovirt-engine

[Sandro Bonazzola]

On Wed, May 3, 2017 at 12:01 PM, Brahim Rifahi 
wrote:

> sudo yum install -y ovirt-engine
> You do not want to work
>

Hi, welcome to oVirt community!
I understand you're trying to install oVirt for the first time.

I guess you already started reading oVirt Install Guide and following
http://www.ovirt.org/documentation/install-guide/chap-Installing_oVirt/ you
 tried to install ovirt-engine without having enabled the ovirt
repositories.

Please read http://www.ovirt.org/download/ before starting the oVirt
installation, it will explain how to get all needed repositories in place
before starting to install it.

I'm also assuming you're trying to run yum on a supported platform. Please
check supported platforms on http://www.ovirt.org/download/

If you need help, you can find us also on IRC, see
http://www.ovirt.org/community/



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


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

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

[ovirt-users] hosted engine unattended install

[Ramachandra Reddy Ankireddypalle]

Hi,
 I am trying to do an unattended install of hosted engine through a
script. All the required parameters are being read from answer file and
that works fine. Is there a way to provide passwords for the ovirt engine
linux box and admin console through answer file.

Thanks and Regards,
Ram
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] unable to set group on volume

[Joel Diaz]

Hi Kasturi,



Yes the ‘/var/lib/glusterd/virt’ was missing from my system.



I’m running ovirt on a RHEL - 7 - 3.1611.el7.centos on a physical machine.



The mistake is due to inexperience on my part. I stated earlier that I
completely removed glusterfs and reinstalled it in order to recreate the
‘/var/lib/glusterd/virt’. The way I was uninstalling and reinstalling
gluster must have been incorrect.



I ran ‘rpm -qa |grep gluster’ to get a list of the gluster components
installed. I then proceeded to remove each one on the list. Then I ran a
‘yum install glusterfs* vdsm-gluster’ since I’m not sure which rpm provides
the ‘/var/lib/glusterd/virt’ file.  I’m not sure if this installs too many
components but after that, the ‘/var/lib/glusterd/virt’ was present on my
the system. I was able to proceed normally after that.



Thanks for taking the time to engage in my question,



Joel

On May 11, 2017 2:20 AM, "knarra"  wrote:

> On 05/10/2017 10:47 PM, Joel Diaz wrote:
>
> I though I would try something different so I removed the key group and
> value virt when creating the volumes. I was able to create the volumes. I
> stopped the data volume. I then tried to set the volume group by issuing a
> "gluster volume data group virt"
>
> Still get "unable to open file '/var/lib/gluster/Virt'. Error: No such
> file or directory.
>
> I don't know if I should continue with the setup until I can set this
> value.
>
> Please let me know if I can provide some logs to identify the issue.
>
> Thanks for your help,
>
> Joel
>
> On May 10, 2017 6:57 AM, "Joel Diaz"  wrote:
>
> Thanks for the reply.
>
> The file is empty. I created the file by issuing a "touch
> /var/lib/glusterd/groups/virt"
>
> The first time I attempted to set the group volume, the error was that the
> file was missing. I read a bug report that advised to remove and reinstall
> the gluster package in order to properly recreate the file. Since that did
> not work, I created it manually.
>
> Thank you,
>
> Joel
>
> Hi Joel,
>
> Do you have this file present on the system ? This file will be
> present when glusterfs is installed. I would like to first understand how
> is it missing on your system? The error is because i see that you do not
> have the file present there. Can you please paste output of "ls -l
> /var/lib/glusterd/groups/virt" ?
>
>
> Thanks
> kasturi
>
>
> On Wed, May 10, 2017 at 2:12 AM, knarra  wrote:
>
>> On 05/10/2017 06:37 AM, Joel Diaz wrote:
>>
>> Hello ovirt users,
>>
>> First off all, thanks for your work. I've been using the software for a
>> few months and the experience has been great.
>>
>> I'm having a hard time trying to set the group on a glusterfs volume
>>
>> PLAY [master] **
>> 
>>
>> TASK [Sets options for volume] **
>> ***
>> failed: [192.168.170.141] (item={u'key': u'group', u'value': u'virt'}) =>
>> {"failed": true, "item": {"key": "group", "value": "virt"}, "msg":
>> "'/var/lib/glusterd/groups/virt' file format not valid.\n"}
>>
>> From this error it looks like the virt file format is not valid? Can you
>> please paste the contents of this file?
>>
>> changed: [192.168.170.141] => (item={u'key': u'storage.owner-uid',
>> u'value': u'36'})
>> changed: [192.168.170.141] => (item={u'key': u'storage.owner-gid',
>> u'value': u'36'})
>> changed: [192.168.170.141] => (item={u'key': u'network.ping-timeout',
>> u'value': u'30'})
>> changed: [192.168.170.141] => (item={u'key':
>> u'performance.strict-o-direct', u'value': u'on'})
>> changed: [192.168.170.141] => (item={u'key': u'network.remote-dio',
>> u'value': u'off'})
>> changed: [192.168.170.141] => (item={u'key':
>> u'cluster.granular-entry-heal', u'value': u'enable'})
>> to retry, use: --limit @/tmp/tmpdTWQ8B/gluster-volume-set.retry
>>
>> PLAY RECAP 
>> *
>> 192.168.170.141: ok=0changed=0unreachable=0
>>  failed=1
>>
>> I've tried to remove remove glusterfs, wiping the glusterfs
>> configurations and reinstalling the service.
>>
>> Any help would be appreciated.
>>
>> Thank you,
>>
>> Joel
>>
>>
>> ___
>> Users mailing 
>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Cloning VM on NFS Leads to Locked Disks

[Charles Tassell]

Hi Freddy,

  Sure, thanks for looking into this.  Here you go:

2017-05-10 11:35:30,249-03 INFO 
[org.ovirt.engine.core.bll.aaa.SessionDataContainer] 
(DefaultQuartzScheduler8) [1c84abac] Not removing session 
'vZyqrcCljPC7hQtcILsk4uDug3QsiinZBOyoGDiQKkYYT2znGyWe4fasrPbjYxdjbfyR3DBnp+UZ9/k20dGsMA==', 
session has running commands for user 'admin@internal-authz'.
2017-05-10 11:35:30,249-03 INFO 
[org.ovirt.engine.core.bll.aaa.SessionDataContainer] 
(DefaultQuartzScheduler8) [1c84abac] Not removing session 
'nLzKb6P4Th3A9zUFNNZYuZgWaL/DraYRfQjOvjmXisa9c3SiI+Sv8xvLZ+n2+9ptKPHqaiw0oNCOG6kDWOaszA==', 
session has running commands for user 'admin@internal-authz'.
2017-05-10 11:35:37,793-03 INFO 
[org.ovirt.engine.core.bll.storage.disk.UpdateVmDiskCommand] (default 
task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] Lock Acquired to object 
'EngineLock:{exclusiveLocks='[6d51dd95-ba25-4ae9-8bee-303f90e76e62=]', 
sharedLocks='[6d51dd95-ba25-4ae9-8bee-303f90e76e62=]'}'
2017-05-10 11:35:37,843-03 INFO 
[org.ovirt.engine.core.bll.storage.disk.UpdateVmDiskCommand] (default 
task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] Running command: 
UpdateVmDiskCommand internal: false. Entities affected : ID: 
d73206ed-89ba-48a9-82ff-c107c1af60f0 Type: DiskAction group 
EDIT_DISK_PROPERTIES with role type USER
2017-05-10 11:35:37,846-03 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] START, 
SetVolumeDescriptionVDSCommand( 
SetVolumeDescriptionVDSCommandParameters:{runAsync='true', 
storagePoolId='0001-0001-0001-0001-0311', 
ignoreFailoverLimit='false', 
storageDomainId='20423d5e-188c-4e10-9893-588ceb81b354', 
imageGroupId='d73206ed-89ba-48a9-82ff-c107c1af60f0', 
imageId='bba1813d-9e91-4e37-bed7-40beedda8051'}), log id: 31e5d891
2017-05-10 11:35:37,846-03 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] -- 
executeIrsBrokerCommand: calling 'setVolumeDescription', parameters:
2017-05-10 11:35:37,846-03 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] ++ 
spUUID=0001-0001-0001-0001-0311
2017-05-10 11:35:37,846-03 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] ++ 
sdUUID=20423d5e-188c-4e10-9893-588ceb81b354
2017-05-10 11:35:37,846-03 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] ++ 
imageGroupGUID=d73206ed-89ba-48a9-82ff-c107c1af60f0
2017-05-10 11:35:37,846-03 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] ++ 
volUUID=bba1813d-9e91-4e37-bed7-40beedda8051
2017-05-10 11:35:37,846-03 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] ++ 
description={"DiskAlias":"Ubu16_Disk1","DiskDescription":""}
2017-05-10 11:35:37,937-03 INFO 
[org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] FINISH, 
SetVolumeDescriptionVDSCommand, log id: 31e5d891
2017-05-10 11:35:37,981-03 INFO 
[org.ovirt.engine.core.bll.storage.disk.UpdateVmDiskCommand] (default 
task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] Lock freed to object 
'EngineLock:{exclusiveLocks='[6d51dd95-ba25-4ae9-8bee-303f90e76e62=]', 
sharedLocks='[6d51dd95-ba25-4ae9-8bee-303f90e76e62=]'}'
2017-05-10 11:35:37,988-03 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-11) [2c63ae40-b59d-4a80-b348-6c9b9fa176b8] EVENT_ID: 
USER_UPDATE_VM_DISK(88), Correlation ID: 
2c63ae40-b59d-4a80-b348-6c9b9fa176b8, Call Stack: null, Custom Event ID: 
-1, Message: VM Ubu16 Xenial_Disk1 disk was updated by admin@internal-authz.
2017-05-10 11:36:19,931-03 INFO 
[org.ovirt.engine.core.bll.CloneVmCommand] (default task-15) 
[6c38dbf9-6c8f-4390-979f-4031b5b46c98] Lock Acquired to object 
'EngineLock:{exclusiveLocks='[chUbu16Clone=]', 
sharedLocks='[d73206ed-89ba-48a9-82ff-c107c1af60f0=, 
6d51dd95-ba25-4ae9-8bee-303f90e76e62=]'}'
2017-05-10 11:36:19,981-03 INFO 
[org.ovirt.engine.core.bll.CloneVmCommand] (default task-15) 
[6c38dbf9-6c8f-4390-979f-4031b5b46c98] Running command: CloneVmCommand 
internal: false. Entities affected :  ID: 
6d51dd95-ba25-4ae9-8bee-303f90e76e62 Type: VMAction group CREATE_VM with 
role type 

Re: [ovirt-users] Glusterd Service Stopped Working After Delete Volume And Peers ID

[knarra]

Hi,

When you say service is not working are you not able to start 
glusterd any more? If yes, can you please look at 
/var/log/glusterfs/glusterd.log and see if there are any errors? How did 
you delete your peer ids? By running gluster peer detach ?


Thanks
kasturi


On 05/11/2017 06:01 PM, Khalid Jamal wrote:


Dear Team


i have error on glusterd service it's not working after delete gluster 
volume and delete all peers id , the service is not working , what 
shall i do , i bake all id peers on all gluster node but service still 
not working is that a bug , by the way my gluster version is (3.8.10) .


best regards


Eng khalid jamal
System Admin@IT Department
Earthlink Telecom

Email: khalid.ja...@earthlinktele.com
No: 3355
skype: engkhalid21986
NO : 07704268321



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



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

[ovirt-users] Glusterd Service Stopped Working After Delete Volume And Peers ID

[Khalid Jamal]

Dear Teami have error on glusterd service it's not working after delete gluster volume and delete all peers id , the service is not working , what shall i do , i bake all id peers on all gluster node but service still not working is that a bug , by the way my gluster version is (3.8.10) .best regardsEng khalid jamalSystem Admin@IT DepartmentEarthlink TelecomEmail: khalid.ja...@earthlinktele.comNo: 3355skype: engkhalid21986NO : 07704268321
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ovirt 4.1: migrate vm to node 2 results in lost connectivity

[yayo (j)]

Hi all,

I have a simple 3 node ovirt 4.1 gluster. All works fine but when I create
or move a vm to node 2 the connection is lost, if I move the vm back to
node 1 all works fine again. Looking to ovirt engine, network seems
identical (for now I have only ovirtmng network). If I ping something from
node 2, ping works fine (internet in general). Where can I check also?
thank you
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Current status of ManageIQ to manage oVirt 4.1.1?

[Michal Skrivanek]

On 11 May 2017, at 10:50, Gianluca Cecchi  wrote:

On Thu, May 11, 2017 at 9:44 AM, Juan Hernández  wrote:

>
> > Do I have to add in any way also the hypervisors to the ManageIQ
> > configuration? Or should it be automatic?
> >
>
> The hosts should be added automatically. Moti, I remember that you
> mentioned some issue with hosts. Was that resolved?
>

Sorry I was misreading the web output at a first sight.
It is ok. I see hosts in Compute --> Infrastructure --> Hosts
I see managers in Compute --> Infrastructure --> Providers



>
> > Also, do you know when I choose to see console in ManageIQ, both the
> > "web console"  and the "WM console" options in "Access" menu, from where
> > the connection is originated: my client where browser is running or from
> > manageiq server and then passed in any way to client?
> > Which protocol does the web console use?
> >
>
> I am not sure about that. Martin, can you answer that question?
>

Ok, I took the time to RTFM ;-)
here:
http://manageiq.org/docs/reference/latest/doc-Managing_Infrastructure_and_Inventory/miq/#_vnc_and_spice_consoles

It seems that for oVirt/RHEV it uses websocket proxy base console.
The 2 options offered in "Fine" version of manageiq are for oVirt:

Access --> VM Console
for spice/vnc through websocket proxy


Right. Just beware it may not work very well


Access -->Web Console
>From the pop-up help message when mouse over it says
Open a new browser window with Cockpit for this VM. This requires that
Cockpit is pre-configured on the VM


Yes, it's not what you would understand as a guest console in oVirt


I should investigate this second option

Thanks for the moment and if there is more information it will be of help
debugging.

BTW: I was able to successfully configure inside ManageIQ 3 environments:
- one standalone host with self hosted engine (in 4.1.2pre)
- one engine that manages 3 hosts (in 4.1.1)
- one ESXi vcenter with 6.0 that manages 6 hosts

Nice environment. I have to understand better role segregation, limits and
such...

Gianluca

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

Re: [ovirt-users] unhappiness with ovirt engine after upgrading file server handling storage domain

[Oved Ourfali]

You also have fencing policies around the cluster.
Those allow you to disable fencing entirely, so define the criteria for
disabling fencing (do not fence if the host maintains its storage lease,
and do not fence in case more than X% of the hosts in the cluster aren't
responding).

On Thu, May 11, 2017 at 8:41 AM, plysan  wrote:

> did you restart your nfs service or reboot your nfs host during the
> upgrade progress ?
> if you did, what's the webadmin portal's storage domain's status at the
> time ?
>
> what i'm suspecting is that you were restarting nfs while ovirt-engine is
> using it.
>
> 2017-05-11 2:02 GMT+08:00 Jason Keltz :
>
>> Hi.
>>
>> I recently upgraded my oVirt infrastructure to the latest
>> 4.1.1.8-1.el7.centos, which went smoothly.  Thanks oVirt team! This
>> morning, I upgraded my NFS file server which manages the storage domain.  I
>> stopped ovirt engine, did a yum update to bring the server from its older
>> CentOS 7.2 release to CentOS 7.3, rebooted it, then restarted engine.   At
>> that point, engine was unhappy because our 4 virtualization hosts had a
>> total of 30 VMs all waiting to reconnect to storage.  The status of all the
>> VMs went to unknown in engine.  It took almost 2 hours before everything
>> was completely normal again.  It seems that the hosts were available long
>> before engine updated status.  I'm assuming it's better to restart engine
>> when I know that NFS has resumed on all the 30 virtalized hosts.  However,
>> it's hard to know when that's happened, without trying to connect manually
>> to all the hosts.  Is there a way to warn engine that you're about to mess
>> with the storage domain, and you don't want it to do anything drastic? Sort
>> of like a "maintenance mode" for storage?I would hate for it to start
>> trying to power off hosts via power management or migrate hosts when it
>> just needs to wait a bit...
>>
>> Thanks!
>>
>> Jason.
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Engine deploy tab is missing when restoring from db-backup?

[gflwqs gflwqs]

Hi list,
I have restored my 4.1 engine.
After i have restored the engine the engine deploy tab is missing?
And since it is not possible anymore to deploy thru command line i am not
able to deploy new hosts?
- Does anybody know a workaround to deploy new hosts?
- Is this a bug or am i doing something wrong when restoring?

This is how i restored:
[root@ovirt-engine ~]# engine-backup --mode=restore --file=backup.tar
--log=restore.log --provision-db --provision-dwh-db --restore-permissions


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

Re: [ovirt-users] Current status of ManageIQ to manage oVirt 4.1.1?

[Gianluca Cecchi]

On Thu, May 11, 2017 at 9:44 AM, Juan Hernández  wrote:

>
> > Do I have to add in any way also the hypervisors to the ManageIQ
> > configuration? Or should it be automatic?
> >
>
> The hosts should be added automatically. Moti, I remember that you
> mentioned some issue with hosts. Was that resolved?
>

Sorry I was misreading the web output at a first sight.
It is ok. I see hosts in Compute --> Infrastructure --> Hosts
I see managers in Compute --> Infrastructure --> Providers



>
> > Also, do you know when I choose to see console in ManageIQ, both the
> > "web console"  and the "WM console" options in "Access" menu, from where
> > the connection is originated: my client where browser is running or from
> > manageiq server and then passed in any way to client?
> > Which protocol does the web console use?
> >
>
> I am not sure about that. Martin, can you answer that question?
>

Ok, I took the time to RTFM ;-)
here:
http://manageiq.org/docs/reference/latest/doc-Managing_Infrastructure_and_Inventory/miq/#_vnc_and_spice_consoles

It seems that for oVirt/RHEV it uses websocket proxy base console.
The 2 options offered in "Fine" version of manageiq are for oVirt:

Access --> VM Console
for spice/vnc through websocket proxy

Access -->Web Console
>From the pop-up help message when mouse over it says
Open a new browser window with Cockpit for this VM. This requires that
Cockpit is pre-configured on the VM

I should investigate this second option

Thanks for the moment and if there is more information it will be of help
debugging.

BTW: I was able to successfully configure inside ManageIQ 3 environments:
- one standalone host with self hosted engine (in 4.1.2pre)
- one engine that manages 3 hosts (in 4.1.1)
- one ESXi vcenter with 6.0 that manages 6 hosts

Nice environment. I have to understand better role segregation, limits and
such...

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

Re: [ovirt-users] Renaming VM needs restart?

[Michal Skrivanek]

> On 11 May 2017, at 10:19, nico...@devels.es wrote:
> 
> Hi,
> 
> We're using oVirt 4.1.1.8-1. I just edited a powered on VM to rename it and a 
> popup was shown stating that a restart is required. Is that new, or is it a 
> bug? I remember not having to do so in prior versions.

correct. As this is how the QEMU process is named.
It was a bug before that it was not reflected correctly after the change, e.g. 
in libvirt-and-below logs.

Thanks,
michal

> 
> I'm attaching a snapshot.
> 
> Thanks.
> 
> Regards. 09-14-47.png>___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

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

[ovirt-users] Renaming VM needs restart?

[nicolas]

Hi,

We're using oVirt 4.1.1.8-1. I just edited a powered on VM to rename it 
and a popup was shown stating that a restart is required. Is that new, 
or is it a bug? I remember not having to do so in prior versions.


I'm attaching a snapshot.

Thanks.

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

Re: [ovirt-users] Current status of ManageIQ to manage oVirt 4.1.1?

[Juan Hernández]

On 05/09/2017 01:02 PM, Gianluca Cecchi wrote:
> On Fri, May 5, 2017 at 4:47 PM, Juan Hernández  > wrote:
> 
> 
> Yes, capablanca is too old.
> 
> The instructions that you mention should still work, but remember to
> make a backup before doing that in your production environment.
> 
> Anyhow, I'd suggest that you install a fresh euwe, if that is an option
> for you.
> 
> There is no support for YUM/RPM upgrades, as far as I know.
> 
> 
> OK, after some attempts to upgrade in place my capablanca VM (just for
> learning), I abandoned it.
> It seems the euwe stable qemu/kvm has some problems too in general... I
> get this during the initialization after VM start
> 
> appliance_console_cli --region 0 --internal --password smartvm
> /opt/rubies/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.14.6/lib/bundler/source/git/git_proxy.rb:225:in
> |allowed_in_path': The git source
> https://github.com/ManageIQ/manageiq-providers-amazon is not yet checked
> out. Please run|bundle install` before trying to start your application
> (Bundler::GitError)
> 
> Then I have tried the just released Fine qemu/kvm rc1 image and it works
> ok, so I'm using it for my tests...
> I was able to add oVirt engine 4.1.2 pre.
> But now I see almost all (VMs, datastores, ecc.) but the hosts...
> Furthermore in Compute --> Infrastructure --> Hosts I do find the engine
> but not the host...
> Do I have to add in any way also the hypervisors to the ManageIQ
> configuration? Or should it be automatic?
> 

The hosts should be added automatically. Moti, I remember that you
mentioned some issue with hosts. Was that resolved?

> Also, do you know when I choose to see console in ManageIQ, both the
> "web console"  and the "WM console" options in "Access" menu, from where
> the connection is originated: my client where browser is running or from
> manageiq server and then passed in any way to client?
> Which protocol does the web console use?
>

I am not sure about that. Martin, can you answer that question?


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

Re: [ovirt-users] Docker images for oVirt engine

[Juan Hernández]

On 05/11/2017 08:54 AM, Barak Korren wrote:
> On 11 May 2017 at 06:02, Leni Kadali Mutungi  wrote:
>>> On 5/10/17, Barak Korren  wrote:
 That one is obsolete AFAIK. The oVirt container images are now being
 worked on in the 'ovirt-containers' repo.
>>
>> Checked it out. It seems more complicated than what I need, which
>> would be just a Dockerfile that pulls the required image. The
>> ovirt-containers repo seems to have a dependency on OpenCluster, which
>> I think I won't need since I'm after a basic install on one machine
>> for documentation purposes. Your advice is appreciated.
> 
> Adding ovirt-containers developers. Yaniv, Juan, Fabian, Sandro,
> Simone - can ovirt-containers be used for his purpose?
> 
> Also adding Rgolan since he did work in the past on a containerized
> dev environment for oVirt.
> 
> If you just want your own little oVirt install "in a box" for
> testing/dev purposes, you can look at Lago and the ovirt-system-tests
> projects.
> 
> 

You may be able to use the engine container independently, with some
effort. But this 'ovirt-containers' project isn't certainly intended for
that simple use case, it is intended to be able to deploy the complete
oVirt system in an OpenShift cluster.

If you are willing to give this a try, and you already have a docker
installation, creating an OpenShift cluster for testing purposes is
really simple. You can use 'oc cluster up'. It is a matter of
downloading the 'oc' tool from here:


https://github.com/openshift/origin/releases/download/v1.5.0/openshift-origin-client-tools-v1.5.0-031cbe4-linux-64bit.tar.gz

That contains the 'oc' binary. Put it in your path and then run this
command:

  oc cluster up

That will pull all the required images, and configure a simple OpenShift
cluster into your machine. Once that completes you can proceed to deploy
the oVirt application. First you need to build the images, as they
aren't yet available in a public repository. To build the images
checkout the code of the project:

  git clone git://gerrit.ovirt.org/ovirt-containers

Then go into that directory and run this:

  make build

That will take quite a long time, as it needs to build all the images,
and it requires downloading of the base images and of the RPMs that go
into the images being built. Be patient.

Once the images are built, you can deploy the complete oVirt application
running this:

  make deploy

Would be great to have you testing this, giving feedback and reporting
any issues you find. But be aware that this is in a very early stage of
development and should be considered experimental.

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

Re: [ovirt-users] Cloning VM on NFS Leads to Locked Disks

[Fred Rolland]

Hi,

Can you provide the engine log ?

Thanks,

Freddy

On Wed, May 10, 2017 at 5:57 PM, Charles Tassell 
wrote:

> Hi Everyone,
>
>   I'm having some issues with my oVirt 4.1 (fully updated to latest
> release as of yesterday) cluster.  When I clone a VM the disks of both the
> original and the clone stay in the locked state, and the only way I can
> resolve it is to go into the database on the engine and run "update images
> set imagestatus=1 where imagestatus=2;"
>
>   I'm using NFS4 as a datastore and the disks seem to copy fine (file
> sizes match and everything), but the locking worries me.  To clone the VM I
> just shut the source VM down and then right click on it and select "Clone"
>
>   I've attached the full VDSM log from my last attempt, but here is the
> excerpt of the lines just referencing the two disks
> (d73206ed-89ba-48a9-82ff-c107c1af60f0 is the original VMs disk and
> 670a7b20-fecd-45c6-af5c-3c7b98258224 is the clone.)
>
> 2017-05-10 11:36:20,120-0300 INFO  (jsonrpc/2) [dispatcher] Run and
> protect: copyImage(sdUUID=u'20423d5e-188c-4e10-9893-588ceb81b354',
> spUUID=u'0001-0001-0001-0001-0311', vmUUID='',
> srcImgUUID=u'd73206ed-89ba-48a9-82ff-c107c1af60f0',
> srcVolUUID=u'bba1813d-9e91-4e37-bed7-40beedda8051',
> dstImgUUID=u'670a7b20-fecd-45c6-af5c-3c7b98258224',
> dstVolUUID=u'013d8855-4e49-4984-8266-6a5e9437dff7', description=u'',
> dstSdUUID=u'20423d5e-188c-4e10-9893-588ceb81b354', volType=8,
> volFormat=5, preallocate=2, postZero=u'false', force=u'false',
> discard=False) (logUtils:51)
> 2017-05-10 11:36:20,152-0300 INFO  (jsonrpc/2) [storage.Image] image
> d73206ed-89ba-48a9-82ff-c107c1af60f0 in domain
> 20423d5e-188c-4e10-9893-588ceb81b354 has vollist
> [u'bba1813d-9e91-4e37-bed7-40beedda8051'] (image:319)
> 2017-05-10 11:36:20,169-0300 INFO  (jsonrpc/2) [storage.Image]
> sdUUID=20423d5e-188c-4e10-9893-588ceb81b354 
> imgUUID=d73206ed-89ba-48a9-82ff-c107c1af60f0
> chain=[] (image:249)
> 2017-05-10 11:36:20,292-0300 INFO  (tasks/0) [storage.Image]
> sdUUID=20423d5e-188c-4e10-9893-588ceb81b354 
> imgUUID=d73206ed-89ba-48a9-82ff-c107c1af60f0
> chain=[] (image:249)
> 2017-05-10 11:36:20,295-0300 INFO  (tasks/0) [storage.Image]
> sdUUID=20423d5e-188c-4e10-9893-588ceb81b354 vmUUID=
> srcImgUUID=d73206ed-89ba-48a9-82ff-c107c1af60f0
> srcVolUUID=bba1813d-9e91-4e37-bed7-40beedda8051
> dstImgUUID=670a7b20-fecd-45c6-af5c-3c7b98258224
> dstVolUUID=013d8855-4e49-4984-8266-6a5e9437dff7
> dstSdUUID=20423d5e-188c-4e10-9893-588ceb81b354 volType=8 volFormat=RAW
> preallocate=SPARSE force=False postZero=False discard=False (image:765)
> 2017-05-10 11:36:20,305-0300 INFO  (tasks/0) [storage.Image] copy source
> 20423d5e-188c-4e10-9893-588ceb81b354:d73206ed-89ba-48a9-
> 82ff-c107c1af60f0:bba1813d-9e91-4e37-bed7-40beedda8051 vol size 41943040
> destination 20423d5e-188c-4e10-9893-588ceb81b354:670a7b20-fecd-45c6-
> af5c-3c7b98258224:013d8855-4e49-4984-8266-6a5e9437dff7 apparentsize
> 41943040 (image:815)
> 2017-05-10 11:36:20,306-0300 INFO  (tasks/0) [storage.Image] image
> 670a7b20-fecd-45c6-af5c-3c7b98258224 in domain
> 20423d5e-188c-4e10-9893-588ceb81b354 has vollist [] (image:319)
> 2017-05-10 11:36:20,306-0300 INFO  (tasks/0) [storage.Image] Create
> placeholder /rhev/data-center/0001-0001-0001-0001-0311/20423
> d5e-188c-4e10-9893-588ceb81b354/images/670a7b20-fecd-45c6-af5c-3c7b98258224
> for image's volumes (image:149)
> 2017-05-10 11:36:20,392-0300 INFO  (tasks/0) [storage.Volume] Request to
> create RAW volume /rhev/data-center/0001-000
> 1-0001-0001-0311/20423d5e-188c-4e10-9893-588ceb81b35
> 4/images/670a7b20-fecd-45c6-af5c-3c7b98258224/013d8855-4e49-4984-8266-6a5e9437dff7
> with size = 20480 sectors (fileVolume:439)
> 2017-05-10 11:37:58,453-0300 INFO  (tasks/0) [storage.VolumeManifest]
> sdUUID=20423d5e-188c-4e10-9893-588ceb81b354 
> imgUUID=670a7b20-fecd-45c6-af5c-3c7b98258224
> volUUID = 013d8855-4e49-4984-8266-6a5e9437dff7 legality = LEGAL
> (volume:393)
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Docker images for oVirt engine

[Barak Korren]

On 11 May 2017 at 06:02, Leni Kadali Mutungi  wrote:
>> On 5/10/17, Barak Korren  wrote:
>>> That one is obsolete AFAIK. The oVirt container images are now being
>>> worked on in the 'ovirt-containers' repo.
>
> Checked it out. It seems more complicated than what I need, which
> would be just a Dockerfile that pulls the required image. The
> ovirt-containers repo seems to have a dependency on OpenCluster, which
> I think I won't need since I'm after a basic install on one machine
> for documentation purposes. Your advice is appreciated.

Adding ovirt-containers developers. Yaniv, Juan, Fabian, Sandro,
Simone - can ovirt-containers be used for his purpose?

Also adding Rgolan since he did work in the past on a containerized
dev environment for oVirt.

If you just want your own little oVirt install "in a box" for
testing/dev purposes, you can look at Lago and the ovirt-system-tests
projects.


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] do we need some documentation mainteiners?

[Yedidyah Bar David]

On Thu, May 11, 2017 at 8:50 AM, Yedidyah Bar David  wrote:
> On Wed, May 10, 2017 at 8:07 PM, Juan Pablo  wrote:
>> I am!  =)
>> but Im dizzy on how/where to start.
>> suggestions/ideas are welcome
>
> Perhaps start by reading the readme file of the site:
>
> https://github.com/oVirt/ovirt-site
>
> and continue with "CONTRIBUTING.md" and "MAINTAINING.md" there.
>
> If you are new to git/github, you should probably read about them too,
> although for simply editing the web site the basics should be enough.
>
> Feel free to ask any questions - perhaps on de...@ovirt.org instead of
> here. Welcome and good luck!

I'd also like to take the opportunity and talk a bit about the content.

Many times people here refer to RHV documentation.
RHV documentation is indeed very good, but has a few problems, if you
consider "simply" copying from there:

1. It's RHV-specific. 99% of times this is irrelevant, but when it is,
RHV doc writers do not make any attempt to be oVirt-compatible. Examples:
It does not cover at all Fedora-specific issues, it did not cover in the
past use of oVirt 3.5 and 3.6 on EL7 (because RHV did not support that).

2. You should study well the legal notices included in the guides there.
The licenses for RHV documentation are quite different from the licenses
for the oVirt projects' source code.

3. It's written by writers, not developers. This means it's much more
organized, more-or-less complete, better written, but still might be
out-of-date or inaccurate.

4. It tends to be less detailed about feature internals, about things
that might break if you do not follow the doc, about non-standard
potential uses, etc. It's mostly intended for people that do things
"by the book" :-) It usually does not cover things that Red Hat
decided to not support, even if they mostly work.

Other sources for content one should consider, both for direct learning
and as a source for writing documentation:

1. Mailing list archives. Both users and devel can be useful.

2. Discussions on bugzilla bugs. Many times you can find there the most
accurate definition of what a feature does, how to test/use it, and how
it was verified.
When you do that, check if the bug is on oVirt or on RHV. In the past,
the distinction wasn't as accurate and not strictly followed, but in
recent versions we try to better make sure that bugs that are opened
on RHV and affect also oVirt are moved to oVirt. See also:

https://www.ovirt.org/develop/dev-process/bugzilla-rework/

3. Source code. In some parts it's rather easy to follow if you have
any experience dealing with source code, and in others you can at least
read the comments. This applies even if you never _wrote_ a single line
of source code in any programming language. when you decide to have a
look at the source code, you should do this by cloning the git projects,
not by downloading the tarballs or SRPMs. This way you win on two fronts:
a. You get at once the entire project history including all its versions,
in a single place.
b. You can then also search the git history and find out when something
was changed, comments about the change, etc.

4. gerrit. gerrit is our review tool, and all patches for the projects
maintained there go through it. This in many cases includes long
discussions between developers about what the patch actually should
do and how it should do that. In some cases you can also see there how
a patch was verified to do what it's supposed to do.
Sadly, gerrit review history isn't as easy to search as the other
sources above. Perhaps we should do something to make it easier as well.

>
>>
>> JP
>>
>> El 10/5/2017 12:20, "Barak Korren"  escribió:
>>>
>>> On 10 May 2017 at 14:18, Juan Pablo  wrote:
>>> > this was not the intention of the thread. so please stop throwing
>>> > bananas
>>> > each other.
>>> >
>>> > Lets focus on the subject here:do we need some documentation
>>> > mainteiners?
>>> > yes/no
>>>
>>> My answer would be definitely.
>>> If you are volunteering, you would be very welcome.
>>>
>>>
>>> --
>>> Barak Korren
>>> RHV DevOps team , RHCE, RHCi
>>> Red Hat EMEA
>>> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
> --
> Didi



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