Bug 7084 – Explicit MAC->IP mappings are ignored after service restart

Bug 7084 - Explicit MAC->IP mappings are ignored after service restart

Summary:

Explicit MAC->IP mappings are ignored after service restart

Status:	RESOLVED FIXED

Product:	Nimbus
Component:	Workspace service
Version:	2.5
Platform:	PC All

Importance:	P3 normal
Target Milestone:	2.6
Assigned To:	Tim Freeman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-06 16:30 by David LaBissoniere
Modified:	2010-09-30 18:11 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From David LaBissoniere 2010-08-06 16:30:18

After the network-pools file is modified, explicit MAC mappings are loaded on
the next service boot. However subsequent boots will disregard these mappings
and generate new ones, unless the network pools file has been modified again.

A workaround is to touch the network pools file before each service restart.

------- Comment #1 From David LaBissoniere 2010-08-06 16:47:01 -------

You can embed a workaround into the container startup script,
$NIMBUS_HOME/libexec/run-services.sh

Add the following at line 6:

touch $NIMBUS_HOME/services/etc/nimbus/workspace-service/network-pools/*


So, for example:

#!/bin/bash

NIMBUS_HOME_REL="`dirname $0`/.."
NIMBUS_HOME=`cd $NIMBUS_HOME_REL; pwd`

touch $NIMBUS_HOME/services/etc/nimbus/workspace-service/network-pools/*

.....

------- Comment #2 From David LaBissoniere 2010-09-30 18:11:14 -------

A fix for this issue was committed to master:

http://github.com/nimbusproject/nimbus/commit/456b63bf4968cb5288ea492fcaaf7d9ffbba877c