Changing networking mode left cloud non working

Bug #514203 reported by Torsten Spindler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
New
Undecided
Unassigned

Bug Description

During the UEC class this week using Ubuntu 9.10 the following problem surfaced:

The cloud was fully operational. The networking mode was changed from MANAGED_NOVLAN to SYSTEM. After rebooting the front-end and node no instance could be started anymore. The instance was left pending and then terminated after a few minutes. Next the networking mode was changed back to MANAGED_NOVLAN. Neither a reboot nor a restart of eucalyptus on front end and node changed the behaviour, e.g. no more instances can be started.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

You need to perform a clean restart of Eucalyptus to discard some system state.

I strongly believe this is a duplicate of Bug #464384.

Revision history for this message
Torsten Spindler (tspindler) wrote :

The complete cloud (frontend and node) was rebooted.

Revision history for this message
Torsten Spindler (tspindler) wrote :

You are right, it is a duplicate, the following worked:
$ sudo restart eucalyptus CLEAN=1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.