Custom Query (894 matches)
Results (7 - 9 of 894)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #399 | desai | naapuri | worksforme | Client succeeds but claims "Symlink /foo/bar cleanup failed" |
| Description |
When installing new symlinks, the client succeeds but says: Installing Symlink /foo/bar Symlink /foo/bar cleanup failed The reason seems obvious. POSIX.py tries to unlink a previous file, which doesn't exist. Unlinking throws an error. |
|||
| #464 | desai | [email protected]… | worksforme | upgrade to 0.9.4 broke /usr/lib/bcfg2-cron --daily |
| Description |
After upgrading to 0.9.4 /usr/lib/bcfg2-cron --daily fails outputting the following message: [email protected]:/usr/lib/bcfg2 # ./bcfg2-cron --daily Bcfg2 takes no arguments, only options -v enable verbose output -e enable extra entry detailed output -f <configspec> configure from a file rather than querying the server -h print this help message -P make automatic backups of config files -D <driver1>,<driver2> Specify tool driver set -c <configspec> store the configuration in a file -B run in build mode -p <profile> assert the given profile for the host -n do not actually change the system -k run in kevlar (bulletproof) mode -b <bundle> only configure the given bundle -q disable some checksum verification -u <user> the user to provide for authentication -F <server fingerprint> Server Fingerprint -x <password> the password to provide for authentication -R <numretries> the number of times to retry network communication -C <configfile> use given config file (default /etc/bcfg2.conf) -r (packages|services|all) force removal of additional configuration items -S <server url> the server hostname to connect to -d enable debugging output -I prompt the user for each change I'm running bcfg2 0.9.4 on SLE 10. |
|||
| #476 | desai | lueningh | worksforme | Schema update needed? |
| Description |
When trying to validate my repo, it is angry about actions: /var/lib/bcfg2/Bundler/network.xml ***FAILS*** to verify <---- /var/lib/bcfg2/Bundler/network.xml:2: element Action: Schemas validity error : Element 'Action', attribute 'timing': The attribute 'timing' is not allowed. /var/lib/bcfg2/Bundler/network.xml:2: element Action: Schemas validity error : Element 'Action', attribute 'command': The attribute 'command' is not allowed. /var/lib/bcfg2/Bundler/network.xml:2: element Action: Schemas validity error : Element 'Action', attribute 'when': The attribute 'when' is not allowed. /var/lib/bcfg2/Bundler/network.xml:2: element Action: Schemas validity error : Element 'Action', attribute 'status': The attribute 'status' is not allowed. /var/lib/bcfg2/Bundler/network.xml fails to validate |
|||
