There was an issue in the migration from CREODIAS to CREODIAS2.
In the config file of one of the servers, Sentinel-1 was still listing CREODIAS (the old data provider) as catalogue. It should have instead listed CREODIAS2.
This caused some issues, like in the run of some processors (e.g. the urban floods detection, relying on Sentinel-1 images)
We should investigate why CREODIAS was considered as a valid provider even if its configuration is not anymore listed between the data providers in the config file and why WASDI did not used the backup provider instead.
There was an issue in the migration from CREODIAS to CREODIAS2.
In the config file of one of the servers, Sentinel-1 was still listing CREODIAS (the old data provider) as catalogue. It should have instead listed CREODIAS2.
This caused some issues, like in the run of some processors (e.g. the urban floods detection, relying on Sentinel-1 images)
We should investigate why CREODIAS was considered as a valid provider even if its configuration is not anymore listed between the data providers in the config file and why WASDI did not used the backup provider instead.