| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes a condition where it would take two Bcfg2 runs to properly
deploy new packages. Prior, if new specification deployed a new Yum
.repo file and new packages from that new repo, Bcfg2 would not be able
to install the new packages until the second run. This change causes
Yum to reload all of its configuration and incorperate any new .repo
files before attempting to install packages.
(cherry picked from commit 059d37b2c385a848764c631d0d735a51908de0cf)
|
| |
|
|
|
|
|
|
|
|
| |
This commit is not compatable with Python 2.4 and below.
Our goal is to support for the foreseeable future 2.4+ for
Bcfg2 server and 2.3+ for Bcfg2 client.
This reverts commit 4310284f6df01caf1b686c9bac8955364a895755.
|
|
|
|
|
|
| |
In earlier versions of python commas (,) could
be used in except statements. The new way is to
use 'as'.
|
|
|
|
| |
* Ticket 1080
|
| |
|
| |
|
| |
|
|
|
|
| |
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>
|
|
|
|
| |
the contents.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Use file size to do an initial comparison to see if the file on disk
differs from the data in the config;
* Only do diffs if necessary: unified diff if -I is used, ndiff if a
file is not sensitive or binary;
* Both diffs have timeouts;
* Fixed edge case where null-content binary files would produce stack
traces, not errors.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ |
|
| |
| |
| |
| |
| | |
This is highly experimental.
All credits goes to Cameron Banta.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
can dramatically reduce memory usage, and fixed several bugs:
* #1014 (Package plugin can't resolve dependencies for rpms with
Require: tags for full paths that aren't Provided explicitly)
* #991 (Dependency Resolution difference between Package and yum)
* #996 (Packages high memory usage)
* Added support for Yum package groups when using yum libraries
(#1039)
* Fixed #911 (bcfg2 output for wrong package version with Packages is
misleading)
* YUMng turns down the Yum debug level itself depending on the
debug/verbosity level requested by bcfg2 so you don't have to reduce
the Yum debug level on a global basis
* Added support for Pulp repositories, including registering Pulp
consumers and binding to repositories
* Added ability to disable magic OS groups
|
| |
| |
| |
| | |
This access is triggered by running "bcfg2 -r Packages".
|
| |
| |
| |
| |
| |
| |
| |
| | |
The umask was set to zero in order to address the issue that mknod(2)'s
mode argument is modified by the process's umask. However, this umask
setting also affected auto-created parent directories of configuration
entries: their permissions were set to `drwxrwxrwx'. So, we now call
chmod(2) after mknod(2) instead of setting the umask to zero.
|
| |
| |
| |
| |
| |
| | |
Make sure the "start_sequence" variable is initialized. This fixes a
traceback which occurred when a <Service> "sequence" has been specified
on Debian systems which use dependency-based booting.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The "-f" option, which tells the client to configure from a file rather
than querying the server, cannot be combined with the "-l" option (nor
with the equivalent setting in the bcfg2.conf(5) file), as a decision
list won't be available. Instead of crashing (with a KeyError:
'decision_list'), the client will now ignore the "-l" option if the "-f"
option also is specified.
|
| |
| |
| |
| |
| |
| | |
If the file /etc/init.d/.legacy-bootordering exists, dependency-based
booting isn't used, even when running on Debian releases newer than
lenny.
|
|/
|
|
|
| |
The client now makes sure that an entry won't be reported as modified if
the Install() method which handled the entry returned False.
|
|
|
|
|
| |
Fix the problem that modified entries weren't included in the client
statistics if their "important" attribute was set to "true".
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
| |
This fix is more complete than 8059a36 and also fixes issues relating to
the use of wildcards in Decisions.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
Don't run 'post' Action entries if they are unlisted in whitelist mode.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
piping stderr to /dev/null to prevent failure
|
| |
|
|
|
|
|
|
| |
The contents/diffs of <Path>s which are marked as "sensitive" are now
omitted from the reports transmitted to the server, so that they won't
end up in the statistics database.
|
|
|
|
|
| |
If the arch is specified use it to select the package in VerifyPackage()
otherwise just work with the default arch.
|
| |
|
|
|
|
|
|
| |
So a package is not "installed" if a package of the same name but
different arch is. This will enable YUMng to handle multilib
package installs.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
| |
This allows for a recursive='true' attribute such that the owner/group
can be set recursively for a directory when using Path type='permissions'.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
Address ticket #955 and attempt to capture the exceptions that
may possibly be generated from Yum or Yum's plugins and return
some sort of error message.
|
|
|
|
|
|
| |
This make the YUMng verification behavior like the APT tool. Before
hand we just turned off package checksums which only worked with
very new versions of Yum.
|
|
|
|
| |
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>
|