yahoo-eng-team team mailing list archive

[Akihiro Motoki <1748097@xxxxxxxxxxxxxxxxxx>]

This is the intentional behavior of nova API.

When you see the list of request parameters of create-server API [1],
the description of "networks.port" field says "Requested security groups
are not applied to pre-existing ports."

[1] https://developer.openstack.org/api-ref/compute/#create-server

** Changed in: horizon
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1748097

Title:
  Security groups not set when port instead of network selected

Status in OpenStack Dashboard (Horizon):
  Won't Fix

Bug description:
  Using 3:11.0.4-0ubuntu1~cloud0 with Ubuntu 16.04 LTS.

  When creating an instance with the horizon web interface, pre-create
  some ports mapped to floating ips. When creating an instance select a
  port instead of the network. Select some security group and launch
  instance. When instance is created there are no selected security
  groups, only the default one.

  Steps to reproduce:
  1) create a network port associated to a floating ip with newtron
  2) go to horizon
  3) create instance 
  4) select a network port already mapped instead of a network
  5) select your security groups and associate them to the instance
  6) launch instance.

  Behavior:
  The instance spawns up correctly but the security groups are not there, only the default one.
  Expected behavior:
  Security group in spawned instance should be the one selected during creation.

  If all steps are followed but a network instead of a port is selected,
  the security groups are saved correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1748097/+subscriptions