| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ \ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
breaking
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of doing a partially complete Install() method for SYSV,
implements a custom _get_package_command that will use the
_sysv_pkg_path attribute added by the pkgmogrify call.
This will allow the installs to complete. Unfortunately, the
single-pass install will still fail if there are any packages with an
http:// URL. The pkgadd invocation for 'device' sources doesn't take
multiple packages and the 'datastream' invocation doesn't handle packages
with an HTTP URL. Finally, there is no reliable standard naming
convention for SYSV datastream files, so the simplename attribute is
re-used.
There is a known issue with this patch - if any packages specified in
the PackageList have an http url, the single-pass install will produce
an error like:
Trying single pass package install for pkgtype sysv
pkgadd: ERROR: Failure occurred with http(s) negotiation: <'Peername' doesn't match 'host' or no matching entry>
pkgadd: ERROR: unable to download package datastream from <http://install1.d.stor.en.desres.deshaw.com/jumpstart10U10/packages>.
Single Pass Failed
because the command that results isn't valid syntax for pkgadd. A
workaround would be to add code to skip the single-pass install if any
packages had the simplename attribute, or by checking the url for the
presence of 'http'. I'm not sure if that should be fixed or if this is
reasonable in this case.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
pkgadd has different syntax for different sources (datastream and file
system format) which makes using a single pkgtool variable difficult.
Also, SYSV packages in datastream format don't necessarily have uniform
names. Therefore, use the existing 'simplename' attribute to specify
the datastream file name.
|
| | |
| | |
| | |
| | | |
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 "Essential" field in the package control fields could be "yes" or "no".
Only yes sould define the package as essential. The value "no" sould be
handled same as not having the field at all.
|
|\ \ \
| | | |
| | | | |
Server/Admin: fatal errors should go to stderr
|
| | | |
| | | |
| | | |
| | | |
| | | | |
If an error occurs, that leads to an termination of the process,
this error should be printed to stderr.
|
| | | |
| | | |
| | | |
| | | | |
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>
|
|\ \ \ \
| |_|/ /
|/| | | |
Use PYVERSION in Makefile and gen-prototypes consistently
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
PYVERSION is already being set in the Makefile but wasn't being used
when setup.py gets invoked.
Use PYVERSION in gen-prototypes to generate complete packages.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Doc: fix repeated word in AWSTags docs
|
| | | | |
|
|/ / / |
|
| | |
| | |
| | | |
This fixes a subtle bug by enforcing that it's a tuple of 2-tuples rather than just a single 2-tuple.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 433974d9311f68f199bedf1c2710381e0bc8d34a.
python-nose is required by bcfg2-test.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
python-nose is only required for running the nosetests. It is not
required by bcfg2-server.
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>
|
| |
| |
| |
| |
| | |
Avoid building client metadata while rereading those files, and expire
the metadata cache afterwards.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes a best effort to watch XIncluded files that do not exist.
Assume that you have XIncluded ``foo.xml``, the following (currently)
fails:
mv foo.xml /tmp
mv /tmp/foo.xml .
Bcfg2 processes the deletion event, and stops watching ``foo.xml``;
consequently, it receives no creation event when you put ``foo.xml``
back.
This does not fix the situation where you add a new file that is
matched by a wildcard XInclude, which turns out to be much more
difficult, and will likely require a significant restructuring of how
wildcard XIncludes are processed. (I.e., we'll need to place a
monitor on the directory or directories where the wildcard XInclude is
looking, and then filter events according to the wildcard.)
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For both Encrypting and Decrypting of Properties
files, we should by default only attempt to execute
on elements that have an "encrypted" attribute defined.
The code will already attempt to encrypt every element
if nothing in the current document matches this xpath,
which catches the case of a user trying to fully
encrypt a completely new properties file.
Conflicts:
src/lib/Bcfg2/Server/Encryption.py
|
|
|
|
|
| |
this greatly decreases startup time with lots of data encrypted with
missing passphrases
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the RPM scriptlets, there's first a check for fedora 18 or greater,
then if that's not true, a check for fedora 16 or greater. Due to
some bug in how nested %if statements work in RPM scriptlets, the
second test is evaluating true even on non-Fedora systems, which is
leading to systemd commands being put in RHEL6 RPM scriptlets.
This change removes the second check. If there needed to be a check
for versions of Fedora 16 and 17, they will no longer work, but since
neither of those are supported versions of Fedora, I suspect we don't
need to include logic for them.
|
|\
| |
| | |
Enable bcfg2-yum-helper to depsolve for arches incompatible with server
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default, the yum dependency resolver uses the host's architecture
to filter compatible packages. This prevents dependency resolution
when the bcfg2 client's architecture is incompatible with the
server's.
This workaround checks the <Arch/> element for each of the client's yum
sources, and if they are all identical, passes that architecture to
bcfg2-yum-helper to override the default.
The rpmUtils.arch module may only be configured for a single
architecture. If multiple architectures are configured in yum
sources, we don't know which one to pick, so use the default behavior
instead.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Formerly, yum did an 'update' to install the correct version of a
package, even if the desired package was older than the installed
package. This is wrong; it needs to do a downgrade. This changes it
to downgrade when the desired package is older, and upgrade if it is
newer.
There is still the possibility of upgrading a package that should be
downgraded if the desired package is only partially specified, but
this should be very rare.
|