Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cluster resync on restart - pf12.1 #7360

Closed
fdurand opened this issue Nov 9, 2022 · 2 comments · Fixed by #7361
Closed

Cluster resync on restart - pf12.1 #7360

fdurand opened this issue Nov 9, 2022 · 2 comments · Fixed by #7361
Assignees
@jrouzierinverse
Labels
Priority: Critical Type: Bug
Milestone
+1 (patch release)

Comments

@fdurand
Copy link
Member

fdurand commented Nov 9, 2022

Describe the bug
There is a resync each time the packetfence's services are restarted

To Reproduce
Steps to reproduce the behavior:

  1. bin/pfcmd service pf restart
  2. Check the logs, you will see "downloading file from ..."

Screenshots
On restart service on cluster2-1:

$VAR1 = {
          'cluster2-1' => '1668018945',
          'cluster2-2' => '1668016404',
          'cluster2-3' => '1668016404'
        };
$VAR2 = {
          '1668018945' => [
                            'cluster2-1'
                          ],
          '1668016404' => [
                            'cluster2-2',
                            'cluster2-3'
                          ]
        };

Once the services finished to restart:

$VAR1 = {
          'cluster2-3' => '1668016404',
          'cluster2-2' => '1668016404',
          'cluster2-1' => '1668016404'
        };
$VAR2 = {
          '1668016404' => [
                            'cluster2-3',
                            'cluster2-2',
                            'cluster2-1'
                          ]
        };

Expected behavior
The cluster should not resync.
@fdurand fdurand added this to the PacketFence-12.1 milestone Nov 9, 2022
@fdurand
Copy link
Member Author

fdurand commented Nov 9, 2022

It also affect 12.0

@jrouzierinverse
Copy link
Member

It looks partialy it is caused by

947dd08

@jrouzierinverse jrouzierinverse mentioned this issue Nov 9, 2022
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jrouzierinverse jrouzierinverse

Labels
Priority: Critical Type: Bug
Projects
None yet
Milestone
+1 (patch release)
Development

Successfully merging a pull request may close this issue.

fix/7360 inverse-inc/packetfence
2 participants
@fdurand @jrouzierinverse