Default MANAGED-NOVLAN network setting not being applied properly

Bug #435130 reported by Soren Hansen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
High
Matt Zimmerman
Karmic
Fix Released
High
Matt Zimmerman

Bug Description

It turns out that our efforts to fix #425914 were insufficient. While some scripts source eucalyptus.conf, the CC parses it itself, so our shell code to source the installer-cc.conf is simply ignored.

We need to put the debconf values directly into eucalyptus.conf or optionally use the new --import-conf option from euca_conf to properly set these values.

Additionally, we need to make sure that the NC also gets the correct value set, and not just the CC.

Tags: eucalyptus
Soren Hansen (soren)
Changed in eucalyptus (Ubuntu):
milestone: none → ubuntu-9.10-beta
status: New → Triaged
importance: Undecided → Medium
Thierry Carrez (ttx)
tags: added: eucalyptus
Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu Karmic):
assignee: nobody → Soren Hansen (soren)
Revision history for this message
Colin Watson (cjwatson) wrote :

The reason I used a separate configuration file for CC_NAME was that it was entirely packaging-specific, and it saved any more fiddling around with a conffile than was absolutely necessary. I still think it's appropriate for CC_NAME to be there. For all the VNET_* stuff that's parsed by upstream code, I think installer-cc.conf is the wrong place.

Revision history for this message
Colin Watson (cjwatson) wrote :

How about this patch? It's entirely untested.

Matt Zimmerman (mdz)
Changed in eucalyptus (Ubuntu Karmic):
importance: Medium → High
assignee: Soren Hansen (soren) → nobody
Matt Zimmerman (mdz)
Changed in eucalyptus (Ubuntu Karmic):
assignee: nobody → Matt Zimmerman (mdz)
Changed in eucalyptus (Ubuntu Karmic):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu7

---------------
eucalyptus (1.6~bzr854-0ubuntu7) karmic; urgency=low

  [ Dustin Kirkland ]
  * tools/eucalyptus-nc.in: exit 0, rather than 1, in the -nc
    init script when unconfigured, related to bug LP: #430075
  * debian/eucalyptus-cc.in, debian/eucalyptus-java-ws.in: help registration
    with local sync, no rsync parameters
  * debian/eucalyptus-common.postrm: prune eucalyptus files from /etc and
    /var on package purge, essential for testing, LP: #436928

  [ Matt Zimmerman ]
  * Revert revno 573, as according to Dan Nurmi it broke registration entirely
  * Apply upstream revno 895, as according to Dan this fixes the same bug that
    revno 573 attempted to fix, but properly (without breaking registration)
  * debian/eucalyptus-cc.postinst: Guard update-rc.d remove calls so that they
    don't run on initial installation. Because -cc could be configured before
    or after -walrus/-cloud, this could cause -cc to clobber -walrus/-cloud
    init scripts on initial installation
  * tools/eucalyptus.conf: Don't try to run shell code here; it isn't (always)
    interpreted as a shell script
  * debian/eucalyptus-cc.postinst: Use euca_conf --import-conf to copy the
    network settings into eucalyptus.conf instead
  * Set the default VNET_MODE to MANAGED-NOVLAN
  * The three preceding changes close LP: #435130
  * Store the CC name in a new config file /etc/eucalyptus/eucalyptus-cc.conf
    and get rid of /etc/eucalyptus/installer-cc.conf

  [ Steve Langasek ]
  * Move eucalyptus-nc "no VT" handling for LP: #426830 to a debconf script
    instead, so that users are a bit more likely to see this.
  * Drop the dpkg-statoverride check on /var/lib/eucalyptus/keys in the
    eucalyptus-common postinst; this was ineffective anyway because we'd done
    a chown -R immediately before that, so the only part that was respecting
    statoverride were the directory perms.

 -- Dustin Kirkland <email address hidden> Sat, 26 Sep 2009 00:30:18 -0700

Changed in eucalyptus (Ubuntu Karmic):
status: Fix Committed → Fix Released
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.