Age | Commit message (Collapse) | Author |
|
It had been changed in code, but not in docs. So we needed
to reflect the change in docs as well so that both are in
sync.
|
|
Now, errors will not be so annoying if the device doesn't exist.
Specifically, if there is no device in a container, only debug messages
will be logged.
LP: #1160462
|
|
In starting containers in lxc, I was seeing errors like:
/proc/self/fd/9: 24: kill: No such process
Which indicated the sleep pid had already died.
I'm not sure how or why it was dead, but this just is less annoying in that
case.
|
|
|
|
This re-works the urlhelper and users of it to use requests rather
than urllib2. The primary benefit is that now when using recent
versions of python-requests (>= 0.8.8) https certificates will be checked.
|
|
|
|
cloudinit/sources/DataSourceCloudStack.py and
cloudinit/sources/DataSourceEc2.py are reverted entirely back to trunk versions
now, rather than the non-behavior change that was left in place.
Also, remove inadvertantly added trailing newline from cloudinit/ec2_utils.py
Overall, this just makes the diff when merged to trunk carry more focused
changes.
|
|
|
|
|
|
|
|
this shouldn't change anything, only the signatures of the methods.
|
|
the previous implementation of url_helper.readurl() would default
to allow_redirects being true.
So, for backwards compat, we should keep that behavior.
|
|
if the error is an ssl error, its extremely unlikely that it would be fixed by
waiting a few seconds and trying again.
|
|
* cloudinit/distros/parsers/resolv_conf.py
added some pylint overrides with 'plXXXXX' syntax.
example: # pl51222 pylint: disable=E0102
The pl51222 there means: http://www.logilab.org/ticket/51222
This specific issue is present in 12.04 pylint, but not 13.04.
* pylint doesn't like the requests special handling we have.
which makes sense as it is only checking versus one specific version.
* general pep8 and pylint cleanups.
|
|
|
|
a.) appease pylint on raring, as it doesn't like subprocess
pylint: 0.26.0-1ubuntu1
This is mentioned in comments at http://www.logilab.org/ticket/46273
b.) tests/unittests/test_util.py:
the mountinfo lines are longer than 80 chars.
Just disable long lines complaints for this file.
|
|
|
|
in earlier versions of requests (pre 0.10.8).
|
|
|
|
As reported in bug 1154599, I'm seeing this on my desktop system:
$ python -c \
'from cloudinit import util; print util.is_resolvable("brickies.neiit")'
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "cloudinit/util.py", line 865, in is_resolvable
socket.SOCK_STREAM, socket.AI_CANONNAME)
LP: #1154599
|
|
1) Refactor util.get_mount_info() to facilitate unit testing.
2) Add unit tests for /proc/$$/mountinfo parsing.
|
|
This re-applies the change in revno 785.
A merge made this test pass rather than skip, but I'd rather have
it skip for now, as we really hope to have the upstart bug fixed.
|
|
|
|
|
|
Refactor the parsing portion of util.get_mount_info() into a new
util.parse_mount_info() method. Now util.get_mount_info() opens
/proc/$$/mountinfo, splits on newlines and passes the lines to
util.parse_mount_info().
|
|
|
|
This adds a very useful mechanism for merging cloud-config, allowing
the user to append to lists (ie, just add more 'run_cmd') or other
things.
See doc/merging.txt for more information, it is intended to be backwards
compatible by default.
LP: #1023179
|
|
|
|
|
|
the default merge type here was appending to strings and extending lists.
Instead we want the same default that cloud-init had previously, which was to
overwrite lists and strings.
|
|
|
|
|
|
E1103: 81,44:TestWriteFile.test_basic_usage: Instance of 'Bunch' has no
'st_mode' member (but some types could not be inferred)
so, if it wants st_mode, for now just give it one.
|
|
This allows the customization of the apt-get command used for installing
packages, and also adds '--force-unsafe-io'. Because this is spawned from
cloud-init, it seems to make sense as a first boot package installation
option.
|
|
|
|
|
|
|
|
|
|
|
|
This adds support for resizing partition tables for mounted partitions.
It thus allows us to remove 'cloud-initramfs-growpart' from running in
the initramfs, and do it here instead.
That depends on:
a.) growpart in cloud-utils 0.2.7 or later
or
parted with 'resizepart' support
b.) kernel 3.8.
|
|
|
|
resize_devices now contains what action occurred for each entry.
|
|
|
|
|
|
growrun --dry-run will exit 1 if it wouldn't do anything.
so call it, check for '1' and if no change, then just return.
|
|
|
|
|
|
|
|
|
|
this fixes a confusing message, most commonly found in /var/log/dmesg
or seen on log screens:
init: cloud-init-nonet main process (307) killed by TERM signal
This was actually *expected* as the upstart job was supposed to block
until networking came up, and the SIGTERM was sent by upstart.
That said, the message was confusing. Now, instead we will see something like
cloud-init-nonet[6.54]: waiting 10 seconds for network device
cloud-init-nonet[12.13]: static networking is now up
Which is much nicer. In the event that networking does not come up
you'll see:
cloud-init-nonet[X.Y]: gave up waiting for a network device.
LP: #1015223
|