Reviewed:  https://review.opendev.org/c/openstack/horizon/+/938239
Committed: 
https://opendev.org/openstack/horizon/commit/53bba73b5ca0f213f265873a39aed8a47d3abb2e
Submitter: "Zuul (22348)"
Branch:    master

commit 53bba73b5ca0f213f265873a39aed8a47d3abb2e
Author: Takashi Kajinami <kajina...@oss.nttdata.com>
Date:   Wed Dec 25 12:13:14 2024 +0900

    Fix the attribute to look up security group ids of a port (3)
    
    ... to fix the "Edit Port" functionality.
    
    Closes-Bug: #2092276
    Change-Id: I815a558e87fef2474eed42cfb175b753ad61713a


** Changed in: horizon
       Status: In Progress => Fix Released

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

Title:
  security group port no attribute

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  'Port' object has no attribute 'security_groups'

  Horizon 25.1
  Neutron 25.1

  After clicking on "Edit Port" button of instance settings I' getting
  errors of port security groups:

  Unable to retrieve security group list. Please try again later. Details
  'Port' object has no attribute 'security_groups'

  Unfortunately, after fixing lines to "sg_ids += p.security_group_ids"
  in both workflows.py and neutron.py (as proposed in
  https://bugs.launchpad.net/horizon/+bug/2089557), error still appears.

  Even after adding SGs to the port and getting success notifications,
  after clicking on button again, ports have still no security groups
  attached to it (port list --long shows also "None" in security groups
  column).

  Should I restart some service to apply changes?

  Thanks.

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


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to