| 2016-01-29 10:49:59 |
Julia Aranovich |
description |
STR:
1) create environment with default wizard settings (Neutron VLAN networking)
2) go to Settings tab and enable Ironic in Additional Services section
3) go to Networks tab and check that baremetal network presented got default node network group. Baremetal network settings on UI are: CIDR, IP range, VLAN tagging
4) create a new node network group:
gateway appears among baremetal network settings for each node network group (I don't know, is it expected behaviour?)
5) make some valid change (uncheck vlan tagging for management network of the second node network group) and click Save Changes
Expected result: the network changes are saved successfully.
Actual result: there is an error message on the page:
"Gateway address belongs to the network's IP range [192.168.3.1-192.168.3.50]."
because of IP range of beremetal network in the second node network group is 192.168.3.1 - 192.168.3.50 and gateway is 192.168.3.1
So, when creating a new node network group, baremetal setting are invalid at the very beginning.
Also (please consider an attached screenshot): the error message gives no information about gateway and IP range of which network are intersected? In what node network group?
And gateways of all networks on the page are higlighted in red because of invalid Nailgun response when trying to save the changes:
{"message": "Gateway address belongs to the network's IP range [192.168.3.1-192.168.3.50].", "errors": [{"errors": ["gateway"], "ids": [1]}, {"errors": ["gateway"], "ids": [17]}, {"errors": ["gateway"], "ids": [18]}, {"errors": ["gateway"], "ids": [19]}, {"errors": ["gateway"], "ids": [21]}, {"errors": ["gateway"], "ids": [22]}, {"errors": ["gateway"], "ids": [23]}, {"errors": ["gateway"], "ids": [24]}, {"errors": ["gateway"], "ids": [26]}, {"errors": ["gateway"], "ids": [27]}]} |
STR on fake UI:
1) create environment with default wizard settings (Neutron VLAN networking)
2) go to Settings tab and enable Ironic in Additional Services section
3) go to Networks tab and check that baremetal network presented got default node network group. Baremetal network settings on UI are: CIDR, IP range, VLAN tagging
4) create a new node network group:
gateway appears among baremetal network settings for each node network group (I don't know, is it expected behaviour?)
5) make some valid change (uncheck vlan tagging for management network of the second node network group) and click Save Changes
Expected result: the network changes are saved successfully.
Actual result: there is an error message on the page:
"Gateway address belongs to the network's IP range [192.168.3.1-192.168.3.50]."
because of IP range of beremetal network in the second node network group is 192.168.3.1 - 192.168.3.50 and gateway is 192.168.3.1
So, when creating a new node network group, baremetal setting are invalid at the very beginning.
Also (please consider an attached screenshot): the error message gives no information about gateway and IP range of which network are intersected? In what node network group?
And gateways of all networks on the page are higlighted in red because of invalid Nailgun response when trying to save the changes:
{"message": "Gateway address belongs to the network's IP range [192.168.3.1-192.168.3.50].", "errors": [{"errors": ["gateway"], "ids": [1]}, {"errors": ["gateway"], "ids": [17]}, {"errors": ["gateway"], "ids": [18]}, {"errors": ["gateway"], "ids": [19]}, {"errors": ["gateway"], "ids": [21]}, {"errors": ["gateway"], "ids": [22]}, {"errors": ["gateway"], "ids": [23]}, {"errors": ["gateway"], "ids": [24]}, {"errors": ["gateway"], "ids": [26]}, {"errors": ["gateway"], "ids": [27]}]} |
|
