Bug 1671322
| Summary: | [CDI] VM using Datavolume with invalid http causes CrashLoopBackOff to virt-controller | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Nelly Credi <ncredi> | ||||||||
| Component: | Virtualization | Assignee: | sgott | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Kedar Bidarkar <kbidarka> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 1.4 | CC: | cnv-qe-bugs, fsimonce, ncredi, sgordon, sgott | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 1.4 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | kubevirt-0.13.3-1.g573d572.79a47ba virt-controller-container-v1.4.0-21 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-02-26 13:24:18 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: | |||||||||||
| Attachments: |
|
||||||||||
Could you provide an example yaml that exhibits this behavior? Also, are you able to obtain the virt-controller logs when that pod is CrashLooping? my yml is attached in the description. will add the virt controller log Created attachment 1525342 [details]
virt controller log
Tested this with the cnv-build=CNV-1.4-RHEL-7-20190205.n.0 VERIFIED with the above build. Created attachment 1527232 [details]
virt-controller does not crash anymore
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/RHEA-2019:0417 |
Created attachment 1525323 [details] vm with dv yml - bad url Description of problem: create a vm using dv with an invalid URL the importer pod and the virt-controller pods stay in CrashLoopBackOff state until the importer is manually deleted Version-Release number of selected component (if applicable): virt-cdi-importer:v1.4.0 virt-controller:v1.4.0 How reproducible: 100% Steps to Reproduce: 1. create a yml with vm kind using dv with an invalid url 2. oc create -f your_yml 3. oc get pods Actual results: importer pod gets into CrashLoopBackOff virt-controller pods get into CrashLoopBackOff as well, at least until the importer pod is manually removed Expected results: i would expect only the importer pod to fail Additional info: once i oc delete -f bad_dv.yml, virt-controller pods get recovered