From dff95122f79c83e7e3b108b12e6b8a48aa62c01d Mon Sep 17 00:00:00 2001
From: Dean Troyer <dtroyer@gmail.com>
Date: Thu, 10 Jan 2013 20:51:28 -0600
Subject: [PATCH] Fix EXTRA_OPTS handling

In the conversion away from add_nova_opt the EXTRA_OPTS handling
inadvertently replaced all '=' chars in the value rather than
just the first.  Additional '=' is legal for an option value.

FWIW here is the setting that tripped it:
EXTRA_OPTS=default_log_levels=sqlalchemy=WARN,boto=WARN,eventlet.wsgi.server=WARN

Change-Id: I2deb139171250eb0ef5028bb924569cec31e1a4e
---
 lib/nova | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/nova b/lib/nova
index 781cc0972f..a987008b4c 100644
--- a/lib/nova
+++ b/lib/nova
@@ -432,8 +432,8 @@ function create_nova_conf() {
     # Define extra nova conf flags by defining the array ``EXTRA_OPTS``.
     # For Example: ``EXTRA_OPTS=(foo=true bar=2)``
     for I in "${EXTRA_OPTS[@]}"; do
-        # Attempt to convert flags to options
-        iniset $NOVA_CONF DEFAULT ${I//=/ }
+        # Replace the first '=' with ' ' for iniset syntax
+        iniset $NOVA_CONF DEFAULT ${I/=/ }
     done
 }