yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #65632
[Bug 1692567] Re: can't create neutron port fixed_ip if subnet associated with segment
Hi Harald Jensås, so I assume that we don't need this bug anymore?
** Changed in: heat
Status: In Progress => Invalid
** Changed in: heat
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1692567
Title:
can't create neutron port fixed_ip if subnet associated with segment
Status in heat:
Incomplete
Status in neutron:
New
Bug description:
There doesn't seem to be a way to create a fixed_ip for an
OS::Neutron::Port if the subnet is associated with a Neutron segment.
For example, using this:
resources:
instance_port:
type: OS::Neutron::Port
properties:
network: ctlplane
fixed_ips: [{"subnet": ctlplane-subnet0, "ip_address": 10.8.146.8}]
my_ironic_instance:
type: OS::Nova::Server
properties:
key_name: default
image: overcloud-full
flavor: baremetal
networks:
- network: ctlplane
port: {get_resource: instance_port}
If the subnet is NOT associated with a segment, I am able to create a
stack with a Neutron port with 10.8.146.8 as expected.
However, in this case the subnet is associated with a neutron segment:
[stack@host01 ~]$ neutron subnet-show ctlplane-subnet0
+-------------------+----------------------------------------------------------------+
| Field | Value |
+-------------------+----------------------------------------------------------------+
| allocation_pools | {"start": "10.8.146.5", "end": "10.8.146.20"} |
| cidr | 10.8.146.0/24 |
| created_at | 2017-05-19T21:57:53Z |
| description | |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 10.8.146.1 |
| host_routes | {"destination": "169.254.169.254/32", "nexthop": "10.8.146.1"} |
| id | 2510cb92-e3f7-4ef3-98a8-ba409c33406b |
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | ctlplane-subnet0 |
| network_id | 5f93540c-b00e-42c7-b1a1-0560906d9a8d |
| project_id | 08b43a05b88c4d4089355b3aba9dd8fb |
| revision_number | 2 |
| segment_id | d5b2dc5d-ee11-4057-9481-fd28fab14b31 |
| service_types | |
| subnetpool_id | |
| tags | |
| tenant_id | 08b43a05b88c4d4089355b3aba9dd8fb |
| updated_at | 2017-05-19T21:57:53Z |
+-------------------+----------------------------------------------------------------+
[stack@host01 ~]$ openstack network segment show d5b2dc5d-ee11-4057-9481-fd28fab14b31
+------------------+--------------------------------------+
| Field | Value |
+------------------+--------------------------------------+
| description | None |
| id | d5b2dc5d-ee11-4057-9481-fd28fab14b31 |
| name | subnet0 |
| network_id | 5f93540c-b00e-42c7-b1a1-0560906d9a8d |
| network_type | flat |
| physical_network | ctlplane |
| segmentation_id | None |
+------------------+--------------------------------------+
The stack is created successfuly, however the neutron port has a fixed_ip from the allocation_pool (10.8.146.15, see below) not the defined fixed_ip in the template.
[stack@host01 ~]$ heat stack-list
+--------------------------------------+------------+-----------------+----------------------+--------------+
| id | stack_name | stack_status | creation_time | updated_time |
+--------------------------------------+------------+-----------------+----------------------+--------------+
| ed4e655b-7ff1-4823-98a8-5a76822e08b9 | test-stack | CREATE_COMPLETE | 2017-05-22T14:48:24Z | None |
+--------------------------------------+------------+-----------------+----------------------+--------------+
[stack@host01 ~]$ neutron port-show da1787b8-f537-4b5f-a5c8-ed986360d7f3
+-----------------------+---------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+---------------------------------------------------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | |
| binding:host_id | host01.beaker.tripleo.lab.eng.rdu2.redhat.com |
| binding:profile | {} |
| binding:vif_details | {"port_filter": true, "ovs_hybrid_plug": true} |
| binding:vif_type | ovs |
| binding:vnic_type | normal |
| created_at | 2017-05-22T14:48:25Z |
| description | |
| device_id | 3aad41e0-4ccb-45ef-8c64-6937712a61c7 |
| device_owner | compute:None |
| extra_dhcp_opts | {"opt_value": "http://10.8.146.1:8088/boot.ipxe";, "ip_version": 4, "opt_name": |
| | "tag:ipxe,bootfile-name"} |
| | {"opt_value": "10.8.146.1", "ip_version": 4, "opt_name": "tftp-server"} |
| | {"opt_value": "undionly.kpxe", "ip_version": 4, "opt_name": "tag:!ipxe |
| | ,bootfile-name"} |
| | {"opt_value": "10.8.146.1", "ip_version": 4, "opt_name": "server-ip-address"} |
| fixed_ips | {"subnet_id": "2510cb92-e3f7-4ef3-98a8-ba409c33406b", "ip_address": |
| | "10.8.146.15"} |
| id | da1787b8-f537-4b5f-a5c8-ed986360d7f3 |
| ip_allocation | deferred |
| mac_address | b0:83:fe:c6:53:21 |
| name | test-stack-instance_port-4idizi33xgm4 |
| network_id | 5f93540c-b00e-42c7-b1a1-0560906d9a8d |
| project_id | 08b43a05b88c4d4089355b3aba9dd8fb |
| revision_number | 12 |
| security_groups | f862fbd3-5c64-41d4-87e6-1825d9d04568 |
| status | DOWN |
| tags | |
| tenant_id | 08b43a05b88c4d4089355b3aba9dd8fb |
| updated_at | 2017-05-22T14:48:35Z |
+-----------------------+---------------------------------------------------------------------------------+
In heat/engine/resources/openstack/neutron/port.py, it doesn't look like segment can be used as a property.
To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1692567/+subscriptions
