EMR JobRun status is not synced anymore after the controller version upgrade

[zip-chanko]

Describe the bug

The jobrun status is no longer synced with AWS after we upgraded the EMR controller version from 1.0.7 to later versions. Also upgraded the CRDs and having the issue. The jobrun status is stuck at SUBMITTED on EKS even thought the status is COMPLETED on AWS.

Before upgrade

After upgrade

Steps to reproduce

1. Install the EMR controller helm with version 1.0.7.
2. Create a virtual cluster.
3. Submit the job and the job status is synced with EKS.
4. Upgrade to later version 1.0.27 or 1.1.2.
5. Submit the job again.

Expected outcome

The job status is synced between AWS and on EKS.

Environment

• Kubernetes version - 1.31
• Using EKS (yes) - eks.44
• AWS service targeted - EMR

[github-actions]

Hello @zip-chanko 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.

We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.

You can find more information about ACK on our website.

[rushmash91]

Hi @zip-chanko ,

Thank you for sharing the screenshots!

Would you mind sharing the controllers logs for the emr controller. The Manifest for the jobrun (you can remove sensitive info) would also be useful.