We definitely cannot remove it in Crux because it was there in 1.2.0, and Crux is an LTS release. However, whether we should remove it from current, or even 1.3 is a more interesting question.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
May 29 2021
It seems to work fine in the latest 1.3, assuming it's no longer an issue.
OpenVPN op mode has been working fine for a while, so I assume it's resolved.
Closing since the reporter isn't responding and similar issues never turned up since that time.
This is, sadly, a WONTFIX for now: it's indeed coming from the old backend. I'm also not sure what a right design would be. That command simply parses the output of a show command and converts it to JSON.
Assuming resolved.
We haven't seen memory leaks in keepalived in a long time, so I assume it's resolved.
Now that 1.3 is near a stable release, it's a good idea to revisit the hardening measures and see if we can enable any new ones.
I can confirm that NAT logging works fine in 1.2.7. So if there was a bug related to it, it's been long fixed.
May 28 2021
@UnicronNL I would like to put default values in the config.boot file, and overwrite them from Cloud-init if a customer provides custom values.
Properly works on the latest 1.4 rolling. Is it possible to backport changes to 1.3?