Re: [Users] Wondering about updating ovirt from 3.0 to 3.1
See the migration instructions at the bottom of the relese notes. Basically you shut down all of your VMs, export them to your export domain. Now all you have to do is preserve that export domain storage. Everything else should be blown away and rebuilt as a completely new install. Then you import that storage domain you saved and restore the VM's. It worked just fine for me. -Jacob From: users-boun...@ovirt.org [users-boun...@ovirt.org] on behalf of Gavin Spurgeon [gspurg...@dageek.co.uk] Sent: Wednesday, August 08, 2012 11:35 AM To: users@ovirt.org Cc: Dale Macartney Subject: Re: [Users] Wondering about updating ovirt from 3.0 to 3.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, I know I am not the 1st to ask, and I know I will not be the last I have oVirt3.0 on F16, The Release Notes for 3.1 give a guide on how to upgrade oVirt to 3.1 via a Fedora Upgrade... Can I do the same thing via a Clean Install of F17 (I do not like Upgrades of OS's) ? Or is there a documented DR procedure assuming the host was backed up and a new Host/OS had to be used to get oVirt back on-line ? Basically, What do I need to backup to then bring down the F16/oVirt3.0 Box and replace it with a F17/oVirt3.1 Box ? Is this Documented yet ? - -- Gavin Spurgeon. AKA Da Geek - -- "The happiest of people don't necessarily have the best of everything, they just make the most of everything that comes along their way.." -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAihzAACgkQvp6arS3vDiqN0wCfblVQ2oS4hY0SCQ1xRID8MBxi 9LUAoLEt8MFkDoXG+jzynE5p2b4XtjVS =Or+C -END PGP SIGNATURE- -- This message was scanned by DaGeek Spam Filter and is believed to be clean. ___ 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] share nfs export volume
Anyone know if I can share an nfs export volume between two discrete ovirt installations? I'm migrating VMs from a 3.0 install to a 3.1 install and wondered if I could have the same export domain connected both that the same time? Just curious. -Jacob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Cannot connect to guest with spice console; SSL validate error
I don't know if this is the same issue but for some reason my CA cert for spice was a blank file. I copied another one from the vdsm directory (mostly guessing) and it worked. cp /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-spice/ca-cert.pem From: users-boun...@ovirt.org [users-boun...@ovirt.org] on behalf of Karli Sjöberg [karli.sjob...@slu.se] Sent: Tuesday, August 07, 2012 10:10 AM To: users@oVirt.org Subject: [Users] Cannot connect to guest with spice console;SSL validate error Hi, I seems very difficult to get this working. I have a Fedora 17 client, installed spice-xpi and tried to access console from User Portal but console never shows up. engine.log prints: 2012-08-07 15:56:18,738 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--0.0.0.0-8009-13) [2a8bc3f4] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 2ad22641-7aeb-4d1b-999e-2c0563376641 Type: VM 2012-08-07 15:56:18,771 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--0.0.0.0-8009-13) [2a8bc3f4] START, SetVmTicketVDSCommand(vdsId = acfc94c0-d7e1-11e1-b35e-b38016c320bb, vmId=2ad22641-7aeb-4d1b-999e-2c0563376641, ticket=NvbcLbRR/7Vx, validTime=120,m userName=karli, userId=de526322-d046-4a06-911e-546e7159556e), log id: 3d61fa94 2012-08-07 15:56:18,816 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--0.0.0.0-8009-13) [2a8bc3f4] FINISH, SetVmTicketVDSCommand, log id: 3d61fa94 >From the F17 client with "ovirt-shell" installed from ovirt-3.1 repo: $ console milli (window briefly flashes and disappeares again) warning: could not fetch host certificate info cause used backend/sdk does not support it. warning: host identity will not be validated. And have also used "spicec" directly from F17 client: # spicec -h cirrus2-1.slu.se -p 5900 -s 5901 -w v36BkUumraDG (The first ticket had by this time expired, so this is a new one) (flashes) Error: failed to connect w/SSL, ssl_error error:0001:lib(0):func(0):reason(1) 140059992839392:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:s3_clnt.c:1063: Warning: SSL Error: # spicec -h cirrus2-1.slu.se -p 5900 -w v36BkUumraDG (flashes) Warning: connect error 5 - need secured connection # rpm -qa | egrep '(ovirt|vdsm)' ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch vdsm-cli-4.10.0-5.fc17.noarch ovirt-engine-config-3.1.0-1.fc17.noarch ovirt-engine-userportal-3.1.0-1.fc17.noarch vdsm-4.10.0-5.fc17.x86_64 ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch ovirt-engine-sdk-3.1.0.4-1.fc17.noarch ovirt-engine-restapi-3.1.0-1.fc17.noarch ovirt-engine-backend-3.1.0-1.fc17.noarch ovirt-engine-3.1.0-1.fc17.noarch ovirt-engine-webadmin-portal-3.1.0-1.fc17.noarch ovirt-engine-notification-service-3.1.0-1.fc17.noarch ovirt-engine-dbscripts-3.1.0-1.fc17.noarch vdsm-python-4.10.0-5.fc17.x86_64 ovirt-engine-genericapi-3.1.0-1.fc17.noarch ovirt-engine-tools-common-3.1.0-1.fc17.noarch ovirt-engine-cli-3.1.0.6-1.fc17.noarch vdsm-xmlrpc-4.10.0-5.fc17.noarch vdsm-bootstrap-4.10.0-5.fc17.noarch ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch ovirt-engine-setup-3.1.0-1.fc17.noarch The engine is installed with SSL as enabled by default, the hosts too. VDSM and libvirt are all active and validate fine towards the engine; have status "UP" and so on, but can't get SPICE console working. VNC works of course, but SPICE would be much cooler:) How do I get console working with SPICE? Best Regards Karli Sjöberg ___ 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] sanlock issues
Solved with a hack. oVirt Node Hypervisor release 2.5.0 (2.0.fc17) Couldn't start a VM because sanlock wasn't running. Sanlock wasn't running because wdmd wasn't running. wdmd was running because softdog kernel module wasn't loaded. As I didn't know of another way of making the change persistent I edited /config/usr/sbin/ifup and added "/sbin/modprobe softdog" to the top of the script. I really think it would be a good idea for the oVirt Node team to add in some persistent script files that are run at various points in the boot process so that people like me can add in hacks where needed to make it work. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] sanlock issues
# grep -v ^# /etc/libvirt/qemu-sanlock.conf auto_disk_leases=0 require_lease_for_disks=0 I did try systemd-vdsmd reconfigure. From: Mark Wu [wu...@linux.vnet.ibm.com] What does "grep -v ^# /etc/libvirt/qemu-sanlock.conf" say? Have you tried `/usr/lib/systemd/systemd-vdsmd reconfigure` ? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] 3.1 network setup
Yes, I can see the VLAN tags both under the "Network Interfaces" tab and when I click on "Setup Host Networks" I can see both the VLANs as if I had used the drag-and-drop function to create them. I can send you screen shots if you wish. From: Livnat Peer [lp...@redhat.com] Sent: Tuesday, August 07, 2012 2:05 AM To: Jacob Wyatt Cc: users@oVirt.org Subject: Re: [Users] 3.1 network setup On 06/08/12 20:52, Jacob Wyatt wrote: > I'm using the iso images for oVirt Node Hypervisor release 2.5.0 (2.0.fc17). > I was able to manually edit the ifcfg files manually run the persist command > against them, reboot, and the engine sees everything just fine. The engine > was able to successfully configure a VLAN interface and then add ovirtmgmt as > a bridge. The problem was adding a second vlan. Instead of just creating a > second VLAN interface and bridge it tried to configure a bridge directly on > the network interface. I'll look at it in more detail when I have time. > Right now I'm having trouble actually starting a VM so I need to work that > out so I can actually test the networking. > Thanks for the input. A stupid question - can you see in the UI the vlan tag defined on the logical network (on the data-center tab -> networks sub tab -> edit network) Livnat > > From: Livnat Peer [lp...@redhat.com] > Sent: Monday, August 06, 2012 2:04 AM > To: Jacob Wyatt > Cc: users@oVirt.org > Subject: Re: [Users] 3.1 network setup > > On 06/08/12 05:06, Jacob Wyatt wrote: >> OK, so I reinstalled yesterday using the prepackaged 3.1 beta yum >> repository. It's better. It now correctly assigns the ovirtmgmt network to >> the node when it is attached. > >> Unfortunately, I still cannot seem to add a second interface or VLAN without >> breaking the networking again. > > I'm wondering if part of it is an issue with the node. If I try to > configure networking through the admin interface on the node it only > lets me configure one interface. Configuring a second interface breaks > the first one. I may try manually editing the config files on the node, > but I'm not sure how the engine will see that. >> >> -Jacob >> > > manually editing the node network should work just fine, you should put > your node in maintenance mode via the UI, do the manual changes you want > and then activate the host which should reflect the new host configuration. > If there is an issue with the above I'll be happy if you can share it > with us so we can fix that. > > Having said the above It would really help us if you can avoid using the > manual edit and let us find what is wrong with the flow from the UI. > > What vdsm version is installed on your host? did you build from source? > Is the second network you are trying to add is a marked as a vm-network? > (vm-network is later translated to bridge on the node) we block more > than one non-vm network on an interface. > can you send the logs (vdsm + engine)? > > > Livnat > >> >> From: Livnat Peer [lp...@redhat.com] >> Sent: Sunday, August 05, 2012 4:59 AM >> To: Jacob Wyatt >> Cc: users@oVirt.org >> Subject: Re: [Users] 3.1 network setup >> >> On 04/08/12 17:51, Jacob Wyatt wrote: >>> I just installed a new 3.1 engine and I have one node with the latest node >>> iso installed. After setting up one of the network interfaces on the node >>> and confirming I have network I am able to attach it to the engine. I've >>> done this starting from both the node and the engine and it seems to work >>> either way. Everything looks good until I go to the network controls in >>> the web interface. I need to configure another network interface but to do >>> so the ovirtmgmt network must be assigned to an interface. I'm not sure >>> why it isn't already since the node is already assigned to a cluster. If I >>> attempt to assign the management network it starts reconfiguring the node >>> and then irrecoverably breaks the network on the node. By irrecoverable I >>> mean I have to manually log in to the node as root and use ifdown to shut >>> off all of the interfaces, delete all of the network configs under /config >>> and then restart the machine and re-setup the network to get it back. >>> Nothing less seems t! o! > ! >> res >>> tore network to the node. From what I can tell when the node is assigned >>> to a cluster the network looks good on the node side. It's running a >>> bri
[Users] sanlock issues
oVirt Node Hypervisor release 2.5.0 (2.0.fc17) Can't start a VM. Same error in any of /var/log/libvirt/qemu/vmname.log libvir: Locking error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified I've tried several suggestions including: modprobe softdog systemctl restart wdmd.service systemctl restart sanlock.service I haven't changed the default configs but I'm heading there next. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] 3.1 network setup
I'm using the iso images for oVirt Node Hypervisor release 2.5.0 (2.0.fc17). I was able to manually edit the ifcfg files manually run the persist command against them, reboot, and the engine sees everything just fine. The engine was able to successfully configure a VLAN interface and then add ovirtmgmt as a bridge. The problem was adding a second vlan. Instead of just creating a second VLAN interface and bridge it tried to configure a bridge directly on the network interface. I'll look at it in more detail when I have time. Right now I'm having trouble actually starting a VM so I need to work that out so I can actually test the networking. From: Livnat Peer [lp...@redhat.com] Sent: Monday, August 06, 2012 2:04 AM To: Jacob Wyatt Cc: users@oVirt.org Subject: Re: [Users] 3.1 network setup On 06/08/12 05:06, Jacob Wyatt wrote: > OK, so I reinstalled yesterday using the prepackaged 3.1 beta yum repository. > It's better. It now correctly assigns the ovirtmgmt network to the node > when it is attached. > Unfortunately, I still cannot seem to add a second interface or VLAN without > breaking the networking again. I'm wondering if part of it is an issue with the node. If I try to configure networking through the admin interface on the node it only lets me configure one interface. Configuring a second interface breaks the first one. I may try manually editing the config files on the node, but I'm not sure how the engine will see that. > > -Jacob > manually editing the node network should work just fine, you should put your node in maintenance mode via the UI, do the manual changes you want and then activate the host which should reflect the new host configuration. If there is an issue with the above I'll be happy if you can share it with us so we can fix that. Having said the above It would really help us if you can avoid using the manual edit and let us find what is wrong with the flow from the UI. What vdsm version is installed on your host? did you build from source? Is the second network you are trying to add is a marked as a vm-network? (vm-network is later translated to bridge on the node) we block more than one non-vm network on an interface. can you send the logs (vdsm + engine)? Livnat > > From: Livnat Peer [lp...@redhat.com] > Sent: Sunday, August 05, 2012 4:59 AM > To: Jacob Wyatt > Cc: users@oVirt.org > Subject: Re: [Users] 3.1 network setup > > On 04/08/12 17:51, Jacob Wyatt wrote: >> I just installed a new 3.1 engine and I have one node with the latest node >> iso installed. After setting up one of the network interfaces on the node >> and confirming I have network I am able to attach it to the engine. I've >> done this starting from both the node and the engine and it seems to work >> either way. Everything looks good until I go to the network controls in the >> web interface. I need to configure another network interface but to do so >> the ovirtmgmt network must be assigned to an interface. I'm not sure why it >> isn't already since the node is already assigned to a cluster. If I attempt >> to assign the management network it starts reconfiguring the node and then >> irrecoverably breaks the network on the node. By irrecoverable I mean I >> have to manually log in to the node as root and use ifdown to shut off all >> of the interfaces, delete all of the network configs under /config and then >> restart the machine and re-setup the network to get it back. Nothing less >> seems to! ! > res >> tore network to the node. From what I can tell when the node is assigned >> to a cluster the network looks good on the node side. It's running a bridge >> named ovirtmgmt and seems to be happy. When the engine tries to assign >> ovirtmgmt to the node it creates a new bridge named after the network >> interface but is unable to start it. I've done a lot troubleshooting of >> network issues on 3.0 and have been able to work around them, but I seem to >> be at an impasse here. Without the additional network config my VM's won't >> work. Is there another way to force the network configuration without using >> the web interface? I know what the network setup should be. I've done all >> kinds of manual bridging, bonding, etc. under Fedora. I just can't seem to >> get oVirt to understand. >> >> -Jacob > > > Hi Jacob, > > You installed the engine from source? if so what is the engine hash > commit you used for installation? > > The reason I am asking that is because we had a major regression last > week were we broke the n
Re: [Users] 3.1 network setup
OK, so I reinstalled yesterday using the prepackaged 3.1 beta yum repository. It's better. It now correctly assigns the ovirtmgmt network to the node when it is attached. Unfortunately, I still cannot seem to add a second interface or VLAN without breaking the networking again. I'm wondering if part of it is an issue with the node. If I try to configure networking through the admin interface on the node it only lets me configure one interface. Configuring a second interface breaks the first one. I may try manually editing the config files on the node, but I'm not sure how the engine will see that. -Jacob From: Livnat Peer [lp...@redhat.com] Sent: Sunday, August 05, 2012 4:59 AM To: Jacob Wyatt Cc: users@oVirt.org Subject: Re: [Users] 3.1 network setup On 04/08/12 17:51, Jacob Wyatt wrote: > I just installed a new 3.1 engine and I have one node with the latest node > iso installed. After setting up one of the network interfaces on the node > and confirming I have network I am able to attach it to the engine. I've > done this starting from both the node and the engine and it seems to work > either way. Everything looks good until I go to the network controls in the > web interface. I need to configure another network interface but to do so > the ovirtmgmt network must be assigned to an interface. I'm not sure why it > isn't already since the node is already assigned to a cluster. If I attempt > to assign the management network it starts reconfiguring the node and then > irrecoverably breaks the network on the node. By irrecoverable I mean I have > to manually log in to the node as root and use ifdown to shut off all of the > interfaces, delete all of the network configs under /config and then restart > the machine and re-setup the network to get it back. Nothing less seems to ! res > tore network to the node. From what I can tell when the node is assigned to > a cluster the network looks good on the node side. It's running a bridge > named ovirtmgmt and seems to be happy. When the engine tries to assign > ovirtmgmt to the node it creates a new bridge named after the network > interface but is unable to start it. I've done a lot troubleshooting of > network issues on 3.0 and have been able to work around them, but I seem to > be at an impasse here. Without the additional network config my VM's won't > work. Is there another way to force the network configuration without using > the web interface? I know what the network setup should be. I've done all > kinds of manual bridging, bonding, etc. under Fedora. I just can't seem to > get oVirt to understand. > > -Jacob Hi Jacob, You installed the engine from source? if so what is the engine hash commit you used for installation? The reason I am asking that is because we had a major regression last week were we broke the network API. It was fixed in commit fa95ed435ac824ae7fc721239d862337053202bc, I suggest you don't cherry pick this specific commit but rebase on it. Thanks, Livnat > > ___ > 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] 3.1 network setup
I just installed a new 3.1 engine and I have one node with the latest node iso installed. After setting up one of the network interfaces on the node and confirming I have network I am able to attach it to the engine. I've done this starting from both the node and the engine and it seems to work either way. Everything looks good until I go to the network controls in the web interface. I need to configure another network interface but to do so the ovirtmgmt network must be assigned to an interface. I'm not sure why it isn't already since the node is already assigned to a cluster. If I attempt to assign the management network it starts reconfiguring the node and then irrecoverably breaks the network on the node. By irrecoverable I mean I have to manually log in to the node as root and use ifdown to shut off all of the interfaces, delete all of the network configs under /config and then restart the machine and re-setup the network to get it back. Nothing less seems to res tore network to the node. From what I can tell when the node is assigned to a cluster the network looks good on the node side. It's running a bridge named ovirtmgmt and seems to be happy. When the engine tries to assign ovirtmgmt to the node it creates a new bridge named after the network interface but is unable to start it. I've done a lot troubleshooting of network issues on 3.0 and have been able to work around them, but I seem to be at an impasse here. Without the additional network config my VM's won't work. Is there another way to force the network configuration without using the web interface? I know what the network setup should be. I've done all kinds of manual bridging, bonding, etc. under Fedora. I just can't seem to get oVirt to understand. -Jacob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] oVirt Node post boot script
If I wanted to have a script run on the on oVirt Node after it has finished booting, where would I do that? Between the persistent files configuration and the newer systemd initialization, I'm trying to find the right way to do this. -Jacob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] image ownership
Frederico, Thank you for responding. I checked the qemu.conf file on all of the nodes and it was correct. What's even more strange is that last night I put all of the nodes into maintenance mode and restarted them. No particular reason for this but I was trying anything I could think of. Now the ownership remains correct. I suppose I'll never know what I did wrong, but at least it is working. I found only 2 other anomalies. One, the live migration did not work because TLS was disabled on the nodes. The "listen_tls = 0" flag was set in /etc/libvirt/libvirtd.conf. I commented that out and migration works. The second thing I noticed is that the iptables service is not starting. This doesn't hinder functionality, but it's a security issue. I'm still checking into why. I doubt either of these issues caused my ownership problem. I'm sure it's some mistake I made. Hopefully I won't make it again next time. Thank you again, -Jacob From: Federico Simoncelli [fsimo...@redhat.com] Sent: Thursday, May 10, 2012 3:38 AM To: Jacob Wyatt Cc: users@ovirt.org Subject: Re: [Users] image ownership - Original Message - > From: "Jacob Wyatt" > To: users@ovirt.org > Sent: Wednesday, May 9, 2012 8:08:54 PM > Subject: [Users] image ownership > > Greetings all, > > I've set up a new oVirt installation and it's behaving strangely with > regard to virtual machine image files on the NFS storage. Whenever > I shut down a machine it's changing the owner of the image to > root:root (0:0) instead of vdsm:kvm (36:36). After that it can't > start or do anything with that image again until I manually change > the ownership back. Everything works fine again until I shut the > machine down. I assume this is some mistake I've made in > installation. I did not have this problem in the test environment, > but I'm stumped as to what went wrong. > > -Jacob Hi Jacob, could you check the dynamic_ownership in /etc/libvirt/qemu.conf: # grep dynamic_ownership /etc/libvirt/qemu.conf #dynamic_ownership = 1 dynamic_ownership=0 # by vdsm Thanks, -- Federico ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Default storage pool won't activate after reboot
Hi,
I'm new to oVirt myself but I thought that the top level directory name was the
UUID of the storage pool. In that case the UUID it lists
(af5bcc86-898a-11e1-9632-003048c85226) isn't there. Have you looked directly
on the storage machine itself? Perhaps the node can't see that directory due
to permission issues?
-Jacob
From: users-boun...@ovirt.org [users-boun...@ovirt.org] on behalf of Ian
Levesque [i...@crystal.harvard.edu]
Sent: Wednesday, May 09, 2012 2:31 PM
To: users@ovirt.org
Subject: [Users] Default storage pool won't activate after reboot
Hello,
Since a recent reboot, my default data storage pool has been inactive and
attempts to activate it fail.
Installed RPMs:
vdsm-4.9.6-0.150.git63061a9.el6.x86_64
ovirt-engine-3.1.0_0001-1.8.el6.x86_64
Relevant-looking output in the vdsm.log file (more @
http://pastebin.com/raw.php?i=cYaFLPEF):
Thread-68465::ERROR::2012-05-09
14:05:00,491::task::853::TaskManager.Task::(_setError)
Task=`937d1fa9-4636-42f1-a6cb-c4cc56b9f2fd`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 861, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/storage/hsm.py", line 526, in getSpmStatus
pool = self.getPool(spUUID)
File "/usr/share/vdsm/storage/hsm.py", line 263, in getPool
raise se.StoragePoolUnknown(spUUID)
StoragePoolUnknown: Unknown pool id, pool not connected:
('af5bcc86-898a-11e1-9632-003048c85226',)
Thread-68465::DEBUG::2012-05-09
14:05:00,491::task::872::TaskManager.Task::(_run)
Task=`937d1fa9-4636-42f1-a6cb-c4cc56b9f2fd`::Task._run:
937d1fa9-4636-42f1-a6cb-c4cc56b9f2fd ('af5bcc86-898a-11e1-9632-003048c85226',)
{} failed - stopping task
The share /is/ mounted on the node:
# mount | grep cmcd-db-vip
cmcd-db-vip.in.hwlab:/vmstore/ovirt on
/rhev/data-center/mnt/cmcd-db-vip.in.hwlab:_vmstore_ovirt type nfs
(rw,soft,nosharecache,timeo=600,retrans=6,nfsvers=3,addr=10.0.10.13)
# ls -l /rhev/data-center/mnt/cmcd-db-vip.in.hwlab:_vmstore_ovirt/
total 0
drwxr-xr-x 5 vdsm kvm 45 Apr 13 12:23 4ddb9dce-1ede-459a-9b9f-52b035622517
drwxr-xr-x 5 vdsm kvm 45 Apr 12 16:17 4ea29e75-ab27-4bc9-bc46-1740d07f4cba
drwxr-xr-x 5 vdsm kvm 45 Apr 19 11:40 e12a0f53-ee72-44bc-ad26-93f9b4613c6c
The closest google turns up is a thread from March, in which there was some
mention of a change in the way metadata is read. Might be a red herring, but
here's that thread:
http://lists.ovirt.org/pipermail/users/2012-March/001423.html
Thanks for any insight!
Ian
___
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] image ownership
Greetings all, I've set up a new oVirt installation and it's behaving strangely with regard to virtual machine image files on the NFS storage. Whenever I shut down a machine it's changing the owner of the image to root:root (0:0) instead of vdsm:kvm (36:36). After that it can't start or do anything with that image again until I manually change the ownership back. Everything works fine again until I shut the machine down. I assume this is some mistake I've made in installation. I did not have this problem in the test environment, but I'm stumped as to what went wrong. -Jacob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
