DRPC didn't get stuck deploying, but the .status.phase is what made it look like DRPC was stuck. The issue is cosmetic, and no functionality is affected or workaround is needed. After a successful deployment, DRPC didn't see the deployed VRG for 30 seconds. That caused the cosmetic issue to show up. That is, instead of showing in the log or the "kubectl get drpc -A" "CURRENTSTATE" output as "Deployed", it showed "Deploying". Needless to say, it is a low-priority bug. Again, the deployment was successful and the failover and relocation should work. Once you failover or relocate, the cosmetic problem will go away.
That's correct. DRPC does not know whether the app has been deployed or not. The "Deployed" state is only saying that all necessary resources have been created for the application to be deployed. The resources for the application are deployed by ACM. Hence, bug https://bugzilla.redhat.com/show_bug.cgi?id=2071494 Sidhant do you think we should use a different word instead of "Deployed"?