Bug 1910111 - ovn-kubernetes IPsec should start after network has been configured
Summary: ovn-kubernetes IPsec should start after network has been configured
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Mark Gray
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-22 17:23 UTC by Mark Gray
Modified: 2021-02-08 17:26 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-08 17:26:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 929 0 None closed Bug 1910111: order startup of IPsec components 2021-02-08 17:25:51 UTC

Description Mark Gray 2020-12-22 17:23:49 UTC
Description of problem:
In order to prevent any unforeseen race conditions. Startup of IPsec processes should be strictly ordered.

Version-Release number of selected component (if applicable):
4.7.0


Note You need to log in before you can comment on or make changes to this bug.