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.

Sign up for GitHub

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

Jump to bottom

OVA: Consume firmware type from virt-v2v kubvirt configuration #855

Open
bkhizgiy opened this issue Apr 9, 2024 · 0 comments
Open

OVA: Consume firmware type from virt-v2v kubvirt configuration #855

bkhizgiy opened this issue Apr 9, 2024 · 0 comments
Assignees
@bkhizgiy
Labels
OVA
Milestone
2.7.0

Comments

@bkhizgiy
Copy link
Member

bkhizgiy commented Apr 9, 2024 •
edited by ahadas
Loading

With recent changes of including the firmware type in virt-v2v -o kubvirt output we want to consume the value from there rather than from scanning the logs manually for OVA provider (when the firmware configuration is missing in the OVF file).

Currently we have this PR open with the changes including this.
#778
@bkhizgiy bkhizgiy added the OVA label Apr 9, 2024
@bkhizgiy bkhizgiy self-assigned this Apr 9, 2024
@ahadas ahadas linked a pull request Apr 9, 2024 that will close this issue
Change created virt-v2v conversion output to -o kubeVirt #778
Closed
@ahadas ahadas assigned ahadas and bkhizgiy and unassigned bkhizgiy and ahadas Apr 10, 2024
@ahadas ahadas added this to the 2.7.0 milestone Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bkhizgiy bkhizgiy

Labels
OVA
Projects
None yet
Milestone
2.7.0
Development

Successfully merging a pull request may close this issue.

Change created virt-v2v conversion output to -o kubeVirt bkhizgiy/forklift
2 participants
@ahadas @bkhizgiy