metadata server cannot be contacted when deploying new instances on EUC
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
## Issue
New instances deployed on EUC cannot contact the metadata server, failing with Connection refused.
## Environment
Distributor ID: Ubuntu
Description: Ubuntu Natty (development branch)
Release: 11.04
Codename: natty
ii eucalyptus-
ii eucalyptus-cc 2.0.1+bzr1256-
ii eucalyptus-cloud 2.0.1+bzr1256-
ii eucalyptus-common 2.0.1+bzr1256-
ii eucalyptus-gl 2.0.1+bzr1256-
ii eucalyptus-
ii eucalyptus-sc 2.0.1+bzr1256-
ii eucalyptus-walrus 2.0.1+bzr1256-
ii libeucalyptus-
## Resolution
- reinstalling usually fixes the issue, but this is suboptimal
## Diagnostic Steps
euca-get-
lxcmount stop/pre-start, process 47
init: udev-fallback-
init: plymouth main process (49) killed by SEGV signal
init: plymouth-splash main process (259) terminated with status 2
cloud-init start-local running: Mon, 18 Apr 2011 22:05:50 +0000. up 7.14 seconds
no instance data found in start-local
init: cloud-init-local main process (255) terminated with status 1
cloud-init start running: Mon, 18 Apr 2011 22:05:50 +0000. up 7.70 seconds
2011-04-18 22:05:50,859 - DataSourceEc2.
2011-04-18 22:05:50,861 - DataSourceEc2.
2011-04-18 22:05:51,864 - DataSourceEc2.
2011-04-18 22:05:52,868 - DataSourceEc2.
...
2011-04-18 19:55:09,908 - DataSourceEc2.
2011-04-18 19:55:15,917 - DataSourceEc2.
found data source: DataSourceEc2
mountall: Event failed
Opening http://
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: eucalyptus-cloud 2.0.1+bzr1256-
ProcVersionSign
Uname: Linux 2.6.38-8-server x86_64
.etc.eucalyptus
Architecture: amd64
Date: Mon Apr 18 18:24:52 2011
ProcEnviron:
LANGUAGE=en_US:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: eucalyptus
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in eucalyptus (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Reinstalling fixes the issue on Maverick, but not fully tested on 11.04, which could be a different issue.