Rolling Updates E2E Tests Failing (10 & 18)

[gflarity]

What happened?

AS per #280.

Tests 10 and 18 are failing. @shmuel-runai is looking into these failures.

Test cases

RU-10	Rolling Update on WL1 with insufficient resources	Initialize a 2-node Grove cluster.Deploy workload WL1, and verify 10 newly created pods.Cordon all worker nodes.Change the specification of pc-a.`The rolling update must not progress since there are insufficient resources in the cluster.Uncordon the node, and the rolling update must continue from where it was stuck.

RU-18	Rolling Update on WL1 with scale-out on standalone PCLQ being updated	Initialize a 2-node Grove cluster,Deploy workload WL1 with 2 replicas, and verify 20 newly created pods.Change the specification of pc-a, pc-b and pc-c.Scale out the PCLQ during its rolling update.The scaled pods must be created with the correct specifications.It should not be updated again before the rolling update ends.

What did you expect to happen?

Tests should pass, or the test cases need adjustment.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!