Auto sync upstream 2022 08 04 07 47#35
Conversation
…r-integration Added integration with the image-builder kubevirt image
In order to debug e2e test failures, add failure printout to the RunCmd function, so we could understand what went wrong in case of a failure. Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Add failure printout to the e2e test RunCmd function
…ntegration Clusterctl integration
…r-docs added docs for creating the image-builder image
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Move to golang 1.18
…access kubevirtci: Add option to interact with the tenant cluster and improve usage (help)
Signed-off-by: David Vossel <davidvossel@gmail.com>
Signed-off-by: David Vossel <davidvossel@gmail.com>
Signed-off-by: David Vossel <davidvossel@gmail.com>
Signed-off-by: David Vossel <davidvossel@gmail.com>
…dates Kubevirtci updates
Add the ability to access the tenant cluster during the test Currently checking only the Nodes exist, need to add more functionality (For example adding new operators/workloads using the network and storage) In order to have this ability, added the following: 1. Using virtctl client for kubevirt resources 2. Performing Virtctl portforward and modifying the tenant cluster kubeconfig
Signed-off-by: David Vossel <davidvossel@gmail.com>
Signed-off-by: David Vossel <davidvossel@gmail.com>
Signed-off-by: David Vossel <davidvossel@gmail.com>
Signed-off-by: David Vossel <davidvossel@gmail.com>
…tal-lb Kubevirtci metal lb support
Add tenant cluster verification to create-cluster test
Signed-off-by: David Vossel <davidvossel@gmail.com>
The domain and cidr ranges of the tenant cluster need to be offset from the default kubeadm settings or else they will likely conflict and overlap with the infra network's settings Signed-off-by: David Vossel <davidvossel@gmail.com>
Signed-off-by: David Vossel <davidvossel@gmail.com>
The test occasionally failed because the Update() vmi call returned an err. This err occurred because the vmi would mutate between the Get and Update calls. To fix this, we use a Patch Signed-off-by: David Vossel <davidvossel@gmail.com>
Add capk user properly when users already defined.
Also, add unit-test for the infracluster package.
Copy Kubeadm userdata secret labels to CAPK secret.
…ookup Fix infra secret lookup so that it defaults to the namespace of the referencing resource
When a host node is deleted, the guest VMIs are evicted, killing the running tenant node in this VMI. This PR gracefully delete the VMI, by first drain the guest node. Only if the drain successful, CAPK will delete the VMI. The PR is based on a feature in KubeVirt, where by setting the eviction strategy to "external" KubeVirt will not delete the VMI, but will set the `vmi.Status.EvacuationNodeName` field to signal to the external controller (CAPK in this case) that the VMI should be evicted. Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Also, add unit tests. Needed to changed the logic to get the guest cluster client, to use the workloadClient type, because the previous code was not testable. Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
If drain is failing for more than 10 minutes, delete the VMI anyway. Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
Graceful deletion of a VirtualMachineInstance
…to_sync_upstream_2022-08-04-07-47 Signed-off-by: Nahshon Unna-Tsameret <nunnatsa@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nunnatsa The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
@nunnatsa: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
ci is failing |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
|
too old |
|
@nunnatsa: Closed this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release notes: