Re: [ovirt-users] Upgrade patch 3.5 -> 3.6

2016-02-16 Thread Yedidyah Bar David 
On Wed, Feb 17, 2016 at 9:09 AM, Николаев Алексей
 wrote:
> You must not configure firewall in backup restore procedure. Because EL6
> backup uses iptables instead EL7 fresh install uses firewalld.

Thanks for pointing that out!

Does this mean you actually tried this and that was the only issue?

Note also that EL7 also has iptables, you can use that if you want.
You'll have to do something like:
yum install iptables-services
systemctl disable firewalld.service
systemctl enable iptables.service
systemctl start iptables.service
You'll not have any default /etc/sysconfig/iptables, though. Either create
one manually (or find somewhere) or use e.g. system-config-firewall-tui.

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

Re: [ovirt-users] question mark in oVirt - "cannot acquire state change lock"

2016-02-16 Thread Nir Soffer 
On Tue, Feb 16, 2016 at 9:58 PM, p...@email.cz  wrote:
> Hello all,
> how can I eliminate question mark from "hanged" VM? ( it happened in
> shutdown process via oVirt  env. )
> Best solution without hypervizor reboot, meaning "power off" , "kill" or
> another workaround for that VM .
> Will help removing task DB record from oVirt mgmt server - if exists ,
> ofcourse ??
> Running  gluster 3.7.5 / oVirt 3.5.2 /
> libvirt-daemon-kvm-1.2.8-16.el7_1.5.x86_64  on centos 7.1.1503 .
>
> thx a lot.
> Pa.
>
> PS: I found similar problem in libvirt library a many years ago ( redhat 5.6
> )
>https://bugzilla.redhat.com/show_bug.cgi?id=676205
>https://bugzilla.redhat.com/show_bug.cgi?id=668438
> problem explanation:
> http://linux.india365.org/2012/01/libvirt-virsh-cannot-acquire-state-change-lock-error-explained/

This is very interesting, I have seen this error in testing
environment on rhel 7.1 or 7.2.

Can you provide vdsm logs showing the time of the error?

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

Re: [ovirt-users] Upgrade patch 3.5 -> 3.6

2016-02-16 Thread Николаев Алексей 
  16.02.2016, 16:31, "Alexander Wels" :On Tuesday, February 16, 2016 12:36:58 PM Johan Kooijman wrote: Ack, thx. On Tue, Feb 16, 2016 at 11:46 AM, Yedidyah Bar David  wrote: > On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman  >  > wrote: > > Didi, > >  > > Ok, the piece of information on engine still supported on 3.6 was >  > unknown to >  > > me. Makes my job a lot easier. > >  > > What would be the recommended path: first upgrade the nodes to 3.6 and >  > then >  > > the engine? Or the other way around? >  > Generally speaking, first engine then nodes. I am pretty certain it's > documented > on the wiki, didn't check. > Basically follow what I wrote should do what you want. Then if you later want to upgrade the engine from EL6 to EL7 you should be able to make a backup of the engine with the engine-backup tool. Then install a fresh engine on EL7 and restore the backup with that tool. Your VMs won't be affected if the engine is gone for a little bit (well besides not being able to manage them during the change over).You must not configure firewall in backup restore procedure. Because EL6 backup uses iptables instead EL7 fresh install uses firewalld. But as Didi wrote, right now EL6 is still supported so you can simply upgrade to oVirt 3.6 on EL6. > > On Tue, Feb 16, 2016 at 8:45 AM, Yedidyah Bar David  >  > wrote: > >> On Tue, Feb 16, 2016 at 9:30 AM, Johan Kooijman  >>  > >> wrote: > >> > Yes. I pasted the information on AIO, that was wrong on my end. I > >> > have > >> > an > >> > engine running on dedicated hardware and about 20 nodes in this >  > cluster. >  > >> > I > >> > do like to upgrade without downtime :) I know how to achieve this on >  > the >  > >> > node-end, but since I have to go from C6 to C7, I wonder what the > >> > procedure > >> > would be for engine. > >>  > >> Please explain exactly what you are trying to do. > >>  > >> Note that engine is still supported on el6. > >>  > >> (new) Hosts are not. > >>  > >> all-in-one is running both together, thus is not supported on el6 >  > either. >  > >> IIRC we do not have a tested procedure to upgrade the engine from C6 to >  > C7 >  > >> yet, see also: > >>  > >> https://bugzilla.redhat.com/show_bug.cgi?id=1234257 > >> https://bugzilla.redhat.com/show_bug.cgi?id=1285743 > >>  > >> Best, > >>  > >> > On Mon, Feb 15, 2016 at 9:21 PM, Alexander Wels  > >> >  > >> > wrote: > >> >> On Monday, February 15, 2016 08:21:40 PM Johan Kooijman wrote: > >> >> > Hi Alexander, > >> >> >  > >> >> > Thanks for the input! My 3.5 is running on C6 however: > >> >> >  > >> >> > Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the > >> >> > packages > >> >> > requiring it are not built anymore for EL6 > >> >>  > >> >> Well that was a piece of information you forgot to mention in your > >> >> initial > >> >> email. So now I am not entirely sure what you are trying to do. Are >  > you >  > >> >> trying > >> >> to save your existing VMs when you reinstall your machine? > >> >>  > >> >> > On Mon, Feb 15, 2016 at 3:37 PM, Alexander Wels  > >> >> >  > >> >> > wrote: > >> >> > > On Monday, February 15, 2016 02:40:47 PM Johan Kooijman wrote: > >> >> > > > Hi, > >> >> > > >  > >> >> > > > Can anybody recommend me best practice upgrade path for an > >> >> > > > upgrade > >> >> > > > from > >> >> > > > oVirt 3.5 on C6 to 3.6 on C7.2? > >> >> > >  > >> >> > > The answer sort of depends on what you want. Do you want no > >> >> > > downtime > >> >> > > on > >> >> > > your > >> >> > > VMs or is downtime acceptable. Also are you running hosted > >> >> > > engine > >> >> > > or > >> >> > > not? > >> >> > >  > >> >> > > This is the basic plan which can be adjusted based on what your > >> >> > > needs > >> >> > > are: > >> >> > >  > >> >> > > 1. Update engine from 3.5 to 3.6 (if hosted engine might be > >> >> > > trickier, > >> >> > > not > >> >> > > sure > >> >> > > haven't played with hosted engine). > >> >> > > 2. Create a new 3.6 cluster. > >> >> > > 3. Put 1 host in maintenance (which will migrate the VMs to the > >> >> > > other > >> >> > > hosts). > >> >> > > 4. Remove the host from the DC. > >> >> > > 5. Install C7.2 on the host > >> >> > > 6. Add that host to the new 3.6 cluster. > >> >> > > 7. Optional (you can cross cluster live migrate some VMs from 6 >  > to >  > >> >> > > 7 > >> >> > > (just > >> >> > > not > >> >> > > the other way around, so once the VM is moved its stuck in the >  > new >  > >> >> > > cluster). > >> >> > > 8. Go to 3 until all hosts are moved. > >> >> > > 9. Your 3.5 cluster should now be empty, and can be removed. > >> >> > > 10. Upgrade your DC to 3.6 (Can't upgrade if any lower clusters > >> >> > > exist). > >> >> > >  > >> >> > > If you can have downtime, then just shut down the VMs running on > >> >> > > the > >> >> > > host > >> >> > > in > >> >> > > step 3 before putting it in maintenance.

Re: [ovirt-users] ovirt and gluster storage domain HA testing

2016-02-16 Thread Nir Soffer 
On Wed, Feb 17, 2016 at 7:57 AM, Sahina Bose  wrote:
>
>
> On 02/17/2016 05:08 AM, Bill James wrote:
>>
>> I have a ovirt cluster with and system running ovirt-engine 3.6.2.6-1 on
>> centos7.2
>> and 3 hardware nodes running glusterfs 3.7.6-1 and centos7.2.
>> I created a gluster volume using gluster cli and then went to add a
>> storage domain.
>>
>> I created it with Path ovirt1-ks.test:/gv1 and all works fine, until
>> ovirt1 goes down.
>> Then ALL VMs pause till ovirt1 comes back up.
>> Do I have to list all nodes in the path for this to work?
>>
>> Path: ovirt1-ks.test:/gv1 ovirt2-ks.test:/gv1 ovirt3-ks.test:/gv1
>>
>> Or how do I prevent ovirt1 from being single point of failure?
>
>
> Which type of storage domain have you created - NFS or GlusterFS?
> With NFS, this could be a problem, as the nfs server running on ovirt1 can
> become single point of failure. To work around this, you will need to set up
> HA with CTDB or pacemaker/corosync depending on version of NFS you're using.
>
> If you're using glusterfs, did the hypervisor node go down as well when
> ovirt1 went down? Only during mounting of the storage domain (either on
> activate of hypervisor host/ reboot of host) is the server provided in path
> required to access volume (ovirt1). You can provide
> backup-volfile-servers=ovirt2-ks:ovirt3-ks in Mount options while creating
> the storage domain.

oVirt is automatically detecting the available bricks and generating the
backup-volfile-servers option when connecting to a gluster storage domain.

You can see if this worked in vdsm.log, the backup-volfile-servers option
should appear in the mount command.

Please attach vdsm.log showing the time you connected to the gluster
storage domain, and the time of the failure.

Attach also /var/log/sanlock.log - this is the best place to detect issues
accessing storage as it reads and writes to all storage domains frequently.

> Please also provide output of gluster volume info. (I'm assuming the bricks
> on the remaining servers were online)

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

Re: [ovirt-users] UCS Integration (vmfex/SRIOV)

2016-02-16 Thread Michael Burman 
HI David)

If everything configured properly on your UCS side and you have a working Port 
Profile id/name your next steps should be:

1) Run for example:
engine-config -s 
CustomDeviceProperties="{type=interface;prop={ifacemacspoof=^(true|false)$;queues=[1-9][0-9]*;vmfex=^[a-zA-Z0-9_.-]{2,32}$;SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}}" --cver=3.5

- Restart your ovirt-engine service
- with --cver=3.5 you can specify your cluster version level. ^^
- If you don't want that it will overwrite your current attributes, you have to 
send them all as well(like on my example above). ^^

2) Install vdsm-hook-vmfex-dev on your nodes 

3) In ovirt engine you can verify that host have the hooks installed under  
'Hosts' main tab - > 'Host Hooks' sub tab
You should see there: a) before_device_migrate_destination b) 
before_device_create c) before_nic_hotplug
 
4) Create new network and edit the vNIC profile. Choose from the 
CustomDeviceProperties the 'vmfex' key(like in your example) and in the right 
field enter your Port Profile id/name(the one that is configured on your UCS 
side)

5) Go to 'Setup Networks' sub tab under 'Hosts' -> attach the network with the 
vmfex profile to NIC on host(drag it)

6) Create VM or use exist one, create/add new vNIC to the VM with the vmfex 
profile

7) Run VM  

Good luck)


- Original Message -
From: "David LeVene" 
To: users@ovirt.org
Sent: Wednesday, February 17, 2016 5:41:21 AM
Subject: [ovirt-users] UCS Integration (vmfex/SRIOV)



Hey All, 



I’ve got a test instance and would like to get vmfex working. I’m very new to 
ovirt, so some of the basics are still new to me. 



I currently have a 3 node setup which are all configured without vmfex, what 
I’d like to do is convert the hosts one by one to use vmfex. 



From the UCS side of things it works and I’m presented with the SRIOV devices 
in the host.. but I can’t get the network config in the ovirt admin setup.. 



I’m following this guide, but not getting very far… 
http://www.ovirt.org/Features/UCS_Integration 



This step says to do this, which is fine.. but when I do this I overwrite the 
current attribute in there. 



engine-config -s 
CustomDeviceProperties='{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}' 



which is… 



# engine-config -g CustomDeviceProperties 

CustomDeviceProperties: version: 3.0 

CustomDeviceProperties: version: 3.1 

CustomDeviceProperties: version: 3.2 

CustomDeviceProperties: version: 3.3 

CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.4 

CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.5 

CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.6 





When I update it using the command above, it replaces it… 



When I append the 2 together, I get see vmfex & prop in the ovirt-engine 
(screen shot) side of things.. so can someone please check my command to ensure 
I’m not missing something! 





engine-config -s 
CustomDeviceProperties='{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}}’ 



# engine-config -g CustomDeviceProperties 

CustomDeviceProperties: version: 3.0 

CustomDeviceProperties: version: 3.1 

CustomDeviceProperties: version: 3.2 

CustomDeviceProperties: version: 3.3 

CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.4 

CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.5 

CustomDeviceProperties: 
{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.6 







As soon as I enable vmfex on a host that was previously working.. it stops 
working and the network no longer works on the host… (this is not using any of 
the config above.. just enabled the vmfex in the UCS manager) 



What is the “correct” way to bring a Host in ovirt using vmfex? 



Regards 

David 






This email and any attachments may contain confidential and proprietary 
information of Blackboard that is for the sole

Re: [ovirt-users] ovirt and gluster storage domain HA testing

2016-02-16 Thread Sahina Bose 



On 02/17/2016 05:08 AM, Bill James wrote:
I have a ovirt cluster with and system running ovirt-engine 3.6.2.6-1 
on centos7.2

and 3 hardware nodes running glusterfs 3.7.6-1 and centos7.2.
I created a gluster volume using gluster cli and then went to add a 
storage domain.


I created it with Path ovirt1-ks.test:/gv1 and all works fine, until 
ovirt1 goes down.

Then ALL VMs pause till ovirt1 comes back up.
Do I have to list all nodes in the path for this to work?

Path: ovirt1-ks.test:/gv1 ovirt2-ks.test:/gv1 ovirt3-ks.test:/gv1

Or how do I prevent ovirt1 from being single point of failure?


Which type of storage domain have you created - NFS or GlusterFS?
With NFS, this could be a problem, as the nfs server running on ovirt1 
can become single point of failure. To work around this, you will need 
to set up HA with CTDB or pacemaker/corosync depending on version of NFS 
you're using.


If you're using glusterfs, did the hypervisor node go down as well when 
ovirt1 went down? Only during mounting of the storage domain (either on 
activate of hypervisor host/ reboot of host) is the server provided in 
path required to access volume (ovirt1). You can provide 
backup-volfile-servers=ovirt2-ks:ovirt3-ks in Mount options while 
creating the storage domain.


Please also provide output of gluster volume info. (I'm assuming the 
bricks on the remaining servers were online)






Thanks.



Cloud Services for Business www.j2.com
j2 | eFax | eVoice | FuseMail | Campaigner | KeepItSafe | Onebox


This email, its contents and attachments contain information from j2 
Global, Inc. and/or its affiliates which may be privileged, 
confidential or otherwise protected from disclosure. The information 
is intended to be for the addressee(s) only. If you are not an 
addressee, any disclosure, copy, distribution, or use of the contents 
of this message is prohibited. If you have received this email in 
error please notify the sender by reply e-mail and delete the original 
message and any copies. (c) 2015 j2 Global, Inc. All rights reserved. 
eFax, eVoice, Campaigner, FuseMail, KeepItSafe, and Onebox are 
registered trademarks of j2 Global, Inc. and its affiliates.

___
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] UCS Integration (vmfex/SRIOV)

2016-02-16 Thread David LeVene 
Hey All,

I've got a test instance and would like to get vmfex working. I'm very new to 
ovirt, so some of the basics are still new to me.

I currently have a 3 node setup which are all configured without vmfex, what 
I'd like to do is convert the hosts one by one to use vmfex.

>From the UCS side of things it works and I'm presented with the SRIOV devices 
>in the host.. but I can't get the network config in the ovirt admin setup..

I'm following this guide, but not getting very far...  
http://www.ovirt.org/Features/UCS_Integration

This step says to do this, which is fine.. but when I do this I overwrite the 
current attribute in there.

engine-config -s 
CustomDeviceProperties='{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}'

which is...

# engine-config -g CustomDeviceProperties
CustomDeviceProperties:  version: 3.0
CustomDeviceProperties:  version: 3.1
CustomDeviceProperties:  version: 3.2
CustomDeviceProperties:  version: 3.3
CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.4
CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.5
CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.6


When I update it using the command above, it replaces it...

When I append the 2 together, I get see vmfex & prop in the ovirt-engine 
(screen shot) side of things.. so can someone please check my command to ensure 
I'm not missing something!


engine-config -s 
CustomDeviceProperties='{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}}'

# engine-config -g CustomDeviceProperties
CustomDeviceProperties:  version: 3.0
CustomDeviceProperties:  version: 3.1
CustomDeviceProperties:  version: 3.2
CustomDeviceProperties:  version: 3.3
CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.4
CustomDeviceProperties: 
{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.5
CustomDeviceProperties: 
{type=interface;prop={vmfex=^[a-zA-Z0-9_.-]{2,32}$}}{type=interface;prop={SecurityGroups=^(?:(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12},
 *)*[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|)$}} version: 3.6

[cid:image001.png@01D16989.E4952270]

As soon as I enable vmfex on a host that was previously working.. it stops 
working and the network no longer works on the host...  (this is not using any 
of the config above.. just enabled the vmfex in the UCS manager)

What is the "correct" way to bring a Host in ovirt using vmfex?

Regards
David



This email and any attachments may contain confidential and proprietary 
information of Blackboard that is for the sole use of the intended recipient. 
If you are not the intended recipient, disclosure, copying, re-distribution or 
other use of any of this information is strictly prohibited. Please immediately 
notify the sender and delete this transmission if you received this email in 
error.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Can't remove snapshot

2016-02-16 Thread Marcelo Leandro 
Thank Greg,

My problem was resolved.

2016-02-16 20:07 GMT-03:00 Greg Padgett :
> On 02/16/2016 05:51 PM, Marcelo Leandro wrote:
>>
>> Hello Greg,
>> I not see disk image at the storage:
>>
>> [root@srv-qemu01 ~]# cd
>>
>> /rhev/data-center/77e24b20-9d21-4952-a089-3c5c592b4e6d/c2dc0101-748e-4a7b-9913-47993eaa52bd/images/b7a27d0c-57cc-490e-a3f8-b4981310a9b0/
>> [root@srv-qemu01 b7a27d0c-57cc-490e-a3f8-b4981310a9b0]# ls
>> 2e59f7f2-9e30-460e-836a-5e0d3d625059
>>
>> But in DB i see :
>>
>> SELECT imagestatus,storage_pool_id, storage_domain_id, image_group_id,
>> image_guid, parentid FROM
>> storage_domains,image_storage_domain_map,images,vm_static,vm_device
>> WHERE image_storage_domain_map.image_id = images.image_guid AND
>> storage_domains.id = image_storage_domain_map.storage_domain_id AND
>> vm_static.vm_guid = vm_device.vm_id AND images.image_group_id =
>> vm_device.device_id AND vm_device.device = 'disk' AND
>> vm_static.vm_name = 'Servidor-Cliente';
>>   imagestatus |   storage_pool_id|
>> storage_domain_id   |image_group_id|
>> image_guid  |   parentid
>>
>>
>> -+--+--+--+--+---
>> ---
>> 1 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
>> c2dc0101-748e-4a7b-9913-47993eaa52bd |
>> b7a27d0c-57cc-490e-a3f8-b4981310a9b0 |
>>  | 2e59f7f2-9e30-460e-836
>> a-5e0d3d625059
>> 4 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
>> c2dc0101-748e-4a7b-9913-47993eaa52bd |
>> b7a27d0c-57cc-490e-a3f8-b4981310a9b0 |
>> 2e59f7f2-9e30-460e-836a-5e0d3d625059 | ---000
>> 0-
>>
>> in this case I have that update the imagem with you describe?
>>
>> """Arguments in your case would be the VM name, snapshot name, and the
>> UUID of the image that is missing from your storage.  (You may need to
>> manually mark the image as illegal first, [2]). ""
>>
>> Thanks.
>
>
> I believe it would still be prudent to verify that image
> 7f8bb099-9a18-4e89-bf48-57e56e5770d2 is supposed to be missing, by running
> the disk info tool from:
>   https://bugzilla.redhat.com/show_bug.cgi?id=1306741.
>
> Once we verify that it's ok to remove the image, then I'd proceed to clean
> up the db records via the image cleanup sql script.
>
> Thanks,
> Greg
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] ovirt and gluster storage domain HA testing

2016-02-16 Thread Bill James 
I have a ovirt cluster with and system running ovirt-engine 3.6.2.6-1 on 
centos7.2

and 3 hardware nodes running glusterfs 3.7.6-1 and centos7.2.
I created a gluster volume using gluster cli and then went to add a 
storage domain.


I created it with Path ovirt1-ks.test:/gv1 and all works fine, until 
ovirt1 goes down.

Then ALL VMs pause till ovirt1 comes back up.
Do I have to list all nodes in the path for this to work?

Path: ovirt1-ks.test:/gv1 ovirt2-ks.test:/gv1 ovirt3-ks.test:/gv1

Or how do I prevent ovirt1 from being single point of failure?


Thanks.



Cloud Services for Business www.j2.com
j2 | eFax | eVoice | FuseMail | Campaigner | KeepItSafe | Onebox


This email, its contents and attachments contain information from j2 Global, 
Inc. and/or its affiliates which may be privileged, confidential or otherwise 
protected from disclosure. The information is intended to be for the 
addressee(s) only. If you are not an addressee, any disclosure, copy, 
distribution, or use of the contents of this message is prohibited. If you have 
received this email in error please notify the sender by reply e-mail and 
delete the original message and any copies. (c) 2015 j2 Global, Inc. All rights 
reserved. eFax, eVoice, Campaigner, FuseMail, KeepItSafe, and Onebox are 
registered trademarks of j2 Global, Inc. and its affiliates.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Can't remove snapshot

2016-02-16 Thread Greg Padgett 

On 02/16/2016 05:51 PM, Marcelo Leandro wrote:

Hello Greg,
I not see disk image at the storage:

[root@srv-qemu01 ~]# cd
/rhev/data-center/77e24b20-9d21-4952-a089-3c5c592b4e6d/c2dc0101-748e-4a7b-9913-47993eaa52bd/images/b7a27d0c-57cc-490e-a3f8-b4981310a9b0/
[root@srv-qemu01 b7a27d0c-57cc-490e-a3f8-b4981310a9b0]# ls
2e59f7f2-9e30-460e-836a-5e0d3d625059

But in DB i see :

SELECT imagestatus,storage_pool_id, storage_domain_id, image_group_id,
image_guid, parentid FROM
storage_domains,image_storage_domain_map,images,vm_static,vm_device
WHERE image_storage_domain_map.image_id = images.image_guid AND
storage_domains.id = image_storage_domain_map.storage_domain_id AND
vm_static.vm_guid = vm_device.vm_id AND images.image_group_id =
vm_device.device_id AND vm_device.device = 'disk' AND
vm_static.vm_name = 'Servidor-Cliente';
  imagestatus |   storage_pool_id|
storage_domain_id   |image_group_id|
image_guid  |   parentid

-+--+--+--+--+---
---
1 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
c2dc0101-748e-4a7b-9913-47993eaa52bd |
b7a27d0c-57cc-490e-a3f8-b4981310a9b0 |
 | 2e59f7f2-9e30-460e-836
a-5e0d3d625059
4 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
c2dc0101-748e-4a7b-9913-47993eaa52bd |
b7a27d0c-57cc-490e-a3f8-b4981310a9b0 |
2e59f7f2-9e30-460e-836a-5e0d3d625059 | ---000
0-

in this case I have that update the imagem with you describe?

"""Arguments in your case would be the VM name, snapshot name, and the
UUID of the image that is missing from your storage.  (You may need to
manually mark the image as illegal first, [2]). ""

Thanks.


I believe it would still be prudent to verify that image 
7f8bb099-9a18-4e89-bf48-57e56e5770d2 is supposed to be missing, by running 
the disk info tool from:

  https://bugzilla.redhat.com/show_bug.cgi?id=1306741.

Once we verify that it's ok to remove the image, then I'd proceed to clean 
up the db records via the image cleanup sql script.


Thanks,
Greg

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

Re: [ovirt-users] Can't remove snapshot

2016-02-16 Thread Marcelo Leandro 
Hello Greg,
I not see disk image at the storage:

[root@srv-qemu01 ~]# cd
/rhev/data-center/77e24b20-9d21-4952-a089-3c5c592b4e6d/c2dc0101-748e-4a7b-9913-47993eaa52bd/images/b7a27d0c-57cc-490e-a3f8-b4981310a9b0/
[root@srv-qemu01 b7a27d0c-57cc-490e-a3f8-b4981310a9b0]# ls
2e59f7f2-9e30-460e-836a-5e0d3d625059

But in DB i see :

SELECT imagestatus,storage_pool_id, storage_domain_id, image_group_id,
image_guid, parentid FROM
storage_domains,image_storage_domain_map,images,vm_static,vm_device
WHERE image_storage_domain_map.image_id = images.image_guid AND
storage_domains.id = image_storage_domain_map.storage_domain_id AND
vm_static.vm_guid = vm_device.vm_id AND images.image_group_id =
vm_device.device_id AND vm_device.device = 'disk' AND
vm_static.vm_name = 'Servidor-Cliente';
 imagestatus |   storage_pool_id|
storage_domain_id   |image_group_id|
   image_guid  |   parentid

-+--+--+--+--+---
---
   1 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
c2dc0101-748e-4a7b-9913-47993eaa52bd |
b7a27d0c-57cc-490e-a3f8-b4981310a9b0 |
7f8bb099-9a18-4e89-bf48-57e56e5770d2 | 2e59f7f2-9e30-460e-836
a-5e0d3d625059
   4 | 77e24b20-9d21-4952-a089-3c5c592b4e6d |
c2dc0101-748e-4a7b-9913-47993eaa52bd |
b7a27d0c-57cc-490e-a3f8-b4981310a9b0 |
2e59f7f2-9e30-460e-836a-5e0d3d625059 | ---000
0-

in this case I have that update the imagem with you describe?

"""Arguments in your case would be the VM name, snapshot name, and the
UUID of the image that is missing from your storage.  (You may need to
manually mark the image as illegal first, [2]). ""

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

Re: [ovirt-users] "bridge port" error when setting up hosted-engine on 2nd oVirt 3.6.2 node

2016-02-16 Thread Bond, Darryl 
I've got the same problem on the second hosted engine server.

When you say available in tomorrows build, when will that be available for yum 
update using the ovirt36-pre repository?


Darryl


From: users-boun...@ovirt.org  on behalf of Simone 
Tiraboschi 
Sent: Tuesday, 16 February 2016 4:15 AM
To: Yedidyah Bar David
Cc: users
Subject: Re: [ovirt-users] "bridge port" error when setting up hosted-engine on 
2nd oVirt 3.6.2 node



On Mon, Feb 15, 2016 at 3:50 PM, Yedidyah Bar David 
> wrote:
On Mon, Feb 15, 2016 at 4:22 PM, Mike DePaulo 
> wrote:
> Hi,
>
> I am getting the following error when I attempt to setup my 2nd ovirt
> node as a hosted-engine:
>
> RuntimeError: The selected device None is not a supported bridge port
>
> The 1st node is death-star (192.168.1.50)
> The 2nd node is starkiller-base (192.168.1.52)
>
> This is not a production environment; this is my apartment.
>
> I am able to access the engine's webGUI.
>
> Both death-star and starkiller-base start out with only eno1 as their only 
> NIC.
> death-star, by the end of the hosted-engine-setup, had ovirtmgmt also
> (with the same MAC address.)
> starkiller-base does not have ovirtmgmt yet.
> I am not using VLANs.
>
> node version: ovirt-node-iso-3.6-0.999.201602121021.el7.centos.iso
> engine appliance version: oVirt-Engine-Appliance-CentOS-x86_64-7-20160126.ova

Seems like a bug in [1] - seems like we do not configure the bridge anymore
on additional host. But I didn't yet try that myself, I might be missing
something. Adding Simone.

[1] https://gerrit.ovirt.org/#/q/Ifcff652ef28e6b912514df2dd2daac2b07eca61e,n,z
--
Didi

Yes, it was a real bug: https://gerrit.ovirt.org/#/c/53428/ should address it.
It should be available in tomorrow build.



The contents of this electronic message and any attachments are intended only 
for the addressee and may contain legally privileged, personal, sensitive or 
confidential information. If you are not the intended addressee, and have 
received this email, any transmission, distribution, downloading, printing or 
photocopying of the contents of this message or attachments is strictly 
prohibited. Any legal privilege or confidentiality attached to this message and 
attachments is not waived, lost or destroyed by reason of delivery to any 
person other than intended addressee. If you have received this message and are 
not the intended addressee you should notify the sender by return email and 
destroy all copies of the message and any attachments. Unless expressly 
attributed, the views expressed in this email do not necessarily represent the 
views of the company.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Can't remove snapshot

2016-02-16 Thread Greg Padgett 

On 02/16/2016 08:50 AM, Rik Theys wrote:

Hi,

I'm trying to determine the correct "bad_img" uuid in my case.

The VM has two snapshots:

* The "Active VM" snapshot which has a disk that has an actual size
that's 5GB larger than the virtual size. It has a creation date that
matches the timestamp at which I created the second snapshot. The "disk
snapshot id" for this snapshot ends with dc39.

* A "before jessie upgrade" snapshot that has status "illegal". It has
an actual size that's 2GB larger than the virtual size. The creation
date matches the date the VM was initialy created. The disk snapshot id
ends with 6249.

 From the above I conclude that the disk with id that ends with 6249 is
the "bad" img I need to specify.


Similar to what I wrote to Marcelo above in the thread, I'd recommend 
running the "VM disk info gathering tool" attached to [1].  It's the best 
way to ensure the merge was completed and determine which image is the 
"bad" one that is no longer in use by any volume chains.


If indeed the "bad" image (whichever one it is) is no longer in use, then 
it's possible the image wasn't successfully removed from storage.  There 
are 2 ways to fix this:


  a) Run the db fixup script to remove the records for the merged image,
 and run the vdsm command by hand to remove it from storage.
  b) Adjust the db records so a merge retry would start at the right
 place, and re-run live merge.

Given that your merge retries were failing, option a) seems most likely to 
succeed.  The db fixup script is attached to [1]; as parameters you would 
need to provide the vm name, snapshot name, and the id of the unused image 
as verified by the disk info tool.


To remove the stale LV, the vdsm deleteVolume verb would then be run from 
`vdsClient` -- but note that this must be run _on the SPM host_.  It will 
not only perform lvremove, but also do housekeeping on other storage 
metadata to keep everything consistent.  For this verb I believe you'll 
need to supply not only the unused image id, but also the pool, domain, 
and image group ids from your database queries.


I hope that helps.

Greg

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1306741



However, I grepped the output from 'lvs' on the SPM host of the cluster
and both disk id's are returned:

[root@amazone ~]# lvs | egrep 'cd39|6249'
   24d78600-22f4-44f7-987b-fbd866736249
a7ba2db3-517c-408a-8b27-ea45989d6416 -wi-ao   34.00g

   81458622-aa54-4f2f-b6d8-75e7db36cd39
a7ba2db3-517c-408a-8b27-ea45989d6416 -wi---5.00g


I expected the "bad" img would no longer be found?

The SQL script only cleans up the database and not the logical volumes.
Would running the script not keep a stale LV around?

Also, from the lvs output it seems the "bad" disk is bigger than the
"good" one.

Is it possible the snapshot still needs to be merged?? If so, how can I
initiate that?

Regards,

Rik


On 02/16/2016 02:02 PM, Rik Theys wrote:

Hi Greg,



2016-02-09 21:30 GMT-03:00 Greg Padgett :

On 02/09/2016 06:08 AM, Michal Skrivanek wrote:




On 03 Feb 2016, at 10:37, Rik Theys  wrote:



I can see the snapshot in the "Disk snapshot" tab of the storage. It has
a status of "illegal". Is it OK to (try to) remove this snapshot? Will
this impact the running VM and/or disk image?



No, it’s not ok to remove it while live merge(apparently) is still ongoing
I guess that’s a live merge bug?



Indeed, this is bug 1302215.

I wrote a sql script to help with cleanup in this scenario, which you can
find attached to the bug along with a description of how to use it[1].

However, Rik, before trying that, would you be able to run the attached
script [2] (or just the db query within) and forward the output to me? I'd
like to make sure everything looks as it should before modifying the db
directly.


I ran the following query on the engine database:

select images.* from images join snapshots ON (images.vm_snapshot_id =
snapshots.snapshot_id)
join vm_static on (snapshots.vm_id = vm_static.vm_guid)
where vm_static.vm_name = 'lena' and snapshots.description='before
jessie upgrade';

The resulting output is:

   image_guid  | creation_date  |size
 |   it_guid|   parentid
   | images
tatus |lastmodified|vm_snapshot_id
   | volume_type | volume_format |image_group_id|
 _create_da
te  | _update_date  | active |
volume_classification
--++-+--+--+---
--++--+-+---+--+---
+---++---

Re: [ovirt-users] Can't remove snapshot

2016-02-16 Thread Greg Padgett 

On 02/16/2016 07:10 AM, Marcelo Leandro wrote:

Hello,
I have the same  problem, i tried delete snapshot but  it did not
success, the status snapshot as illegal , look the engine.log follow
you can see the messages error:


Hi Marcelo,

The problem in your log,
  error = Drive image file could not be found, code = 13
is a little different but may have been triggered by the same bug in a 
previous merge attempt.


In this case, would you run the "VM disk info gathering tool" from [1]? 
See Adam's comment in the bug about its execution.


If this shows that the VM is no longer dependent on that missing volume, 
then please shut down engine, back up the db, and run the "post-merge 
failure repair script", also attached to [1].


Arguments in your case would be the VM name, snapshot name, and the UUID 
of the image that is missing from your storage.  (You may need to manually 
mark the image as illegal first, [2]).


HTH,
Greg

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1306741
[2] UPDATE images SET imagestatus = 4 WHERE image_guid = ''::UUID;




2016-02-16 08:46:20,059 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommandCallback]
(DefaultQuartzScheduler_Worker-57) [46dd2ef7] Waiting on Live Merge
child commands to complete
2016-02-16 08:46:21,069 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotSingleDiskLiveCommand]
(DefaultQuartzScheduler_Worker-40) [15b703ee] Waiting on Live Merge
command step 'MERGE' to complete
2016-02-16 08:46:22,072 INFO
[org.ovirt.engine.core.bll.MergeCommandCallback]
(DefaultQuartzScheduler_Worker-65) [30cdf6ed] Waiting on merge command
to complete
2016-02-16 08:46:23,670 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommand] (default task-48)
[5e0c088f] Lock Acquired to object
'EngineLock:{exclusiveLocks='[94d788f4-eba4-49ee-8091-80028cc46627=]', sharedLocks='null'}'
2016-02-16 08:46:23,795 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommand] (default task-48)
[5e0c088f] Running command: RemoveSnapshotCommand internal: false.
Entities affected :  ID: 94d788f4-eba4-49ee-8091-80028cc46627 Type:
VMAction group MANIPULATE_VM_SNAPSHOTS with role type USER
2016-02-16 08:46:23,824 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommand] (default task-48)
[5e0c088f] Lock freed to object
'EngineLock:{exclusiveLocks='[94d788f4-eba4-49ee-8091-80028cc46627=]', sharedLocks='null'}'
2016-02-16 08:46:23,876 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotSingleDiskLiveCommand]
(pool-7-thread-5) [1be123ac] Running command:
RemoveSnapshotSingleDiskLiveCommand internal: true. Entities affected
:  ID: ---- Type: Storage
2016-02-16 08:46:23,921 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-48) [] Correlation ID: 5e0c088f, Job ID:
aa811e83-24fb-4658-b849-d36439f58d95, Call Stack: null, Custom Event
ID: -1, Message: Snapshot 'BKP the VM' deletion for VM
'Servidor-Cliente' was initiated by admin@internal.
2016-02-16 08:46:24,093 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotSingleDiskLiveCommand]
(DefaultQuartzScheduler_Worker-14) [1be123ac] Executing Live Merge
command step 'EXTEND'
2016-02-16 08:46:24,122 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommandCallback]
(DefaultQuartzScheduler_Worker-14) [] Waiting on Live Merge child
commands to complete
2016-02-16 08:46:24,133 INFO
[org.ovirt.engine.core.bll.MergeExtendCommand] (pool-7-thread-6)
[766ffc9f] Running command: MergeExtendCommand internal: true.
Entities affected :  ID: c2dc0101-748e-4a7b-9913-47993eaa52bd Type:
Storage
2016-02-16 08:46:24,134 INFO
[org.ovirt.engine.core.bll.MergeExtendCommand] (pool-7-thread-6)
[766ffc9f] Base and top image sizes are the same; no image size update
required
2016-02-16 08:46:25,133 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotSingleDiskLiveCommand]
(DefaultQuartzScheduler_Worker-16) [1be123ac] Executing Live Merge
command step 'MERGE'
2016-02-16 08:46:25,168 INFO  [org.ovirt.engine.core.bll.MergeCommand]
(pool-7-thread-7) [1b7bc421] Running command: MergeCommand internal:
true. Entities affected :  ID: c2dc0101-748e-4a7b-9913-47993eaa52bd
Type: Storage
2016-02-16 08:46:25,169 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand]
(pool-7-thread-7) [1b7bc421] START, MergeVDSCommand(HostName = Host01,
MergeVDSCommandParameters:{runAsync='true',
hostId='d4f29978-1540-44d9-ab22-1e6ff750059f',
vmId='94d788f4-eba4-49ee-8091-80028cc46627',
storagePoolId='77e24b20-9d21-4952-a089-3c5c592b4e6d',
storageDomainId='c2dc0101-748e-4a7b-9913-47993eaa52bd',
imageGroupId='b7a27d0c-57cc-490e-a3f8-b4981310a9b0',
imageId='7f8bb099-9a18-4e89-bf48-57e56e5770d2',
baseImageId='2e59f7f2-9e30-460e-836a-5e0d3d625059',
topImageId='7f8bb099-9a18-4e89-bf48-57e56e5770d2', bandwidth='0'}),
log id: 2a7ab7b7
2016-02-16 08:46:25,176 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand]
(pool-7-thread-7) [1b7bc421] Failed in 'MergeVDS' method
2016-02-16 08:46:25,179

[ovirt-users] question mark in oVirt - "cannot acquire state change lock"

2016-02-16 Thread p...@email.cz 

Hello all,
how can I eliminate question mark from "hanged" VM? ( it happened in shutdown 
process via oVirt  env. )
Best solution without hypervizor reboot, meaning "power off" , "kill" or 
another workaround for that VM .
Will help removing task DB record from oVirt mgmt server - if exists , ofcourse 
??
Running  gluster 3.7.5 / oVirt 3.5.2 / 
libvirt-daemon-kvm-1.2.8-16.el7_1.5.x86_64  on centos 7.1.1503 .

thx a lot.
Pa.

PS: I found similar problem in libvirt library a many years ago ( redhat 5.6 )
   https://bugzilla.redhat.com/show_bug.cgi?id=676205
   https://bugzilla.redhat.com/show_bug.cgi?id=668438
problem explanation:
http://linux.india365.org/2012/01/libvirt-virsh-cannot-acquire-state-change-lock-error-explained/

  So it means that this bug was not fixed to this time ??

regs.

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

Re: [ovirt-users] lvm_dev_whitelist vdsm.conf option

2016-02-16 Thread Adam Litke 

On 16/02/16 13:46 +0100, Johannes Tiefenbacher wrote:

On 2016-02-15 17:05, jojo wrote:

On 2016-02-15 16:09, Adam Litke wrote:

On 11/02/16 17:22 +0100, Johannes Tiefenbacher wrote:

Hi,
I am wondering what the lvm_dev_whitelist vdsm.conf option is for?

I had some issues whith vdsm switching off logical volumes that 
it better should keep it's hands off.


Could this option help to handle this?


Yes this option should be exactly what you are looking for.  You
specify a comma separated list of glob expressions and vdsm will
instruct lvm to ignore all devices which are not matched by your list.

See:
https://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/lvm_filters.html

for more background information on the LVM filters.



perfect, I will try this out.
thanks a lot for your answer.
all the best
Jojo


Hi Adam,

I configured this now but I am not sure how I could confirm if I have 
the syntax correct.

I want vdsm to leave alone the VGs called ovirt and kvmvg.


lvm_dev_whitelist = [ "r|^/dev/kvmvg|", "r|^/dev/ovirt|" ]


This is a whitelist not a blacklist.  You should only specify the
devices you want to allow.  Sorry if that's not ideal for you here but
it's the way the code currently works.  Please do not use the r||
syntax.  Just use a comma separated string of wildcards that you want
to allow.  For example:

lvm_dev_whitelist = "^/dev/fast*,^/dev/furious*"

You should be able to check the vdsm log and see the lvm queries will
include your whitelist converted into the format expected by the lvm
commands.



I restarted vdsmd and did not get any error.

I also tried to write some bollocks to vdsm.conf, restarted and 
searched for an error in vdsm.log. surprisingly that also seems to 
work !?!


so the general question actually is: how can i make sure that 
vdsm.conf options are read correctly. where and when is this checked? 
what to look for in vdsm.log (or even other log files?)


thanks
Jojo
LINBIT VIE


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

Re: [ovirt-users] Can't remove snapshot

2016-02-16 Thread Rik Theys 
Hi,

I'm trying to determine the correct "bad_img" uuid in my case.

The VM has two snapshots:

* The "Active VM" snapshot which has a disk that has an actual size
that's 5GB larger than the virtual size. It has a creation date that
matches the timestamp at which I created the second snapshot. The "disk
snapshot id" for this snapshot ends with dc39.

* A "before jessie upgrade" snapshot that has status "illegal". It has
an actual size that's 2GB larger than the virtual size. The creation
date matches the date the VM was initialy created. The disk snapshot id
ends with 6249.

From the above I conclude that the disk with id that ends with 6249 is
the "bad" img I need to specify.

However, I grepped the output from 'lvs' on the SPM host of the cluster
and both disk id's are returned:

[root@amazone ~]# lvs | egrep 'cd39|6249'
  24d78600-22f4-44f7-987b-fbd866736249
a7ba2db3-517c-408a-8b27-ea45989d6416 -wi-ao   34.00g

  81458622-aa54-4f2f-b6d8-75e7db36cd39
a7ba2db3-517c-408a-8b27-ea45989d6416 -wi---5.00g


I expected the "bad" img would no longer be found?

The SQL script only cleans up the database and not the logical volumes.
Would running the script not keep a stale LV around?

Also, from the lvs output it seems the "bad" disk is bigger than the
"good" one.

Is it possible the snapshot still needs to be merged?? If so, how can I
initiate that?

Regards,

Rik


On 02/16/2016 02:02 PM, Rik Theys wrote:
> Hi Greg,
> 
>>
>> 2016-02-09 21:30 GMT-03:00 Greg Padgett :
>>> On 02/09/2016 06:08 AM, Michal Skrivanek wrote:


> On 03 Feb 2016, at 10:37, Rik Theys  wrote:
> 
>> I can see the snapshot in the "Disk snapshot" tab of the storage. It has
>> a status of "illegal". Is it OK to (try to) remove this snapshot? Will
>> this impact the running VM and/or disk image?


 No, it’s not ok to remove it while live merge(apparently) is still ongoing
 I guess that’s a live merge bug?
>>>
>>>
>>> Indeed, this is bug 1302215.
>>>
>>> I wrote a sql script to help with cleanup in this scenario, which you can
>>> find attached to the bug along with a description of how to use it[1].
>>>
>>> However, Rik, before trying that, would you be able to run the attached
>>> script [2] (or just the db query within) and forward the output to me? I'd
>>> like to make sure everything looks as it should before modifying the db
>>> directly.
> 
> I ran the following query on the engine database:
> 
> select images.* from images join snapshots ON (images.vm_snapshot_id =
> snapshots.snapshot_id)
> join vm_static on (snapshots.vm_id = vm_static.vm_guid)
> where vm_static.vm_name = 'lena' and snapshots.description='before
> jessie upgrade';
> 
> The resulting output is:
> 
>   image_guid  | creation_date  |size
> |   it_guid|   parentid
>   | images
> tatus |lastmodified|vm_snapshot_id
>   | volume_type | volume_format |image_group_id|
> _create_da
> te  | _update_date  | active |
> volume_classification
> --++-+--+--+---
> --++--+-+---+--+---
> +---++---
>  24d78600-22f4-44f7-987b-fbd866736249 | 2015-05-19 15:00:13+02 |
> 34359738368 | ---- |
> ---- |
> 4 | 2016-01-30 08:45:59.998+01 |
> 4b4930ed-b52d-47ec-8506-245b7f144102 |   1 | 5 |
> b2390535-744f-4c02-bdc8-5a897226554b | 2015-05-19 15:00:1
> 1.864425+02 | 2016-01-30 08:45:59.999422+01 | f  | 1
> (1 row)
> 
> Regards,
> 
> Rik
> 
> 
>>>
>>> Thanks,
>>> Greg
>>>
>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1302215#c13
>>> (Also note that the engine should be stopped before running this.)
>>>
>>> [2] Arguments are the ovirt db name, db user, and the name of the vm you
>>> were performing live merge on.
>>>
>>>
 Thanks,
 michal

>
>
> Regards,
>
> Rik
>
> On 02/03/2016 10:26 AM, Rik Theys wrote:
>>
>> Hi,
>>
>> I created a snapshot of a running VM prior to an OS upgrade. The OS
>> upgrade has now been succesful and I would like to remove the snapshot.
>> I've selected the snapshot in the UI and clicked Delete to start the
>> task.
>>
>> After a few minutes, the task has failed. When I click delete again on
>> the same snapshot, the failed message is returned after a few seconds.
>>
>>>  From browsing through the engine log (attached) it seems the snapshot
>>
>>

Re: [ovirt-users] Upgrade patch 3.5 -> 3.6

2016-02-16 Thread Alexander Wels 
On Tuesday, February 16, 2016 12:36:58 PM Johan Kooijman wrote:
> Ack, thx.
> 
> On Tue, Feb 16, 2016 at 11:46 AM, Yedidyah Bar David 
> 
> wrote:
> > On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman 
> > 
> > wrote:
> > > Didi,
> > > 
> > > Ok, the piece of information on engine still supported on 3.6 was
> > 
> > unknown to
> > 
> > > me. Makes my job a lot easier.
> > > 
> > > What would be the recommended path: first upgrade the nodes to 3.6 and
> > 
> > then
> > 
> > > the engine? Or the other way around?
> > 
> > Generally speaking, first engine then nodes. I am pretty certain it's
> > documented
> > on the wiki, didn't check.
> > 

Basically follow what I wrote should do what you want. Then if you later want 
to upgrade the engine from EL6 to EL7 you should be able to make a backup of 
the engine with the engine-backup tool. Then install a fresh engine on EL7 and 
restore the backup with that tool. Your VMs won't be affected if the engine is 
gone for a little bit (well besides not being able to manage them during the 
change over).

But as Didi wrote, right now EL6 is still supported so you can simply upgrade 
to oVirt 3.6 on EL6.

> > > On Tue, Feb 16, 2016 at 8:45 AM, Yedidyah Bar David 
> > 
> > wrote:
> > >> On Tue, Feb 16, 2016 at 9:30 AM, Johan Kooijman  > >> 
> > >> wrote:
> > >> > Yes. I pasted the information on AIO, that was wrong on my end. I
> > >> > have
> > >> > an
> > >> > engine running on dedicated hardware and about 20 nodes in this
> > 
> > cluster.
> > 
> > >> > I
> > >> > do like to upgrade without downtime :) I know how to achieve this on
> > 
> > the
> > 
> > >> > node-end, but since I have to go from C6 to C7, I wonder what the
> > >> > procedure
> > >> > would be for engine.
> > >> 
> > >> Please explain exactly what you are trying to do.
> > >> 
> > >> Note that engine is still supported on el6.
> > >> 
> > >> (new) Hosts are not.
> > >> 
> > >> all-in-one is running both together, thus is not supported on el6
> > 
> > either.
> > 
> > >> IIRC we do not have a tested procedure to upgrade the engine from C6 to
> > 
> > C7
> > 
> > >> yet, see also:
> > >> 
> > >> https://bugzilla.redhat.com/show_bug.cgi?id=1234257
> > >> https://bugzilla.redhat.com/show_bug.cgi?id=1285743
> > >> 
> > >> Best,
> > >> 
> > >> > On Mon, Feb 15, 2016 at 9:21 PM, Alexander Wels 
> > >> > 
> > >> > wrote:
> > >> >> On Monday, February 15, 2016 08:21:40 PM Johan Kooijman wrote:
> > >> >> > Hi Alexander,
> > >> >> > 
> > >> >> > Thanks for the input! My 3.5 is running on C6 however:
> > >> >> > 
> > >> >> > Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the
> > >> >> > packages
> > >> >> > requiring it are not built anymore for EL6
> > >> >> 
> > >> >> Well that was a piece of information you forgot to mention in your
> > >> >> initial
> > >> >> email. So now I am not entirely sure what you are trying to do. Are
> > 
> > you
> > 
> > >> >> trying
> > >> >> to save your existing VMs when you reinstall your machine?
> > >> >> 
> > >> >> > On Mon, Feb 15, 2016 at 3:37 PM, Alexander Wels 
> > >> >> > 
> > >> >> > wrote:
> > >> >> > > On Monday, February 15, 2016 02:40:47 PM Johan Kooijman wrote:
> > >> >> > > > Hi,
> > >> >> > > > 
> > >> >> > > > Can anybody recommend me best practice upgrade path for an
> > >> >> > > > upgrade
> > >> >> > > > from
> > >> >> > > > oVirt 3.5 on C6 to 3.6 on C7.2?
> > >> >> > > 
> > >> >> > > The answer sort of depends on what you want. Do you want no
> > >> >> > > downtime
> > >> >> > > on
> > >> >> > > your
> > >> >> > > VMs or is downtime acceptable. Also are you running hosted
> > >> >> > > engine
> > >> >> > > or
> > >> >> > > not?
> > >> >> > > 
> > >> >> > > This is the basic plan which can be adjusted based on what your
> > >> >> > > needs
> > >> >> > > are:
> > >> >> > > 
> > >> >> > > 1. Update engine from 3.5 to 3.6 (if hosted engine might be
> > >> >> > > trickier,
> > >> >> > > not
> > >> >> > > sure
> > >> >> > > haven't played with hosted engine).
> > >> >> > > 2. Create a new 3.6 cluster.
> > >> >> > > 3. Put 1 host in maintenance (which will migrate the VMs to the
> > >> >> > > other
> > >> >> > > hosts).
> > >> >> > > 4. Remove the host from the DC.
> > >> >> > > 5. Install C7.2 on the host
> > >> >> > > 6. Add that host to the new 3.6 cluster.
> > >> >> > > 7. Optional (you can cross cluster live migrate some VMs from 6
> > 
> > to
> > 
> > >> >> > > 7
> > >> >> > > (just
> > >> >> > > not
> > >> >> > > the other way around, so once the VM is moved its stuck in the
> > 
> > new
> > 
> > >> >> > > cluster).
> > >> >> > > 8. Go to 3 until all hosts are moved.
> > >> >> > > 9. Your 3.5 cluster should now be empty, and can be removed.
> > >> >> > > 10. Upgrade your DC to 3.6 (Can't upgrade if any lower clusters
> > >> >> > > exist).
> > >> >> > > 
> > >> >> > > If you can have downtime, then just shut down the VMs running

Re: [ovirt-users] Can't remove snapshot

2016-02-16 Thread Rik Theys 
Hi Greg,

> 
> 2016-02-09 21:30 GMT-03:00 Greg Padgett :
>> On 02/09/2016 06:08 AM, Michal Skrivanek wrote:
>>>
>>>
 On 03 Feb 2016, at 10:37, Rik Theys  wrote:

> I can see the snapshot in the "Disk snapshot" tab of the storage. It has
> a status of "illegal". Is it OK to (try to) remove this snapshot? Will
> this impact the running VM and/or disk image?
>>>
>>>
>>> No, it’s not ok to remove it while live merge(apparently) is still ongoing
>>> I guess that’s a live merge bug?
>>
>>
>> Indeed, this is bug 1302215.
>>
>> I wrote a sql script to help with cleanup in this scenario, which you can
>> find attached to the bug along with a description of how to use it[1].
>>
>> However, Rik, before trying that, would you be able to run the attached
>> script [2] (or just the db query within) and forward the output to me? I'd
>> like to make sure everything looks as it should before modifying the db
>> directly.

I ran the following query on the engine database:

select images.* from images join snapshots ON (images.vm_snapshot_id =
snapshots.snapshot_id)
join vm_static on (snapshots.vm_id = vm_static.vm_guid)
where vm_static.vm_name = 'lena' and snapshots.description='before
jessie upgrade';

The resulting output is:

  image_guid  | creation_date  |size
|   it_guid|   parentid
  | images
tatus |lastmodified|vm_snapshot_id
  | volume_type | volume_format |image_group_id|
_create_da
te  | _update_date  | active |
volume_classification
--++-+--+--+---
--++--+-+---+--+---
+---++---
 24d78600-22f4-44f7-987b-fbd866736249 | 2015-05-19 15:00:13+02 |
34359738368 | ---- |
---- |
4 | 2016-01-30 08:45:59.998+01 |
4b4930ed-b52d-47ec-8506-245b7f144102 |   1 | 5 |
b2390535-744f-4c02-bdc8-5a897226554b | 2015-05-19 15:00:1
1.864425+02 | 2016-01-30 08:45:59.999422+01 | f  | 1
(1 row)

Regards,

Rik


>>
>> Thanks,
>> Greg
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1302215#c13
>> (Also note that the engine should be stopped before running this.)
>>
>> [2] Arguments are the ovirt db name, db user, and the name of the vm you
>> were performing live merge on.
>>
>>
>>> Thanks,
>>> michal
>>>


 Regards,

 Rik

 On 02/03/2016 10:26 AM, Rik Theys wrote:
>
> Hi,
>
> I created a snapshot of a running VM prior to an OS upgrade. The OS
> upgrade has now been succesful and I would like to remove the snapshot.
> I've selected the snapshot in the UI and clicked Delete to start the
> task.
>
> After a few minutes, the task has failed. When I click delete again on
> the same snapshot, the failed message is returned after a few seconds.
>
>>  From browsing through the engine log (attached) it seems the snapshot
>
> was correctly merged in the first try but something went wrong in the
> finalizing fase. On retries, the log indicates the snapshot/disk image
> no longer exists and the removal of the snapshot fails for this reason.
>
> Is there any way to clean up this snapshot?
>
> I can see the snapshot in the "Disk snapshot" tab of the storage. It has
> a status of "illegal". Is it OK to (try to) remove this snapshot? Will
> this impact the running VM and/or disk image?

-- 
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440  - B-3001 Leuven-Heverlee
+32(0)16/32.11.07

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

[ovirt-users] Manually assign DC and Cluster to Blank template

2016-02-16 Thread nicolas 

Hi,

We upgraded from oVirt 3.5 and 3.6 and deleted the Default cluster, so 
now we have the Blank template with no DC and no Cluster, thus our users 
can't use it.


Is there a way to manually set these two parameters to the current DC 
and Cluster values for the Blank template? I tried editing it but see no 
option to set them.


Thanks.

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

Re: [ovirt-users] Can't remove snapshot

2016-02-16 Thread Marcelo Leandro 
Hello,
I have the same  problem, i tried delete snapshot but  it did not
success, the status snapshot as illegal , look the engine.log follow
you can see the messages error:


2016-02-16 08:46:20,059 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommandCallback]
(DefaultQuartzScheduler_Worker-57) [46dd2ef7] Waiting on Live Merge
child commands to complete
2016-02-16 08:46:21,069 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotSingleDiskLiveCommand]
(DefaultQuartzScheduler_Worker-40) [15b703ee] Waiting on Live Merge
command step 'MERGE' to complete
2016-02-16 08:46:22,072 INFO
[org.ovirt.engine.core.bll.MergeCommandCallback]
(DefaultQuartzScheduler_Worker-65) [30cdf6ed] Waiting on merge command
to complete
2016-02-16 08:46:23,670 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommand] (default task-48)
[5e0c088f] Lock Acquired to object
'EngineLock:{exclusiveLocks='[94d788f4-eba4-49ee-8091-80028cc46627=]', sharedLocks='null'}'
2016-02-16 08:46:23,795 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommand] (default task-48)
[5e0c088f] Running command: RemoveSnapshotCommand internal: false.
Entities affected :  ID: 94d788f4-eba4-49ee-8091-80028cc46627 Type:
VMAction group MANIPULATE_VM_SNAPSHOTS with role type USER
2016-02-16 08:46:23,824 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommand] (default task-48)
[5e0c088f] Lock freed to object
'EngineLock:{exclusiveLocks='[94d788f4-eba4-49ee-8091-80028cc46627=]', sharedLocks='null'}'
2016-02-16 08:46:23,876 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotSingleDiskLiveCommand]
(pool-7-thread-5) [1be123ac] Running command:
RemoveSnapshotSingleDiskLiveCommand internal: true. Entities affected
:  ID: ---- Type: Storage
2016-02-16 08:46:23,921 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-48) [] Correlation ID: 5e0c088f, Job ID:
aa811e83-24fb-4658-b849-d36439f58d95, Call Stack: null, Custom Event
ID: -1, Message: Snapshot 'BKP the VM' deletion for VM
'Servidor-Cliente' was initiated by admin@internal.
2016-02-16 08:46:24,093 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotSingleDiskLiveCommand]
(DefaultQuartzScheduler_Worker-14) [1be123ac] Executing Live Merge
command step 'EXTEND'
2016-02-16 08:46:24,122 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotCommandCallback]
(DefaultQuartzScheduler_Worker-14) [] Waiting on Live Merge child
commands to complete
2016-02-16 08:46:24,133 INFO
[org.ovirt.engine.core.bll.MergeExtendCommand] (pool-7-thread-6)
[766ffc9f] Running command: MergeExtendCommand internal: true.
Entities affected :  ID: c2dc0101-748e-4a7b-9913-47993eaa52bd Type:
Storage
2016-02-16 08:46:24,134 INFO
[org.ovirt.engine.core.bll.MergeExtendCommand] (pool-7-thread-6)
[766ffc9f] Base and top image sizes are the same; no image size update
required
2016-02-16 08:46:25,133 INFO
[org.ovirt.engine.core.bll.RemoveSnapshotSingleDiskLiveCommand]
(DefaultQuartzScheduler_Worker-16) [1be123ac] Executing Live Merge
command step 'MERGE'
2016-02-16 08:46:25,168 INFO  [org.ovirt.engine.core.bll.MergeCommand]
(pool-7-thread-7) [1b7bc421] Running command: MergeCommand internal:
true. Entities affected :  ID: c2dc0101-748e-4a7b-9913-47993eaa52bd
Type: Storage
2016-02-16 08:46:25,169 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand]
(pool-7-thread-7) [1b7bc421] START, MergeVDSCommand(HostName = Host01,
MergeVDSCommandParameters:{runAsync='true',
hostId='d4f29978-1540-44d9-ab22-1e6ff750059f',
vmId='94d788f4-eba4-49ee-8091-80028cc46627',
storagePoolId='77e24b20-9d21-4952-a089-3c5c592b4e6d',
storageDomainId='c2dc0101-748e-4a7b-9913-47993eaa52bd',
imageGroupId='b7a27d0c-57cc-490e-a3f8-b4981310a9b0',
imageId='7f8bb099-9a18-4e89-bf48-57e56e5770d2',
baseImageId='2e59f7f2-9e30-460e-836a-5e0d3d625059',
topImageId='7f8bb099-9a18-4e89-bf48-57e56e5770d2', bandwidth='0'}),
log id: 2a7ab7b7
2016-02-16 08:46:25,176 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand]
(pool-7-thread-7) [1b7bc421] Failed in 'MergeVDS' method
2016-02-16 08:46:25,179 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(pool-7-thread-7) [1b7bc421] Correlation ID: null, Call Stack: null,
Custom Event ID: -1, Message: VDSM Host01 command failed: Drive image
file could not be found
2016-02-16 08:46:25,179 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand]
(pool-7-thread-7) [1b7bc421] Command
'org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand' return
value 'StatusOnlyReturnForXmlRpc [status=StatusForXmlRpc [code=13,
message=Drive image file could not be found]]'
2016-02-16 08:46:25,179 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand]
(pool-7-thread-7) [1b7bc421] HostName = Host01
2016-02-16 08:46:25,179 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand]
(pool-7-thread-7) [1b7bc421] Command 'MergeVDSCommand(HostName =
Host01, MergeVDSCommandParameters:{runAsync='true',

Re: [ovirt-users] Upgrade patch 3.5 -> 3.6

2016-02-16 Thread Johan Kooijman 
Ack, thx.

On Tue, Feb 16, 2016 at 11:46 AM, Yedidyah Bar David 
wrote:

> On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman 
> wrote:
> > Didi,
> >
> > Ok, the piece of information on engine still supported on 3.6 was
> unknown to
> > me. Makes my job a lot easier.
> >
> > What would be the recommended path: first upgrade the nodes to 3.6 and
> then
> > the engine? Or the other way around?
>
> Generally speaking, first engine then nodes. I am pretty certain it's
> documented
> on the wiki, didn't check.
>
> >
> > On Tue, Feb 16, 2016 at 8:45 AM, Yedidyah Bar David 
> wrote:
> >>
> >> On Tue, Feb 16, 2016 at 9:30 AM, Johan Kooijman  >
> >> wrote:
> >> > Yes. I pasted the information on AIO, that was wrong on my end. I have
> >> > an
> >> > engine running on dedicated hardware and about 20 nodes in this
> cluster.
> >> > I
> >> > do like to upgrade without downtime :) I know how to achieve this on
> the
> >> > node-end, but since I have to go from C6 to C7, I wonder what the
> >> > procedure
> >> > would be for engine.
> >>
> >> Please explain exactly what you are trying to do.
> >>
> >> Note that engine is still supported on el6.
> >>
> >> (new) Hosts are not.
> >>
> >> all-in-one is running both together, thus is not supported on el6
> either.
> >>
> >> IIRC we do not have a tested procedure to upgrade the engine from C6 to
> C7
> >> yet, see also:
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1234257
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1285743
> >>
> >> Best,
> >>
> >> >
> >> > On Mon, Feb 15, 2016 at 9:21 PM, Alexander Wels 
> >> > wrote:
> >> >>
> >> >> On Monday, February 15, 2016 08:21:40 PM Johan Kooijman wrote:
> >> >> > Hi Alexander,
> >> >> >
> >> >> > Thanks for the input! My 3.5 is running on C6 however:
> >> >> >
> >> >> > Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the
> >> >> > packages
> >> >> > requiring it are not built anymore for EL6
> >> >> >
> >> >>
> >> >> Well that was a piece of information you forgot to mention in your
> >> >> initial
> >> >> email. So now I am not entirely sure what you are trying to do. Are
> you
> >> >> trying
> >> >> to save your existing VMs when you reinstall your machine?
> >> >>
> >> >>
> >> >> > On Mon, Feb 15, 2016 at 3:37 PM, Alexander Wels 
> >> >> > wrote:
> >> >> > > On Monday, February 15, 2016 02:40:47 PM Johan Kooijman wrote:
> >> >> > > > Hi,
> >> >> > > >
> >> >> > > > Can anybody recommend me best practice upgrade path for an
> >> >> > > > upgrade
> >> >> > > > from
> >> >> > > > oVirt 3.5 on C6 to 3.6 on C7.2?
> >> >> > >
> >> >> > > The answer sort of depends on what you want. Do you want no
> >> >> > > downtime
> >> >> > > on
> >> >> > > your
> >> >> > > VMs or is downtime acceptable. Also are you running hosted engine
> >> >> > > or
> >> >> > > not?
> >> >> > >
> >> >> > > This is the basic plan which can be adjusted based on what your
> >> >> > > needs
> >> >> > > are:
> >> >> > >
> >> >> > > 1. Update engine from 3.5 to 3.6 (if hosted engine might be
> >> >> > > trickier,
> >> >> > > not
> >> >> > > sure
> >> >> > > haven't played with hosted engine).
> >> >> > > 2. Create a new 3.6 cluster.
> >> >> > > 3. Put 1 host in maintenance (which will migrate the VMs to the
> >> >> > > other
> >> >> > > hosts).
> >> >> > > 4. Remove the host from the DC.
> >> >> > > 5. Install C7.2 on the host
> >> >> > > 6. Add that host to the new 3.6 cluster.
> >> >> > > 7. Optional (you can cross cluster live migrate some VMs from 6
> to
> >> >> > > 7
> >> >> > > (just
> >> >> > > not
> >> >> > > the other way around, so once the VM is moved its stuck in the
> new
> >> >> > > cluster).
> >> >> > > 8. Go to 3 until all hosts are moved.
> >> >> > > 9. Your 3.5 cluster should now be empty, and can be removed.
> >> >> > > 10. Upgrade your DC to 3.6 (Can't upgrade if any lower clusters
> >> >> > > exist).
> >> >> > >
> >> >> > > If you can have downtime, then just shut down the VMs running on
> >> >> > > the
> >> >> > > host
> >> >> > > in
> >> >> > > step 3 before putting it in maintenance. Once the host is moved
> to
> >> >> > > the
> >> >> > > new
> >> >> > > cluster you can start the VMs.
> >> >> > >
> >> >> > > Alexander
> >> >> > > ___
> >> >> > > Users mailing list
> >> >> > > Users@ovirt.org
> >> >> > > http://lists.ovirt.org/mailman/listinfo/users
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Met vriendelijke groeten / With kind regards,
> >> > Johan Kooijman
> >> >
> >> > ___
> >> > Users mailing list
> >> > Users@ovirt.org
> >> > http://lists.ovirt.org/mailman/listinfo/users
> >> >
> >>
> >>
> >>
> >> --
> >> Didi
> >
> >
> >
> >
> > --
> > Met vriendelijke groeten / With kind regards,
> > Johan Kooijman
>
>
>
> --
> Didi
>



-- 
Met vriendelijke groeten / With kind regards,
Johan Kooijman

Re: [ovirt-users] Upgrade patch 3.5 -> 3.6

2016-02-16 Thread Yedidyah Bar David 
On Tue, Feb 16, 2016 at 11:58 AM, Johan Kooijman  wrote:
> Didi,
>
> Ok, the piece of information on engine still supported on 3.6 was unknown to
> me. Makes my job a lot easier.
>
> What would be the recommended path: first upgrade the nodes to 3.6 and then
> the engine? Or the other way around?

Generally speaking, first engine then nodes. I am pretty certain it's documented
on the wiki, didn't check.

>
> On Tue, Feb 16, 2016 at 8:45 AM, Yedidyah Bar David  wrote:
>>
>> On Tue, Feb 16, 2016 at 9:30 AM, Johan Kooijman 
>> wrote:
>> > Yes. I pasted the information on AIO, that was wrong on my end. I have
>> > an
>> > engine running on dedicated hardware and about 20 nodes in this cluster.
>> > I
>> > do like to upgrade without downtime :) I know how to achieve this on the
>> > node-end, but since I have to go from C6 to C7, I wonder what the
>> > procedure
>> > would be for engine.
>>
>> Please explain exactly what you are trying to do.
>>
>> Note that engine is still supported on el6.
>>
>> (new) Hosts are not.
>>
>> all-in-one is running both together, thus is not supported on el6 either.
>>
>> IIRC we do not have a tested procedure to upgrade the engine from C6 to C7
>> yet, see also:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1234257
>> https://bugzilla.redhat.com/show_bug.cgi?id=1285743
>>
>> Best,
>>
>> >
>> > On Mon, Feb 15, 2016 at 9:21 PM, Alexander Wels 
>> > wrote:
>> >>
>> >> On Monday, February 15, 2016 08:21:40 PM Johan Kooijman wrote:
>> >> > Hi Alexander,
>> >> >
>> >> > Thanks for the input! My 3.5 is running on C6 however:
>> >> >
>> >> > Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the
>> >> > packages
>> >> > requiring it are not built anymore for EL6
>> >> >
>> >>
>> >> Well that was a piece of information you forgot to mention in your
>> >> initial
>> >> email. So now I am not entirely sure what you are trying to do. Are you
>> >> trying
>> >> to save your existing VMs when you reinstall your machine?
>> >>
>> >>
>> >> > On Mon, Feb 15, 2016 at 3:37 PM, Alexander Wels 
>> >> > wrote:
>> >> > > On Monday, February 15, 2016 02:40:47 PM Johan Kooijman wrote:
>> >> > > > Hi,
>> >> > > >
>> >> > > > Can anybody recommend me best practice upgrade path for an
>> >> > > > upgrade
>> >> > > > from
>> >> > > > oVirt 3.5 on C6 to 3.6 on C7.2?
>> >> > >
>> >> > > The answer sort of depends on what you want. Do you want no
>> >> > > downtime
>> >> > > on
>> >> > > your
>> >> > > VMs or is downtime acceptable. Also are you running hosted engine
>> >> > > or
>> >> > > not?
>> >> > >
>> >> > > This is the basic plan which can be adjusted based on what your
>> >> > > needs
>> >> > > are:
>> >> > >
>> >> > > 1. Update engine from 3.5 to 3.6 (if hosted engine might be
>> >> > > trickier,
>> >> > > not
>> >> > > sure
>> >> > > haven't played with hosted engine).
>> >> > > 2. Create a new 3.6 cluster.
>> >> > > 3. Put 1 host in maintenance (which will migrate the VMs to the
>> >> > > other
>> >> > > hosts).
>> >> > > 4. Remove the host from the DC.
>> >> > > 5. Install C7.2 on the host
>> >> > > 6. Add that host to the new 3.6 cluster.
>> >> > > 7. Optional (you can cross cluster live migrate some VMs from 6 to
>> >> > > 7
>> >> > > (just
>> >> > > not
>> >> > > the other way around, so once the VM is moved its stuck in the new
>> >> > > cluster).
>> >> > > 8. Go to 3 until all hosts are moved.
>> >> > > 9. Your 3.5 cluster should now be empty, and can be removed.
>> >> > > 10. Upgrade your DC to 3.6 (Can't upgrade if any lower clusters
>> >> > > exist).
>> >> > >
>> >> > > If you can have downtime, then just shut down the VMs running on
>> >> > > the
>> >> > > host
>> >> > > in
>> >> > > step 3 before putting it in maintenance. Once the host is moved to
>> >> > > the
>> >> > > new
>> >> > > cluster you can start the VMs.
>> >> > >
>> >> > > Alexander
>> >> > > ___
>> >> > > Users mailing list
>> >> > > Users@ovirt.org
>> >> > > http://lists.ovirt.org/mailman/listinfo/users
>> >>
>> >
>> >
>> >
>> > --
>> > Met vriendelijke groeten / With kind regards,
>> > Johan Kooijman
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>>
>>
>>
>> --
>> Didi
>
>
>
>
> --
> Met vriendelijke groeten / With kind regards,
> Johan Kooijman



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

Re: [ovirt-users] How does VDSM-Fake actually work?

2016-02-16 Thread Roman Mohr 
On Fri, Feb 12, 2016 at 12:45 PM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
> On 09 Feb 2016, at 12:15, Nicolás  wrote:
>
> Is there a way to get an account on mojo.redhat.com or is it internal?
> I'm trying to open the document but credentials are required and I see no
> option to create an account.
>
>
> yes it is
>
> Eldad, would you please move it to ovirt.org instead?
>
>
I recently played with fakevdsm myself. The result was the patch series in
[1]. At least an updated README for the result of my patches can be found
in [2].


> Thanks,
> michal
>
>
> El 04/02/16 a las 13:49, emarcian escribió:
>
> Hi,
> Seems like you need to change this settings update vdc_options set
> option_value='false' where option_name='InstallVds';
> follow the instructions here:
> 
> https://mojo.redhat.com/docs/DOC-990399
>
> in case you using 3.6 there is a new war (if you run the simulator as
> standalone).
>
> -Eldad
>
>
> On 02/04/2016 03:04 PM, Piotr Kliczewski wrote:
>
> Eldad is working on making it working with engine 3.6. He should be able to
> give you information you need.
>
> On Wed, Feb 3, 2016 at 12:33 PM,    
> wrote:
>
> Anything?
>
> El 2016-02-02 10:18, Nicolás escribió:
>
> Hi,
>
>  I'm trying to set up VDSM-Fake
> (git://gerrit.ovirt.org/ovirt-vdsmfake.git) for some tests, however,
> I'm a bit confused about how does it actually work. As the
> instructions say, I was able to build the project with Maven (however,
> the org.ovirt.vdsm-jsonrpc-java dependency version had to be changed
> to 1.1.5 instead of 1.1.2-SNAPSHOT in pom.xml as this latter is no
> longer provided at the repository).
>
>  Once built, I run mvn jetty:run and the server started correctly:
>
>
> 2016-02-02 11:01:51.957:INFO::jetty-6.1.26 [1]
> 2016-02-02 11:01:52.804:INFO::No [2] Transaction manager found - if
> your webapp requires one, please configure one.
> 2016-02-02 11:01:53,424 Application initialized.
> 2016-02-02 11:01:53,442 Opening a Stomp server localhost:54322
> 2016-02-02 11:01:53.702:INFO::Started [3]SelectChannelConnector@0.0.0.0:54321
> [INFO] Started Jetty Server
> [INFO] Starting scanner at interval of 10 seconds.
>
>  I could indeed verify it's listening on the VDSM port:
>
>
> [root@host ovirt-vdsmfake]# netstat -atpn | grep 54321
> tcp6   0  0
> :::54321
> :::*LISTEN
> 44870/java
>
>  So the next step is to add a fake host via REST. I used scripts
> provided here [4] and I successfully added the host, however, it
> starts installing all the VDSM packages as it were a normal host and
> therefore it tries to start vdsmd as well, which throws an error as
> the Jetty Server is already listening on the 54321 port. I shut down
> the Jetty Server and allowed oVirt Manager to install all the packages
> properly, then stopped vdsmd and started the Jetty Server, but
> expectedly oVirt Engine fails with message "Host xxx is non
> responsive", so what I actually got is a real VDSM host and not a fake
> one.
>
>  FWIW, the fake VDSM runs on a different host, ports are reacheable
> from the oVirt engine, proper /etc/hosts has been added to the engine
> to reach the host, and no further customization of web.xml has been
> done.
>
>  I feel like I'm missing something here. Could someone shed some light
> on what's wrong?
>
>  Thanks.
>
>  Nicolás
>
>
@Nicolas I would recommend you to use the top of my gerrit patches to run
vdsmake:

  git clone git://gerrit.ovirt.org/ovirt-vdsmfake
  cd ovirt-vdsmfake
  git fetch git://gerrit.ovirt.org/ovirt-vdsmfake refs/changes/70/53570/2
&& git checkout FETCH_HEAD

then follow the instructions in the README of the checked out repository
[3].

Hope that helps.

Best Regards,
Roman


>
> [1]
https://gerrit.ovirt.org/#/q/status:open+project:ovirt-vdsmfake+branch:master+topic:easy_access
[2] https://gerrit.ovirt.org/#/c/53570/
[3] https://gerrit.ovirt.org/#/c/53570/2/README
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Upgrade patch 3.5 -> 3.6

2016-02-16 Thread Johan Kooijman 
Didi,

Ok, the piece of information on engine still supported on 3.6 was unknown
to me. Makes my job a lot easier.

What would be the recommended path: first upgrade the nodes to 3.6 and then
the engine? Or the other way around?

On Tue, Feb 16, 2016 at 8:45 AM, Yedidyah Bar David  wrote:

> On Tue, Feb 16, 2016 at 9:30 AM, Johan Kooijman 
> wrote:
> > Yes. I pasted the information on AIO, that was wrong on my end. I have an
> > engine running on dedicated hardware and about 20 nodes in this cluster.
> I
> > do like to upgrade without downtime :) I know how to achieve this on the
> > node-end, but since I have to go from C6 to C7, I wonder what the
> procedure
> > would be for engine.
>
> Please explain exactly what you are trying to do.
>
> Note that engine is still supported on el6.
>
> (new) Hosts are not.
>
> all-in-one is running both together, thus is not supported on el6 either.
>
> IIRC we do not have a tested procedure to upgrade the engine from C6 to C7
> yet, see also:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1234257
> https://bugzilla.redhat.com/show_bug.cgi?id=1285743
>
> Best,
>
> >
> > On Mon, Feb 15, 2016 at 9:21 PM, Alexander Wels 
> wrote:
> >>
> >> On Monday, February 15, 2016 08:21:40 PM Johan Kooijman wrote:
> >> > Hi Alexander,
> >> >
> >> > Thanks for the input! My 3.5 is running on C6 however:
> >> >
> >> > Upgrade of All-in-One on EL6 is not supported in 3.6. VDSM and the
> >> > packages
> >> > requiring it are not built anymore for EL6
> >> >
> >>
> >> Well that was a piece of information you forgot to mention in your
> initial
> >> email. So now I am not entirely sure what you are trying to do. Are you
> >> trying
> >> to save your existing VMs when you reinstall your machine?
> >>
> >>
> >> > On Mon, Feb 15, 2016 at 3:37 PM, Alexander Wels 
> >> > wrote:
> >> > > On Monday, February 15, 2016 02:40:47 PM Johan Kooijman wrote:
> >> > > > Hi,
> >> > > >
> >> > > > Can anybody recommend me best practice upgrade path for an upgrade
> >> > > > from
> >> > > > oVirt 3.5 on C6 to 3.6 on C7.2?
> >> > >
> >> > > The answer sort of depends on what you want. Do you want no downtime
> >> > > on
> >> > > your
> >> > > VMs or is downtime acceptable. Also are you running hosted engine or
> >> > > not?
> >> > >
> >> > > This is the basic plan which can be adjusted based on what your
> needs
> >> > > are:
> >> > >
> >> > > 1. Update engine from 3.5 to 3.6 (if hosted engine might be
> trickier,
> >> > > not
> >> > > sure
> >> > > haven't played with hosted engine).
> >> > > 2. Create a new 3.6 cluster.
> >> > > 3. Put 1 host in maintenance (which will migrate the VMs to the
> other
> >> > > hosts).
> >> > > 4. Remove the host from the DC.
> >> > > 5. Install C7.2 on the host
> >> > > 6. Add that host to the new 3.6 cluster.
> >> > > 7. Optional (you can cross cluster live migrate some VMs from 6 to 7
> >> > > (just
> >> > > not
> >> > > the other way around, so once the VM is moved its stuck in the new
> >> > > cluster).
> >> > > 8. Go to 3 until all hosts are moved.
> >> > > 9. Your 3.5 cluster should now be empty, and can be removed.
> >> > > 10. Upgrade your DC to 3.6 (Can't upgrade if any lower clusters
> >> > > exist).
> >> > >
> >> > > If you can have downtime, then just shut down the VMs running on the
> >> > > host
> >> > > in
> >> > > step 3 before putting it in maintenance. Once the host is moved to
> the
> >> > > new
> >> > > cluster you can start the VMs.
> >> > >
> >> > > Alexander
> >> > > ___
> >> > > Users mailing list
> >> > > Users@ovirt.org
> >> > > http://lists.ovirt.org/mailman/listinfo/users
> >>
> >
> >
> >
> > --
> > Met vriendelijke groeten / With kind regards,
> > Johan Kooijman
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
>
> --
> Didi
>



-- 
Met vriendelijke groeten / With kind regards,
Johan Kooijman
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [FC22] ovirt-engine-reports missing in 3.6 repos

2016-02-16 Thread David Marzal Canovas 
Ok, thank you both for the information, I will explore the possibility
of using another server for the reports. 

It may be useful for other if this is mentioned on the web (Fedora is
the first suggestion I've seen everywhere in the documentation) 

El 2016-02-14 14:46, Yaniv Dary escribió:

> You can install DWH and reports on a CentOS 6 VM in the installation and 
> connect them to the engine machine. 
> 
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
> 
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
> 
> On Sat, Feb 13, 2016 at 3:14 PM, Sandro Bonazzola  wrote:
> 
> Sadly reports is not compatible with java 8 so it's not available on fedora 
> 22.
> 
> Il 12/Feb/2016 12:04, "David Marzal Canovas"  ha 
> scritto: 
> 
> Hi, I have installed oVirt 3.6 in a production system with FC22.
> I want to install the Reports Portal, but I can't find the packages in the 
> repo.
> 
> FC22: There is no ovirt-engine-reports* , ovirt-engine-dwh
> http://resources.ovirt.org/pub/ovirt-3.6/rpm/fc22/noarch/
> BUT in el7**, el6* they are availables
> http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7/noarch/ 
> 
> For oVirt 3.5 the packages exits: 
> 
> http://resources.ovirt.org/pub/ovirt-3.5/rpm/fc20/noarch/
> 
> Searching I found in Jenkins:
> http://jenkins.ovirt.org/job/ovirt-reports_master_create-rpms-fc22-x86_64_created/
>  
> 
> http://jenkins.ovirt.org/job/ovirt-reports_master_create-rpms-fc22-x86_64_merged/
> 
> So I'm not sure if the Reports Portail is only available in a Centos/RHEV 
> installation or if there is some problem with the sync on the repos.
> There is no documentation with any reference to this in the wiki or the 
> mailing-list. 
> 
> Does anyone know anything about this?
> 
> -- 
> 
> David Marzal Cánovas 
> Servicio de Mecanización e Informática
> Asamblea Regional de Murcia
> Paseo Alfonso XIII, nº53
> 30203 - Cartagena
> Tlfno: 968326800 
> 
> ___
> 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

-- 

 David Marzal Cánovas 
Servicio de Mecanización e Informática
Asamblea Regional de Murcia
Paseo Alfonso XIII, nº53
30203 - Cartagena
Tlfno: 968326800 

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

[ovirt-users] [Node] Maintenance mode and update

2016-02-16 Thread Lionel Caignec 
Hello,

I am concerned about maintenance mode and system updates.
In which case it is essential to put host in maintenance mode?
No worries for Content Updates requiring a reboot.

But for example in the case of updates like VDSM* or kvm it seems essential, 
but is it?

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