holland-coredev team mailing list archive
-
holland-coredev team
-
Mailing list archive
-
Message #00112
[Bug 753070] Re: mkvirtenv.py issues - holland-test config not parsed
This was largely due to a missing default setting for --config in the
command line interface. This was a simple fix here:
https://github.com/holland-
backup/holland/commit/6135fd3257180ae8a5b5df8b57c11ccf0a39b2e7
There was also an issue with mkvirtenv.py not adjusting the holland.conf
appropriately to log/write backups to ~/holland-test/ as well. I made a
quick fix to rewrite that config file file and put backups in ~/holland-
test/backups/ and holland logs in ~/holland-test/logs/ here:
https://github.com/holland-
backup/holland/commit/39a5bd2d329dafbc40bcc7660a5cbf21eaec8536
I should note that holland backup is a little more configurable now - a
holland.conf is no longer required (it just sets better defaults). You
can adjust this on the command line with the --backup-directory (-d)
option:
% holland backup --backup-directory=local_backup/ $PWD/config/backupsets/default.conf
% holland --config=/dev/null backup -d local_backup/ $PWD/config/backupsets/default.conf
2011-04-07 00:54:41,552 [INFO] Failed to open log file: [Errno 13] Permission denied: '/var/log/holland/holland.log'
2011-04-07 00:54:41,552 [INFO] Skipping file logging.
...
2011-04-07 00:57:29,166 [INFO] Backup job default completed in 2 minutes, 46.80 seconds
...
% ls ./local_backup/default/20110407_005441.lKL26I/
backup.conf backup_data holland.my.cnf job.info
** Changed in: holland-backup
Status: New => Fix Committed
** Changed in: holland-backup/1.1
Status: New => Fix Committed
--
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/753070
Title:
mkvirtenv.py issues - holland-test config not parsed
Status in Holland Backup Framework:
Fix Committed
Status in holland-backup 1.1 series:
Fix Committed
Bug description:
Previously (< 1.1.x), running ./scripts/mkvirtenv.py would just 'work'
out of the box.. meaning I could run the script, and start issuing
holland commands. In Amsterdam (current) it seems to no longer look
for the config in ~/holland-test/etc/holland:
[wdierkes@derks-linux holland]$ ./scripts/mkvirtenv.py
New python executable in /home/wdierkes/holland-test/bin/python
Installing setuptools...............done.
[INFO] Installed holland-core.
[INFO] Installing holland plugins
[INFO] Installed plugin holland.lib.common
[INFO] Installed plugin holland.lib.mysql
[INFO] Installed plugin holland.lib.lvm
[INFO] Installed plugin holland.backup.mysqldump
[INFO] Installed plugin holland.backup.mysql_lvm
[INFO] Installed plugin holland.backup.xtrabackup
[INFO] An existing config already exists in /home/wdierkes/holland-test/etc/holland. Not installing test configs.
[INFO] Starting shell in virtual environment /bin/bash - use ctrl-d to exit
[holland-test]% holland list-backups
2011-04-06 18:39:05,974 [ERROR] Failed to read /etc/holland/holland.conf: [Errno 2] No such file or directory: '/etc/holland/holland.conf'
2011-04-06 18:39:05,975 [INFO] Failed to open log file: [Errno 13] Permission denied: '/var/log/holland/holland.log'
2011-04-06 18:39:05,975 [INFO] Skipping file logging.
2011-04-06 18:39:06,001 [INFO] No backup-directory specified
References