github-actions[bot] commented on issue #13752: URL: https://github.com/apache/cloudstack/issues/13752#issuecomment-5356778309
## ๐ฏ Triage report On VMware with NSX integration, `HypervisorHostHelper.prepareNetwork` performs only a single immediate lookup of the NSX-backed distributed virtual port group after `CreateNsxSegmentCommand` succeeds. Since the NSX segment is created outside vCenter, the DV port group can take a short time to become visible via the vCenter API, causing a race that fails `PlugNicCommand` and rolls back guest network implementation on VPC tiers. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:bug | Race condition/timing bug in NSX network implementation on VMware | | **Component** | component:vmware, component:vpc | Affects `HypervisorHostHelper`/VMware DVS handling for NSX-backed VPC guest networks | | **Severity** | Severity:Major | Blocks network implementation intermittently, a functional failure with a known code path already available to fix it (existing `waitForDvPortGroupReady`) | | **Labels** | type:bug, component:vmware, component:vpc, Severity:Major | See above | | **Coding agent** | Suitable | Root cause is precisely identified with file/method names, and a concrete proposed fix (reuse the existing `waitForDvPortGroupReady` bounded-wait path for NSX broadcast domains, plus a regression test) is already specified | ### ๐ Similar issues No closely related open duplicates found. <details><summary>๐ก Notes and suggestions</summary> The proposed fix is well-scoped: enable the existing `waitForDvPortGroupReady` retry/wait logic for the NSX broadcast domain type in `HypervisorHostHelper.prepareNetwork`, with a regression test simulating an empty first vCenter lookup followed by a successful one. This looks like a strong candidate for a small, targeted PR. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/32375697891) ยท sonnet50 224.8K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) > <details> <summary>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 32375697891, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/32375697891 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
