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" asegurap@redhat.com To: "vdsm-devel" vdsm-devel@fedorahosted.org 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> run(**argDict) File "/usr/share/vdsm/vdsm", line 67, in run lconfig.fileConfig(loggerConfFile) File "/usr/lib64/python2.7/logging/config.py", line 78, in fileConfig handlers = _install_handlers(cp, formatters) File "/usr/lib64/python2.7/logging/config.py", line 156, in _install_handlers h = klass(*args) File "/usr/lib64/python2.7/logging/handlers.py", line 392, in __init__ logging.FileHandler.__init__(self, filename, mode, encoding, delay) File "/usr/lib64/python2.7/logging/__init__.py", line 902, in __init__ StreamHandler.__init__(self, self._open()) File "/usr/lib64/python2.7/logging/__init__.py", 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
Best,
Toni _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel