lp:~dpb/cloud-init/fix-landscape-init-example

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~cloud-init-dev/cloud-init/trunk at revision 939

cloud-init Commiters: Pending requested 2014-02-10

Diff: 15 lines (+4/-4)

1 file modified

doc/examples/cloud-config-landscape.txt (+4/-4)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1277746: landscape module not working

Low

Fix Released

Link a bug report

Related blueprints

940. By David Britton on 2014-02-10

oops

939. By David Britton on 2014-02-10

properlly format the landscape example

938. By Scott Moser on 2014-02-10

DataSourceEc2: Fix incorrect return in _get_url_settings

get_url_settings should return a pair of max wait and timeout and not
false, fix this bug by checking the max_wait <= 0 in the calling function
and returning correctly from there instead.

937. By Scott Moser on 2014-02-10

rpm build fixes

- failing build due to missing Requires (changed to requirements.txt)
- RH: require sudo >= 1.7.2p2-3 (with sudoers.d/)

936. By Scott Moser on 2014-02-10

Azure: fix issue with stale data in /var/lib/waagent

If a datasource was found other than in /var/lib/waagent, and /var/lib/waagent
contained all the files necessary for 'wait_for_files' (most likely
'SharedConfig.xml'), then cloud-init would continue on before looking properly.

To address this, if the ovf-env.xml came from somewhere other than
/var/lib/waagent, and it differs from the file in /var/lib/waagent, then
we clean up some files that we expect to be provided by 'wait_for_files'.

Also some minor changes to the tests here.

935. By Scott Moser on 2014-01-29

DataSourceNoCloud: support reading vendor-data

Here we add the ability to read vendor-data from a file named
vendor-data at the same location as the user-data and meta-data files.

At the moment, vendor-data is not read at all from 'seedfrom'.

934. By Vlastimil Holer on 2014-01-28

util.is_ipv4: realize that 0 is a valid number in a ipv4 address.

Due to bug in function "cloudinit.util.is_ipv4" an IPv4 address with zero (0)
at any component wasn't evaluated as IPv4 address.

E.g.: having local datasource with 192.168.0.1 in meta-data/local-hostname. The
correct behaviour would be to generate ip-192-168-0-1 hostname. With this bug,
the hostname (with IPv4) was considered as FQDN (no IPv4 inside) and just first
component (supposed to be hostname there) was taken. It generated hostname
"192".

Fixes for SmartOS datasource

1. fixed conflation of user-data and cloud-init user-data. Cloud-init
   user-data is now namespaced as 'cloud-init:user-data'.
2. user-scripts (not user-data) are now fetched from the meta-data service
   each boot and executed as in the scripts directory
3. datacenter name is now namespaced as sdc:datacenter
4. user-scripts will now have '#!/bin/bash' magically prepended
   if the 'file' thinks its plain text and it does not start with '#!'

read_file_or_url: raise UrlError with 404 on ENOENT

This makes it easier to call read_file_or_url and handle file or url
errors. Now read_file_or_url will raise a UrlError in either case
on errors.

933. By Scott Moser on 2014-01-25

read_file_or_url: raise UrlError with 404 on ENOENT

This makes it easier to call read_file_or_url and handle file or url
errors. Now read_file_or_url will raise a UrlError in either case
on errors.

932. By Joshua Harlow on 2014-01-25

Don't try to create members if group creation fails

931. By Joshua Harlow on 2014-01-25

Fix logexc usage in freebsd distro

- There appeared to be a few logexc calls
  that did not pass the logger in, fix those
  locations where this occured.
- When a group member adding fails, log the
  error and try the next member instead of
  failing adding any more members