3.2.2: On saving a new virtual-network, the customer IPAM gets reset to the default IPAM

[Sandeep Sridhar]

This is for a contrail installation (3.2.2) with the RedHat Openstack 10 installed using tripleO deployment. This looks to be a GUI/WebUI issue only.

We create an IPAM and associate the same while creating a virtual-network. On saving the newly created virtual-network, the WebUI shows the default-ipam for the subnet and not the one which was actually associated while creating the VN.

However, from vncApi, it looks like the right IPAM is associated: (ddhk-ipam is the ipam that we have created for the VN).

>>> vn_obj.network_ipam_refs
[{u'to': [u'default-domain', u'admin', u'ddhk-ipam'], u'href': u'http://172.16.201.91:8082/network-ipam/db322205-c75a-4ee9-98ab-a55f73558674', u'attr': ipam_subnets = [subnet = ip_prefix = 192.168.101.0, ip_prefix_len = 24, default_gateway = 192.168.101.1, dns_server_address = 192.168.101.2, subnet_uuid = 09320241-deb2-4f5d-bd97-fc307ada52eb, enable_dhcp = True, dns_nameservers = [], allocation_pools = [start = 192.168.101.10, end = 192.168.101.20], addr_from_start = True, dhcp_option_list = None, host_routes = None, subnet_name = 09320241-deb2-4f5d-bd97-fc307ada52eb, alloc_unit = 1], host_routes = None, u'uuid': u'db322205-c75a-4ee9-98ab-a55f73558674'}]
>>>

Please fix this WebUI bug.

-Sandeep.

[Manoj (manojgn)]

Unable to reproduce on our setups. The IPAMs seems to be set correctly. Requesting for a setup where this issue is happening.

[Jeba Paulaiyan (jebap)]

Hi Jeba,

I am ok. Even I could not replicate it on my setups.

Greetings,
Sandeep.