Project

General

Profile

Bug #6756

Updating cloned backend in WebGUI updates the original backend instead of the cloned backend

Added by Goran Tornqvist over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
haproxy
Target version:
-
Start date:
09/02/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.3.2
Affected Architecture:
amd64

Description

This bug has appeared for me 3 times now when I clone an existing https to a new backend.
I have multiple SSL sites on the same IP so for me it is simplest to clone an existing frontend/backend to keep the custom settings.

  1. I clone a backend.
  2. Edit the new cloned backend, change the ipaddress/hostname to the correct one.
  3. When I check the old backend which was used for cloning it now has the ip/hostname of the cloned backend.
  4. Not completely sure but I believe the cloned backend was changed as well to the correct ip/hostname

haproxy 0.48 / pfsense 2.3.2

This will probably happen again so I will take more notes when it does.

History

#1 Updated by Pi Ba over 2 years ago

I think it fixed in 0.50 .

https://github.com/pfsense/FreeBSD-ports/commit/36e0556b6b19a8a524a4ba3a7c55f87e9a6bd6a5#diff-8901498da5326453d17f69659d2d17caR326

In the mean time save the backend directly after cloning, then reopen it to make wanted changes.

Also available in: Atom PDF