[MCOL-4928] non-interactive update in Debian is broken Created: 2021-11-18  Updated: 2022-06-27  Resolved: 2022-02-11

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 5.6.2, 6.2.2
Fix Version/s: 5.6.4, 6.3.1

Type: Bug Priority: Minor
Reporter: Roman Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2021-17

 Description   

The server team complains about a warning that breaks non-interactive auto-update process in deb-based distros.
Running minor or major upgrade one gets a warning from deb packaging about Columnstore.xml was changed since installation. The important fact is that nobody changes the xml. The xml file attributes are changed by a number of clauses in columnstore-post-install:

  • mcsSetConfig in columnstore-post-install
  • mcsSetConfig in columnstoreSyslogSetup.sh
  • chown in columnstore-post-install

The suggested solution is to remove offending mcsSetConfig clauses and move chown into corresponding post-inst step scripts of a packaging systems(for both RPM and DEB).

 Comments   
Comment by Roman Navrotskiy [ 2021-11-19 ]

localized the problem to the level of a mcsSetConfig call. as says above it occures in two places:

/usr/bin/columnstore-post-install
/usr/bin/columnstoreSyslogSetup.sh

chown does not affect the problem

Comment by Roman [ 2022-02-01 ]

Plz review.

Comment by Daniel Lee (Inactive) [ 2022-02-03 ]

So what was changed/fixed? What method of upgrade was done (reinstalling deb packages, update from repo?). Do you have the output of the error/complain?

Comment by Roman [ 2022-02-08 ]

I removed mcsSetConfig command from 2 install-time scripts:

  • /usr/bin/columnstore-post-install
  • /usr/bin/columnstoreSyslogSetup.sh

You need to install MDB+MCS(the latest-1) in deb-based distro. If you upgrade MDB+MCS then this update operation asks for operator input complaining that original /etc/columnstore/Columnstore.xml was manually altered(even if it wasn't). The fixed packages must not complain about this. Feel free to ask for more details in Slack dleeyh.

Comment by Roman [ 2022-02-09 ]

The server test scripts made minor upgrades,e.g. 6.1.1 to 6.2.2 using deb remote repo. What is the command you upgraded with?

Comment by Daniel Lee (Inactive) [ 2022-02-11 ]

Builds verified: 5.6.4-2 (#3781), 6.2.4-1 (#3778)

Still could not reproduce the issue when upgrading using local repository, but was able to reproduce by uninstalling and re-installing the deb packages.

{noforamt}

s1pm1: Configuration file '/etc/columnstore/Columnstore.xml'
s1pm1: ==> Modified (by you or by a script) since installation.
s1pm1: ==> Package distributor has shipped an updated version.
s1pm1: What would you like to do about it ? Your options are:
s1pm1: Y or I : install the package maintainer's version
s1pm1: N or O : keep your currently-installed version
s1pm1: D : show the differences between the versions
s1pm1: Z : start a shell to examine the situation
s1pm1: The default action is to keep your current version.
s1pm1: *** Columnstore.xml (Y/I/N/O/D/Z) [default=N] ? 

 

Using 6.2.4 with the fix, I still had some issues upgrading from some earlier releases.

When upgrading from 6.1.1 to 6.2.4 (with fix), had issue
When upgrading from 6.2.2 to 6.2.4 (with fix), no issue

According to the developer, the fix is for upgrading from the fixed version and beyond since earlier release already had the Columnstore.xml file modified. It worked fine when I 'upgraded' from 6.2.4 to 6.2.4 (The same release)

The same tests also work the for 5.x releases.

Generated at Thu Feb 08 02:54:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.