Skip to content

Make openstack VM provisioning error visiable#1686

Merged
cb-spider merged 1 commit intocloud-barista:masterfrom
seokho-son:master
Mar 24, 2026
Merged

Make openstack VM provisioning error visiable#1686
cb-spider merged 1 commit intocloud-barista:masterfrom
seokho-son:master

Conversation

@seokho-son
Copy link
Copy Markdown
Member

The current OpenStack driver does not provide a clear error message during VM provisioning.

It keep checking strings.ToLower(serverResult.Status) == "active" regardless of its internal Error..

And, only returns failed to start VM, exceeded maximum retry count (240), which prevents users from understanding the root cause.


This PR fix the issue.

Signed-off-by: Seokho Son <shsongist@gmail.com>
Copilot AI review requested due to automatic review settings March 24, 2026 08:27
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Improves the OpenStack driver’s VM provisioning wait loop so that VM creation failures surface the underlying Nova fault details instead of timing out with a generic “exceeded maximum retry count” message.

Changes:

  • Adds periodic status logging while waiting for a VM to transition to ACTIVE.
  • Detects ERROR status during provisioning and returns an error containing Nova fault information when available.
  • Enhances the timeout error to include the VM’s last observed status.

@powerkimhub powerkimhub requested a review from cb-spider March 24, 2026 08:44
@cb-spider cb-spider merged commit a4e397e into cloud-barista:master Mar 24, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants