"network auto allocated topology create --check-resources" Fails with: "Request requires an ID but none was found"
Bug #1677252 reported by
John Davidge
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Attempting to run the command:
openstack network auto allocated topology create --check-resources
Will fail with error:
Request requires an ID but none was found
The command works fine without the '--check-resources' flag.
Seen on latest OSC master.
Changed in python-openstackclient: | |
assignee: | nobody → Reedip (reedip-banerjee) |
To post a comment you must log in.
Hi John,
I faced the same issue.
Then I realized that my openstack SDK was on 0.9.13
stack@openstack -nti-16: ~/python- openstacksdk$ pip freeze | grep openstacksdk =0.9.13
openstacksdk=
I upgraded to 0.9.14 , and now:
openstack network auto allocated topology create --check-resources
+---------+-------+
| Field | Value |
+---------+-------+
| dry_run | None |
+---------+-------+
Can you your version of Openstack SDK? I guess you pulled up the master of OSC but not of the SDK, maybe?