Bug 1710879 - Impossible to update existing subnet using --no-host-route option
Summary: Impossible to update existing subnet using --no-host-route option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-openstackclient
Version: 13.0 (Queens)
Hardware: All
OS: All
medium
medium
Target Milestone: z8
: 13.0 (Queens)
Assignee: Julie Pichon
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-16 13:39 UTC by Alex Stupnikov
Modified: 2019-09-03 16:58 UTC (History)
5 users (show)

Fixed In Version: python-openstackclient-3.14.3-4.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, host routes took an empty string by default. As a result, updating a subnet with the `openstack subnet set` command failed when setting the `--no-host-route` option. With this update, the host routes accept an empty list by default, and updating a subnet with the `openstack subnet set` command succeeds even when you do not set the `--no-host-route` option.
Clone Of:
Environment:
Last Closed: 2019-09-03 16:58:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 659545 0 None NEW Fix subnet host_routes error 2020-03-30 09:56:14 UTC
Red Hat Product Errata RHBA-2019:2623 0 None None None 2019-09-03 16:58:32 UTC

Description Alex Stupnikov 2019-05-16 13:39:48 UTC 
Description of problem:

RHOSP 13 is affected by upstream bug [1], the fix [2] was cherry-picked to stable/queens, but is blocked by broken CI


[1] https://bugs.launchpad.net/python-openstackclient/+bug/1747101
[2] https://review.opendev.org/#/c/659545/
Comment 1 Alex Stupnikov 2019-05-16 13:42:38 UTC 
Steps to reproduce:

- Create test subnet with static routes.
- Run the following command for new subnet: ""openstack subnet set test-rh-subnet --no-host-route""

Expected result: associated routes are removed

Actual result: BadRequestException: Unknown error
Comment 10 errata-xmlrpc 2019-09-03 16:58:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2623
Note You need to log in before you can comment on or make changes to this bug.