** Changed in: eucalyptus
Status: New => Fix Released
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
** Branch linked: lp:~ubuntu-virt/ubuntu/maverick/eucalyptus/2.0
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Branch linked: lp:ubuntu/eucalyptus
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
This bug was fixed in the package eucalyptus - 2.0~bzr1231-0ubuntu1
---
eucalyptus (2.0~bzr1231-0ubuntu1) maverick; urgency=low
* New upstream snapshot, -r1231, bugs fixed by upstream:
- LP: #566792 - metadata service returns empty data with 200 OK
- LP: #606243 - euca-descr
** Changed in: eucalyptus (Ubuntu Maverick)
Assignee: Dave Walker (davewalker) => Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu Maverick)
Status: Triaged => In Progress
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification
Reopening. On my first test run on r1230 I got the following results:
2010-08-13 15:16:03,002 SUMMARY:INFO not-tested=16
2010-08-13 15:16:03,002 SUMMARY:INFO being-tested=0
2010-08-13 15:16:03,002 SUMMARY:INFO success=130
2010-08-13 15:16:03,002 SUMMARY:INFO failed=54
2010-08-13 15:16:03,002 SUMMA
Marking fixed release, as the fix is now released :)
** Changed in: eucalyptus (Ubuntu Maverick)
Status: Fix Committed => Fix Released
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Recent results indicate that this issue is fixed in an upstream
snapshot.
** Changed in: eucalyptus (Ubuntu Maverick)
Status: Confirmed => Fix Committed
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
** Changed in: eucalyptus (Ubuntu Maverick)
Assignee: (unassigned) => Dave Walker (davewalker)
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
logs uploaded:
bzr+ssh://bazaar.launchpad.net/~hggdh2/%2Bjunk/uec-qa/
Pushed up to revision 28.
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Seems to still happen on r1219. I have just ran a small (200) instances
test, and I got one such error. I will be uploading the logs to the bzr
repository in a few.
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubu
Could you verify this is still happening with the latest commits? I
guess one of my fixes solves the problem.
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Also affects: eucalyptus (Ubuntu Maverick)
Importance: High
Status: Confirmed
** Changed in: eucalyptus (Ubuntu Maverick)
Milestone: maverick-alpha-3 => ubuntu-10.10-beta
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because
milestoning to Alpha3
** Changed in: eucalyptus (Ubuntu)
Milestone: None => maverick-alpha-3
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
@Dave W:
> Is this behavior presenting similar characteristics to the pre SRU
Lucid (1.6.2) version?
no, signature is distinct. On bug 566792 we would have the instance
startup and reach RUNNING, with both private and public IPs set to the
same (private). Here the instance does not ever seen to g
@C de-Avillez: Is this behavior presenting similar characteristics to
the pre SRU Lucid (1.6.2) version? Is it totally unrelated to bug
#566792 ?
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => High
** Changed in: eucalyptus (Ubuntu)
Status: New => Confirmed
--
Instance fails to start
https://bugs.launchpad.net/bugs/610479
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I searched the logs for one such instance:
ubu...@cempedak:/var/log/eucalyptus$ grep i-58C70904 *
cc.log.2:[Mon Jul 26 20:32:27 2010][013178][EUCADEBUG ] RunInstances(): running
instance i-58C70904 with emiId emi-3C7E1C5B...
cc.log.2:[Mon Jul 26 20:42:45 2010][013178][EUCADEBUG ] TerminateInstanc
19 matches
Mail list logo
