PR #68 findings

[mbach04]

#68 two things to note in my latest test of this PR:

1. In project rfe, nexus-setup-* pod fails, no logs to capture.
2. rfe-image-builder-vm does not deploy. Argo fails to sync this manifest. Argo logs below

error validating data: ValidationError(Job.spec.template.spec.containers[0].volumeMounts[0].readOnly): invalid type for io.k8s.api.core.v1.VolumeMount.readOnly: got "string", expected "boolean"

error validating data: [ValidationError(Job.spec.template.spec.containers[0].volumeMounts[0].readOnly): invalid type for io.k8s.api.core.v1.VolumeMount.readOnly: got "string", expected "boolean", ValidationError(Job.spec.template.spec.containers[0].volumeMounts[1].readOnly): invalid type for io.k8s.api.core.v1.VolumeMount.readOnly: got "string", expected "boolean"]

[mbach04]

Just throwing this on here to share findings

[mbach04]

I applied the VM manifest manually to see what I could gather. The virt-launcher-image-builder- is failing to schedule (on rhpds cluster):

0/5 nodes are available: 2 Insufficient devices.kubevirt.io/kvm, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.

[mbach04]

As Andrew suggested, enabling software emulation on the kubevirt-config ConfigMap got the VM scheduling, it's just failing to connect now (from importer-image-builder-rootdisk- pod):

I0517 16:52:44.170909       1 importer.go:52] Starting importer
I0517 16:52:44.170972       1 importer.go:134] begin import process
E0517 16:52:44.175470       1 http-datasource.go:330] http: expected status code 200, got 404
E0517 16:52:44.176386       1 http-datasource.go:266] http: expected status code 200, got 404
E0517 16:52:44.176416       1 importer.go:140] expected status code 200, got 404. Status: 404 Not Found
kubevirt.io/containerized-data-importer/pkg/importer.createHTTPReader
	/remote-source/app/pkg/importer/http-datasource.go:267
kubevirt.io/containerized-data-importer/pkg/importer.NewHTTPDataSource
	/remote-source/app/pkg/importer/http-datasource.go:82
main.main
	/remote-source/app/cmd/cdi-importer/importer.go:138
runtime.main
	/usr/lib/golang/src/runtime/proc.go:203
runtime.goexit
	/usr/lib/golang/src/runtime/asm_amd64.s:1373

Software emulation ref: https://developers.redhat.com/blog/2020/09/17/how-to-switch-red-hat-openshift-virtualization-from-hardware-virtualization-to-software-emulation#step_3__start_the_virtual_machine_using_software_emulation

[mbach04]

The importer-image-builder-rootdisk- pod failing is related to the rfe-httpd pod having nothing in /opt/rh/httpd24/root/var/www/html I believe

[pkliczewski]

I confirm this issue still exists. The vm is still unable to boot due to missing image-builder-rootdisk datavolume.