Re: [vdsm] Recent changes in vdsmd startup
- Original Message - > From: "Dan Kenigsberg" > To: "Antoni Segura Puimedon" > Cc: "arch" , "VDSM Project Development" > > Sent: Thursday, October 10, 2013 11:51:30 PM > Subject: Re: [vdsm] Recent changes in vdsmd startup > > On Thu, Oct 10, 2013 at 04:40:36PM -0400, Antoni Segura Puimedon wrote: > > Is this what happened with the network functional testing? After these > > last changes, before the yum install of the new vdsm and the yum erase > > of the old I had to add the vdsm-tool libvirt reconfigure and start. > > Otherwise vdsm would not be able to reply to VdsGetCaps (on f19, on el6 > > somehow it didn't happen). > > IMO what you've experienced is the intended change that Yaniv has > reported in this thread. Fresh installation of vdsm now requires > more-than-just `service vdsmd start`. > > I'm trying to understand our action on the unattended upgrade path. Interesting point. Thanks for raising that up, raising such issues was part of this mail goals You are right that after an upgrade we will need to restart libvirt service manually to start working with new configuration, But, AFAIK we don't force vdsmd restart after upgrading. If the user updated the package and still wants the new configuration, manual vdsmd restart will be required anyway. So the print to restart also related service is just enough. > ___ > Arch mailing list > a...@ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch > ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] Resizing disks destroys contents
We should update both of vdsm and ovirt-engine or vdsm is enough? I check ovirt el repo and it does not have new version for vdsm. On 10/12/2013 02:11 AM, Dan Kenigsberg wrote: On Sat, Oct 12, 2013 at 12:27:02AM +0330, Mohsen Saeedi wrote: I have same problem too. I have one node as ovirt engine and as hypervisor too. I successfully upgrade our engine from 3.1 to 3.2 and then from 3.2 to 3.3 and everything is ok. then i upgrade our cluster version to 3.3 and then our datacenter to 3.3. I increase 1GB on virtual machine with 20GB thin disk and I receive success message on event and our disk increase to 21GB but after host reboot, i saw message that contains no bootable disk is available!!! then i try to install new os on that disk (Centos 6.4 minimal) and anaconda show the error on screen : No usable disks have found. I think disk corrupt after resizing. it was test VM but it's very if occur for real and functional VMs. Yes, this is indeed a bad bad bug. It was inadvertantly fixed on the master branch a while ago. Yesterday, we've backported the fix to 3.3.0.1 http://lists.ovirt.org/pipermail/users/2013-October/017018.html Please avoid trying ovirt-3.3.0's new disk resize feature on file-based storage, unless you upgrade to vdsm vdsm-4.12.1-4 first. Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] Resizing disks destroys contents
On Sat, Oct 12, 2013 at 11:07:07PM +0330, Mohsen Saeedi wrote: >We should update both of vdsm and ovirt-engine or vdsm is enough? I check >ovirt el repo and it does not have new version for vdsm. >On 10/12/2013 02:11 AM, Dan Kenigsberg wrote: Only a vdsm update is required for resolving this issue. Apparently, vdsm-4.12.1-4 is still in testing stage http://resources.ovirt.org/releases/updates-testing/rpm/EL/6/x86_64/ Please try it out! > > On Sat, Oct 12, 2013 at 12:27:02AM +0330, Mohsen Saeedi wrote: > > I have same problem too. I have one node as ovirt engine and as > hypervisor too. I successfully upgrade our engine from 3.1 to 3.2 and then > from 3.2 to 3.3 and everything is ok. > then i upgrade our cluster version to 3.3 and then our datacenter to 3.3. > I increase 1GB on virtual machine with 20GB thin disk and I receive > success message on event and our disk increase to 21GB but after host > reboot, i saw message that contains no bootable disk is available!!! > then i try to install new os on that disk (Centos 6.4 minimal) and > anaconda show the error on screen : No usable disks have found. I think > disk corrupt after resizing. > it was test VM but it's very if occur for real and functional VMs. > > Yes, this is indeed a bad bad bug. It was inadvertantly fixed on the > master branch a while ago. Yesterday, we've backported the fix to > 3.3.0.1 > > http://lists.ovirt.org/pipermail/users/2013-October/017018.html > > Please avoid trying ovirt-3.3.0's new disk resize feature on file-based > storage, > unless you upgrade to vdsm vdsm-4.12.1-4 first. > > Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
