transient network/keyscan issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Won't Fix
|
Low
|
Scott Moser | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
Natty |
Invalid
|
Low
|
Scott Moser |
Bug Description
Binary package hint: cloud-init
In maverick release testing (20101007.1) I found a transient-ish network failure.
Here, out of 18 instances in this test 4 of them did not have ssh keys per keyscan. Subsequently those 4 failed the ssh connection test.
Then, one instance that *passed* the connection test failed the root connection test.
I also saw a similar issue, again x86_64 and us-west-1, when testing maverick RC. There, I 7 keys out of 36 found. Again, very strange, all but one of the ssh connections passed after ssh keyscan had major issues.
I think part of this might be an issue with ssh-keyscan, where failure of one host in the arguments causes failure of others.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: cloud-init 0.5.15-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-22-virtual x86_64
Architecture: amd64
Date: Fri Oct 8 03:03:39 2010
Ec2AMI: ami-681f4f2d
Ec2AMIManifest: ubuntu-
Ec2Availability
Ec2InstanceType: m1.large
Ec2Kernel: aki-9ba0f1de
Ec2Ramdisk: unavailable
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
tags: | added: iso-testing |
Changed in cloud-init (Ubuntu Natty): | |
assignee: | nobody → Scott Moser (smoser) |
Note, only a cloud-init bug because I have no better location.