D4Science Infrastructure

The dataminer service is failing on gCube 4.13.1.
The service will be upgraded when the new version is available in 4.13.1

the dataminer instances have been upgraded.

Hi @roberto.cirillo@isti.cnr.it , the service does not work there are dependencies that have not been correctly inherited (for example common-clients).
An update of the boms may be necessary.
Better to test smaller components like the uri-resolver first to see if they work.

I'm waiting a new build

New build available. I'm going to upgrade the service instances in preproduction

please @g.panichi@isti.cnr.it let me know if it works properly now

@roberto.cirillo@isti.cnr.it there is a problem of conflicting versions on jersey libraries.
We made a fix and re-launched the build on ETICS.

After a new deploy it works now.

@roberto.cirillo@isti.cnr.it in pre-production there is the DataMiner service that I had fixed yesterday, it should still put what it has built in gCube 4.13.1 to check that the dependencies are now correct.

Please, check that the deletion of the file already_installed_algorithms.txt is added to the ansible script at the end of the installation

dataminer1-pre:~/wps_algorithms_install_log$ rm already_installed_algorithms.txt

In this way, when the dataminer is restarted loads all the algorithms correctly.

Done.

@roberto.cirillo@isti.cnr.it , now the service has the right libraries, the Etics build is correct.
As for the file already_installed_algorithms.txt, however, it seems that the moment when the cancellation is done is not good.
Because if you check the file it's empty and the DataMiner service has not loaded any algorithms.
Perhaps the deletion should be done after restarting the service in the ansible script.

This is not an explanation and I didn't realize that. IMHO this is not a clean behavior and should be avoided.
@andrea.dellamico@isti.cnr.it do you think it is possible to do it by ansible since the container restart is managed as handler event?

Roberto Cirillo wrote:

This is not an explanation and I didn't realize that. IMHO this is not a clean behavior and should be avoided.
@andrea.dellamico@isti.cnr.it do you think it is possible to do it by ansible since the container restart is managed as handler event?

It's doable but very complex. Also, that behaviour didn't change in many months: why is it a problem now?
Last: after an upgrade, all the algorithms are installed again.

Ok it's not a big deal for now.