Custom Query (894 matches)
Results (172 - 174 of 894)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#392 | desai | [email protected]… | fixed | New entries in client.xml fail until server restarted |
Description |
Adding a new entry in clients.xml (with corresponding entries in groups.xml) fails with: bcfg2-server[3d29375196c124405db4d256dc8368f39e9160d1] (SVN r4833): Processed 2 gamin events in 0.123 seconds. 0 collapsed bcfg2-server[3d29375196c124405db4d256dc8368f39e9160d1] (SVN r4833): Cannot set group for client conway.wsg.mcgill.ca; no default group set bcfg2-server[3d29375196c124405db4d256dc8368f39e9160d1] (SVN r4833): Client metadata resolution error for 132.216.177.33 Here are the corresponding entries in clients.xml and groups.xml: clients.xml <Client profile="ras-server" name="conway.wsg.mcgill.ca" pingable="Y"/> groups.xml <Group profile="true" public="false" name="ras-server"> <Group name="el4-i386"/> <Group name="syslog-client"/> <Group name="mail-client"/> <Group name="postgresql-server"/> <Group name="httpd-server"/> </Group> Restarting bcfg2-server fixes the problem. |
|||
#393 | desai | [email protected]… | fixed | Non-base64 binary file inclusion causes traceback in the client |
Description |
I have mistakenly included a binary file without marking it as "encoding: base64". That resulted in two things:
Setting 'encoding: base64' fixes the immediate problem. Sorry, I can't send you the misbehaving file for testing, since it's a keytab. :) |
|||
#394 | desai | [email protected]… | fixed | Incorrect "epoch" handling for packages |
Description |
Currently bcfg2 ignores "epochs", which are part of package versioning. This is particularly noticeable with the yum driver, since the sync script generates versions with epochs, and bcfg2 will then claim that incorrect versions are installed. To generate the list of installed packages bcfg2 currently uses: rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE}\n' It should instead use: rpm -qa --qf '%{NAME} %{EPOCH}:%{VERSION}-%{RELEASE}\n' | sed 's/(none)://g' or something similar. I think it will break existing setups, though -- but it's a bug that should be fixed in order to have correct behaviour. |