Not obvious a "Clean" restart is needed after config changes
Bug #464384 reported by
Thierry Carrez
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland | ||
Lucid |
Fix Released
|
High
|
Dustin Kirkland |
Bug Description
On regular restarts (once bug 460089 is fixed) the CC will retain network state so that active VMs can continue to run.
If the CC network configuration is changed in /etc/eucalyptus
We might need to make it more apparent to the user, by providing a eucalyptus-
Changed in eucalyptus (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in eucalyptus (Ubuntu Lucid): | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
I'm actually raising this priority to High.
I've been struggling with this (silly) problem for a couple of days now, wondering why my changes aren't taking effect.
This should be documented in the manpage, and *possibly* in line in the eucalyptus. (local. )conf files. We should knock this out at the sprint.