Bug 1666267 - API Change: Remove volumeName
Summary: API Change: Remove volumeName
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: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-15 11:26 UTC by Fabian Deutsch
Modified: 2019-02-26 13:24 UTC (History)
3 users (show)

Fixed In Version: kubevirt-0.13.0-1.g7b9cb66.f6a440c virt-api-container-v1.4.0-12
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)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:0417 0 None None None 2019-02-26 13:24:23 UTC

Description Fabian Deutsch 2019-01-15 11:26:32 UTC
Description of problem:
We want to pull in an upstream change which is breaking the API.

We want to pull it in, because we want to get our CNV API into a shape which can be kept stable over time once we reach GA.

The fix to this bug is to effectveily pull in KubeVirt 0.13

Version-Release number of selected component (if applicable):
1.4

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Israel Pinto 2019-01-15 11:29:33 UTC
I update the kubevirt-ansible test with the change
PR: https://github.com/kubevirt/kubevirt-ansible/pull/550
Will do some manual test also

Comment 3 Israel Pinto 2019-01-24 08:59:19 UTC
Automation test update in Kubevirt ansible: https://github.com/kubevirt/kubevirt-ansible/pull/556 
Manual check - PASS

Comment 6 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.