[vdsm] Recent changes in vdsmd startup

Dan Kenigsberg danken at redhat.com
Thu Oct 10 20:51:30 UTC 2013


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.



More information about the Arch mailing list