Project

General

Profile

Actions

Bug #15225

closed

Killing states on downed gateways breaks for static interface configurations

Added by Marcos M 3 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Gateways
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
24.03
Release Notes:
Default
Affected Version:
2.7.2
Affected Architecture:

Description

An interface with a static configuration can have a pending gateway status. In this scenario, killing states for downed gateways does not work.

Actions #1

Updated by Marcos M 3 months ago

  • Status changed from New to Waiting on Merge
  • Assignee set to Marcos M
  • Target version set to 2.8.0
  • % Done changed from 0 to 100
  • Plus Target Version set to 24.03
Actions #2

Updated by Marcos M 3 months ago

  • Status changed from Waiting on Merge to Feedback
Actions #3

Updated by Danilo Zrenjanin 3 months ago

I couldn't find a way to make the statically defined gateway in the pending status.

I tried:

On a physical appliance, by disconnecting the cable.
On a physical appliance by administratively disabling the port on the switch.
On a VM by disconnecting the interface on the VM itself.
Changing the IP address on the default gateway side, to be out of scope.

None of the above made the gateway in the pending status. It always just goes to Offline status.

Actions #4

Updated by Marcos M 3 months ago

  • Status changed from Feedback to Resolved

I can reproduce it here by disconnecting the VM link on the host side using ESXi 7. The patch resolves the issue in this case.

Actions

Also available in: Atom PDF