The HA flag of user defined flavos routers is always set to true
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Miguel Lavalle |
Bug Description
Since [1] was merged, non HA user defined flavor routers cannot be created.
100% reproducible following these steps:
1) Create a non high availability flavor profile:
$ openstack network flavor profile create --description "User-defined router flavor profile" --enable --driver neutron.
+------
| Field | Value |
+------
| description | User-defined router flavor profile |
| driver | neutron.
| enabled | True |
| id | 04f95202-
| meta_info | |
| project_id | None |
+------
2) Create a router flavor and associate to the profile:
$ openstack network flavor create --service-type L3_ROUTER_NAT --description "User-defined flavor for routers in the L3 OVN plugin" user-defined-
+------
| Field | Value |
+------
| description | User-defined flavor for routers in the L3 OVN plugin |
| enabled | True |
| id | a350b61e-
| name | user-defined-
| service_profile_ids | [] |
| service_type | L3_ROUTER_NAT |
+------
$ openstack network flavor add profile user-defined-
3) Attempt to create a non-HA user defined flavor router:
$ openstack router create router-
+-------+-------+
| Field | Value |
+-------+-------+
| ha | True |
+-------+-------+
The expected result is:
+-------+-------+
| Field | Value |
+-------+-------+
| ha | False |
+-------+-------+
Changed in neutron: | |
assignee: | nobody → Miguel Lavalle (minsel) |
status: | New → Confirmed |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. opendev. org/c/openstack /neutron/ +/913276
Review: https:/