opnsense / opnsense/plugins

os-tayga: no configuration synchronization

Open
#5,503 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

support
Dominant language
PHP
Stars
1.2k
Forks
863
Avg merge
2d 6h
Merged PRs (30d)
10

Description

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug
Running a HA opnsense cluster, and recently added tayga as service to the primary node.
Configuration is synchronized via XMLRPC to the second node. Tayga is selected to be included in the configuration on the primary node, but configuration changes are not present on the secondary node after sync.

To Reproduce
Steps to reproduce the behavior:

  1. Create HA cluster
  2. Setup XMLRPC sync, added tayga as included service
  3. Enable tayga on primary node and re-sync configuration manually
  4. tayga plugin is not enabled on secondary node

Expected behavior
Changes to the plugin configuration should be synchronized

Environment
Versions
OPNsense 26.1.10-amd64
FreeBSD 14.3-RELEASE-p15
os-tayga 1.5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Start by tracing the os-tayga configuration's XMLRPC synchronization path using the reproduction steps, then verify that enabling and changing tayga on the primary is reflected on the secondary.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
infrastructure, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.