Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: demo_content.yaml contains VirtualMachinePreset instead of VirtualMachineInstancePreset Version-Release number of selected component (if applicable): kubevirt/0.7.0/14.a6de7bc How reproducible: 100% Steps to Reproduce: 1.the manifest is under /usr/share/kubevirt/manifests/release/ 2.try to apply it with oc command 3. Actual results: yaml has: # Virtual Machine Presets apiVersion: kubevirt.io/v1alpha2 kind: VirtualMachinePreset error: unable to recognize \"STDIN\": no matches for kind \"VirtualMachinePreset\" in version \"kubevirt.io/v1alpha2\"", "stderr_lines": ["+ set -o pipefail", "++ rpm -ql kubevirt-manifests", "++ grep 'manifests$'", "+ manifests_dir=/usr/share/kubevirt/manifests", "+ '[' -d /usr/share/kubevirt/manifests ']'", "+ for manifest in '\"release/kubevirt.yaml\"' '\"release/demo-content.yaml\"'", "+ sed -e 's|\"/virt-\\([^\"]*\\)\"|\"/usr/bin/virt-\\1\"|' -e Expected results: yaml should have: # Virtual Machine Presets apiVersion: kubevirt.io/v1alpha2 kind: VirtualMachineInstancePreset oc apply -f should work Additional info:
Upstream fix https://github.com/kubevirt/kubevirt/pull/1264 Please review
lgtm & it already got merged anyway :)
I dont see this yaml in the environment anymore and there is this card: https://trello.com/c/JX8wqEkM/137-5-ship-presets-epic-deployment so should we have this yaml in D/S builds? as part of the kubevirt-manifests rpm? should it get extracted on deployment?
discussed with Lukas. Since the yaml is ok now, ill mark this bug as verified and open a bug for kubevirt apb, which doesnt deploy presets one thing to consider though is changing the name of this manifest to something more meaningful