Reviewed: https://review.openstack.org/652662 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=97549a2c416873ed0ef4a497095524516386579c Submitter: Zuul Branch: master
commit 97549a2c416873ed0ef4a497095524516386579c Author: Stephen Finucane <[email protected]> Date: Mon Apr 15 14:34:55 2019 +0100 Handle unsetting '[DEFAULT] dhcp_domain' Fix a long-standing issue whereby setting 'dhcp_domain' to 'None' would result in a hostname of '${hostname}None' instead of '${hostname}'. Change-Id: Ic9aa74f5344ba469b61a87de1ebd27e6f49c3318 Closes-Bug: #1824813 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1824813 Title: Unsetting '[DEFAULT] dhcp_domain' results in hostname corruption Status in OpenStack Compute (nova): Fix Released Bug description: Unsetting '[DEFAULT] dhcp_domain' will result in the metadata service/config drive reporting an instance hostname of '${hostname}None' instead of '${hostname}'. This is clearly incorrect behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1824813/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp

