Back to bug 2222605
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-07-13 09:13:45 UTC | Link ID | Red Hat Issue Tracker OSP-26580 | |
| Eran Kuris | 2023-07-13 10:14:15 UTC | QA Contact | ekuris | mblue |
| Slawek Kaplonski | 2023-07-17 14:40:11 UTC | CC | skaplons | |
| Priority | unspecified | high | ||
| Assignee | rhos-maint | egarciar | ||
| Severity | unspecified | high | ||
| Maor | 2023-07-17 17:24:41 UTC | CC | rsafrono | |
| Flags | needinfo?(rsafrono) | |||
| Roman Safronov | 2023-07-17 17:59:12 UTC | Flags | needinfo?(rsafrono) | |
| Elvira | 2023-07-20 16:33:21 UTC | QA Contact | mblue | ekuris |
| Assignee | egarciar | mblue | ||
| Component | python-networking-ovn | python-neutron-tests-tempest | ||
| Keywords | AutomationBlocker, Triaged | |||
| Lukas Svaty | 2023-07-21 13:24:23 UTC | Flags | needinfo?(egarciar) | |
| CC | egarciar, lsvaty | |||
| Eran Kuris | 2023-07-23 10:56:15 UTC | Severity | high | medium |
| Keywords | AutomationBlocker | Automation | ||
| Maor | 2023-07-23 15:43:30 UTC | Status | NEW | ON_DEV |
| Elvira | 2023-07-24 06:37:23 UTC | Flags | needinfo?(egarciar) | |
| Maor | 2023-07-24 07:39:21 UTC | Status | ON_DEV | VERIFIED |
| Priscila Gutierres | 2023-08-02 16:29:57 UTC | Resolution | --- | NOTABUG |
| Status | VERIFIED | CLOSED | ||
| CC | prgutier | |||
| Last Closed | 2023-08-02 16:29:57 UTC | |||
| Ian Frangs | 2023-08-03 15:46:23 UTC | CC | mblue | |
| Flags | needinfo?(mblue) | |||
| Maor | 2023-08-07 10:46:27 UTC | CC | ifrangs | |
| Doc Type | If docs needed, set a value | Release Note | ||
| Doc Text | When events happen with small time difference, related security group log entries may not appear in exact order of events, time signatures up to supported precision in log entry should be observed instead. | |||
| Flags | needinfo?(mblue) | needinfo?(ifrangs) needinfo?(egarciar) | ||
| Elvira | 2023-08-07 14:21:30 UTC | Flags | needinfo?(egarciar) | |
| Greg Rakauskas | 2023-08-08 19:34:51 UTC | Doc Type | Release Note | Known Issue |
| CC | gregraka | |||
| Flags | needinfo?(ifrangs) | needinfo?(mblue) | ||
| Doc Text | When events happen with small time difference, related security group log entries may not appear in exact order of events, time signatures up to supported precision in log entry should be observed instead. | In RHOSP 17.1 GA there is a known issue for security group log entries. When events occur in short time intervals of each other, the related security group log entries are not listed in the correct order. + Workaround: Observe instead the time signatures of each event up to the supported precision. |
||
| Greg Rakauskas | 2023-08-09 13:21:22 UTC | Doc Text | In RHOSP 17.1 GA there is a known issue for security group log entries. When events occur in short time intervals of each other, the related security group log entries are not listed in the correct order. + Workaround: Observe instead the time signatures of each event up to the supported precision. | In RHOSP 17.1 GA there is a known issue for security group log entries. When events occur in short time intervals of each other, the related security group log entries are not listed in the correct order. For example, for each log entry, the first, higher precision timestamp might not be correct according to the order of events. + Workaround: Read the second timestamp for each log entry--with up to a millisecond (0.001) accuracy--to infer the order of events. When the second timestamp is identical in each entry, the events occurred within the same millisecond, and you cannot infer the correct order of events. |
| Maor | 2023-08-10 08:40:35 UTC | Flags | needinfo?(mblue) | |
| Doc Text | In RHOSP 17.1 GA there is a known issue for security group log entries. When events occur in short time intervals of each other, the related security group log entries are not listed in the correct order. For example, for each log entry, the first, higher precision timestamp might not be correct according to the order of events. + Workaround: Read the second timestamp for each log entry--with up to a millisecond (0.001) accuracy--to infer the order of events. When the second timestamp is identical in each entry, the events occurred within the same millisecond, and you cannot infer the correct order of events. | Events triggered which should be logged within a small time frame, may be processed by OVN backend in a slightly different order of events by the time they reached the processing point. | ||
| Maor | 2023-08-10 08:47:07 UTC | Target Release | --- | 17.1 |
| Target Milestone | --- | ga | ||
| Greg Rakauskas | 2023-08-10 14:31:47 UTC | Doc Text | Events triggered which should be logged within a small time frame, may be processed by OVN backend in a slightly different order of events by the time they reached the processing point. | In RHOSP 17.1 GA there is a known issue for security group log entries. When events occur in short time intervals of each other, the related security group log entries can be listed in an incorrect order. This is caused by how the OVN back end processes events. Currently, there is no workaround. |
| Flags | needinfo?(mblue) | |||
| Maor | 2023-08-10 14:48:55 UTC | Flags | needinfo?(mblue) | needinfo?(egarciar) |
| Elvira | 2023-08-17 09:34:00 UTC | Flags | needinfo?(egarciar) | |
| Jenny-Anne Lynch | 2023-08-17 09:45:35 UTC | CC | jelynch | |
| Doc Text | In RHOSP 17.1 GA there is a known issue for security group log entries. When events occur in short time intervals of each other, the related security group log entries can be listed in an incorrect order. This is caused by how the OVN back end processes events. Currently, there is no workaround. | In RHOSP 17.1, there is a known issue for security group log entries. When events occur in short time intervals of each other, the related security group log entries can be listed in an incorrect order. This is caused by how the OVN back end processes events. Currently, there is no workaround. |
Back to bug 2222605