Tempest Rhel7: subnet configures with 0.0.0.0 when sending gateway None
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Won't Fix
|
Medium
|
Hampapur Ajay | |||
R3.0.2.x |
Won't Fix
|
Medium
|
Hampapur Ajay | |||
R3.0.3.x |
Won't Fix
|
Medium
|
Hampapur Ajay | |||
R3.1 |
Won't Fix
|
Medium
|
Hampapur Ajay | |||
R3.2 |
Fix Committed
|
Medium
|
Sahil Sabharwal | |||
R4.0 |
Fix Committed
|
Medium
|
Sahil Sabharwal | |||
Trunk |
Fix Committed
|
Medium
|
Sahil Sabharwal |
Bug Description
Build: Rhel7 2.20-65~juno
Tempest Case: tempest.
As a part of this case, when subnet is created with gateway=None, it gets configured with gateway == 0.0.0.0 which is unacceptable.
Posted Body:
Body: {"subnet": {"ip_version": 4, "network_id": "cfc8734b-
Received Body:
Body: {"subnet": {"name": "", "enable_dhcp": true, "network_id": "cfc8734b-
}}}
Via CLI:
[root@b4s10 ~(keystone_admin)]# neutron subnet-create np-test-net --name np-test-subnet --no-gateway 10.5.5.0/24
Created a new subnet:
+------
| Field | Value |
+------
| allocation_pools | {"start": "10.5.5.1", "end": "10.5.5.254"} |
| cidr | 10.5.5.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 0.0.0.0 |
| host_routes | |
| id | e5668218-
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | np-test-subnet |
| network_id | d81221e8-
| tenant_id | 13df8b8a797440f
+------
[root@b4s10 ~(keystone_admin)]#
tags: | added: rhosp-tempest |
Changed in juniperopenstack: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
assignee: | Ashish Ranjan (aranjan-n) → Hampapur Ajay (hajay) |
tags: | added: tempest |
tags: |
added: osp7-cert osp8-cert rhos-tempest removed: rhosp-tempest |
information type: | Proprietary → Public |
Following testcase because of this behavior
tempest. api.network. test_networks. NetworksIpV6Tes tJSON.test_ create_ list_subnet_ with_no_ gw64_one_ network