Merge lp:~smoser/maas/cleaner-shutdown into lp:maas/trunk
| Status: | Merged |
|---|---|
| Approved by: | Scott Moser on 2012-10-10 |
| Approved revision: | 1246 |
| Merged at revision: | 1250 |
| Proposed branch: | lp:~smoser/maas/cleaner-shutdown |
| Merge into: | lp:maas/trunk |
| Diff against target: |
61 lines (+30/-5) 2 files modified
contrib/preseeds_v2/enlist_userdata (+15/-1) etc/maas/commissioning-user-data (+15/-4) |
| To merge this branch: | bzr merge lp:~smoser/maas/cleaner-shutdown |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Julian Edwards (community) | 2012-10-09 | Approve on 2012-10-10 | |
|
Review via email:
|
|||
Commit Message
fix annoying cloud-init warnings caused by shutting down
when /sbin/shutdown is called from a user-data script, it ends up
making upstart kill syslog or even cloud-init itself, and cloud-init
is somewhat annoying about it to the console.
This ensures that cloud-final (the job that runs user-scripts) has
finished before shutting down.
Description of the Change
fix annoying cloud-init warnings caused by shutting down
when /sbin/shutdown is called from a user-data script, it ends up
making upstart kill syslog or even cloud-init itself, and cloud-init
is somewhat annoying about it to the console.
This ensures that cloud-final (the job that runs user-scripts) has
finished before shutting down.
| Scott Moser (smoser) wrote : | # |
This change removes the polling and the status output.
Reguarding the copied code, I dont like it either.
We can and should re-factor the way user-data is created so that we can re-use the code more effectively. Thats a more invasive change though.
| MAAS Lander (maas-lander) wrote : | # |
No commit message specified.


Is there any way of factoring the common code in the enlist and commissioning user data? If there's a bug in it (which is hard to tell, since we don't have tests) then it'll be in two places.
16 + echo "$state [$2] after $i"
39 + echo "$state [$2] after $i"
This is a poor message, can you make it something like:
"After $i seconds, cloud-final still in state $2"
and then at the top of the function please add something like
echo "Waiting for cloud-final to shut down."
Also, some capital letters and punctuation would not go amiss (we're sticklers for that in the Launchpad^WCloud Engineering team).
Approved if you ran and tested this.