Custom Query (894 matches)


Show under each result:

Results (40 - 42 of 894)

Ticket Owner Reporter Resolution Summary
#44 desai bradshaw fixed traceback with a python warning during package install

The wierd thing is that the package is installed and verifies just fine. there just must be something wierd it is reporting when queried.

Traceback (most recent call last):

File "/usr/lib/python2.3/site-packages/Bcfg2/Client/", line 206, in VerifyEntry?

method = getattr(self, "Verify%s" % (entry.tag))

AttributeError?: 'ToolsetImpl?' object has no attribute 'VerifyPacakge?' Entry: <Pacakge name="libsoap-lite-perl"/> /usr/lib/python2.3/site-packages/Bcfg2/Client/ FutureWarning?: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up

print "State verify evidently failed for %s" % (msg)

State verify evidently failed for <Element Pacakge at b77967b8>

#45 desai [email protected] fixed default install is "dangerous"

Currently the default bcfg2 client install "does things" by default, which I consider dangerous. And it bit me this weekend.

To be specific, the /etc/init.d/bcfg2 script is set to run when a machine is rebooted. When it is run, it uses hard-coded options that make it try to sync against the bcfg2 server.

A simple fix can address the desired behavior, and make it non-dangerous by default. Simply add an entry to /etc/default/bcfg2 with something like "INIT_SCRIPT_ARGS = -q -n", and have /etc/init.d/bcfg2 run with "bcfg2 $INIT_SCRIPT_ARGS".

Note that if you include the "-n" in the configuration as part of the standard installation, then it becomes non-dangerous. However, it can easily be modified by the user to actually "do" things.

#46 desai [email protected] fixed SSH keys left laying around

I was doing some spring cleaning and noted that bcfg leaves copies of generated ssh keys in /tmp after they are created and put in place in the proper sshbase directory.

Note: See TracQuery for help on using queries.