Skip to main content

Hi, all.

 

We’re trying to move from 23.2 to 24. 

In the correct path, using the correct YAML files.

 

.\installer.cmd --values E:\[CORRECT PATH]\ifscloud-values.yaml --values E:\[CORRECT PATH]ifs-cloud-24.1.0-paqara3-5.0.0-20240619T133210Z-success\InstallationFiles\solutionset.yaml --set dbinstaller.sysPassword=[CORRECT PASSWORD]

 

We’re getting this error, but we’re definitely on 23.2. Has anyone experienced this? Why doesn’t the installer recognize the correct version?

 

[Tue Jul 30 12:45:26 EDT 2024] - SEVERE: The delivery not in sequence! Last delivery installed is ifs-cloud-23.1.5-paqara3-2.0.0-20231103T130434Z but expected is ifs-cloud-23.2.2-paqara3-4.0.0-20240213T220018Z
[Tue Jul 30 12:45:26 EDT 2024] - SEVERE: Validation failed.

 

When I login to IFS, it definitely says we’re on 23.2.

 

 

Ideas?

 

Thanks!

Hi @NerakYak ,

I would suggest checking the “Delivery Registrations” page in the target environment to see if the last delivery (23.2) has been correctly updated there. It it’s not there, you probably would end up having to re-install the said delivery.


Cheers

Did you end up resolving this?

Hi ​@NerakYak 

Alternatively, connect to the PDB and execute the following command:

SELECT * FROM ifsapp.delivery_registration_tab;

Ensure the specified delivery is included in the output.

Is there any insight folks have here to address when the delivery id has not been updated in the delivery registration but the delivery installation was successful? 

​@ecostanzo_GOGH In IFS Cloud, if the Delivery ID is not updated in the delivery registration after a successful installation, it usually indicates an issue during the post-installation process. Review the logs for any errors or warnings that occurred during this phase. Manual updates to the Delivery ID are not recommended, as they could lead to failures in subsequent delivery installations. Instead, it is advisable to contact IFS Support for assistance in resolving the issue.

Thank you. We’ve opened a ticket and will proceed there. If we come to a resolution I will make a note to update everyone here. Regards, 

Terms & ConditionsCookie settingsAccessibility statement