[Starlingx-discuss] openstack network segment range create FAILED

[Qin, Kailun]

Just FYI, the issue was not discovered due to a functional test bug [1][2] in openstackclient. The functional test for network segment range in OSC was skipped unexpectedly because of this.
Now we've added tests at unit level [3] to have it covered.

[1] https://review.openstack.org/#/c/642074/
[2] https://storyboard.openstack.org/#!/story/2005169
[3] https://review.openstack.org/#/c/642707/

From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com]
Sent: Tuesday, March 12, 2019 9:42 PM
To: Qin, Kailun <kailun.qin at intel.com>; Alonso, Juan Carlos <juan.carlos.alonso at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: RE: [Starlingx-discuss] openstack network segment range create FAILED

My apologies. I didn't realize that the code needs to go in openstack-client ...not in starlingx.

From: Khalil, Ghada
Sent: Tuesday, March 12, 2019 9:39 AM
To: 'Qin, Kailun'; Alonso, Juan Carlos; starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: RE: [Starlingx-discuss] openstack network segment range create FAILED

Hi Kailun,
All bugs need to be reported in Launchpad. Moving forward, please do not open stories for bugs.

JC already opened a Launchpad bug for the issue he reported:
https://bugs.launchpad.net/starlingx/+bug/1819541

I've assigned it to you.

Please update your commit message to add "Closes-Bug: 1819541"

Thanks,
Ghada

From: Qin, Kailun [mailto:kailun.qin at intel.com]
Sent: Tuesday, March 12, 2019 5:59 AM
To: Alonso, Juan Carlos; starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] openstack network segment range create FAILED

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 at intel.com]
Sent: Tuesday, March 12, 2019 1:51 AM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at 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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190313/0ae798f0/attachment.html>