cc looses database information after restart

Bug #742443 reported by Christoph Martin on 2011-03-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eucalyptus
Invalid
Undecided
Daniel Nurmi
eucalyptus (Ubuntu)
Medium
Unassigned

Bug Description

When doing

restart eucalyptus-cc

(not 'restart eucalyptus-cc CLEAN=1') the cc database information are lost.

iptables-save does not show anymore the forwarding/nat rules for the vm's

also the file //var/run/eucalyptus/net/euca-dhcp.conf does not anymore include the dhcp information for the vm's

I know that there existed an old bug, but it was reported as fixed some time ago.

I tried version 2.0+bzr1241-0ubuntu4.1 from maverick and 2.0.1+bzr1256-0ubuntu2 from natty.

The problem persists in both versions.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: eucalyptus-cc 2.0.1+bzr1256-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-27.48-server 2.6.35.11
Uname: Linux 2.6.35-27-server x86_64
.etc.eucalyptus.eucalyptus.cc.conf: CC_NAME="cluster1"
Architecture: amd64
Date: Fri Mar 25 14:10:45 2011
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eucalyptus

Revision history for this message
Christoph Martin (martin-uni-mainz) wrote :
Dave Walker (davewalker) on 2011-04-19
Changed in eucalyptus (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Daniel Nurmi (nurmi) on 2011-04-25
Changed in eucalyptus:
assignee: nobody → Daniel Nurmi (nurmi)
Revision history for this message
Daniel Nurmi (nurmi) wrote :

This is a UEC upstart init script related issue; marking as invalid against the eucalyptus upstream.

Changed in eucalyptus:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers