Custom Query (894 matches)


Show under each result:

Results (169 - 171 of 894)

Ticket Owner Reporter Resolution Summary
#393 desai [email protected] fixed Non-base64 binary file inclusion causes traceback in the client

I have mistakenly included a binary file without marking it as "encoding: base64". That resulted in two things:

  1. The server did not complain
  2. The client crashed with the following traceback:
    Unknown failure
    Traceback (most recent call last):
      File "/usr/lib/python2.3/site-packages/Bcfg2/Client/", line 110, in run_method
        ret = apply(method, self._authinfo + methodArgs)
      File "/usr/lib/python2.3/", line 1029, in __call__
        return self.__send(self.__name, args)
      File "/usr/lib/python2.3/", line 1316, in __request
      File "/usr/lib/python2.3/", line 1080, in request
        return self._parse_response(h.getfile(), sock)
      File "/usr/lib/python2.3/", line 1214, in _parse_response
      File "/usr/lib/python2.3/", line 528, in feed
        self._parser.Parse(data, 0)
    ExpatError: not well-formed (invalid token): line 35, column 120
    GetConfig failed:
    Could not connect to bcfg2
    Failed to download configuration from bcfg2

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

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.

#395 desai desai fixed Documentation Topics

This ticket will be used to track topics that need better documentation. Anyone can add topics to this list. Support for existing topics on the list can be voiced by adding a + after the topic (limit one per customer, offer may not be combined with other offers) Try to keep the list on detailed subjects (ie How does subsystem X work, or how do i achieve goal Y) so that they can be written individually. Topics will be removed once the documentation is written.

The list:

Note: See TracQuery for help on using queries.