Description of problem: The following instructions do not work for OSP10z6 https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/network_functions_virtualization_configuration_guide/part-dpdk-configure#sect-ovs-dpdk-flavor-deploy-instance openstack network create --provider-network-type=vlan --provider-segment=<VLAN-ID> --provider-physical-network=tenant net1 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: [heat-admin@controller-0 ~]$ openstack network create net1 --provider:network_type=vlan --provider:segmentation_id=1201 --provider:physical_network=tenant Actual results: usage: openstack network create [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--max-width <integer>] [--noindent] [--prefix PREFIX] [--share | --no-share] [--enable | --disable] [--project <project>] [--project-domain <project-domain>] [--availability-zone-hint <availability-zone>] [--enable-port-security | --disable-port-security] [--external | --internal] [--default | --no-default] [--provider-network-type <provider-network-type>] [--provider-physical-network <provider-physical-network>] [--provider-segment <provider-segment>] [--transparent-vlan | --no-transparent-vlan] <name> openstack network create: error: unrecognized arguments: --provider:network_type=vlan --provider:segmentation_id=1201 --provider:physical_network=tenant Expected results: [heat-admin@controller-0 ~]$ openstack network create --provider-network-type=vlan --provider-segment=1201 --provider-physical-network=net-n0 net1 +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | UP | | availability_zone_hints | | | availability_zones | | | created_at | 2018-04-17T14:34:03Z | | description | | | headers | | ...
This is the same for OSP 11 and 12.
Assigning to James for review. James, I'm assigning you this one and bug 1525590 because they describe the same command syntax error but for different sections of the guide. It might be worth checking for any other places this syntax is used, and running this by the DFG for review. I've flagged the fix for 10, 11, 12, and 13. Christopher confirms in comments above that the problem occurs in 10, 11, and 12; you'll need to check with the DFG whether it will also occur in the yet-to-be-released version 13.
*** This bug has been marked as a duplicate of bug 1607897 ***