Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[backport v1.3] [BUG] Unable to create pc-q35 VM with Error NO PCI buses available #5784

Closed
harvesterhci-io-github-bot opened this issue May 10, 2024 · 10 comments
Assignees
Labels
area/vm-lifecycle kind/bug Issues that are defects reported by users or that we know have reached a real release need-reprioritize not-require/test-plan Skip to create a e2e automation test issue regression reproduce/always Reproducible 100% of the time require/investigate severity/1 Function broken (a critical incident with very high impact)
Milestone

Comments

@harvesterhci-io-github-bot

backport the issue #5437

@harvesterhci-io-github-bot harvesterhci-io-github-bot added area/vm-lifecycle kind/bug Issues that are defects reported by users or that we know have reached a real release need-reprioritize not-require/test-plan Skip to create a e2e automation test issue regression reproduce/always Reproducible 100% of the time require/investigate severity/1 Function broken (a critical incident with very high impact) labels May 10, 2024
@harvesterhci-io-github-bot harvesterhci-io-github-bot added this to the v1.3.1 milestone May 10, 2024
@harvesterhci-io-github-bot
Copy link
Author

harvesterhci-io-github-bot commented May 13, 2024

Pre Ready-For-Testing Checklist

  • If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
    The HEP PR is at:

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:

  • Create a VM or Edit a VM from GUI, in the "Advanced Options" tab -> Show more -> Machine type should only display None or q35. VM should start with both option.
  • Is there a workaround for the issue? If so, where is it documented?
    The workaround is at:

  • Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
    The PR is at:

    • Does the PR include the explanation for the fix or the feature?

    • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
      The PR for the YAML change is at:
      The PR for the chart change is at:

  • If labeled: area/ui Has the UI issue filed or ready to be merged?
    The UI issue/PR is at:

  • If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
    The documentation/KB PR is at:

  • If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

    • The automation skeleton PR is at:
    • The automation test case PR is at:
  • If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
    The compatibility issue is filed at:

@irishgordo irishgordo self-assigned this May 17, 2024
@irishgordo
Copy link

This looks good on v1.3-head:

rancher@node8-v13head:~> cat /etc/os-release 
NAME="SLE Micro"
VERSION="5.4"
VERSION_ID="5.4"
PRETTY_NAME="Harvester v1.3"
ID="sle-micro-rancher"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sle-micro-rancher:5.4"
VARIANT="Harvester"
VARIANT_ID="Harvester-v1.3-20240515

Version: master-f38da5f7-head

I'll go ahead and close this out, thanks @a110605 👍 😄

Screenshot from 2024-05-17 12-54-51
Screenshot from 2024-05-17 12-54-01
Screenshot from 2024-05-17 12-52-41

@irishgordo
Copy link

Re-Opening, need to revalidate due to:
harvester/harvester-installer#737

@irishgordo
Copy link

@a110605 - based on re-validation noticing this is failing.

Version: v1.3-95b4f9dc-head

Validation Failure

    "error": false,
    "lastProbeTime": null,
    "lastTransitionTime": "2024-05-22T19:27:41Z",
    "lastUpdateTime": "2024-05-22T19:27:41Z",
    "message": "server error. command SyncVMI failed: \"LibvirtError(Code=27, Domain=20, Message='XML error: No PCI buses available')\"",
    "reason": "Synchronizing with the Domain failed.",
    "status": "False",
    "transitioning": false,
    "type": "Synchronized"

Screenshot from 2024-05-22 12-33-35

On Harvester

@irishgordo irishgordo removed their assignment May 22, 2024
@bk201
Copy link
Member

bk201 commented May 23, 2024

@torchiaf @a110605 The reason is currently the backend is using the ui-index:

DefaultDashboardUIURL = "https://releases.rancher.com/harvester-ui/dashboard/release-harvester-v1.3.0/index.html"

We used the release-harvester-v1.3.0 branch in v1.3.0 development time, are we safe to move to release-harvester-v1.3 now?

@a110605
Copy link

a110605 commented May 23, 2024

@torchiaf @a110605 The reason is currently the backend is using the ui-index:

DefaultDashboardUIURL = "https://releases.rancher.com/harvester-ui/dashboard/release-harvester-v1.3.0/index.html"

We used the release-harvester-v1.3.0 branch in v1.3.0 development time, are we safe to move to release-harvester-v1.3 now?

Thanks @bk201 for clarify the root cause.
release-harvester-v1.3 branch contains all the backport PRs for v1.3.1 release. (including this issue fix commit)

I think it's okay but let @torchiaf double confirm.

@bk201
Copy link
Member

bk201 commented May 23, 2024

Update the UI index: #5857

@bk201
Copy link
Member

bk201 commented May 23, 2024

Move back to ready for testing, the UI assets should be correct in v1.3 ISO:
截圖 2024-05-23 下午3 09 29
截圖 2024-05-23 下午3 09 14

@torchiaf
Copy link

I confirm that 1.3 contains the 1.3.1 backports for fresh installations. The auto value in ui-source setting should prevent to fetch future backports .

@irishgordo irishgordo self-assigned this May 23, 2024
@irishgordo
Copy link

This looks good in Version: v1.3-274e20ac-head 😄 👍 - thanks @torchiaf
Screenshot from 2024-05-23 14-27-47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/vm-lifecycle kind/bug Issues that are defects reported by users or that we know have reached a real release need-reprioritize not-require/test-plan Skip to create a e2e automation test issue regression reproduce/always Reproducible 100% of the time require/investigate severity/1 Function broken (a critical incident with very high impact)
Projects
None yet
Development

No branches or pull requests

5 participants