Changing VNET_SUBNET in eucalyptus.conf has no effect

Bug #800817 reported by Sasa Vilic on 2011-06-22
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Low
Unassigned

Bug Description

Uncommenting and changing VNET_SUBNET in eucalyptus.conf has no effect. Even after clean restart of eucalyptus-cloud and eucalyptus-cc,
the virtuall Machines still get IP from old subnet 172.19.0.0. The only way to change this is to edit eucalyptus.local.conf.

Since eucalyptus.local.conf should not be changed directly, there is no ordinary way to change subnet used in cloud systems.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: eucalyptus-cloud 2.0.1+bzr1256-0ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.38-8.42-server 2.6.38.2
Uname: Linux 2.6.38-8-server x86_64
.etc.eucalyptus.eucalyptus.cc.conf: CC_NAME="cluster1"
Architecture: amd64
Date: Wed Jun 22 19:55:41 2011
InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eucalyptus
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Sasa Vilic (sasavilic) wrote :
Dave Walker (davewalker) on 2011-07-14
Changed in eucalyptus (Ubuntu):
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers