geoserver-2.26-SNAPSHOT-gwc-azure-blobstore-plugin doent work anymore in the 2.26.x series

brtvrbck · November 26, 2024, 10:40am

We have been using this module for years, now it doesnt work anymore.

In the admin console, when creating a new blobstore, the azure blobstore option soes not appear.

Trying to load a configuration with azure blobstores (that works in 2.25.4) geoserver crashes.

Is this a known issue? Will womething be done about it?

ianturton · November 26, 2024, 10:52am

That is a community module so there is no real expectation that someone will fix it for you. If you depend on this module then you’ll either need to fix it yourself or pay someone to fix it for you.

Ian

brtvrbck · November 26, 2024, 11:28am

info for anyone who is blocked by this issue:
2.26.1 works with the 2.25.x module.
Needs testing of course

jive · November 28, 2024, 8:20am

It is not a known issue, your feedback helps bring it to everyone’s attention.

As you are the first person to notice, do you have any idea what is not working? Anything warning in the logs etc…

Can you compare the jars included in the download with the previous version - maybe something important was left out? Sometimes when updating jars not everything is included in the download zip correctly.

aaime-geosolutions · November 28, 2024, 10:09am

Yep, it happened for example when upgrading the S3 libraries and an external contributor diagnosed the issue and provided a patch, it was indeed some missing library:

github.com/geoserver/geoserver

Add missing JARs to assembly.xml file for cog-s3 plugin

geoserver:main ← aims-ks:bug/missing-jars-for-cog-s3-plugin

opened 11:08PM - 08 Oct 24 UTC

mhn17

+4 -0

The dependency `AWS SDK` of the `cog-s3` plugin requires additional libraries af…ter it was upgraded from version 2.24.13 to 2.27.23. This fixes the issue discussed in https://discourse.osgeo.org/t/missing-jars-for-cog-s3-plugin-in-assembly-xml/110332 # Checklist - [X] I have read the [contribution guidelines](https://github.com/geoserver/geoserver/blob/main/CONTRIBUTING.md). - [ ] I have sent a [Contribution Licence Agreement](https://docs.geoserver.org/latest/en/developer/policies/committing.html) (not required for small changes, e.g., fixing typos in documentation). - [X] First PR targets the `main` branch (backports managed later; ignore for branch specific issues). - [ ] All the build checks are green ([see automated QA checks](https://docs.geoserver.org/latest/en/developer/qa-guide/index.html)). For core and extension modules: - [ ] New unit tests have been added covering the changes. - [ ] [Documentation](https://github.com/geoserver/geoserver/tree/main/doc/en/user/source) has been updated (if change is visible to end users). - [ ] The [REST API docs](https://github.com/geoserver/geoserver/tree/main/doc/en/api/1.0.0) have been updated (when changing configuration objects or the REST controllers). - [ ] There is an issue in the [GeoServer Jira](https://osgeo-org.atlassian.net/browse/GEOS/summary) (except for changes that do not affect administrators or end users in any way). - [ ] Commit message(s) must be in the form ``[GEOS-XYZWV] Title of the Jira ticket``. - [ ] Bug fixes and small new features are presented as a single commit. - [ ] Each commit has a single objective (if there are multiple commits, each has a separate JIRA ticket describing its goal).

This could be the same, the Azure libraries have received a major upgrade in the last few months.

Cheers
Andrea