When upgrading from previous version, it must be ensured that older extensions are removed

[bertysentry]

Problem

When upgrading "in place", the new install does not remove older extensions. When the product initializes, the older extensions are loaded first, which prevents the product from working at all.

Specification

Either implement a mechanism to load only extensions marked with the proper version number, or make sure the upgrade removes older files. For Community Edition, at least document the fact that older extensions must be deleted on upgrade.

[NassimBtk]

While trying to upgrade MetricsHub EE from 1.0.02 to the latest 1.1.00, we are unable to reproduce this issue. The entire MetricsHub directory is emptied and then repopulated with the new assets from the latest version.

Regarding the httpcli issue, it is a real problem that needs to be fixed:

C:\Program Files\MetricsHub>httpcli --method get --url https://dev-01:443/users
IllegalStateException: Failed to execute HTTP get query.

  NullPointerException: Cannot read the array length because "<parameter1>" is null

[NassimBtk]

NPE here https://github.com/sentrysoftware/metricshub/blob/main/metricshub-agent/src/main/java/org/sentrysoftware/metricshub/cli/HttpCli.java#L418 when password is null.

[NassimBtk]

Re-opened #572
I will keep this issue open until we fully understand the actual use case, as we are currently unable to reproduce it.

[CherfaElyes]

@bertysentry After testing on my Windows 11 laptop, the upgrade (using the .msi file) deletes all the C:\Program Files\MetricsHub content before re-installing the new MetricsHub version 🤷‍♂️

[bertysentry]

Yes, and that’s a good news! The problem is with the Community Edition. When you upgrade “in place” (unzip the archive), all extensions from previous version remain, and it prevents the product from working. So we either need a mechanism that selects the extensions, or properly document that the user need to delete all previous extensions while upgrading.