It's due to recent unified net persistence patches that were merged yesterday.

If you change the persistence model to ifcfg it shouldn't happen. Alternatively
you can:
touch /var/lib/vdsm/upgrade/UnifiedPersistence

And the upgrade won't run even if you're using unified persistence and VDSM 
will boot.

I'll look into why this is happening and send a patch today.

Assaf Muller, Cloud Networking Engineer 
Red Hat 

----- Original Message -----
From: "Antoni Segura Puimedon" <>
To: "vdsm-devel" <>
Sent: Wednesday, December 4, 2013 12:05:20 PM
Subject: [vdsm] Latest master fails to start due to logging

Hi List,

I just upgraded my testing vdsm to the new master and vdsmd fails to go
up due to:

    [vdsm@nx01]~% /usr/share/vdsm/vdsm
    Traceback (most recent call last):
      File "/usr/share/vdsm/vdsm", line 175, in <module>
      File "/usr/share/vdsm/vdsm", line 67, in run
      File "/usr/lib64/python2.7/logging/", line 78, in fileConfig
        handlers = _install_handlers(cp, formatters)
      File "/usr/lib64/python2.7/logging/", line 156, in 
        h = klass(*args)
      File "/usr/lib64/python2.7/logging/", line 392, in __init__
        logging.FileHandler.__init__(self, filename, mode, encoding, delay)
      File "/usr/lib64/python2.7/logging/", line 902, in __init__
        StreamHandler.__init__(self, self._open())
      File "/usr/lib64/python2.7/logging/", line 925, in _open
        stream = open(self.baseFilename, self.mode)
    IOError: [Errno 13] Permission denied: '/var/log/vdsm/upgrade.log'

I'd appreciate it if somebody could point me if there is a known patch for that


vdsm-devel mailing list
vdsm-devel mailing list

Reply via email to