yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53359
[Bug 1282582] Re: Ignoring network id during instance launching
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY
** Changed in: nova
Importance: Low => Undecided
** Changed in: nova
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1282582
Title:
Ignoring network id during instance launching
Status in OpenStack Compute (nova):
Expired
Bug description:
I have met strange behavior of nova API.
When we create instance and send request with network parameters (port_id, network_id, fixed_ip) with not None values,
nova ignore network_id without any message. As result we get instance only with pointed port_id.
In case when we send same request using interface-attach we get BadRequest answer here
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/contrib/attach_interfaces.py#L96
because we have port_id and network_id together in request.
Also I have look in v3 plugins and it have a little difference.
If we have not None value for port_id and fixed_ip, will be raised Error
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/plugins/v3/servers.py#L348
but it still ignore network_id.
If it's normal behavior: Could you explain why nova send BadRequest
Error in same case during attaching interface.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1282582/+subscriptions
References