I’m currently upgrading from VyOS 1.5-rolling-202502030007 to 2025.03.05-0017-rolling. Prior to the upgrade, I had installed AWS SSM and NewRelic agents, but after upgrading, both services are no longer present.
I would like to avoid performing the manual install of these agents on the new version. Is there a way to retain my old configuration or find a solution that allows me to migrate these services without breaking them during the upgrade process?
Any advice or solutions on how to smoothly upgrade while keeping these services intact would be greatly appreciated!
There is no supported way to have packages move, no.
Really doing a dpkg -i <thing> is totally unsupported - yes it often works, but you’re on your own.
The best way is to keep binaries of whatever you need in /config/scripts or similar, and then ensure that you say "Y" when asked "Do you want to copy /config" (not the exact message!) when moving to a new image, or to use the containers system which is designed for exactly this sort of thing.
@tjh , thanks for your input. Script that I am placing under /config/scripts is not running at all. I have to include it in the vyos-postconfig-bootup.script to get executed. problem with this is, my script is getting executed before network settings completed. i.e its not running as a last step. how can I solve this?
The easiest way I can think of would be to put a sleep statement in your script so it pauses for ~2 minutes, so that all networking etc can establish before it continues. That said, I don’t know if running a postconfig-bootup script is blocking or not - you would need to test (or look at the code)
You could also maybe setup a cron job in VyOS (task-scheduler) that runs every 5 minutes, but stop execution if a check early in the script detects the process(es) you need running already are etc.