network state is lost if the cluster controller (CC) is stopped
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Karmic |
Fix Released
|
Medium
|
Mathias Gug |
Bug Description
in the eucalyptus-cc upstart script, the line:
rm -f /var/lib/
will always clear all CC state when the service is stopped. The upstream init scripts use:
stop/start/restart
to control the service while maintaining CC state (stored in /var/lib/
cleanstop/
will remove the state. With upstart, an idea is to wrap the above line in a conditional that will only be true if a variable is defined on the cmdline (i.e. the default behavior would be to leave the state, and if an admin really wanted to start from a clean state, or re-read the config file, they would have to set the variable on the cmdline):
start eucalyptus-cc CLEAN=1
stop eucalyptus-cc CLEAN=1
restart eucalyptus-cc CLEAN=1
and in the file:
if ( test "$CLEAN" == "1" ); then
rm -f /var/lib/
fi
-Dan
===================
SRU verification
Impact:
If the CC is restarted or rebooted (to be exact if eucalyptus-cc is stopped) all the network configuration for running instances is lost.
How the bug has been addressed:
The post script of the eucalyptus-cc upstart job has been modified to only delete the network state file if the CLEAN environment variable has been set to 1.
To reproduce the bug:
1. Install a CC and one NC.
2. Start an instance with a public IP and log into the running instance.
3. Reboot the CC.
4. After the CC has rebooted, the running instance cannot be accessed via its previous public IP.
5. Once the CC has been upgraded, a reboot of the CC should not prevent login into running instances using their previously assigned public IP.
Regression potential:
The discover-ability of the new CLEAN option may be improved.
===================
Related branches
- Dustin Kirkland : Needs Fixing
-
Diff: 24 lines2 files modifieddebian/changelog (+2/-0)
debian/eucalyptus-cc.upstart (+1/-2)
Changed in eucalyptus (Ubuntu): | |
status: | Incomplete → Triaged |
Changed in eucalyptus (Ubuntu Karmic): | |
milestone: | none → karmic-updates |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in eucalyptus (Ubuntu Karmic): | |
assignee: | nobody → Mathias Gug (mathiaz) |
Changed in eucalyptus (Ubuntu Karmic): | |
status: | Triaged → In Progress |
description: | updated |
Changed in eucalyptus (Ubuntu Karmic): | |
status: | In Progress → Fix Committed |
tags: | added: uec |
Could you explain what exactly this "network state" covers and why we would generally like to keep it over CC restarts or system reboots ?