Configuration management, using the Infrastructure as Code model.
We're willing to provide configuration for our production service in rOPS using Salt.
Configuration management, using the Infrastructure as Code model.
We're willing to provide configuration for our production service in rOPS using Salt.
It could be solved upstream with 3006.26.
@yousra It seems better with last Salt versions on 3006 LTS branch.
Also, for reference, I solved the issue in a new Salt repo with 9002:9002
A quick note for reference, as I was looking this task to recreate the same issue in a new Salt environment, the core role provides:
Next steps on complector:
New poudriere run
After pinning Salt version with D4113:
Instead of building packages by hand, we can also automate with Poudriere and create a temporary packages repository "15-salt".
On WindRiver, /usr/ports/sysutils/py-salt/work-py311/pkg/py311-salt-3006.26,1.pkg is Salt 3006.26 + Python 3.11, built on FreeBSD 15.1
Finally check after T2319 :
@dereckson While testing and modifying the GRE tunnel, it took so long on Ysul that SSH stopped responding, and we lost access to the machine.
Now, regardless of whether router-002 or router-003 is the primary router, the tunnel with Windriver works perfectly. However, there is still an issue with Ysul: the tunnel works when router-003 is primary, but it does not work when router-002 is primary.
We noticed that Windriver is unable to ping the public IP addresses of router-002 and router-003. However, GRE tunnel creation is successful, and tunnel connectivity works with router-002, although pinging its public IP is still unsuccessful.