Increase osasinfra post-ceph EDPM Ready wait to 60m

[tusharjadhav3302]

Summary

• Raise edpm-post-ceph-deployment osdpns openstack-edpm Ready wait from 40m → 60m in osasinfra and osasinfra-ipv6 VA definitions.
• Fixes flaky shiftstack-rhel9-rhoso18.0-ocp5.1 periodic failures on serval71 where deploy succeeded ~20s after the 40m timeout expired.

Root cause (serval71, 2026-08-28)

deploy-architecture.sh failed on:

oc -n openstack wait osdpns openstack-edpm --for condition=Ready --timeout=40m

Phase	Wall time
Pre-ceph EDPM ansible	13.1m
Ceph hook (Deploy Ceph)	11.6m
Post-ceph EDPM ansible	33.9m
Operator finalize → Ready	1.9m
Total wait window	40.3m (Ready at +20s)

Post-ceph slowest ansible pods (3 compute nodes):

Service	Pod duration
libvirt	8.2m
telemetry	7.1m
nova	4.9m

Pre-ceph is lighter (bootstrap/network/OS install only); post-ceph pulls in libvirt, nova, telemetry, OVN, ceph-client, etc., which is why it consumes ~3× the wall time.

Test plan

• Re-run shiftstack-rhel9-rhoso18.0-ocp5.1 on serval71 (or resume from current env if still up)
• Confirm edpm-post-ceph-deployment stage completes without osdpns wait timeout
• Verify no regression on shorter osasinfra deploy paths (pre-ceph still 30m)

Made with Cursor

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tusharjadhav3302
Once this PR has been reviewed and has the lgtm label, please assign abays for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @tusharjadhav3302. Thanks for your PR.

I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 9cfad292-4707-451d-bd87-b8ef81d8d63b

---

_{Comment @coderabbitai help to get the list of available commands.}