Blue-Green deploy stuck on IDLE (invalid route)

[agiguere]

I recently opened an incident to SAP, but they are struggling to find it out, maybe you guys could have an idea

When we deployed a Fiori Element app built with CAP in BAS via CICD to CTMS

When I import the MTAR generated via CICD to our target subaccount, the route is stuck with the IDLE in it, and the managed app route can't find that route

if we deploy our app from BAS directly to our target subaccount, then no problem

In CTMS, the deployment strategy on my node is blue-green. I did not have a chance to test it with Default, but my guess is that it will work

Here is an example

alex

[theghost5800]

Hi @agiguere , "idle" suffix in application route is coming from blue-green deployment approach to deploy/update mtas. This "idle" suffix must be used only first phase of blue-green update flow and after validation and continue the operation, new application will be updated to the live routes and old ones will be deleted. You can read more about blue-green update flow here.

If you don't want to update your applications using blue-green deployment, then you can use default "cf deploy" command without "--strategy blue-green" argument, in cTMS this setting is managed by node settings and configure "default" deployment strategy.

If you have any other questions, please let me know.

[agiguere]

@theghost5800 Yes, we will try the default deployment strategy

That does not explain the problem why the app is stuck on IDLE, with blue-green we expect after deployment the app works as usual (regarding blue-green option in CTMS, there is no settings to change in CICD or in the app MTA file, correct)

[theghost5800]

@agiguere It could stuck with "idle" suffixes in case blue-green deployment is started without --skip-testing-phase or --no-confirm flags in cf cli commands if deployment runs outside of CTMS tool. The reason for this is because if these flags are not specified, blue-green update will stop when new applications are deployed and we'll wait to validate and confirm that everything is fine and execute additional commands to continue with deployment and switch newer applications to productive routes.