Bug 1556955

Summary:	Impossible to manipulate MTU from undercloud (openstack network create/set)
Product:	Red Hat OpenStack	Reporter:	Roee Agiman <ragiman>
Component:	python-openstackclient	Assignee:	Julie Pichon <jpichon>
Status:	CLOSED ERRATA	QA Contact:	Shai Revivo <srevivo>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	amuller, apevec, bhaley, chrisw, ihrachys, lhh, nusiddiq, nyechiel, srevivo, supadhya
Target Milestone:	beta	Keywords:	Triaged
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-openstackclient-3.14.0-2.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-27 13:46:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1546994, 1925290

Description Roee Agiman 2018-03-15 15:39:46 UTC

Description of problem:
There is no option to manipulate MTU upon creating/setting network from UC.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.Deploy OSP13
2.Execute 'openstack network create --help' | grep -i mtu
3.Option missing

Actual results:
Missing MTU manipulation option

Expected results:
MTU option is available

Additional info:

Comment 1 Ihar Hrachyshka 2018-03-15 16:13:22 UTC

I forgot to add support for the field to openstackclient when implementing the feature in neutron. The old neutronclient should work as-is because it allows to pass unknown fields, but openstackclient requires specific changes to allow the attribute to pass through to the server.

Comment 2 Brian Haley 2018-03-15 17:12:04 UTC

See https://review.openstack.org/#/c/553374/ which proposed adding --mtu to the openstackclient just this morning.

Comment 4 Ihar Hrachyshka 2018-03-26 14:27:26 UTC

Queens backport: https://review.openstack.org/#/c/556545/

Comment 5 Ihar Hrachyshka 2018-04-04 14:27:10 UTC

The fix is included in 3.14.1. We just need to check the rebase happened.

Comment 7 Julie Pichon 2018-04-05 13:36:48 UTC

*** Bug 1559051 has been marked as a duplicate of this bug. ***

Comment 15 errata-xmlrpc 2018-06-27 13:46:53 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/RHEA-2018:2086