Add post_infra hook processing to create-infra.yml#4016
Conversation
The adoption deploy-infra job uses create-infra.yml which did not process post_infra hooks. This meant hooks like vlanprovider_mtu (which sets the hypervisor trunk bridge MTU) only ran in greenfield via cifmw_setup but never in adoption. Adding run_hook after deploy_layout ensures the trunk bridge MTU is set before VMs boot. Assisted-by: Claude Code Opus 4.6 Related-to: OSPRH-30634 Signed-off-by: Renjing Xiao <rxiao@redhat.com>
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 05m 40s |
The adoption deploy-infra job uses create-infra.yml which did not process post_infra hooks. This meant hooks like vlanprovider_mtu (which sets the hypervisor trunk bridge MTU) only ran in greenfield via cifmw_setup but never in adoption. Adding run_hook after deploy_layout ensures the trunk bridge MTU is set before VMs boot.
Assisted-by: Claude Code Opus 4.6
Related-to: OSPRH-30634