| Age | Commit message (Collapse) | Author |
|---|
|
A cloud-init job (user-data) might invoke /sbin/reboot or in some other
way end up killing cloud-init. Rather than spewing the stack trace,
we just print a nicer message.
|
|
I had previously asked for this, but we're hoping to handle it in a
more generic way. Just because we receive a signal doesn't mean that
all logging is broken.
The more general solution we'll chase is to catch a failure of a log
message and fall back if necessary across the board. That way cloud-init
will still send logging to the right places on a user interupt.
|
|
the unit test required access to /dev/console due to the logging.
|
|
|
|
update_package_sources on RHEL called "yum update", which actually
upgrades packages on the system. Thix fix makes it instead call "yum
makecache" instead.
|
|
servers and add in the writing of /etc/resolv.conf in rhel from that
translation.
|
|
Network Manager (LP: #1053048), and apparently fedora/redhat do not like
comments in this file.
LP: #1052664
|
|
|
|
This adds trailing newlines to /etc/default/locale, /etc/hostname,
/etc/timezone.
|
|
Fedora and RHEL and friends' useradd program supports an "--selinux-user"
option that sets what SELinux user a new user should log in with. This commit
introduces an "selinux-user" directive to cloud-config "users" lists that
exposes this option.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the signal information in one block instead of many.
|
|
|
|
LP: #1050962
|
|
do not 'start networking' in cloud-init-nonet, but add
cloud-init-container job that runs only if in container and emits
net-device-added (LP: #1031065)
LP: #1031065
|
|
|
|
|
|
|
|
This changes the way that we avoid cloud-init-nonet hanging in a container.
Previously, under LP: #800824 we tried 'start networking', but that caused
issues described in LP: #1031065.
Here, we emit the net-device-added for any devices that have not yet been
seen.
LP: #1031065
|
|
|
|
handle those signals more gracefully and
with better messaging than what comes builtin.
|
|
LP: #1046946
|
|
This modifies /etc/default/landscape-client to have 'RUN=1' if and only
if the cloud-config (user-data or local) was non-empty.
LP: #1042758
|
|
|
|
|
|
1. Docs for launch-index + examples
2. Tests for launch-index + data files
3. Fixing a bug with cloud-archive yaml types allowed (likes a tuple not a list
for some reason) (LP: #1044594)
4. Setting the 'part' content-type if what we actually use is different.
LP: #1044594
|
|
The admin group is deprecated in 12.04, so this removes the ubuntu
user from that group (by default).
The second change here is to fix the 'set_password' for the 'password'
cloud-config. if 'password' is set in cloud_config, then
* if 'users' is given, it applies to user[0]
* if 'users' is not given, then it applies to the distro default user
LP: #1044553
|
|
|
|
support in a cloud-archive format as well as a cloud-config
format and explain how this will affect the final userdata
available to an instance.
|
|
2. Add a set of tests+data that ensure the launch index filtering
works as expected in the various modes including raw yaml
and via mime/email message formats.
|
|
its original content type said it is, make sure we set
the new value, also unsure if the old top level message
should have the same header (which will flip-flop).
|
|
indexes (since they will be handled beforehand) and fix
the types being checked on the root of the archive format
to be a tuple instead of a list (which oddly causes complaints).
|
|
Fixed change password behavior to work with new user list handling
(LP: #1044553)
|
|
EC2 and openstack provide 'launch_index' in their metadata. This allows
the user to specify cloud-config or multipart mime data that includes the
'Launch-Index' header.
If launch index is available in the metadata service, then:
* any part that contains a launch index other than the current launch-index
of this instance will be ignored.
* any part that does not contain a launch index will be considered as
for this instance.
If there is no such header, or launch_index is not available in the metadata
service, then no such filtering will be done.
LP: #1023177
|
|
- Converted user list to user dict to allow exclusion of the default user
on Ubuntu systems via cloud-config (LP: #1041384).
- Fixed bug with user creation on Ubuntu where the default user groups are
not set properly (LP: #1044044).
- Fixed documentation for user creation (LP: #1044508).
LP: #1041384, #1044044, #1044508
|
|
|
|
|
|
on Ubuntu systems via cloud-config (LP: #1041384).
- Fixed bug with user creation on Ubuntu where the default user groups are
not set properly (LP: #1044044).
- Fixed documentation for user creation (LP: #1044508).
|
|
The systemd unit files are somewhat out of date. Fixes here include telling
systemd to send stdout to a tty so it shows up in console output, updating the
ways they call cloud-init, and disabling timeouts so cloud-config work doesn't
get timed out after 90 seconds.
|
|
ensure that we recreate all child messages correctly
if they also contain submessages, ensuring that
we don't flatten the message list when we previously
used walk.
|
|
|
|
|
|
can contain filters that serve this purpose only and add in
the initial launch-index filter and replace the code in
the datasource class that previously did this.
|
|
move the section on user and group adds into
doc/examples/cloud-config-user-groups.txt
|
|
If a user hadn't been created in the image, when the public_key was to
be injected by cc_ssh into the user's account, it didn't exist yet.
This moves the population of the authorized_keys from the metadata service
into user_groups, and puts that before cc_ssh runs. moving before cc_ssh
means that when ssh comes up, the users will be ready.
ssh-import-id then handles any ssh-import-id users after networking is up.
LP: #1042459
|
