Closed sgoveas closed 3 months ago
Hi @sgoveas. Thanks for your PR.
I'm waiting for a metal3-io 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.
No description provided.
I would like to get some description ? Are you experimenting or there is some need for this changes ? I do have clear idea about the difference between the two definition
Are you experimenting or there is some need for this changes ? I do have clear idea about the difference between the two definition
I expect the final version of the PR to contain an explanation, but tl;dr the versioned machine types can disappear in future versions of libvirt, and apparently this one is no longer available. Just "virt" means "the latest version".
/ok-to-test
/test metal3-centos-e2e-integration-test-release-1-7
/test metal3-dev-env-integration-test-ubuntu-main
/test metal3-dev-env-integration-test-ubuntu-main
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: elfosardo
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/test metal3-centos-e2e-integration-test-release-1-7
The versioned machine types can disappear in future versions of libvirt, and the one in use 'virt-rhel8.2.0' is no longer available. "virt" means "the latest version"
Signed-off-by: Steeve Goveas sgoveas@redhat.com