Bug 1841505
| Summary: | [CNV-2.4] virt-template-validator container fails to start | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Lukas Bednar <lbednar> |
| Component: | SSP | Assignee: | Karel Šimon <ksimon> |
| Status: | CLOSED ERRATA | QA Contact: | Israel Pinto <ipinto> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.4.0 | CC: | cnv-qe-bugs, fdeutsch, lbednar, rnetser |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 2.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kubevirt-ssp-operator-container-v2.4.0-43 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-28 19:10:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
We can not lunch VM because of it, so making it as test blocker.
HTTP response body: b'{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal error occurred: failed calling webhook \\"virt-template-admission.kubevirt.io\\": Post https://virt-template-validator.openshift-cnv.svc:443/virtualmachine-template-validate?timeout=30s: service \\"virt-template-validator\\" not found","reason":"InternalError","details":{"causes":[{"message":"failed calling webhook \\"virt-template-admission.kubevirt.io\\": Post https://virt-template-validator.openshift-cnv.svc:443/virtualmachine-template-validate?timeout=30s: service \\"virt-template-validator\\" not found"}]},"code":500}\n'
It was reproduced with HCO v2.3.0-269 Template validator is running: virt-template-validator-7d4b698cc6-pvrhs 1/1 Running 0 19h virt-template-validator-7d4b698cc6-qzjlm 1/1 Running 0 19h A VM using a template can be created. Version: kubevirt-ssp-operator-container-v2.4.0-46 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3194 |
Description of problem: virt-template-validator-7b59c64fdf-2gk6d 0/1 Error 2 29s virt-template-validator-7b59c64fdf-grxsv 0/1 Error 2 29s [cloud-user@ocp-psi-executor ~]$ oc logs -n openshift-cnv virt-template-validator-7b59c64fdf-2gk6d unknown flag: --cert-file unknown flag: --cert-file Usage of /usr/sbin/kubevirt-template-validator: --alsologtostderr log to standard error as well as files -c, --cert-dir string specify path to the directory containing TLS key and certificate - this enables TLS --kubeconfig string absolute path to the kubeconfig file --listen string Address where to listen on (default "0.0.0.0") --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0) --log_dir string If non-empty, write log files in this directory --logtostderr log to standard error instead of files (default false) --master string master url --port int Port to listen on (default 8443) -S, --skip-informers don't initialize informerers - use this only in devel mode --stderrthreshold severity logs at or above this threshold go to stderr (default 2) -v, --v Level log level for V logs (default 0) -V, --version show version and exit --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging Version-Release number of selected component (if applicable): HCO v2.3.0-268 How reproducible: 100 Steps to Reproduce: 1. deploy CNV 2. observe status of virt-template-validator 3. Actual results: validator pods in error state Expected results: validator pods in up and running state Additional info: