Bug 1707427

Summary: Document that kubectl drain and oc adm drain do not behave as expected
Product: Container Native Virtualization (CNV) Reporter: Fabian Deutsch <fdeutsch>
Component: DocumentationAssignee: Pan Ousley <pousley>
Status: CLOSED CURRENTRELEASE QA Contact: Irina Gulina <igulina>
Severity: high Docs Contact:
Priority: high    
Version: 2.0CC: aburden, cnv-qe-bugs, ipinto, lmandavi, ncredi, pousley, rmohr, sgordon
Target Milestone: ---   
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-24 14:53:16 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:

Description Fabian Deutsch 2019-05-07 13:55:05 UTC
We need a documentation item which describes how CNV behaves with oc adm drain (kubectl drain).

The problem is as follows:
Today CNV (kubevirt) can not reliably identify node drains if they are triggered through a call of "oc adm drain" (or "kubectl drain").
If these commands are called on a node of a cluster with CNV deployed, then those nodes might not go to maintenance if there are VMs running on top of that node.

Workaround:
The current solution is to use the Node Maintenance Operator for putting nodes into maintenance.

Comment 2 Pan Ousley 2019-06-09 19:23:32 UTC
Fabian, could you please provide the original BZ URL for this issue? Thanks!

Comment 3 Fabian Deutsch 2019-06-11 12:46:08 UTC
There was no original bug.

ROman/rmohrRoan can provide the relevant details for this item.

Comment 15 Pan Ousley 2019-09-24 14:53:16 UTC
The content associated with this bug was published in the CNV 2.0 Release Notes: https://docs.openshift.com/container-platform/4.1/cnv/cnv_release_notes/cnv-release-notes.html

Comment 17 Israel Pinto 2019-10-23 14:40:09 UTC
@Pan,
I verify with Dev, the issue should also be in 2.1 release notes.