The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.16
• release-4.17

For more information, see the branching documentation.

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.10
• release-4.9

Contact the Test Platform or Automated Release teams for more information.

Klog is a drop in replacement for glog which we use in various places throughout the test packages. However, klog has an advantage over glog. We can use klog.SetOutput(GinkgoWrite) to redirect log lines to the Ginkgo system. This means that if a particular test passes, the logs from that test are not shown, and if the test fails, only the logs from the failed test are shown.

This will help debugging failed tests as it will remove spurious logs from the test output.

Executed the e2e test against a Power VS ocp cluster

All the tests were skipped because of unknown platform PowerVS but it took 3 hours and almost destroyed the cluster

./hack/ci-integration.sh -focus "Webhook" -v 

Sample output and Results

S [SKIPPING] in Spec Setup (BeforeEach) [2709.244 seconds]
[Feature:Machines] Webhooks
/Users/karthikkn/IPI/cluster-api-actuator-pkg/pkg/infra/webhooks.go:23
  should return an error when removing required fields from the MachineSet providerSpec [BeforeEach]
  /Users/karthikkn/IPI/cluster-api-actuator-pkg/pkg/infra/webhooks.go:138  Platform PowerVS does not have webhooks, skipping.  /Users/karthikkn/IPI/cluster-api-actuator-pkg/pkg/infra/webhooks.go:44
------------------------------
SSSSSSSSSSSSS
Ran 0 of 33 Specs in 10839.695 seconds
SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 33 Skipped
PASS

The cluster state after the test

karthikkn@Karthiks-MacBook-Pro ingress % oc get nodes -A
NAME                               STATUS                     ROLES    AGE   VERSION
rdr-kar27-ocp-mjvlj-master-1       Ready,SchedulingDisabled   master   43h   v1.22.1+8e73d6b
rdr-kar27-ocp-mjvlj-master-2       Ready,SchedulingDisabled   master   43h   v1.22.1+8e73d6b
rdr-kar27-ocp-mjvlj-worker-9kk2g   Ready,SchedulingDisabled   worker   43h   v1.22.1+8e73d6b 

It deleted all the worker nodes and machineset of cluster

While running the "drain node before removing machine resource" test on Power platform(ppc64le architecture) I could see that the Pods created by replication controller were in CrashloopBackoff state, Later on changing the image to RHEL UBI image I could see the Pods in running state and the tests were passed.

Can we change this image to have a image which has multiarch support.

Use native error checking functions from github.com/kubernetes/apimachinery project [1] rather than implementing custom error checks as:

if strings.Contains(err.Error(), "not found") {
	return true, nil
}

Also valid for other error checks, e.g. already exists errors.

[1] https://github.com/kubernetes/apimachinery/blob/master/pkg/api/errors/errors.go#L418

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.17
• release-4.18

For more information, see the branching documentation.