NCPA Linux update is fragile
Posted: Wed Nov 29, 2023 9:13 am
Every time NCPA updates it pauses the apt upgrade process waiting for user input (even when run with apt upgrade -y).
This also leads to some users who don't know any better selecting to use the new config file which wipes out the NCPA community_string and breaks communication with Nagios XI. What can be done to avoid this situation on future NCPA updates?
If we keep our existing file, then we miss any new configurations added. This is a bad update experience for all available choices.
The only custom change in my config file is setting the community_string.
This also leads to some users who don't know any better selecting to use the new config file which wipes out the NCPA community_string and breaks communication with Nagios XI. What can be done to avoid this situation on future NCPA updates?
If we keep our existing file, then we miss any new configurations added. This is a bad update experience for all available choices.
The only custom change in my config file is setting the community_string.
Code: Select all
Setting up ncpa (3.0.0-latest-1) ...
Configuration file '/usr/local/ncpa/etc/ncpa.cfg'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** ncpa.cfg (Y/I/N/O/D/Z) [default=N] ?