Hi Juan Carlos,

I can reproduce this issue locally. This is a regression issue due to the requirement change of the network-segment-range OSC CLI during the feature patch review.

I’ve filed bugs [1][2] and submitted patches [3][4] for them.

Currently you can work around this by not specifying --shared and it’ll default to a shared range.

Let me know if any further question. Thanks a lot.

BR,

Kailun

[1] https://storyboard.openstack.org/#!/story/2005205

[2] https://storyboard.openstack.org/#!/story/2005206

[3] https://review.openstack.org/#/c/642707/

[4] https://review.openstack.org/#/c/642708/

From: Alonso, Juan Carlos [mailto:juan.carlos.alonso@intel.com]
Sent: Tuesday, March 12, 2019 1:51 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] openstack network segment range create FAILED

Hi,

In “Providernetworking setup: Network Segment Ranges (Stein)” section, in the second command:

openstack network segment range create  ${PHYSNET0}-b --network-type vlan  --physical-network ${PHYSNET0}  --minimum 10 --maximum 10 --shared

I got the following error:

BadRequestException: 400: Client Error for url: http://neutron.openstack.svc.cluster.local:80/v2.0/network_segment_ranges, Invalid input for tenant_id. Reason: 'None' is not a valid string.

I tried to add --project ${ADMINID} but --project is only allowed with --private.

Has this command been updated? Because the wiki does not show an update.

Regards.

Juan Carlos Alonso