Hi Parikshit, Looks like a bug. Currently if port is specified its security groups are not updated, it shpould be fixed. I've reported https://bugs.launchpad.net/nova/+bug/1373774 to track this. Thanks for reporting! Thanks, Oleg On Thu, Sep 25, 2014 at 10:15 AM, Parikshit Manur < parikshit.manur at citrix.com> wrote: > Hi All, > > 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. > > > > Is this the expected behaviour / are there any other options which needs > to be specified to add the security group when port-id needs to be attached > during boot. > > > > Thanks, > > Parikshit Manur > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140925/935844b7/attachment.html>