maverick i386 UEC: Instance does not start
Bug #613514 reported by
Thierry Carrez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Topo1 / i386 / A3 candidate
Instance fail to start.
Messages like:
error: file /var/lib/
libvirt: monitor socket did not show up.: No such file or directory (code=38)
in nc.log
May or may not be the same as bug 610479, instance shows up with a good public and private IP for me:
RESERVATION r-4ED908D3 admin default
INSTANCE i-2F1D069A emi-4C3E1655 192.168.0.230 172.19.1.2
terminated mykey 0 c1.medium 2010-08-
cluster1 eki-A0791B5C
Revision history for this message
| Thierry Carrez (ttx) wrote | #1 |
| tags: | added: iso-testing |
Revision history for this message
| Scott Moser (smoser) wrote | #2 |
| Changed in eucalyptus (Ubuntu): | |
| importance: | Undecided → Medium |
Revision history for this message
| Thierry Carrez (ttx) wrote | #3 |
| summary: |
- Instance does not start + Mavreick i386 UEC: Instance does not start |
| summary: |
- Mavreick i386 UEC: Instance does not start + maverick i386 UEC: Instance does not start |
Revision history for this message
| Dave Walker (davewalker) wrote | #4 |
| Changed in eucalyptus (Ubuntu): | |
| status: | New → Fix Released |
Revision history for this message
| C de-Avillez (hggdh2) wrote | #5 |
To post a comment you must log in.
Thierry, does this fail 100% of the time ?