Re: [ovirt-users] preallocated storage issue?
Storage is NFS. What logs would you like to see?
Many thanks.
Simon
On Sun, Aug 7, 2016 at 8:53 AM +0100, "Fred Rolland"
<froll...@redhat.com<mailto:froll...@redhat.com>> wrote:
Simon hi,
What storage type are you using in source and target storage domains ? (NFS,
ISCSI)
Can you share the logs?
Thanks,
Fred
On Fri, Aug 5, 2016 at 6:37 PM, Simon Barrett
<simon.barr...@tradingscreen.com<mailto:simon.barr...@tradingscreen.com>> wrote:
Another example. This one was moved to a new storage domain
root@ovirt_host1> qemu-img info dd6f25f6-7830-4024-915f-a20268797c34
image: dd6f25f6-7830-4024-915f-a20268797c34
file format: raw
virtual size: 200G (214748364800 bytes)
disk size: 5.0G
root@ ovirt_host1> cat dd6f25f6-7830-4024-915f-a20268797c34.meta
DOMAIN=53560d43-874a-49c5-9c5a-8b90487c79f8
VOLTYPE=LEAF
CTIME=1470305678
FORMAT=RAW
IMAGE=741976cd-d1cb-4031-bdbe-6a745dff16ef
DISKTYPE=2
PUUID=----
LEGALITY=LEGAL
MTIME=0
POOL_UUID=
SIZE=419430400
TYPE=PREALLOCATED
DESCRIPTION=
EOF
This one has not been moved:
r...@ny2-lvb-066.mgt> qemu-img info 155f0d33-c280-4236-8d1e-fcb88f9a1242
image: 155f0d33-c280-4236-8d1e-fcb88f9a1242
file format: raw
virtual size: 90G (96636764160 bytes)
disk size: 90G
r...@ny2-lvb-066.mgt> cat 155f0d33-c280-4236-8d1e-fcb88f9a1242.meta
DOMAIN=59bde2ff-e10d-477e-91c1-6355abff0999
CTIME=1464946639
FORMAT=RAW
DISKTYPE=2
LEGALITY=LEGAL
SIZE=188743680
VOLTYPE=LEAF
DESCRIPTION={"DiskAlias":"ny2-laa-010.prod_Disk1","DiskDescription":""}
IMAGE=82158182-81a4-458e-a41b-663756962666
PUUID=----
MTIME=0
POOL_UUID=
TYPE=PREALLOCATED
EOF
See the mismatch between “virtual size” and “disk size” on the one that was
moved.
TIA,
Simon
From: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>
[mailto:users-boun...@ovirt.org<mailto:users-boun...@ovirt.org>] On Behalf Of
Simon Barrett
Sent: Friday, 5 August, 2016 10:25
To: users@ovirt.org<mailto:users@ovirt.org>
Subject: [ovirt-users] preallocated storage issue?
If I create a preallocated disk for a VM, I see the disk image file listing as
the size I requested (100G):
cd
/rhev/data-center/mnt/storage_host1:_vol_pa1__nas__01b__oVirt__prod__01/53560d43-874a-49c5-9c5a-8b90487c79f8/images/d97f7706-3662-40bf-9358-80e0dc51bff4
root@ovirt_host> ls -l
total 105064644
-rw-rw 1 vdsm kvm 107374182400 Aug 5 10:57
75c14559-e18f-4cc8-a3fe-bc0de507720b
-rw-rw 1 vdsm kvm 1048576 Aug 5 10:57
75c14559-e18f-4cc8-a3fe-bc0de507720b.lease
-rw-r--r-- 1 vdsm kvm 313 Aug 5 10:57
75c14559-e18f-4cc8-a3fe-bc0de507720b.meta
and the corresponding space used on disk matches
root@ ovirt_host > du -sh *
101G75c14559-e18f-4cc8-a3fe-bc0de507720b
1.1M75c14559-e18f-4cc8-a3fe-bc0de507720b.lease
4.0K75c14559-e18f-4cc8-a3fe-bc0de507720b.meta
If I then migrate that storage (while the VM is shutdown) to a new storage
domain, the size on disk does not match the allocated size. In this case there
is nothing in the disk yet so it shows as 0.
cd
/rhev/data-center/mnt/storage_host2:_vol_pa1__ovirt__uatprod/1f2c2b48-1e77-4c98-a6da-5dc09b78cead/images/d97f7706-3662-40bf-9358-80e0dc51bff4
root@ ovirt_host> ls -l
total 1032
-rw-rw 1 vdsm kvm 107374182400 Aug 5 11:06
75c14559-e18f-4cc8-a3fe-bc0de507720b
-rw-rw 1 vdsm kvm 1048576 Aug 5 11:06
75c14559-e18f-4cc8-a3fe-bc0de507720b.lease
-rw-r--r-- 1 vdsm kvm 313 Aug 5 11:06
75c14559-e18f-4cc8-a3fe-bc0de507720b.meta
root@ ovirt_host > du -sh *
0 75c14559-e18f-4cc8-a3fe-bc0de507720b
1.1M75c14559-e18f-4cc8-a3fe-bc0de507720b.lease
4.0K75c14559-e18f-4cc8-a3fe-bc0de507720b.meta
oVirt still lists the disk as preallocated in the GUI but it is in fact thin
provisioned.
I see the same issue if I clone a preallocated VM. The size on disk ends up
being the equivalent of a thin-provisioned disk. I also had the issue when
importing VM’s from an export domain when I had selected preallocated in the
import dialog box.
Is this a known issue? Should preallocated not mean preallocated on physical
disk?
Ovirt Engine is running 3.6.4.1-1.el6
The ovirt nodes are running:
OS Version:RHEL - 7 - 2.1511.el7.centos.2.10
Kernel Version: 3.10.0 - 327.4.5.el7.x86_64
KVM Version:2.3.0 - 31.el7_2.7.1
LIBVIRT Version: libvirt-1.2.17-13.el7_2.2
VDSM Version: vdsm-4.17.23.2-0.el7.centos
SPICE Version: 0.12.4 - 15.el7
GlusterFS Version: [N/A]
CEPH Version: librbd1-0.80.7-3.el7
Many thanks,
Simon
___
Users mailing list
Users@ovirt.org<mailto: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] preallocated storage issue?
If I create a preallocated disk for a VM, I see the disk image file listing as the size I requested (100G): cd /rhev/data-center/mnt/storage_host1:_vol_pa1__nas__01b__oVirt__prod__01/53560d43-874a-49c5-9c5a-8b90487c79f8/images/d97f7706-3662-40bf-9358-80e0dc51bff4 root@ovirt_host> ls -l total 105064644 -rw-rw 1 vdsm kvm 107374182400 Aug 5 10:57 75c14559-e18f-4cc8-a3fe-bc0de507720b -rw-rw 1 vdsm kvm 1048576 Aug 5 10:57 75c14559-e18f-4cc8-a3fe-bc0de507720b.lease -rw-r--r-- 1 vdsm kvm 313 Aug 5 10:57 75c14559-e18f-4cc8-a3fe-bc0de507720b.meta and the corresponding space used on disk matches root@ ovirt_host > du -sh * 101G75c14559-e18f-4cc8-a3fe-bc0de507720b 1.1M75c14559-e18f-4cc8-a3fe-bc0de507720b.lease 4.0K75c14559-e18f-4cc8-a3fe-bc0de507720b.meta If I then migrate that storage (while the VM is shutdown) to a new storage domain, the size on disk does not match the allocated size. In this case there is nothing in the disk yet so it shows as 0. cd /rhev/data-center/mnt/storage_host2:_vol_pa1__ovirt__uatprod/1f2c2b48-1e77-4c98-a6da-5dc09b78cead/images/d97f7706-3662-40bf-9358-80e0dc51bff4 root@ ovirt_host> ls -l total 1032 -rw-rw 1 vdsm kvm 107374182400 Aug 5 11:06 75c14559-e18f-4cc8-a3fe-bc0de507720b -rw-rw 1 vdsm kvm 1048576 Aug 5 11:06 75c14559-e18f-4cc8-a3fe-bc0de507720b.lease -rw-r--r-- 1 vdsm kvm 313 Aug 5 11:06 75c14559-e18f-4cc8-a3fe-bc0de507720b.meta root@ ovirt_host > du -sh * 0 75c14559-e18f-4cc8-a3fe-bc0de507720b 1.1M75c14559-e18f-4cc8-a3fe-bc0de507720b.lease 4.0K75c14559-e18f-4cc8-a3fe-bc0de507720b.meta oVirt still lists the disk as preallocated in the GUI but it is in fact thin provisioned. I see the same issue if I clone a preallocated VM. The size on disk ends up being the equivalent of a thin-provisioned disk. I also had the issue when importing VM's from an export domain when I had selected preallocated in the import dialog box. Is this a known issue? Should preallocated not mean preallocated on physical disk? Ovirt Engine is running 3.6.4.1-1.el6 The ovirt nodes are running: OS Version:RHEL - 7 - 2.1511.el7.centos.2.10 Kernel Version: 3.10.0 - 327.4.5.el7.x86_64 KVM Version:2.3.0 - 31.el7_2.7.1 LIBVIRT Version: libvirt-1.2.17-13.el7_2.2 VDSM Version: vdsm-4.17.23.2-0.el7.centos SPICE Version: 0.12.4 - 15.el7 GlusterFS Version: [N/A] CEPH Version: librbd1-0.80.7-3.el7 Many thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] vhostmd vdsm-hook
Thanks again but how does that work when a VM is configured to have more than one disk? If I have a VM with a /dev/vda disk and a /dev/vdb disk, when I turn the vhostmd hook on the vm metric device gets created as /dev/vdb and the original /dev/vdb disk gets bumped to /dev/vdc. Is that expected behavior? Will that not cause problems? Thanks, Simon From: Arsène Gschwind [mailto:arsene.gschw...@unibas.ch] Sent: Tuesday, 19 April, 2016 13:06 To: Simon Barrett <simon.barr...@tradingscreen.com>; users@ovirt.org Subject: Re: [ovirt-users] vhostmd vdsm-hook The metric information are available on this additional disk /dev/vdb. You may install the package vm-dump-metrics and use the command vm-dump-metrics which will display all metrics in an xml format. Arsène On 04/19/2016 10:48 AM, Simon Barrett wrote: Thanks Arsène, I have vhostmd running on the ovirt node and have set the sap_agent to true on the VM configuration. I also stopped and started the VM to ensure that the config change took effect. On the oVirt node I see the vhostmd running and see the following entry in the qemu-kvm output: drive file=/dev/shm/vhostmd0,if=none,id=drive-virtio-disk701,readonly=on,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk701,id=virtio-disk701 The part I wasn't quite understanding was how this presented itself on the VM but I now see a new disk device "/dev/vdb". If I cat the contents of /dev/vdb I now see the information that is provided from the ovirt node, which is great news and very useful. Thanks for your help. Simon From: users-boun...@ovirt.org<mailto:users-boun...@ovirt.org> [mailto:users-boun...@ovirt.org] On Behalf Of Arsène Gschwind Sent: Monday, 18 April, 2016 16:03 To: users@ovirt.org<mailto:users@ovirt.org> Subject: Re: [ovirt-users] vhostmd vdsm-hook Hi Simon, You will need to have vhostmd running on the oVirt node and set the "sap_agent" custom property for the vm as you may see on the screenshot. [sap_agent] Arsène On 04/15/2016 12:15 PM, Simon Barrett wrote: I'm trying to use the vhostmd vdsm host to access ovirt node metrics from within a VM. Vhostmd is running and updating the /dev/shm/vhostmd0 on the ovirt node. The part I'm stuck on is: "This disk image is exported read-only to guests. Guests can read the disk image to see metrics" from http://www.ovirt.org/develop/developer-guide/vdsm/hook/vhostmd/ Does the hook do this by default? I don't see any new read-only device mounted in the guest. Is there additional work I need to do to mount this and access the data from within the guest? Many thanks, Simon ___ Users mailing list Users@ovirt.org<mailto: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] vhostmd vdsm-hook
Thanks Arsène, I have vhostmd running on the ovirt node and have set the sap_agent to true on the VM configuration. I also stopped and started the VM to ensure that the config change took effect. On the oVirt node I see the vhostmd running and see the following entry in the qemu-kvm output: drive file=/dev/shm/vhostmd0,if=none,id=drive-virtio-disk701,readonly=on,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk701,id=virtio-disk701 The part I wasn't quite understanding was how this presented itself on the VM but I now see a new disk device "/dev/vdb". If I cat the contents of /dev/vdb I now see the information that is provided from the ovirt node, which is great news and very useful. Thanks for your help. Simon From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Arsène Gschwind Sent: Monday, 18 April, 2016 16:03 To: users@ovirt.org Subject: Re: [ovirt-users] vhostmd vdsm-hook Hi Simon, You will need to have vhostmd running on the oVirt node and set the "sap_agent" custom property for the vm as you may see on the screenshot. [sap_agent] Arsène On 04/15/2016 12:15 PM, Simon Barrett wrote: I'm trying to use the vhostmd vdsm host to access ovirt node metrics from within a VM. Vhostmd is running and updating the /dev/shm/vhostmd0 on the ovirt node. The part I'm stuck on is: "This disk image is exported read-only to guests. Guests can read the disk image to see metrics" from http://www.ovirt.org/develop/developer-guide/vdsm/hook/vhostmd/ Does the hook do this by default? I don't see any new read-only device mounted in the guest. Is there additional work I need to do to mount this and access the data from within the guest? Many thanks, Simon ___ Users mailing list Users@ovirt.org<mailto: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] vhostmd vdsm-hook
I'm trying to use the vhostmd vdsm host to access ovirt node metrics from within a VM. Vhostmd is running and updating the /dev/shm/vhostmd0 on the ovirt node. The part I'm stuck on is: "This disk image is exported read-only to guests. Guests can read the disk image to see metrics" from http://www.ovirt.org/develop/developer-guide/vdsm/hook/vhostmd/ Does the hook do this by default? I don't see any new read-only device mounted in the guest. Is there additional work I need to do to mount this and access the data from within the guest? Many thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] 3.6 on el6
Apologies if this has been answered previously but can anyone confirm if oVirt 3.6.x is supported on el6? I run the nodes on CentOS 6.7 but see that vdsm is no longer in the repo. Many thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] 3.6 on el6
Thanks for the confirmation. From: Simone Tiraboschi [mailto:stira...@redhat.com] Sent: Friday, February 12, 2016 10:31 To: Simon Barrett <simon.barr...@tradingscreen.com> Cc: users@ovirt.org Subject: Re: [ovirt-users] 3.6 on el6 On Fri, Feb 12, 2016 at 11:18 AM, Simon Barrett <simon.barr...@tradingscreen.com<mailto:simon.barr...@tradingscreen.com>> wrote: Apologies if this has been answered previously but can anyone confirm if oVirt 3.6.x is supported on el6? You can run ovirt-engine from 3.6 on el6 or on el7. VDSM from 3.6 is available only for el7. A 3.6 engine can also manage el6 hosts in cluster with 3.5 compatibility mode. You cannot mix el6 and el7 hosts in the same cluster. I run the nodes on CentOS 6.7 but see that vdsm is no longer in the repo. Many thanks, Simon ___ Users mailing list Users@ovirt.org<mailto: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] 3.6 on el6
One last question re: “You cannot mix el6 and el7 hosts in the same cluster.” Can we not mix them if the “compatibility version” is set to 3.5. i.e. a version that both the el6 & el7 nodes would support. Thanks From: Simone Tiraboschi [mailto:stira...@redhat.com] Sent: Friday, February 12, 2016 10:31 To: Simon Barrett <simon.barr...@tradingscreen.com> Cc: users@ovirt.org Subject: Re: [ovirt-users] 3.6 on el6 On Fri, Feb 12, 2016 at 11:18 AM, Simon Barrett <simon.barr...@tradingscreen.com<mailto:simon.barr...@tradingscreen.com>> wrote: Apologies if this has been answered previously but can anyone confirm if oVirt 3.6.x is supported on el6? You can run ovirt-engine from 3.6 on el6 or on el7. VDSM from 3.6 is available only for el7. A 3.6 engine can also manage el6 hosts in cluster with 3.5 compatibility mode. You cannot mix el6 and el7 hosts in the same cluster. I run the nodes on CentOS 6.7 but see that vdsm is no longer in the repo. Many thanks, Simon ___ Users mailing list Users@ovirt.org<mailto: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] Live VM snapshot deletion
I don't appear to be able to delete snapshots for a running VM. Is that on the roadmap at all? Many thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Live VM snapshot deletion
Thanks for the info. Do you know if there are any plans for it in el6? Simon From: Yaniv Dary [mailto:yd...@redhat.com] Sent: Tuesday, January 26, 2016 10:42 To: Simon Barrett <simon.barr...@tradingscreen.com> Cc: users@ovirt.org Subject: Re: [ovirt-users] Live VM snapshot deletion It was added for el7 only in oVirt 3.5. Already supported for a long while. 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<mailto:yd...@redhat.com> IRC : ydary On Tue, Jan 26, 2016 at 12:05 PM, Simon Barrett <simon.barr...@tradingscreen.com<mailto:simon.barr...@tradingscreen.com>> wrote: I don’t appear to be able to delete snapshots for a running VM. Is that on the roadmap at all? Many thanks, Simon ___ Users mailing list Users@ovirt.org<mailto: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] The field is not attached to any instance type
Many thanks for the info. Makes sense now. Simon -Original Message- From: Tomas Jelinek [mailto:tjeli...@redhat.com] Sent: 30 September 2015 12:09 To: Simon Barrett <simon.barr...@tradingscreen.com> Cc: users@ovirt.org Subject: Re: [ovirt-users] The field is not attached to any instance type - Original Message - > From: "Simon Barrett" <simon.barr...@tradingscreen.com> > To: users@ovirt.org > Sent: Wednesday, September 30, 2015 11:44:34 AM > Subject: [ovirt-users] The field is not attached to any instance type > > > > I’ve recently upgraded from 3.5.3 to 3.5.4.2-el6. Now when I edit a VM > I see a small icon to the left of some fields. It looks like an unlinked > symbol. > When I hover over it the following text pops up: > > > > The field is not attached to any instance type > > > > I see it on various fields. E.G.: > > > > Edit Virtual Machine > > - System Tab > > -- Memory Size > > -- Total Virtual CPUs > > -- Cores per Virtual Socket > > -- Virtual Sockets > > > > - Host tab > > -- The two migration option fileds > > > > I don’t see the same icon when editing hosts, storage, networks etc. > > > > VM live migration and restarts are all OK. I can also edit the values > and the changes take effect as set. > > > > Does anyone have any idea what this means? It is a feature [1] :) The point is that when you pick an instance type, and you do not change any of this fields, the VM will be attached to that picked instance type (the icon will be joined). Now, when you change the picked instance type, all VMs which are attached to this instance type will be edited accordingly. [1]: http://www.ovirt.org/Features/Instance_Types > > > > Many thanks, > > > > Simon > > ___ > 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] oVirt 3.5.3 and Network Unified Persistence issues?
Thanks for the info. Sadly, I'm seeing some inconsistency between different oVirt nodes as to how management interfaces are being handled. On one host, the ifcfg-bond0, ifcfg-eth0, ifcfg-eth1 interface files that the management interface is dependent on are being set with "ONBOOT=no". The --force on the restore-nets just re-instates those files with the incorrect "ONBOOT=no" configuration. On another host those same interfaces are left as ONBOOT=yes. I'm still trying to work out what the differences are between the two hosts. I was also looking to see if I could use vdsClient to manually add the config for ifcfg-bond0, ifcfg-eth0, ifcfg-eth1 so at least vdsm would know about them and apply the correct configuration. Not sure if this is a sensible approach or not. Thanks, Simon -Original Message- From: Ido Barkan [mailto:ibar...@redhat.com] Sent: 01 September 2015 13:12 To: Michael Burman <mbur...@redhat.com> Cc: Simon Barrett <simon.barr...@tradingscreen.com>; users@ovirt.org Subject: Re: [ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues? Hi Simon. In the meantime (until 3.5.4 is out) you can run "vdsm-tool restore-nets --force" to solve this after "service network restart". Vdsm will skip restoration if this was done since last boot. The --force flags will skip this check. Ido On Tue, Aug 25, 2015 at 7:45 PM, Michael Burman <mbur...@redhat.com> wrote: > Hi Simon, > > This issue will be fixed on 3.5.4 > see - https://bugzilla.redhat.com/show_bug.cgi?id=1203422 > > On 3.5.3, vdsm generating all ifcfg-* files to ONBOOT=NO by default, except > the management network and the interface it is attached to. In your case bond > (bond0,bond.108 and the slaves). > - You can configure your ifcfg-* files manually to ONBOOT=yes and restart > network service as a workaround for now. > > Kind regards, > Michael B > > - Original Message - > From: "Simon Barrett" <simon.barr...@tradingscreen.com> > To: users@ovirt.org > Sent: Monday, August 24, 2015 5:01:45 PM > Subject: [ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues? > > > > I’m running into a problem with my upgrades to oVirt 3.5.3 and wanted to > check if the following is a known issue. > > > > I have multiple vlan tagged interfaces configured. The files are being > generated as expected by vdsm. The vlan 108 interface below is used by the > ovirtmgmt bridge. The uatdev_ben, bond0.192, dev_office, bond0.124 interface > definitions all have ONBOOT=no. > > > > root@host> grep -i onboot ifcfg* | grep -v bak > > ifcfg-bond0:ONBOOT=yes > > ifcfg-bond0.108:ONBOOT=yes > > ifcfg-bond0.124:ONBOOT=no > > ifcfg-bond0.192:ONBOOT=no > > ifcfg-dev_office:ONBOOT=no > > ifcfg-eth0:ONBOOT=yes > > ifcfg-eth1:ONBOOT=yes > > ifcfg-eth2:ONBOOT=no > > ifcfg-eth3:ONBOOT=no > > ifcfg-lo:ONBOOT=yes > > ifcfg-ovirtmgmt:ONBOOT=yes > > ifcfg-uatdev_ben:ONBOOT=no > > > > The persistence configuration files are where they should be (I think): > > > > root@host> ls -l /var/lib/vdsm/persistence/netconf/nets/ > > total 12 > > -rw-r--r-- 1 root root 121 Aug 24 22:44 dev_office > > -rw-r--r-- 1 root root 173 Aug 24 22:44 ovirtmgmt > > -rw-r--r-- 1 root root 121 Aug 24 22:44 uatdev_ben > > > > If I were to do a “service network restart” on the node, the uatdev_ben, > dev_office, bond0.124 & bond0.192 are removed and then not restored as the > “ONBOOT=no”. I assumed that vdsmd would re-create the dev_office and > uatdev_ben interfaces so restarted vdsmd but they were not restored. I tried > a “vdsm-tool restore-nets” to see if that would restore the interfaces but no > joy. > > > > Am I missing something? Is there another method I should use to recover the > missing interfaces? Should the ifcfg files all be configured with > “ONBOOT=yes” just in case someone does run a “service network restart”? > > > > My oVirt nodes are CentOS 6.5, I’m not using the node iso. > > > > Many thanks in advance for any assistance. > > > > Regards, > > > > Simon Barrett > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- > Michael Burman > RedHat Israel, RHEV-M QE Network Team > > Mobile: 054-5355725 > IRC: mburman > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- Thanks, Ido Barkan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues?
I'm running into a problem with my upgrades to oVirt 3.5.3 and wanted to check if the following is a known issue. I have multiple vlan tagged interfaces configured. The files are being generated as expected by vdsm. The vlan 108 interface below is used by the ovirtmgmt bridge. The uatdev_ben, bond0.192, dev_office, bond0.124 interface definitions all have ONBOOT=no. root@host grep -i onboot ifcfg* | grep -v bak ifcfg-bond0:ONBOOT=yes ifcfg-bond0.108:ONBOOT=yes ifcfg-bond0.124:ONBOOT=no ifcfg-bond0.192:ONBOOT=no ifcfg-dev_office:ONBOOT=no ifcfg-eth0:ONBOOT=yes ifcfg-eth1:ONBOOT=yes ifcfg-eth2:ONBOOT=no ifcfg-eth3:ONBOOT=no ifcfg-lo:ONBOOT=yes ifcfg-ovirtmgmt:ONBOOT=yes ifcfg-uatdev_ben:ONBOOT=no The persistence configuration files are where they should be (I think): root@host ls -l /var/lib/vdsm/persistence/netconf/nets/ total 12 -rw-r--r-- 1 root root 121 Aug 24 22:44 dev_office -rw-r--r-- 1 root root 173 Aug 24 22:44 ovirtmgmt -rw-r--r-- 1 root root 121 Aug 24 22:44 uatdev_ben If I were to do a service network restart on the node, the uatdev_ben, dev_office, bond0.124 bond0.192 are removed and then not restored as the ONBOOT=no. I assumed that vdsmd would re-create the dev_office and uatdev_ben interfaces so restarted vdsmd but they were not restored. I tried a vdsm-tool restore-nets to see if that would restore the interfaces but no joy. Am I missing something? Is there another method I should use to recover the missing interfaces? Should the ifcfg files all be configured with ONBOOT=yes just in case someone does run a service network restart? My oVirt nodes are CentOS 6.5, I'm not using the node iso. Many thanks in advance for any assistance. Regards, Simon Barrett ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt 3.5.3 and Network Unified Persistence issues?
I'm running into a problem with my upgrades to oVirt 3.5.3 and wanted to check if the following is a known issue. I have multiple vlan tagged interfaces configured. The files are being generated as expected by vdsm. The vlan 108 interface below is used by the ovirtmgmt bridge. The uatdev_ben, bond0.192, dev_office, bond0.124 interface definitions all have ONBOOT=no. root@host grep -i onboot ifcfg* | grep -v bak ifcfg-bond0:ONBOOT=yes ifcfg-bond0.108:ONBOOT=yes ifcfg-bond0.124:ONBOOT=no ifcfg-bond0.192:ONBOOT=no ifcfg-dev_office:ONBOOT=no ifcfg-eth0:ONBOOT=yes ifcfg-eth1:ONBOOT=yes ifcfg-eth2:ONBOOT=no ifcfg-eth3:ONBOOT=no ifcfg-lo:ONBOOT=yes ifcfg-ovirtmgmt:ONBOOT=yes ifcfg-uatdev_ben:ONBOOT=no The persistence configuration files are where they should be (I think): root@host ls -l /var/lib/vdsm/persistence/netconf/nets/ total 12 -rw-r--r-- 1 root root 121 Aug 24 22:44 dev_office -rw-r--r-- 1 root root 173 Aug 24 22:44 ovirtmgmt -rw-r--r-- 1 root root 121 Aug 24 22:44 uatdev_ben If I were to do a service network restart on the node, the uatdev_ben, dev_office, bond0.124 bond0.192 are removed and then not restored as the ONBOOT=no. I assumed that vdsmd would re-create the dev_office and uatdev_ben interfaces so restarted vdsmd but they were not restored. I tried a vdsm-tool restore-nets to see if that would restore the interfaces but no joy. Am I missing something? Is there another method I should use to recover the missing interfaces? Should the ifcfg files all be configured with ONBOOT=yes just in case someone does run a service network restart? My oVirt nodes are CentOS 6.5, I'm not using the node iso. Many thanks in advance for any assistance. Regards, Simon Barrett ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Dashboard - Page Not Found
I am running oVirt Engine Version: 3.5.3.1-1.el6 and get a Page Not Found error when I click on the Dashboards tab at the top right of the admin portal. The Reports server is setup and working fine and I can see Cluster Dashboard, Datacenter Dashboard, System Dashboard reports in Webadmin Dashboards when viewing them directly through the oVirt Engine reports web interface. I couldn't find any logs that would assist in diagnosing this and couldn't find any other solutions. Any suggestions as to how I fix this? Many thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] ovirt-engine admin GUI
Is there a way to configure the pause button to prompt with a confirmation dialog box in the same way that the shutdown button does (Are you sure you want to Shut down the following Virtual Machines?) . VM's with large amounts of memory in use take a while to pause so could be out of action for a while if pause was clicked by mistake. I looked through the engine-config options but couldn't see anything. Thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt-engine admin GUI
Thanks. I submitted this: https://bugzilla.redhat.com/show_bug.cgi?id=1148034 -Original Message- From: Eli Mesika [mailto:emes...@redhat.com] Sent: 30 September 2014 15:31 To: Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] ovirt-engine admin GUI - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Tuesday, September 30, 2014 3:37:37 PM Subject: [ovirt-users] ovirt-engine admin GUI Is there a way to configure the “pause” button to prompt with a confirmation dialog box in the same way that the “shutdown” button does (Are you sure you want to Shut down the following Virtual Machines?) . VM’s with large amounts of memory in use take a while to pause so could be out of action for a while if pause was clicked by mistake. I looked through the engine-config options but couldn’t see anything. Seems like it is not supported in 3.5 , you can open a RFE on oVirt https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt Thanks, Simon ___ 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] oVirt - Node install on CentOS
One thing I do have to tweak is the group on /var/run/sanlock/sanlock.sock. By
default, when I reboot the owner/group/perms are this:
srw-rw 1 sanlock root 0 Jun 13 09:08 sanlock.sock
vdsm then has problems accessing sanlock.sock and I see errors like this in
engine.log:
2014-06-13 06:18:41,436 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStoragePoolVDSCommand]
(org.ovirt.thread.pool-6-thread-17) [12b48409] Command
org.ovirt.engine.core.vdsbroker.vdsbroke
r.CreateStoragePoolVDSCommand return value
StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=661, mMessage=Cannot
acquire host id: ('634aad80-503a-4e59-9738-15b6fb1bf10a', SanlockException(13,
'Sanlock lockspace add failure', 'Permission denied'))]]
If I chgrp qemu /var/run/sanlock/sanlock.sock then all works fine.
I know I can change the default group membership for sanlock in
/etc/libvirt/qemu-sanlock.conf but was wondering if this is something that the
vdsm install should take care of?
Thanks,
Simon
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Joop
Sent: 13 June 2014 11:54
Cc: users@ovirt.org
Subject: Re: [ovirt-users] oVirt - Node install on CentOS
Sven Kieske wrote:
+1 from me, this should work without manual tweaking (except for live
snapshots).
Am 09.06.2014 20:32, schrieb Joop:
If you install a minimal Centos-6.5 and add the ovirt repository and
then add the host using the webui of engine then it will install all
needed packages (vdsm/libvirt/kvm) and you're done. You can then replace
the standard qemu with the one that will do live snapshots. Depending on
where you're storage is located you shouldn't have to tinker with
memberships etc.
Looking at this again I would like the webui install process to add the repo
too :-)
If engine-setup is up to date it could know the location of the ovirt-repo.rpm
and install it automatically. There is probably a very good reason why it
doesn't do this since I can't imagine I'm the first one to think about this.
Joop
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] oVirt - Node install on CentOS
Could anyone please confirm the correct process to run oVirt node on a standard CentOS install, rather than using the node iso? I'm currently doing the following: - Install CentOS 6.5 - Install qemu-kvm-rhev rpm's to resolve live snapshot issues on the CentOS supplied rpm's - Yum install vdsm ovirt-node-plugin-vdsm vdsm-reg o I have to remove noexec from /tmp or the config fails - I then add the node from the ovirt-engine gui After resolving some problems with group memberships and vdsm requiring sudo access, all is working. Live snapshots and storage migration are OK (tested NFS and Gluster as well). I couldn't really find any docs on how to do this so I just wanted to confirm if what I am doing makes sense. I also don't have the text configuration interface that I would normally get on the oVirt node iso. Can I install this and use it on a non node iso install? Many thanks for any assistance. Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Running oVirt node on existing OS installation
http://www.ovirt.org/Quick_Start_Guide#Install_Fedora_Host The above doc says In addition to hypervisor hosts, you can also reconfigure servers which are running Fedora to be used as virtual machine hosts. It then has a line to install the repos: yum localinstall http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm but then jumps to iptables configuration. Am I missing something? Can anyone give me any pointers on the steps I need to do (after the intial ovirt-release34.rpm yum install) to install and configure ovirt-node on a CentOS or Fedora host? Thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained. Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot? Many thanks, Simon Hi Simon, it actually sounds like a bug to me, as node are supposed to support gluster. Ryan / Fabian- thoughts? Hey, I vaguely remember that we were seeing a bug like this some time ago. We fixed /var/lib/glusterd to be writable (using tmpfs), but it can actually be that we need to persist those contents. But Simon, can you give details which configuration files are missing and why glusterd is not starting? Is glusterd starting? I'm getting the impression that it's starting, but that it has no configuration. As far as I know, Gluster keeps most of the configuration on the brick itself, but it finds brick information in /var/lib/glusterd. The last patch simply opened the firewall, and it's entirely possible that we need to persist this. It may be a good idea to just persist the entire directory from the get-go, unless we want to try to have a thread watching /var/lib/glusterd for relevant files, but then we're stuck trying to keep up with what's happening with gluster itself... Can we Thanks fabian Either way I suggest you take a look in the below link- http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Per sisting_changes Let s know how it works. Doron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained. Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot? Many thanks, Simon Hi Simon, it actually sounds like a bug to me, as node are supposed to support gluster. Ryan / Fabian- thoughts? Hey, I vaguely remember that we were seeing a bug like this some time ago. We fixed /var/lib/glusterd to be writable (using tmpfs), but it can actually be that we need to persist those contents. But Simon, can you give details which configuration files are missing and why glusterd is not starting? Is glusterd starting? I'm getting the impression that it's starting, but that it has no configuration. As far as I know, Gluster keeps most of the configuration on the brick itself, but it finds brick information in /var/lib/glusterd. The last patch simply opened the firewall, and it's entirely possible that we need to persist this. It may be a good idea to just persist the entire directory from the get-go, unless we want to try to have a thread watching /var/lib/glusterd for relevant files, but then we're stuck trying to keep up
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
I just wasn't sure if I was missing something in the configuration to enable this. I'll stick with the workarounds I have for now and see how it goes. Thanks again. Simon -Original Message- From: Fabian Deutsch [mailto:fdeut...@redhat.com] Sent: 28 May 2014 15:20 To: Simon Barrett Cc: Ryan Barry; Doron Fediuck; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett: I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Hey Simon, I was also investigating both the steps you did. And was also about to recommend them :) They are more a workaround. We basically need some patches to change the defaults on Node, to let gluster work out of the box. This would include persisting the correct paths and enabling glusterd if enabled. - fabian Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Persisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: users@ovirt.org Sent: Friday, May 23, 2014 11:29:39 AM Subject: [ovirt-users] Persisting glusterfs configs on an oVirt node I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained. Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot? Many thanks, Simon Hi Simon
Re: [ovirt-users] Persisting glusterfs configs on an oVirt node
Will do. Thanks -Original Message- From: Doron Fediuck [mailto:dfedi...@redhat.com] Sent: 28 May 2014 16:17 To: Simon Barrett Cc: Fabian Deutsch; Ryan Barry; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node - Original Message - From: Simon Barrett simon.barr...@tradingscreen.com To: Fabian Deutsch fdeut...@redhat.com Cc: Ryan Barry rba...@redhat.com, Doron Fediuck dfedi...@redhat.com, users@ovirt.org Sent: Wednesday, May 28, 2014 5:22:17 PM Subject: RE: [ovirt-users] Persisting glusterfs configs on an oVirt node I just wasn't sure if I was missing something in the configuration to enable this. I'll stick with the workarounds I have for now and see how it goes. Thanks again. Simon -Original Message- From: Fabian Deutsch [mailto:fdeut...@redhat.com] Sent: 28 May 2014 15:20 To: Simon Barrett Cc: Ryan Barry; Doron Fediuck; users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Am Mittwoch, den 28.05.2014, 14:14 + schrieb Simon Barrett: I did a persist /var/lib/glusterd and things are looking better. The gluster config is now still in place after a reboot. As a workaround to getting glusterd running on boot, I added service glusterd start to /etc/rc.local and ran persist /etc/rc.local. It appears to be working but feels like a bit of a hack. Does anyone have any other suggestions as to the correct way to do this? Hey Simon, I was also investigating both the steps you did. And was also about to recommend them :) They are more a workaround. We basically need some patches to change the defaults on Node, to let gluster work out of the box. This would include persisting the correct paths and enabling glusterd if enabled. - fabian Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 28 May 2014 14:12 To: Ryan Barry; Fabian Deutsch; Doron Fediuck Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node Thanks for the replies. I cannot get glusterd to start on boot and I lose all gluster config every reboot. The following shows what I did on the node to start glusterd, create a volume etc, followed by the state of the node after a reboot. [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# service glusterd start Starting glusterd:[ OK ] gluster volume create vmstore 10.22.8.46:/data/glusterfs/vmstore volume create: vmstore: success: please start the volume to access data gluster vol start vmstore volume start: vmstore: success gluster vol info Volume Name: vmstore Type: Distribute Volume ID: 5bd01043-1352-4014-88ca-e632e264d088 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.22.8.46:/data/glusterfs/vmstore [root@ovirt_node]# ls -1 /var/lib/glusterd/vols/vmstore/ bricks node_state.info trusted-vmstore-fuse.vol cksum rbstate vmstore.10.22.8.46.data-glusterfs-vmstore.vol info run vmstore-fuse.vol [root@ovirt_node]# grep gluster /etc/rwtab.d/* /etc/rwtab.d/ovirt:files /var/lib/glusterd [root@ovirt_node]# chkconfig glusterd on [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:on3:on4:on5:on6:off I then reboot the node and see the following: [root@ovirt_node]# service glusterd status glusterd is stopped [root@ovirt_node]# chkconfig --list glusterd glusterd0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@ovirt_node]# ls -l /var/lib/glusterd/vols/ total 0 No more gluster volume configuration files. I've taken a look through http://www.ovirt.org/Node_Troubleshooting#Making_changes_last_.2F_Pe rsisting_changes but I'm unsure what needs to be done to persist this configuration. To get glusterd to start on boot, do I need to manually persist /etc/rc* files? I see files /var/lib/glusterd mentioned in /etc/rwtab.d/ovirt. Is this a list of the files/dirs that should be persisted automatically? If so, is it recursive and should it include everything in /var/lib/glusterd/vols? TIA for any help with this. Simon -Original Message- From: Ryan Barry [mailto:rba...@redhat.com] Sent: 27 May 2014 14:01 To: Fabian Deutsch; Doron Fediuck; Simon Barrett Cc: users@ovirt.org Subject: Re: [ovirt-users] Persisting glusterfs configs on an oVirt node On 05/26/2014 04:14 AM, Fabian Deutsch wrote: Am Sonntag, den 25.05.2014, 08:18 -0400 schrieb Doron Fediuck: - Original
[ovirt-users] Persisting glusterfs configs on an oVirt node
I am working through the setup of oVirt node for a 3.4.1 deployment. I setup some glusterfs volumes/bricks on oVirt Node Hypervisor release 3.0.4 (1.0.201401291204.el6) and created a storage domain. All was working OK until I rebooted the node and found that the glusterfs configuration had not been retained. Is there something I should be doing to persist any glusterfs configuration so it survives a node reboot? Many thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] selinux on oVirt Node
I set SELINUX=disabled in /etc/selinux/config and ran a persist /etc/selinux/config. After the node reboots, the file has the correct SELINUX=disabled line but I see that selinux is still enabled: # grep ^SELINUX= /etc/selinux/config SELINUX=disabled # getenforce Enforcing # cat /selinux/enforce 1 It's like the bind mounts for the files in config happen after selinux is setup. Is there something else I should be doing to make a change to selinux survive a node reboot? Many thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] selinux on oVirt Node
I added enforcing=0 to my pxe menu and re-installed the node. All looks better now. # sestatus SELinux status: enabled SELinuxfs mount:/selinux Current mode: permissive Mode from config file: disabled Policy version: 24 Policy from config file:targeted # cat /selinux/enforce 0 Thanks for the information. Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Sven Kieske Sent: 23 May 2014 09:45 To: users@ovirt.org Subject: Re: [ovirt-users] selinux on oVirt Node afaik you need to disable selinux by passing the relevant parameter direct via kernel boot options. search the ML or the net if you need the exact command line. HTH Am 23.05.2014 10:36, schrieb Simon Barrett: I set SELINUX=disabled in /etc/selinux/config and ran a persist /etc/selinux/config. After the node reboots, the file has the correct SELINUX=disabled line but I see that selinux is still enabled: # grep ^SELINUX= /etc/selinux/config SELINUX=disabled # getenforce Enforcing # cat /selinux/enforce 1 It's like the bind mounts for the files in config happen after selinux is setup. Is there something else I should be doing to make a change to selinux survive a node reboot? Many thanks, Simon -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ 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: [Users] Logical Network VLAN Tagging and DataCenters
Looks very much like what I am seeing. Many thanks for the info. I'll test when 3.4.1 is available. -Original Message- From: Lior Vernia [mailto:lver...@redhat.com] Sent: 02 April 2014 07:58 To: Simon Barrett Cc: users@ovirt.org Subject: Re: [Users] Logical Network VLAN Tagging and DataCenters Hi Simon, I think what you're experiencing is this: https://bugzilla.redhat.com/show_bug.cgi?id=1070835 So this is not by design, there shouldn't be any issue with having the same VLAN ID defined across multiple DCs. Should be fine when oVirt 3.4.1 is released, or using nightly build. Yours, Lior. On 01/04/14 13:26, Simon Barrett wrote: Is it possible/supported to have the same VLAN ID defined across multiple datacenters logical networks? I am seeing a situation where if I have two Datacenters, both with a logical network that have the same vlan tag. E.G. DC = London, Logical network = prod, VLAN = 123 DC = Paris, Logical network = prod, VLAN = 123 If I edit one of the VM's running in the London datacenter, the VM NIC shows up as empty even though if I click on the VM and go to the Network Interfaces tab at the bottom of the screen it lists up the prod network under Network Name. All works OK for VM's that are assigned a logical network that is only defined once (i.e. has not been added to both datacenters). This configuration is on oVirt Engine 3.3.2-1.el6. I am planning on moving to 3.4 very soon so will test out again on that version. Thanks, Simon ___ 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] Logical Network VLAN Tagging and DataCenters
Is it possible/supported to have the same VLAN ID defined across multiple datacenters logical networks? I am seeing a situation where if I have two Datacenters, both with a logical network that have the same vlan tag. E.G. DC = London, Logical network = prod, VLAN = 123 DC = Paris, Logical network = prod, VLAN = 123 If I edit one of the VM's running in the London datacenter, the VM NIC shows up as empty even though if I click on the VM and go to the Network Interfaces tab at the bottom of the screen it lists up the prod network under Network Name. All works OK for VM's that are assigned a logical network that is only defined once (i.e. has not been added to both datacenters). This configuration is on oVirt Engine 3.3.2-1.el6. I am planning on moving to 3.4 very soon so will test out again on that version. Thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] VM Status Unknown
Was this ever resolved? I have a similar situation where a node was reset while a VM was running on it. Now the VM is in an unknown state and I cannot stop/start etc. I also cannot put the node into maintenance mode as it thinks it still has running VM’s [oVirt shell (connected)]# list vms --query id=807593a5-8667-4265-a0ab-b3e37feb1fc1 --show-all | grep status status-state : unknown [oVirt shell (connected)]# action vm 807593a5-8667-4265-a0ab-b3e37feb1fc1 stop ERROR status: 409 reason: Conflict detail: Cannot stop VM. VM is not running. === [oVirt shell (connected)]# action host d3a555b1-b5dd-48d1-802c-03096bdf8b00 deactivate ERROR status: 409 reason: Conflict detail: Cannot switch Host to Maintenance mode. Host still has running VMs on it and is in Non Responsive state. === Thanks, From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Omer Frenkel Sent: 12 January 2014 08:47 To: Meital Bourvine Cc: users@ovirt.org Subject: Re: [Users] VM Status Unknown From: Meital Bourvine mbour...@redhat.commailto:mbour...@redhat.com To: Ryan Womer ryan.wo...@cytechservices.commailto:ryan.wo...@cytechservices.com Cc: users@ovirt.orgmailto:users@ovirt.org Sent: Friday, January 10, 2014 11:54:51 AM Subject: Re: [Users] VM Status Unknown Can you please provide vdsm.log (of both hosts) and engine.log? also, what version are you using? we had some bugs around this solved for 3.3 From: Ryan Womer ryan.wo...@cytechservices.commailto:ryan.wo...@cytechservices.com To: users@ovirt.orgmailto:users@ovirt.org Sent: Thursday, January 9, 2014 10:43:37 PM Subject: [Users] VM Status Unknown During a migration, the destination host lost connectivity to the san and crashed. Once the server came back up, 3 VMs that didn’t finish migrating have been stuck in status “Unknown.” Vdsclient doesn’t list any of the vms on either host. Qemu doesn’t have them listed as mounted on either host. Action vm start and stop result in “Status: 409”. The disks for all 3 VMs are listed as green in the WebAdmin. I’ve tried “action vm name start” “action vm name stop” “update vm name --status-state down” no joy. They remain in “unknown.” ___ Users mailing list Users@ovirt.orgmailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.orgmailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] VM Status Unknown
I tried that but it is the last node connected to the storage device and I get the following: Manual fence did not revoke the selected SPM (ln2-lvb-002.mgt) since the master storage domain was not active or could not use another host for the fence operation. I just wondered if there was a way to force VM and/or Host removal? Thanks, Simon From: Omer Frenkel [mailto:ofren...@redhat.com] Sent: 26 March 2014 09:10 To: Simon Barrett Cc: Meital Bourvine; users@ovirt.org Subject: Re: [Users] VM Status Unknown From: Simon Barrett simon.barr...@tradingscreen.commailto:simon.barr...@tradingscreen.com To: Omer Frenkel ofren...@redhat.commailto:ofren...@redhat.com, Meital Bourvine mbour...@redhat.commailto:mbour...@redhat.com Cc: users@ovirt.orgmailto:users@ovirt.org Sent: Wednesday, March 26, 2014 10:44:15 AM Subject: RE: [Users] VM Status Unknown Was this ever resolved? I have a similar situation where a node was reset while a VM was running on it. Now the VM is in an unknown state and I cannot stop/start etc. I also cannot put the node into maintenance mode as it thinks it still has running VM’s [oVirt shell (connected)]# list vms --query id=807593a5-8667-4265-a0ab-b3e37feb1fc1 --show-all | grep status status-state : unknown [oVirt shell (connected)]# action vm 807593a5-8667-4265-a0ab-b3e37feb1fc1 stop ERROR status: 409 reason: Conflict detail: Cannot stop VM. VM is not running. === [oVirt shell (connected)]# action host d3a555b1-b5dd-48d1-802c-03096bdf8b00 deactivate ERROR status: 409 reason: Conflict detail: Cannot switch Host to Maintenance mode. Host still has running VMs on it and is in Non Responsive state. === Thanks, your host in non-responsive, means the engine cant verify its status and the vms status on it. if you dont have power management (i guess you dont) and you absolutely sure the vms are really not running there anymore you can mark the host as been rebooted, and clear the its state. in the UI - right click the host and choose confirm rebooted in rest i think its called manual fence From: users-boun...@ovirt.orgmailto:users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Omer Frenkel Sent: 12 January 2014 08:47 To: Meital Bourvine Cc: users@ovirt.orgmailto:users@ovirt.org Subject: Re: [Users] VM Status Unknown From: Meital Bourvine mbour...@redhat.commailto:mbour...@redhat.com To: Ryan Womer ryan.wo...@cytechservices.commailto:ryan.wo...@cytechservices.com Cc: users@ovirt.orgmailto:users@ovirt.org Sent: Friday, January 10, 2014 11:54:51 AM Subject: Re: [Users] VM Status Unknown Can you please provide vdsm.log (of both hosts) and engine.log? also, what version are you using? we had some bugs around this solved for 3.3 From: Ryan Womer ryan.wo...@cytechservices.commailto:ryan.wo...@cytechservices.com To: users@ovirt.orgmailto:users@ovirt.org Sent: Thursday, January 9, 2014 10:43:37 PM Subject: [Users] VM Status Unknown During a migration, the destination host lost connectivity to the san and crashed. Once the server came back up, 3 VMs that didn’t finish migrating have been stuck in status “Unknown.” Vdsclient doesn’t list any of the vms on either host. Qemu doesn’t have them listed as mounted on either host. Action vm start and stop result in “Status: 409”. The disks for all 3 VMs are listed as green in the WebAdmin. I’ve tried “action vm name start” “action vm name stop” “update vm name --status-state down” no joy. They remain in “unknown.” ___ Users mailing list Users@ovirt.orgmailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.orgmailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] el6 live snapshots and storage migration
Is there any current combination of el6 based Engine and Node iso that support live snapshots and storage migration? I tried oVirt Node - 3.0.4 - 1.0.2014012912 but had problems with VDSM compatibility (VDSM version (4.14) and cannot join cluster - cluster is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10].) I now see this mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 I did try upgrading Engine to 3.3.4-1.el6 but still see the same VDSM 4.14 problem. I also tried building the iso (as per http://www.ovirt.org/Node_Building) and could see that it was downloading the qemu-kvm-rhev (which I think is needed to enable the live snapshot functionality). However I got stuck adding the vdsm plugin as the iso was being built with the 3.4.0.57rhs versions of the glusterfs packages whereas the plugin was dependant on glusterfs 3.4.0-8. I already have a working Engine (3.3.2-1.el6) and Node (3.0.1 - 1.0.2.el6) test configuration but would very much like to be able to add the live snapshot functionality. Many thanks Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] edit-node problems
I'm trying to use edit-node to add the ovirt-node-plugin-vdsm plugin to the ovirt-node-iso-3.0.2-1.0.0.el6.iso that I downloaded from here: http://resources.ovirt.org/releases/node-base/stable/iso/ovirt-node-iso-3.0.2-1.0.0.el6.iso Whenever I run any edit-node commands against this iso I get the error below: # ./ovirt-node/tools/edit-node -dv --print-rpm-manifest /app/iso/ovirt-node-iso-3.0.2-1.0.0.el6.iso /app/iso/ovirt-node-iso-3.0.2-1.0.0.el6.iso Losetup add /dev/loop0 mapping to /app/iso/ovirt-node-iso-3.0.2-1.0.0.el6.iso Mounting /dev/loop0 at /var/tmp/edit-liveos-nEP1ae/tmp-IrE34t Losetup add /dev/loop1 mapping to /var/tmp/edit-liveos-nEP1ae/tmp-IrE34t/LiveOS/squashfs.img Mounting /dev/loop1 at /var/tmp/edit-liveos-nEP1ae/tmp-VOGtjF mount: block device /dev/loop1 is write-protected, mounting read-only Unmounting directory /var/tmp/edit-liveos-nEP1ae/tmp-VOGtjF Losetup remove /dev/loop1 Unmounting directory /var/tmp/edit-liveos-nEP1ae/tmp-IrE34t Losetup remove /dev/loop0 /usr/lib/python2.6/site-packages/imgcreate/errors.py:45: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 return unicode(self.message) Error editing LiveOS : Failed to copy base live image to /var/tmp/edit-liveos-nEP1ae/ex/ext3fs.img for modification: [Errno 5] Input/output error If I try the same with ovirt-node-iso-3.0.1-1.0.2.el6.iso (downloaded from the same location) all works as expected. I've tried this on CentOS 6.2 and 6.4, same results on both. Can anyone tell me where I am going wrong? Alternatively is there a newer node ISO that already has the ovirt-node-plugin-vdsm plugin installed? Thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] edit-node problems
Looks like I was downloading the wrong ISO. VDSM enabled versions already exist here: http://resources.ovirt.org/releases/3.3/iso/ From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 11 March 2014 13:26 To: 'users@ovirt.org' Subject: [Users] edit-node problems I'm trying to use edit-node to add the ovirt-node-plugin-vdsm plugin to the ovirt-node-iso-3.0.2-1.0.0.el6.iso that I downloaded from here: http://resources.ovirt.org/releases/node-base/stable/iso/ovirt-node-iso-3.0.2-1.0.0.el6.iso Whenever I run any edit-node commands against this iso I get the error below: # ./ovirt-node/tools/edit-node -dv --print-rpm-manifest /app/iso/ovirt-node-iso-3.0.2-1.0.0.el6.iso /app/iso/ovirt-node-iso-3.0.2-1.0.0.el6.iso Losetup add /dev/loop0 mapping to /app/iso/ovirt-node-iso-3.0.2-1.0.0.el6.iso Mounting /dev/loop0 at /var/tmp/edit-liveos-nEP1ae/tmp-IrE34t Losetup add /dev/loop1 mapping to /var/tmp/edit-liveos-nEP1ae/tmp-IrE34t/LiveOS/squashfs.img Mounting /dev/loop1 at /var/tmp/edit-liveos-nEP1ae/tmp-VOGtjF mount: block device /dev/loop1 is write-protected, mounting read-only Unmounting directory /var/tmp/edit-liveos-nEP1ae/tmp-VOGtjF Losetup remove /dev/loop1 Unmounting directory /var/tmp/edit-liveos-nEP1ae/tmp-IrE34t Losetup remove /dev/loop0 /usr/lib/python2.6/site-packages/imgcreate/errors.py:45: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 return unicode(self.message) Error editing LiveOS : Failed to copy base live image to /var/tmp/edit-liveos-nEP1ae/ex/ext3fs.img for modification: [Errno 5] Input/output error If I try the same with ovirt-node-iso-3.0.1-1.0.2.el6.iso (downloaded from the same location) all works as expected. I've tried this on CentOS 6.2 and 6.4, same results on both. Can anyone tell me where I am going wrong? Alternatively is there a newer node ISO that already has the ovirt-node-plugin-vdsm plugin installed? Thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Network profile lost after host edit
I built a new Engine Server on 3.3.2-1.el6, rebuilt my VM's and I no longer see the issue. All is now working as expected. Simon -Original Message- From: Simon Barrett Sent: 08 January 2014 08:50 To: Lior Vernia; Itamar Heim Cc: users@ovirt.org Subject: RE: [Users] Network profile lost after host edit To test this further I setup another 3.3.2-1.el6 ovirt-engine. I'm not seeing the same problem on the new engine. I'm going to try and move all configuration/VM's etc from the problem ovirt-engine install to the new one to see if the problem re-appears. I'll let you know how it goes. Simon -Original Message- From: Lior Vernia [mailto:lver...@redhat.com] Sent: 08 January 2014 06:02 To: Itamar Heim Cc: Simon Barrett; users@ovirt.org Subject: Re: [Users] Network profile lost after host edit On 07/01/14 23:16, Itamar Heim wrote: On 01/07/2014 08:59 AM, Lior Vernia wrote: Hi Simon, Thank you so much for tracking this down. I'm currently immersed in oVirt 3.4 feature stuff, but I just wanted to let you know I saw this and am planning to take care of it; I'll take a look in a week or two when things calm down. The bad news are, I suspect there will be no workaround other than upgrading to the next version that will include the fix (likely 3.3.3). is there an ovirt bug targeted to 3.3.3 tracking this? I'll open one as soon as I test the issue. Unless Simon would like to pick up the gauntlet and open one on bugzilla.redhat.com?... Yours, Lior. On 06/01/14 12:21, Simon Barrett wrote: I am now able to reproduce the problem where network profile definitions are lost on VM edit. - Create VM - From the Network Interfaces tab, click on New and assign the ovirtmgt profile to nic1 - Edit VM, from the nic1 drop down select another profile and click OK - Edit the same VM again and nic1 lists as Empty I upgraded to 3.3.2-1.el6 and still see the problem. As ever, any help is very much appreciated. Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 12 December 2013 21:53 To: Lior Vernia Cc: users@ovirt.org Subject: Re: [Users] Network profile lost after host edit Lior, I'm running 3.3.1. I think it may be related to how I created the VM's. Another VM created using the blank template works fine and the network config displays correctly when I click on edit. The problem VM's were created with a different template. I'll dig a bit further to see if I can narrow it down any further. I don't have to click show advanced to exhibit the problem. Thanks for the response Simon On 12 Dec 2013, at 16:44, Lior Vernia lver...@redhat.com wrote: Hi Simon, I apologize for the delay in my response. I've worked quite a bit on that part of the dialog since oVirt 3.3, and while it was quite buggy I haven't encountered this exact issue you're describing. It does remind me of one bug though; could it be that pressing the Show Advanced Options is what triggers the strange behavior? What version of oVirt engine are you running? Both 3.3.1 and 3.3.2 should be quite stable as far as this dialog is concerned, so upgrading might be a good idea. As for workarounds, it sounds like a GUI issue so I don't think there's anything you can do apart from upgrading the engine. Yours, Lior. On 11/12/13 13:40, Simon Barrett wrote: I have a problem where VM network profiles are lost when editing a host. E.G. * VM is running fine on the correct network. Network Interfaces tab shows nic1 and Network Name shows the correct network profile. * I shutdown the VM then right click and Edit. * The General settings for the node shows nic1 Empty. If I then edit config, something like increasing memory or changing CPU cores then click on OK, the VM configuration is saved without a network profile. * When I boot the VM I cannot connect to it. * I then have to edit the node again configure back in the correct network profile. Does anyone know if this is a known issue? If not, any suggestions as to how I correct this so that the original network profile definition is retained after an edit? Many thanks, Simon ___ 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Network profile lost after host edit
To test this further I setup another 3.3.2-1.el6 ovirt-engine. I'm not seeing the same problem on the new engine. I'm going to try and move all configuration/VM's etc from the problem ovirt-engine install to the new one to see if the problem re-appears. I'll let you know how it goes. Simon -Original Message- From: Lior Vernia [mailto:lver...@redhat.com] Sent: 08 January 2014 06:02 To: Itamar Heim Cc: Simon Barrett; users@ovirt.org Subject: Re: [Users] Network profile lost after host edit On 07/01/14 23:16, Itamar Heim wrote: On 01/07/2014 08:59 AM, Lior Vernia wrote: Hi Simon, Thank you so much for tracking this down. I'm currently immersed in oVirt 3.4 feature stuff, but I just wanted to let you know I saw this and am planning to take care of it; I'll take a look in a week or two when things calm down. The bad news are, I suspect there will be no workaround other than upgrading to the next version that will include the fix (likely 3.3.3). is there an ovirt bug targeted to 3.3.3 tracking this? I'll open one as soon as I test the issue. Unless Simon would like to pick up the gauntlet and open one on bugzilla.redhat.com?... Yours, Lior. On 06/01/14 12:21, Simon Barrett wrote: I am now able to reproduce the problem where network profile definitions are lost on VM edit. - Create VM - From the Network Interfaces tab, click on New and assign the ovirtmgt profile to nic1 - Edit VM, from the nic1 drop down select another profile and click OK - Edit the same VM again and nic1 lists as Empty I upgraded to 3.3.2-1.el6 and still see the problem. As ever, any help is very much appreciated. Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 12 December 2013 21:53 To: Lior Vernia Cc: users@ovirt.org Subject: Re: [Users] Network profile lost after host edit Lior, I'm running 3.3.1. I think it may be related to how I created the VM's. Another VM created using the blank template works fine and the network config displays correctly when I click on edit. The problem VM's were created with a different template. I'll dig a bit further to see if I can narrow it down any further. I don't have to click show advanced to exhibit the problem. Thanks for the response Simon On 12 Dec 2013, at 16:44, Lior Vernia lver...@redhat.com wrote: Hi Simon, I apologize for the delay in my response. I've worked quite a bit on that part of the dialog since oVirt 3.3, and while it was quite buggy I haven't encountered this exact issue you're describing. It does remind me of one bug though; could it be that pressing the Show Advanced Options is what triggers the strange behavior? What version of oVirt engine are you running? Both 3.3.1 and 3.3.2 should be quite stable as far as this dialog is concerned, so upgrading might be a good idea. As for workarounds, it sounds like a GUI issue so I don't think there's anything you can do apart from upgrading the engine. Yours, Lior. On 11/12/13 13:40, Simon Barrett wrote: I have a problem where VM network profiles are lost when editing a host. E.G. * VM is running fine on the correct network. Network Interfaces tab shows nic1 and Network Name shows the correct network profile. * I shutdown the VM then right click and Edit. * The General settings for the node shows nic1 Empty. If I then edit config, something like increasing memory or changing CPU cores then click on OK, the VM configuration is saved without a network profile. * When I boot the VM I cannot connect to it. * I then have to edit the node again configure back in the correct network profile. Does anyone know if this is a known issue? If not, any suggestions as to how I correct this so that the original network profile definition is retained after an edit? Many thanks, Simon ___ 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Network profile lost after host edit
I am now able to reproduce the problem where network profile definitions are lost on VM edit. - Create VM - From the Network Interfaces tab, click on New and assign the ovirtmgt profile to nic1 - Edit VM, from the nic1 drop down select another profile and click OK - Edit the same VM again and nic1 lists as Empty I upgraded to 3.3.2-1.el6 and still see the problem. As ever, any help is very much appreciated. Thanks, Simon -Original Message- From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of Simon Barrett Sent: 12 December 2013 21:53 To: Lior Vernia Cc: users@ovirt.org Subject: Re: [Users] Network profile lost after host edit Lior, I'm running 3.3.1. I think it may be related to how I created the VM's. Another VM created using the blank template works fine and the network config displays correctly when I click on edit. The problem VM's were created with a different template. I'll dig a bit further to see if I can narrow it down any further. I don't have to click show advanced to exhibit the problem. Thanks for the response Simon On 12 Dec 2013, at 16:44, Lior Vernia lver...@redhat.com wrote: Hi Simon, I apologize for the delay in my response. I've worked quite a bit on that part of the dialog since oVirt 3.3, and while it was quite buggy I haven't encountered this exact issue you're describing. It does remind me of one bug though; could it be that pressing the Show Advanced Options is what triggers the strange behavior? What version of oVirt engine are you running? Both 3.3.1 and 3.3.2 should be quite stable as far as this dialog is concerned, so upgrading might be a good idea. As for workarounds, it sounds like a GUI issue so I don't think there's anything you can do apart from upgrading the engine. Yours, Lior. On 11/12/13 13:40, Simon Barrett wrote: I have a problem where VM network profiles are lost when editing a host. E.G. * VM is running fine on the correct network. Network Interfaces tab shows nic1 and Network Name shows the correct network profile. * I shutdown the VM then right click and Edit. * The General settings for the node shows nic1 Empty. If I then edit config, something like increasing memory or changing CPU cores then click on OK, the VM configuration is saved without a network profile. * When I boot the VM I cannot connect to it. * I then have to edit the node again configure back in the correct network profile. Does anyone know if this is a known issue? If not, any suggestions as to how I correct this so that the original network profile definition is retained after an edit? Many thanks, Simon ___ 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
Re: [Users] oVirt Node ISO
I would rather stick with the el6 iso if possible for the reasons mentioned in the previous email. However, if there are no plans to continue with the production of el6 ovirt-node iso's I'll switch to fc19. So I suppose the question still stands, are there plans to release an el6 iso for oVirt Node 3.0.3-1-1? Many thanks. -Original Message- From: Itamar Heim [mailto:ih...@redhat.com] Sent: 09 December 2013 19:47 To: Bob Doolittle; Simon Barrett; users@ovirt.org; Fabian Deutsch Subject: Re: [Users] oVirt Node ISO On 12/09/2013 08:58 PM, Bob Doolittle wrote: Hi, The point of Node is that it should be like an appliance. You should not care what is under the covers. You just use it as a back-end appliance that talks to oVirt. So it should not matter what version of OS it runs, right? If you start doing things that are particular to the OS, two major disadvantages come to mind: 1. You will start bloating the system by adding new dependencies. This dilutes the value of a minimal node that minimizes management requirements 2. You will diverge from what's been tested by the oVirt QA team. This increases the risk of your deployment. Since Node is supposed to be an appliance, I would prefer that the oVirt team focus their energies on making it as small and robust as possible, rather than putting their energy into multiple OS versions of Node. not sure i agree. there are differences between the fedora and .el6 distro's, especially around things like testing of backward compatibility for live migration between different versions (for a clean upgrade path). the fedora one covers newer features / fast moving the .el6 one is more robust / tested. so depends on what you are trying to do. -Bob On 12/09/2013 06:31 AM, Simon Barrett wrote: Are there plans to release an el6 iso for oVirt Node 3.0.3-1-1? I only see the fc19 version currently: Index of /releases/3.3/iso [ICO] NameLast modified SizeDescription [DIR] Parent Directory- [ ] ovirt-node-iso-3.0.1-1.0.1.vdsm.el6.iso 28-Aug-2013 04:56 219M [ ] ovirt-node-iso-3.0.1-1.0.1.vdsm.fc19.iso 28-Aug-2013 04:56 250M [ ] ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso 11-Sep-2013 05:18 219M [ ] ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso 11-Sep-2013 05:19 250M [ ] ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso 27-Nov-2013 07:54 252M Many Thanks, Simon ___ 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
Re: [Users] oVirt Node ISO
Thanks Fabian. I'll wait for the el6 version. -Original Message- From: Fabian Deutsch [mailto:fabi...@redhat.com] Sent: 11 December 2013 11:14 To: Simon Barrett Cc: Itamar Heim; Bob Doolittle; users@ovirt.org; Fabian Deutsch Subject: Re: [Users] oVirt Node ISO Am Mittwoch, den 11.12.2013, 10:32 + schrieb Simon Barrett: I would rather stick with the el6 iso if possible for the reasons mentioned in the previous email. However, if there are no plans to continue with the production of el6 ovirt-node iso's I'll switch to fc19. So I suppose the question still stands, are there plans to release an el6 iso for oVirt Node 3.0.3-1-1? Hey Simon, yes - it is still planned to do el6/CentOS based ovirt-node-iso releases. Contributions and testing is always welcome. - fabian Many thanks. -Original Message- From: Itamar Heim [mailto:ih...@redhat.com] Sent: 09 December 2013 19:47 To: Bob Doolittle; Simon Barrett; users@ovirt.org; Fabian Deutsch Subject: Re: [Users] oVirt Node ISO On 12/09/2013 08:58 PM, Bob Doolittle wrote: Hi, The point of Node is that it should be like an appliance. You should not care what is under the covers. You just use it as a back-end appliance that talks to oVirt. So it should not matter what version of OS it runs, right? If you start doing things that are particular to the OS, two major disadvantages come to mind: 1. You will start bloating the system by adding new dependencies. This dilutes the value of a minimal node that minimizes management requirements 2. You will diverge from what's been tested by the oVirt QA team. This increases the risk of your deployment. Since Node is supposed to be an appliance, I would prefer that the oVirt team focus their energies on making it as small and robust as possible, rather than putting their energy into multiple OS versions of Node. not sure i agree. there are differences between the fedora and .el6 distro's, especially around things like testing of backward compatibility for live migration between different versions (for a clean upgrade path). the fedora one covers newer features / fast moving the .el6 one is more robust / tested. so depends on what you are trying to do. -Bob On 12/09/2013 06:31 AM, Simon Barrett wrote: Are there plans to release an el6 iso for oVirt Node 3.0.3-1-1? I only see the fc19 version currently: Index of /releases/3.3/iso [ICO] NameLast modified SizeDescription [DIR] Parent Directory- [ ] ovirt-node-iso-3.0.1-1.0.1.vdsm.el6.iso 28-Aug-2013 04:56 219M [ ] ovirt-node-iso-3.0.1-1.0.1.vdsm.fc19.iso 28-Aug-2013 04:56 250M [ ] ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso 11-Sep-2013 05:18 219M [ ] ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso 11-Sep-2013 05:19 250M [ ] ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso 27-Nov-2013 07:54 252M Many Thanks, Simon ___ 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
[Users] oVirt Node ISO
Are there plans to release an el6 iso for oVirt Node 3.0.3-1-1? I only see the fc19 version currently: Index of /releases/3.3/iso [ICO] NameLast modified SizeDescription [DIR] Parent Directory - [ ]ovirt-node-iso-3.0.1-1.0.1.vdsm.el6.iso 28-Aug-2013 04:56 219M [ ]ovirt-node-iso-3.0.1-1.0.1.vdsm.fc19.iso 28-Aug-2013 04:56 250M [ ]ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso 11-Sep-2013 05:18 219M [ ]ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso 11-Sep-2013 05:19 250M [ ]ovirt-node-iso-3.0.3-1.1.vdsm.fc19.iso 27-Nov-2013 07:54 252M Many Thanks, Simon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
