Misalignment with extra-dhcp-options between neutronclient & openstackclient
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Low
|
Unassigned |
Bug Description
The SetPort class from the openstack client does not support --extra-dhcp-option [1]
(overcloud) $ openstack port set --extra-dhcp-option name=mtu,
usage: openstack port set [-h] [--description <description>]
openstack port set: error: unrecognized arguments: --extra-dhcp-option port-test-202
The UpdatePort class from the neutron client supports --extra-dhcp-opt [2]
This is aligned with the neutron API [3]
(overcloud) $ neutron port-update port-test-202 --extra-dhcp-opt opt_name=
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Updated port: port-test-202
(overcloud) $ neutron port-show port-test-202 | grep mtu
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
| | {"opt_name": "mtu", "opt_value": "1750", "ip_version": 4} |
[1] https:/
[2] https:/
[3] https:/
description: | updated |
Changed in neutron: | |
importance: | Undecided → Low |
status: | New → Triaged |
This seems for me like lack of feature in the openstackclient. OSC uses storyboard to track issues. I opened bug in storyboard https:/ /storyboard. openstack. org/#!/ story/2009095 and I'm closing this one here.