Project

General

Profile

Actions

Bug #11090

closed

OpenVPN assigned interfaces inconstant status

Added by Danilo Zrenjanin about 5 years ago. Updated about 5 years ago.

Status:
Needs Patch
Priority:
Very Low
Assignee:
-
Category:
High Availability
Target version:
-
Start date:
11/20/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

If there are multiple OpenVPN instances in HA setup, and ovpnsX interfaces are assigned to each instance, their status will be inconsistent on the Secondary node. Some of them will be up, the others will be down no matter the status of the OpenVPN instances are all down.

I didn't notice any functional issues.

Actions #1

Updated by Jim Pingle about 5 years ago

  • Status changed from New to Needs Patch
  • Priority changed from Low to Very Low
  • Target version deleted (2.5.0)

If this is causing no functional problems I see no reason for us to take any action on it. Certainly not a 2.5.0 blocker.

If someone wants to try coming up with a fix, we can consider a PR for it, but unless we can find some actual negative impact here, it's not worth spending time on.

Actions #2

Updated by Viktor Gurov about 5 years ago

maybe related to #11091

Actions

Also available in: Atom PDF