seed_random runs too early if local datasource used

Bug #1322692 reported by Scott Moser on 2014-05-23
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)

Bug Description

right now, seed_random is running in 'cloud_init_modules'.
The reason for that was to ensure that it ran before the ssh config module (which writes the ssh keys).

The problem is that cloud_init_modules is not guaranteed to have network access, and we're running 'pollinate -q', which depends on network.

the result is that if you seed an image (cloud-localds) or use config-drive, pollinate will/may run before network is available.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cloud-init 0.7.5-0ubuntu1
ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
Date: Fri May 23 16:09:11 2014
Ec2AMI: ami-00000005
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
PackageArchitecture: all
 PATH=(custom, no user)
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)

Scott Moser (smoser) wrote :
Changed in cloud-init (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Changed in cloud-init:
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers