lp:~therve/cloud-init/landscape-conf-permissions

Branch merges

Propose for merging

No branches dependent on this one.

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

cloud-init Commiters: Pending requested 2012-10-15

Diff: 24 lines (+5/-2)

1 file modified

cloudinit/config/cc_landscape.py (+5/-2)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1066115: The landscape client plugin doesn't create the config file with the proper permissions

Medium

Fix Released

Link a bug report

Related blueprints

687. By Thomas Herve on 2012-10-15

Skip install when there is not configuration, and install the package to be setup properly.

686. By Joshua Harlow on 2012-10-08

Merge rpm subrelease branch.

685. By Joshua Harlow on 2012-10-05

Bring in the config drive fixes so that
it adjusts the fstab correctly and adds
tests in that verify the actions that
should happen (also tested on a real
system).

684. By Joshua Harlow on 2012-10-05

Merged brpm changelog fixes

683. By Scott Moser on 2012-10-05

bump version to 0.7.1

682. By Scott Moser on 2012-10-05

update ChangeLog for previous 2 commits.

Note, I've marked this as fixing LP: #1061964, but clearly it does not.
that was fixed under revision 680.

681. By Joshua Harlow on 2012-10-05

sysvinit: fix cloud-init job for RHEL 5.6

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.

680. By Joshua Harlow on 2012-10-05

config-drive: map hostname to local-hostname

Ensure that for config drive that we map 'hostname' to 'local-hostname' so that
the modules work correctly with the cfgdrive style of data.

679. By Scott Moser on 2012-10-01

fix tools/make-dist-tarball

678. By Scott Moser on 2012-10-01

fix oauth time skew. actual implementation was returning 401 not 403.

This fixes (tested) bug 978127. The server was actually returning a 401
not a 403. As such, the fix here was insufficient. This will now take
either of those 2 error codes. I've also tested it by changing the clock
in the cloud-init upstart job with a stanza like below, and verifying
that we do see the problem and then it resolve itself:

  pre-start script
    offset="10 minutes ago"
    past=$(date -R --date "$offset")
    date --set "$past" &&
      echo ===== "set date to $past [$offset]" ===== ||
      echo ===== "failed to set date to $past [$offset]" ====
  end script