SYMC: "__no_rule__" security group read fails even with multitenancy set to False
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
In Progress
|
Medium
|
Ignatious Johnson Christopher | |||
OpenContrail |
New
|
Medium
|
Ignatious Johnson Christopher |
Bug Description
When all the security groups are deleted from a port, "__no_default__" security group gets added to the port which has "user_visible" flag set to False. Hence, the security group is not readable. Ideally, with multi-tenancy set to False, objects with user_visible as False should still be readable, but it's not.
Also, since this security group is not added by user but by the system, while reading/updating the relevant port, it should not throw a 500
Following is the backtrace we see:
The above is a description of an error in a Python program. Here is
the original traceback:
Traceback (most recent call last):
File "/usr/lib/
port[
File "/usr/lib/
return func(self, *args, **kwargs)
File "/usr/lib/
port_obj = self._port_
File "/usr/lib/
sg_obj = self._vnc_
File "/usr/lib/
content = self._request_
File "/usr/lib/
retry_
File "/usr/lib/
% (op, url, data, content))
NoIdError: Unknown id: Error: oper 2 url /security-
Changed in opencontrail: | |
importance: | Undecided → Medium |
description: | updated |
summary: |
- "__no_rule__" security group read fails even with multitenancy set to - False + SYMC: "__no_rule__" security group read fails even with multitenancy set + to False |
tags: | added: config |
Changed in opencontrail: | |
assignee: | nobody → Ignatious Johnson Christopher (ijohnson-x) |
In 2.20 or earlier, port-show would have listed NO_RULE SG as the security group attached. We changed that in master so that it is completely hidden from neutron/nova, so this problem should not arise.