| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
contain no failures
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
backtraces
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added bcfg2-yum-helper to offload Yum API calls to a short-lived
process. As absurd as this is, it appears to be the standard way to
get around Yum's atrocious memory handling (cf. yum-updatesd).
* Added SourceInitError for non-fatal errors instantiating new
sources.
* Fixed bug that caused all cached data to be removed on server
startup (reported by mikemccllstr on IRC).
* Fixed a number of overly aggressive caching issues.
* Fixed the way sources are loaded at server startup.
* Fixed handling of Yum package groups.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
* Fixed mode argument parsing when a config file is supplied
* Fixed loading help messages when Reports is not configured
* Improved option parsing; used Bcfg2.Options.OptionParser
|
|
|
|
|
|
|
| |
The command "bcfg2-info generators" didn't spit out anything useful,
just an unexpanded $Id$ keyword for each of the current generators.
It's been that way for quite some time now, and nobody seemed to miss
the command.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
| |
Catch I/O errors which might occur while reading a file specified as
argument to --badentry, --extraentry, or --modifiedentry.
|
|
|
|
|
| |
On getopt errors, print a proper usage message instead of spitting out a
traceback.
|
|
|
|
|
|
|
| |
This also moves the exception handling added in #1012 to the bcfg2 code
for consistency (as per Holger Weiß's suggestion).
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
Add a "-t NAME" option which reports the total (and good) number of
managed entries on the host NAME. Also, allow for specifying "total",
"good", and "bad" fields via --fields and --sort.
|
|
|
|
|
| |
bcfg2-reports now shows modified entries if it's called with
--modifiedentry, -m, or -s.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
an ugly stack trace if a file fails to validate
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 5d69ff7e966c4ffa911c78d11a6879b48e90aef8.
As the "rawconfig" variable now holds a UTF-8 encoded string, it would
have to be decoded before re-encoding it using a different encoding.
However, the cached configuration shouldn't be written using a non-UTF-8
encoding anyway, as "bcfg2 -f <configuration>" currently doesn't accept
any other encodings. (If this is to be changed, the XML encoding
declaration of the configuration would have to be adjusted accordingly.)
|
|
|
|
|
|
|
|
|
| |
The client receives the configuration specification as a Unicode string
and then hands it over to the XML() function, which expects a UTF-8
encoded string. Therefore, the configuration specification is now
converted to UTF-8.
Resolves ticket #1009.
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The reporting system schema has been changed. This change lead to
exceptions such as
| AttributeError: 'Entries_interactions' object has no attribute 'name'
when running bcfg2-reports with the --badentry or --extraentry options.
|
| |
|
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
(cherry picked from commit beb08649193f2c799017024bb738dc31b3420cb2)
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
| |
The man page for 'bcfg2' says to use -r 'all', 'Service' or 'Package',
but the code only responded to -r 'all', 'service' or 'package'.
Update the client to allow 'all', 'service', 'Service', 'package' and
'Package'.
|
|
|
|
|
|
| |
combine config files
get full stack trace from failed plugins for easier troubleshooting
|
|
|
|
|
|
| |
* fixed bcfg2-lint bug with older pythons
* made bcfg2-lint silent by default on success
* adjusted bcfg2-lint defaults and alerting levels to work better out-of-the-box
|
|
|
|
|
|
|
|
|
| |
* Changed all references to bcfg2-repo-validate in the documentation
to bcfg2-lint
* Wrote man pages for bcfg2-lint and bcfg2-lint.conf
* Cleaned up straggling references to bcfg2-repo-validate in
Makefiles, spec files, and the POSIX tool
* A few minor bug fixes
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
|
| |
interface to be lots more flexible and extensible. Added several more
tests. If bcfg2-lint is run as bcfg2-repo-validate, it roughly
emulates the functionality of that program.
TODO: Need to figure out correct way to symlink bcfg2-repo-validate to
bcfg2-lint on install.
|
|
|
|
| |
group file
|
| |
|
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
|