cloud-final job did not run in ec2-automated-tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: cloud-init
In natty beta-1 testing, we had 2 occurrences where it appears the upstart job cloud-final did not run after 15 minutes of waiting.
This occurred once on eu-west-1 and ap-southeast-1. both were m1.small (i386).
I will attach the console output of each. Note, that in that console output, the '[]' is from the 'timezone' cloud-config plugin. This gives us info that cloud-init-config had gotten past the 'apt-update-
cloud-config upstart job has:
start on (filesystem and started rsyslog)
cloud-config-final upstart job has:
start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config)
[1] http://
[2] http://
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: cloud-init 0.6.1-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.38-7-virtual i686
Architecture: i386
Date: Wed Mar 30 18:27:30 2011
Ec2AMI: ami-183b424a
Ec2AMIManifest: ubuntu-
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-13d5aa41
Ec2Ramdisk: unavailable
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | added: iso-testing |
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
summary: |
- cloud-final job did not run + cloud-final job did not run in ec2-automated-tests |
tags: | added: server-nrs |
it would seem to me that the most likely cause for cloud-final not running would be something blocked in sysvinit scripts.