Both blocking bugs have been fixed, so we'll suppose it's fixed now.
Please reopen if you can still reproduce it. I will conduct some testing
on instance-running soon and will reopen/file new bugs if any issue
remains.
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Tags added: eucalyptus
--
Instance fail to run
https://bugs.launchpad.net/bugs/429754
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Etienne, could you check the the node controller is running as the
eucalyptus user and that the eucalyptus user is a member of the libvirtd
group? Also, does /var/run/eucalyptus exist on the node controller?
** Changed in: eucalyptus (Ubuntu)
Status: New = Incomplete
--
Instance fail to
Unfortunately, I had to revert back to 1.5 for a specific project, and I
do not have the hardware to run two clusters in parallel (a stable one
on jaunty/1.5, and one for testing on karmic/1.6). I will not be able
to test any earlier than late next week. Sorry! :(
--
Instance fail to run
I believe that there are two problems here; first, the latest
apparmor/libvirt is preventing the NC from being able to start VMs:
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/431090
second, the 'nc-stat' error is caused by /var/run/eucalyptus directories
are not getting the right
** Attachment added: nc.log
http://launchpadlibrarian.net/31806315/nc.log
--
Instance fail to run
https://bugs.launchpad.net/bugs/429754
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
