Activity log for bug #1805645

Date Who What changed Old value New value Message
2018-11-28 15:02:42 Pedro Guimarães bug added bug
2018-11-28 15:14:40 Pedro Guimarães bug added subscriber Canonical Field Critical
2018-11-28 15:35:45 Pedro Guimarães description We are facing an issue to configure metadata service correctly. Neutron API charm's dns-domain was configured for an specific value but nova metadata service continues to return original "NAME_OF_SERVER.novalocal." as hostname. dns-domain seems to correctly configure DHCP domain name. However, not all types of Guest OS follow DHCP's definition of domain. RHEL-based guest OS, for example, set their hostnames to the value present on metadata service despite DHCP's original configuration. Although one can work-around this by using user_data flag on "openstack server create" and setting "preserve_hostname: true", there are situations where this is not feasible (e.g. when OpenStack is under management of an orchestrator). We have a request to setup Designate to register all machines that are connected to a self-service network. That deployment is using BGP to advertise that SSN. On a particular customer, we have the following configuration set: Neutron-api: https://pastebin.canonical.com/p/vPhfkCbdw6/ Please, check that vni_ranges jump on one value, that was necessary to make the SSN available to Designate, as described on: https://docs.openstack.org/mitaka/networking-guide/config-dns-int.html Nova-cloud-controller: https://pastebin.canonical.com/p/yThtgY95BT/ Neutron-Gateway: https://pastebin.canonical.com/p/q97hqfgMCP/ Neutron-Openvswitch: https://pastebin.canonical.com/p/MPJ3zKSYxK/ We are facing an issue to configure metadata service correctly. Neutron API charm's dns-domain was configured for an specific value but nova metadata service continues to return original "NAME_OF_SERVER.novalocal." as hostname. dns-domain seems to correctly configure DHCP domain name. curl http://169.254.169.254/openstack/latest/meta_data.json returns: {"random_seed": "redacted", "type": "ssh", "name": "dnstest"}], "hostname": "tdnsserver.novalocal", "launch_index": 0, "devices": [], "public_keys": {"dnstest": "redacted"}, "project_id": "redacted", "name": "tdnsserver"} While /var/lib/dhclient/dhclient.leases contains the correct domain name. However, not all types of Guest OS follow DHCP's definition of domain. RHEL-based guest OS, for example, set their hostnames to the value present on metadata service despite DHCP's original configuration. Although one can work-around this by using user_data flag on "openstack server create" and setting "preserve_hostname: true", there are situations where this is not feasible (e.g. when OpenStack is under management of an orchestrator). We have a request to setup Designate to register all machines that are connected to a self-service network. That deployment is using BGP to advertise that SSN. On a particular customer, we have the following configuration set: Neutron-api: https://pastebin.canonical.com/p/vPhfkCbdw6/ Please, check that vni_ranges jump on one value, that was necessary to make the SSN available to Designate, as described on: https://docs.openstack.org/mitaka/networking-guide/config-dns-int.html Nova-cloud-controller: https://pastebin.canonical.com/p/yThtgY95BT/ Neutron-Gateway: https://pastebin.canonical.com/p/q97hqfgMCP/ Neutron-Openvswitch: https://pastebin.canonical.com/p/MPJ3zKSYxK/
2018-11-28 16:12:46 Ryan Beisner charm-neutron-gateway: importance Undecided High
2018-11-28 16:12:52 Ryan Beisner charm-neutron-gateway: assignee David Ames (thedac)
2018-11-28 16:12:56 Ryan Beisner charm-neutron-gateway: milestone 19.04
2018-11-28 17:48:48 David Ames charm-neutron-gateway: status New Triaged
2018-11-28 17:57:59 OpenStack Infra charm-neutron-gateway: status Triaged In Progress
2018-11-28 18:41:55 David Ames bug task added charm-neutron-api
2018-11-28 18:42:09 David Ames bug task added charm-nova-cloud-controller
2018-11-28 18:42:21 David Ames charm-neutron-api: status New Triaged
2018-11-28 18:42:22 David Ames charm-neutron-api: importance Undecided Medium
2018-11-28 18:42:24 David Ames charm-neutron-api: assignee David Ames (thedac)
2018-11-28 18:42:27 David Ames charm-neutron-api: milestone 19.04
2018-11-28 18:42:32 David Ames charm-nova-cloud-controller: status New Triaged
2018-11-28 18:42:35 David Ames charm-nova-cloud-controller: importance Undecided Medium
2018-11-28 18:42:37 David Ames charm-nova-cloud-controller: assignee David Ames (thedac)
2018-11-28 18:42:39 David Ames charm-nova-cloud-controller: milestone 19.04
2018-11-28 18:44:50 OpenStack Infra charm-neutron-api: status Triaged In Progress
2018-11-28 19:28:53 OpenStack Infra charm-nova-cloud-controller: status Triaged In Progress
2018-11-28 19:34:24 Vern Hart bug added subscriber Vern Hart
2018-11-29 18:34:18 David Ames charm-neutron-gateway: status In Progress Fix Released
2018-11-29 18:34:29 David Ames charm-neutron-api: status In Progress Fix Committed
2018-11-30 00:39:49 Chris Newcomer bug added subscriber Chris Newcomer
2018-11-30 15:55:19 David Ames charm-nova-cloud-controller: status In Progress Fix Committed
2018-12-06 11:55:28 James Page charm-neutron-api: status Fix Committed Fix Released
2018-12-06 11:55:29 James Page charm-nova-cloud-controller: status Fix Committed Fix Released
2020-01-09 15:47:26 David Ames bug task added charm-nova-compute
2020-01-09 15:47:37 David Ames charm-nova-compute: status New In Progress
2020-01-09 15:47:41 David Ames charm-nova-compute: importance Undecided High
2020-01-09 15:47:43 David Ames charm-nova-compute: assignee David Ames (thedac)
2020-01-09 15:47:54 David Ames charm-nova-compute: milestone 20.02
2020-02-12 14:47:09 James Page charm-nova-compute: status In Progress Fix Committed
2020-02-17 17:26:35 Liam Young charm-nova-compute: status Fix Committed Fix Released
2020-05-14 21:30:27 David Ames charm-nova-compute: status Fix Released Triaged
2020-05-14 21:38:37 David Ames charm-nova-compute: status Triaged Fix Released