| Age | Commit message (Collapse) | Author |
|---|
|
the fully qualified domain name should end
up in /etc/sysconfig/network by passing the
fqdn to the update and set hostname methods
and using it accordingly.
LP: #1076759
|
|
This change does 3 things:
* revert the fix from revno 697
* minor clean up some local variable usage and definition
* make Z99-cloud-locale-test.sh actually work when shell is zsh
the last is done by detecting if this is zsh, and if so, changing the zsh
behavior for this function to emulate sh. As a result of the '-L' in
'emulate -L sh', we have no negative affect on the user's shell.
LP: #1073077
|
|
This makes zsh act like 'sh', but only for the function local function.
This way, we do not affect the user's shell, but get the behavior we
want.
|
|
|
|
|
|
|
|
1. Remove the usage of the path.join function now that all code should
be going through the util file methods (and they can be mocked out as
needed).
2. Adjust all occurences of the above join function to either not use it
or replace it with the standard os.path.join (which can also be mocked
out as needed)
3. Fix pylint from complaining about the tests folder 'helpers.py' not
being found.
4. Add a pylintrc file that is used instead of the options hidden in the
'run_pylint' tool.
|
|
|
|
This splits code in apt_update_upgrade into 'apt-update-upgrade' and
'apt-configure' and 'package-update-upgrade-install'.
The 'package-update-upgrade-install' then uses the generic distro
package mechanisms for acheiving the same goal.
Also, adjusts some of the reboot backoffs and log flushing/sleeping that was
happening there.
|
|
|
|
|
|
|
|
|
|
|
|
Fix the case where a unknown type is seen and it has contents which are in
unicode. That caused python to blow-up when this happens since
'string-escape' doesn't work on unicode (at least in 2.6).
LP: #1075756
|
|
|
|
attempt the unicode-escape path.
|
|
it has contents which are in unicode which seems
to cause python to blow-up when this happens since
'string-escape' doesn't work on unicode (at least in 2.6).
LP: #1075756
|
|
LP: #1073077
|
|
1. Remove the usage of the path.join function
now that all code should be going through
the util file methods (and they can be
mocked out as needed).
2. Adjust all occurences of the above join
function to either not use it or replace
it with the standard os.path.join (which
can also be mocked out as needed)
3. Fix pylint from complaining about the
tests folder 'helpers.py' not being found
4. Add a pylintrc file that is used instead
of the options hidden in the 'run_pylint'
tool.
|
|
Use only util methods for reading/loading/appending/peeking
at files since it is likely soon that we will add a new
way of adjusting the root of files read, also it is useful
for debugging to track what is being read/written in a central
fashion.
|
|
Add a new example test that will patch utils and os
functions so that they can be 'retargeted' to a temporary
directory, which allows us the ability to run a full set
of cloud-init stages.
Neat things:
1. All cloud-init code is unchanged (as long as it goes
through the utils functions for most functionality)
2. Allows for a natural way to setup a temporary directory
then patch the new directory as the new 'root' and then
run cloud-init stages and then check the contents of
what was placed as desired.
Note:
This is now exposing what I think was just an issue in
./tools/run-pylint.
./tools/run-pylint ./tests/unittests/test_filters/test_launch_index.py
and
./tools/run-pylint ./tests/unittests/test_simple_run
was always failing, but now I'm seeing errors.
need to fix that. any tests that 'import helper' have issues.
|
|
users groups function when
its provided by the get user
function.
|
|
LP: #1065116
|
|
LP: #1070345
|
|
Create /etc/sudoers.d if not present.
Attempt to determine if /etc/sudoers.d will be used by /etc/sudoers.
If determined not, then add a line to /etc/sudoers.
|
|
|
|
|
|
|
|
Remove the need to have 'default_user' and 'default_user_groups' groups be
hard coded into the distro class, instead let that set of configuration be
located in the config file where it should be specified instead.
|
|
|
|
that removes some of the code in apt_update_upgrade
to do upgrades and installs and places it in a
generic package module and adjusts some of the
reboot backoffs and log flushing/sleeping that
was happening there.
|
|
LP: #1066115
|
|
setup properly.
|
|
LP: #1065116
|
|
|
|
differently in the rpm spec file template instead
of being joined with the release.
|
|
release number which can be to increment
cloud-init while still maintaining the
'major' cloud-init version number from bzr.
|
|
it adjusts the fstab correctly and adds
tests in that verify the actions that
should happen (also tested on a real
system).
|
|
|
|
to ensure that even if they are found that they
are also valid, before they are assumed to be
the correct device name.
|
|
Also fix the extraction of the metadata key name
since it actually uses 'dashes' instead of being
a single word.
|
|
translate the device name to a actual device using
logic that will try the ec2 metadata (if avail) or
will try using 'blkid' to find a corresponding label.
LP: #1062540
|
|
|
|
|
|
use the datetime.now(), the others get
a warning message.
|
|
since this causes rpmbuild to croak with errors like
'changelog not in descending chronological order'.
|
|
|
|
Note, I've marked this as fixing LP: #1061964, but clearly it does not.
that was fixed under revision 680.
LP: #1061964
|
|
For the cloud-init rc.d, ensure that the cloud-init-local mode is attempted
as a hard requirement (instead of the previous soft requirement) which in the
rhel5.6 case makes it not run in the right order.
|
