"verify Network" does not detect overlap of L3 Network and public network

[Rajesh Mallah]

In a fresh environment consisting of bare metal server . "Verify Network" passes even if there is an overlap between "public network" and internal L3 Network. This misconfiguration is manifested during open stack controller installation in the puppet log as "Bad Request" .

also running the below from cmdline of controller after source sourcing
env variables:

# /usr/bin/neutron router-interface-add --format=shell router04 subnet=net04__subnet

Bad Request (HTTP 400) (Request-ID: req-e222ae9e-c124-43a8-a9b8-eaad9fe1cbdc)

checking the neutron log reveals the overlap message.

[Rajesh Mallah (mallah)]

this entry was inadvertently submitted.

[Rajesh Mallah (mallah)]

Intended Subject : "verify Network" does not detect invalid L3 Neutron configuration.

Intended Body:

In a fresh environment consisting of bare metal server . "Verify Network" passes even if
there is an overlap between "public network" and internal L3 Network.

This misconfiguration is manifested during openstack controller installation in the
puppet log as "Bad Request" .

/usr/bin/neutron router-interface-add --format=shell router04 subnet=net04__subnet
Bad Request (HTTP 400) (Request-ID: req-e222ae9e-c124-43a8-a9b8-eaad9fe1cbdc)

checking the neutron log reveals the overlap message.

@Admin , please correct the subject of the entry. thanks.

[Ihor Kalnytskyi (ikalnytskyi)]

Rajesh Mallah, could you please provide a diagnostic snapshot?