Bug 1671322 - [CDI] VM using Datavolume with invalid http causes CrashLoopBackOff to virt-controller
Summary: [CDI] VM using Datavolume with invalid http causes CrashLoopBackOff to virt-c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 1.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 1.4
Assignee: sgott
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-31 11:59 UTC by Nelly Credi
Modified: 2019-02-26 13:24 UTC (History)
5 users (show)

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:
Clone Of:
Environment:
Last Closed: 2019-02-26 13:24:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vm with dv yml - bad url (806 bytes, text/plain)
2019-01-31 11:59 UTC, Nelly Credi 		no flags Details
virt controller log (8.79 KB, text/plain)
2019-01-31 12:53 UTC, Nelly Credi 		no flags Details
virt-controller does not crash anymore (1.78 KB, text/plain)
2019-02-05 16:59 UTC, Kedar Bidarkar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 1996 0 None None None 2019-01-31 15:32:45 UTC
Github kubevirt kubevirt pull 1997 0 None None None 2019-01-31 19:33:01 UTC
Red Hat Product Errata RHEA-2019:0417 0 None None None 2019-02-26 13:24:23 UTC

Description Nelly Credi 2019-01-31 11:59:15 UTC 
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
Comment 1 sgott 2019-01-31 12:36:23 UTC 
Could you provide an example yaml that exhibits this behavior?
Comment 2 sgott 2019-01-31 12:38:15 UTC 
Also, are you able to obtain the virt-controller logs when that pod is CrashLooping?
Comment 3 Nelly Credi 2019-01-31 12:51:15 UTC 
my yml is attached in the description. 
will add the virt controller log
Comment 4 Nelly Credi 2019-01-31 12:53:23 UTC 
Created attachment 1525342 [details]
virt controller log
Comment 7 Kedar Bidarkar 2019-02-05 16:56:20 UTC 
Tested this with the cnv-build=CNV-1.4-RHEL-7-20190205.n.0

VERIFIED with the above build.
Comment 8 Kedar Bidarkar 2019-02-05 16:59:02 UTC 
Created attachment 1527232 [details]
virt-controller does not crash anymore
Comment 11 errata-xmlrpc 2019-02-26 13:24:18 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.