← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1373774] [NEW] security groups are not attached to an instance if port-id is specified during boot

 

Public bug reported:

Creation of server with command  
‘nova boot  --image <image> --flavor m1.medium --nic port-id=<port-id> --security-groups  <sec_grp> <name>’ 
fails to attach the security group to the port/instance. The response payload has the security group added but only default security group is attached to the instance.  
Separate action has to be performed on the instance to add sec_grp, and it is successful. Supplying the same with ‘--nic net-id=<net-id>’ works as expected

** Affects: nova
     Importance: Undecided
     Assignee: Oleg Bondarev (obondarev)
         Status: New


** Tags: network

-- 
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/1373774

Title:
  security groups are not attached to an instance if port-id is
  specified during boot

Status in OpenStack Compute (Nova):
  New

Bug description:
  Creation of server with command  
  ‘nova boot  --image <image> --flavor m1.medium --nic port-id=<port-id> --security-groups  <sec_grp> <name>’ 
  fails to attach the security group to the port/instance. The response payload has the security group added but only default security group is attached to the instance.  
  Separate action has to be performed on the instance to add sec_grp, and it is successful. Supplying the same with ‘--nic net-id=<net-id>’ works as expected

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


Follow ups

References