Unable to delete broken instance in CAL

[RCapozzo]

Hello,

I tried to deploy an instance (data Intelligence) but for problems on the infrastructure the provisioning job has failed. Unfortunately, as of now I cannot retry to deployment again for the same solution, because I'm unable to delete the previous one. The strange thing is that my colleague tried to deploy the solution (that one that resulted in error), but isn't visible in its "instances"; I see it but I cannot delete it. I tried to delete the user that launched the provision but the system tells me that I have to first delete the solution...so I'm in a deadlock.

Can someone help me?

Roberto

[former_member397351]

Hello Wallace and Roberto,

The 'terminate' operation is available unless:

• There is another operation in progress.
• The CAL account is in status 'Inactive', which usually means that the configured programmatic credentials have disabled, deleted etc.
• The instance is transitioning from state to state e.g the status is 'Activating' when the instance has just been activated but has not yet reached state 'Activated'

Does any of those condition matches your environment ?

Best Regards,

Tsanko

[Wallace]

For us, its in prepared status with an error

When we terminate it, it comes back to the error.

[former_member397351]

Hello Roberto,

Does the problem still persists? We observed some unusually long termination operations but in the end all of them completed successfully.

Best Regards,

Tsanko

[RCapozzo]

Hi Tsanko,

yes, the job was deployed on 4 July.The job status is "prepared". But the job has finished with error (step: Create Managed Clusters, error: mismatch between the kubernetes version of CAL and AZURE). I cannot terminate the job (the action is grayed), and the user that released the job do not see the job itself in "instances"; if he try to deactivate the solution, the system automatically re-assign the status "activated" to the solution.

Roberto

[Wallace]

Curious if this is solved, what the resolution was. We have one of these in our CAL instance list, but removing it hasn't been a priority for us as it failed before consuming Cloud Provider resources.