| 2023-01-23 11:46:06 |
Elvira García Ruiz |
bug |
|
|
added bug |
| 2023-01-23 11:46:40 |
Elvira García Ruiz |
description |
With the OVN security group logging feature enabled there is only one direction (from client to server) packets are actually logged. It happens because there is a single OpenFlow rule created for the returned traffic and it has no logging action
Steps:
- Create server associated to security group.
- Add a network log object that logs accepted traffic from that security group.
- Check logs in ovn-controller.log
Expected results:
- We get the packets incoming and outcoming from the server.
Actual results:
- We only see incoming packets. |
With the OVN security group logging feature enabled there is only one direction (from client to server) packets are actually logged. It happens because there is a single OpenFlow rule created for the returned traffic and it has no logging action
Steps:
- Create server associated to security group.
- Add a network log object that logs accepted traffic from that security group.
- Check logs in ovn-controller.log
Expected results:
- We get the packets incoming and outcoming from the server.
Actual results:
- We only see incoming packets.
More info at: https://bugzilla.redhat.com/show_bug.cgi?id=2152877 |
|
| 2023-01-23 13:34:33 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
| 2023-01-23 15:21:27 |
Oleg Bondarev |
neutron: importance |
Undecided |
Medium |
|
| 2023-02-01 21:44:09 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2023-02-02 15:48:26 |
OpenStack Infra |
tags |
ovn |
in-stable-xena ovn |
|
| 2023-02-02 16:18:01 |
OpenStack Infra |
tags |
in-stable-xena ovn |
in-stable-xena in-stable-yoga ovn |
|
| 2023-02-02 16:18:57 |
OpenStack Infra |
tags |
in-stable-xena in-stable-yoga ovn |
in-stable-wallaby in-stable-xena in-stable-yoga ovn |
|
| 2023-02-02 19:55:20 |
OpenStack Infra |
tags |
in-stable-wallaby in-stable-xena in-stable-yoga ovn |
in-stable-wallaby in-stable-xena in-stable-yoga in-stable-zed ovn |
|
