Empty option values no longer allowed

[Mark McLoughlin]

As reported here:

  http://lists.openstack.org/pipermail/openstack-dev/2012-July/000075.html

  Looks like the new openstack-common changes can't handle a line that has an
  empty value like:

    api_extensions_path =

  You should be able to work around it just by changing the line to:

    api_extensions_path = ""

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/9891

[yong sheng gong (gongysh)]

I think we should comment this line since the default value of this option service this purpose well.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/9891
Committed: http://github.com/openstack/openstack-common/commit/ace759e55d7c87dc66a500d598d1355dd3c0408f
Submitter: Jenkins
Branch: master

commit ace759e55d7c87dc66a500d598d1355dd3c0408f
Author: Mark McLoughlin <email address hidden>
Date: Tue Jul 17 05:52:51 2012 +0100

    cfg: allow empty config values

    Fixes bug #1025522

    Commit 83044a7 caused this to stop working in Quantum:

      api_extensions_path =

    and could only be worked around with:

      api_extensions_path = ""

    Change-Id: I8c1a57225a2c135e6baf567b8e71d61e974da4e2