Skip to content

Unnecessary machine creation and immediate deletion fix#1069

Merged
gardener-prow[bot] merged 5 commits intogardener:masterfrom
r4mek:unnecessary-machine-creation
Feb 17, 2026
Merged

Unnecessary machine creation and immediate deletion fix#1069
gardener-prow[bot] merged 5 commits intogardener:masterfrom
r4mek:unnecessary-machine-creation

Conversation

@r4mek
Copy link
Contributor

@r4mek r4mek commented Feb 16, 2026

What this PR does / why we need it:
This PR contains fix for the issue #1068, where MCM was creating a machine and immediately deletes it. This happened because of timing issue in MCM. Refer the issue for further details.

Summarizing the approach:
This PR solves the issue by first letting MachineSet controller take scaling decisions based on what view it has of the cluster. And the stale machine termination is done at the end. We know that in the next reconciliation, MachineSet controller will also observe the deletion of staleMachines done in the previous reconciliation. Hence, MachineSet controller at all times will atmost lag behind MachineDeployment controller by 1 reconciliation.

Which issue(s) this PR fixes:
Fixes #1068

Special notes for your reviewer:

Release note:

Fix machines termination in machine set replica management to avoid needless scale-up of machines because of stale replica count.

@r4mek r4mek requested a review from a team as a code owner February 16, 2026 07:31
@gardener-prow gardener-prow bot added do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 16, 2026
@r4mek
Copy link
Contributor Author

r4mek commented Feb 16, 2026

Manual Testing to mock the error scenario

func (c *controller) manageReplicas(ctx context.Context, allMachines []*v1alpha1.Machine, machineSet *v1alpha1.MachineSet) error {
	machineSetKey, err := KeyFunc(machineSet)
        if err != nil {
		utilruntime.HandleError(fmt.Errorf("Couldn't get key for %v %#v: %v", machineSet.Kind, machineSet, err))
		return nil
	}

	// Testing the timing issue.
	mcd := c.getMachineDeploymentsForMachineSet(machineSet)
	if mcd[0].Spec.Replicas == 5 {
		mcdCopy := mcd[0].DeepCopy()
		mcdCopy.Spec.Replicas = 4
		mcdCopy.Annotations[machineutils.TriggerDeletionByMCM] = allMachines[0].Name
		_, err = c.controlMachineClient.MachineDeployments(c.namespace).Update(ctx, mcdCopy, metav1.UpdateOptions{})
	}
        ...
}

Logs

Previous logs
I0216 12:54:51.165641   47769 deployment.go:462] Processing the machinedeployment "shoot--i759930--mcm-test-aws-worker-wvzit-z1" (with replicas 5)           <---- Original MachineDeployment ReplicaCount
I0216 12:54:51.165883   47769 machineset.go:540] Processing the machineset "shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f" with replicas 5 associated with machine class: "shoot--i759930--mcm-test-aws-worker-wvzit-z1-ea1f0"           <---- MachineSet ReplicaCount is 5
I0216 12:54:52.603338   47769 deployment.go:462] Processing the machinedeployment "shoot--i759930--mcm-test-aws-worker-wvzit-z1" (with replicas 4)            <---- MachineDeployment ReplicaCount changed to 4
I0216 12:54:52.867647   47769 deployment.go:678] Machine "shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f-g9glh" of MachineDeployment "shoot--i759930--mcm-test-aws-worker-wvzit-z1" marked with MachinePriority=1 annotation successfully           <---- Machine being marked for deletion
...
I0216 12:54:53.123005   47769 machineset.go:364] Deleting stale machines [shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f-g9glh]                <---- Marked Machine is being deleted
...
I0216 12:54:53.908718   47769 machineset.go:419] Too few replicas for MachineSet shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f, need 5, creating 1      <---- MachineSet has stale ReplicaCount value and decides to create a Machine
...
I0216 12:54:54.267229   47769 event.go:377] Event(v1.ObjectReference{Kind:"MachineSet", Namespace:"shoot--i759930--mcm-test-aws", Name:"shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f", UID:"9c0ab6bb-b15f-4ef3-9950-dd307e121fa1", APIVersion:"machine.sapcloud.io/v1alpha1", ResourceVersion:"15109174873", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created Machine: shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f-v89fb           <---- Machine is created
...
I0216 12:54:54.579871   47769 machineset.go:467] Too many replicas for  shoot--i759930--mcm-test-aws/shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f, need 4, deleting 1               <---- MachineSet ReplicaCount is in sync with MachineDeployment ReplicaCount. Hence, deleting the previously created Machine
...
I0216 12:54:54.835495   47769 event.go:377] Event(v1.ObjectReference{Kind:"MachineSet", Namespace:"shoot--i759930--mcm-test-aws", Name:"shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f", UID:"9c0ab6bb-b15f-4ef3-9950-dd307e121fa1", APIVersion:"machine.sapcloud.io/v1alpha1", ResourceVersion:"15109215658", FieldPath:""}): type: 'Normal' reason: 'SuccessfulDelete' Deleted machine: shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f-v89fb            <---- Previously created Machine is deleted
...
Code-fix logs
I0216 10:34:05.210045   42527 deployment.go:462] Processing the machinedeployment "shoot--i759930--mcm-test-aws-worker-wvzit-z1" (with replicas 5)             <---- Original MachineDeployment ReplicaCount
I0216 10:34:05.210509   42527 machineset.go:516] Processing the machineset "shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f" with replicas 5 associated with machine class: "shoot--i759930--mcm-test-aws-worker-wvzit-z1-ea1f0".                   <---- MachineSet ReplicaCount is 5
I0216 10:34:06.685749   42527 deployment.go:462] Processing the machinedeployment "shoot--i759930--mcm-test-aws-worker-wvzit-z1" (with replicas 4)               <---- MachineDeployment ReplicaCount changed to 4
...
I0216 10:34:06.949244   42527 deployment.go:678] Machine "shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f-282tq" of MachineDeployment "shoot--i759930--mcm-test-aws-worker-wvzit-z1" marked with MachinePriority=1 annotation successfully                     <---- Machine is being marked for deletion
...
I0216 10:34:08.297444   42527 machineset.go:422] Too many replicas for  shoot--i759930--mcm-test-aws/shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f, need 4, deleting 1                   <---- Marked Machine is being deleted
...
I0216 10:34:08.564636   42527 event.go:377] Event(v1.ObjectReference{Kind:"MachineSet", Namespace:"shoot--i759930--mcm-test-aws", Name:"shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f", UID:"9c0ab6bb-b15f-4ef3-9950-dd307e121fa1", APIVersion:"machine.sapcloud.io/v1alpha1", ResourceVersion:"15107574339", FieldPath:""}): type: 'Normal' reason: 'SuccessfulDelete' Deleted machine: shoot--i759930--mcm-test-aws-worker-wvzit-z1-5954f-282tq            <---- Previously marked Machine is deleted
...

@r4mek r4mek marked this pull request as draft February 16, 2026 08:37
@gardener-prow gardener-prow bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 16, 2026
@gardener-prow gardener-prow bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 17, 2026
@r4mek r4mek marked this pull request as ready for review February 17, 2026 08:27
@gardener-prow gardener-prow bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 17, 2026
Copy link
Member

@takoverflow takoverflow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the careful consideration of in-place update scenarios. Have added some comments, PTAL!

@elankath
Copy link
Member

elankath commented Feb 17, 2026

@r4mek can you please summarize how the fix solves the issue (for posterity) and also add the release note ?

@r4mek
Copy link
Contributor Author

r4mek commented Feb 17, 2026

Done.

@gardener-prow gardener-prow bot added the lgtm Indicates that a PR is ready to be merged. label Feb 17, 2026
@gardener-prow
Copy link

gardener-prow bot commented Feb 17, 2026

LGTM label has been added.

DetailsGit tree hash: d1d1085fdfd175291add6a31a0a581166f45ba28

@gardener-prow
Copy link

gardener-prow bot commented Feb 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: takoverflow

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gardener-prow gardener-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 17, 2026
@takoverflow takoverflow added kind/enhancement Enhancement, improvement, extension and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Feb 17, 2026
@gardener-prow gardener-prow bot merged commit 7256bdb into gardener:master Feb 17, 2026
13 checks passed
@takoverflow
Copy link
Member

/cherry-pick rel-v0.61

@gardener-ci-robot
Copy link

@takoverflow: new pull request created: #1071

Details

In response to this:

/cherry-pick rel-v0.61

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-sigs/prow repository.

@r4mek
Copy link
Contributor Author

r4mek commented Feb 17, 2026

Integration Logs

Details
Running Suite: Controller Suite - /Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/test/integration/controller
===============================================================================================================================================
Random Seed: 1771335980

Will run 10 of 10 specs
------------------------------
[BeforeSuite]
/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/test/integration/controller/controller_test.go:47
  > Enter [BeforeSuite] TOP-LEVEL @ 02/17/26 19:16:32.288
  STEP: Checking for the clusters if provided are available @ 02/17/26 19:16:32.289
  2026/02/17 19:16:32 Control cluster kube-config - /Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/dev/kube-configs/kubeconfig_control.yaml
  2026/02/17 19:16:32 Target cluster kube-config  - /Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/dev/kube-configs/kubeconfig_target.yaml
  STEP: Killing any existing processes @ 02/17/26 19:16:34.909
  STEP: Checking Machine-Controller-Manager repo is available at: ../../../dev/mcm @ 02/17/26 19:16:35.147
  STEP: Scaledown existing machine controllers @ 02/17/26 19:16:35.148
  STEP: Starting Machine Controller  @ 02/17/26 19:16:35.328
  STEP: Starting Machine Controller Manager @ 02/17/26 19:16:35.336
  STEP: Cleaning any old resources @ 02/17/26 19:16:35.341
  2026/02/17 19:16:35 machinedeployments.machine.sapcloud.io "test-machine-deployment" not found
  2026/02/17 19:16:35 machines.machine.sapcloud.io "test-machine" not found
  2026/02/17 19:16:35 machineclasses.machine.sapcloud.io "test-mc-v1" not found
  2026/02/17 19:16:36 machineclasses.machine.sapcloud.io "test-mc-v2" not found
  STEP: Setup MachineClass @ 02/17/26 19:16:36.056
  STEP: Looking for machineclass resource in the control cluster @ 02/17/26 19:16:37.336
  STEP: Looking for secrets refered in machineclass in the control cluster @ 02/17/26 19:16:37.516
  STEP: Initializing orphan resource tracker @ 02/17/26 19:16:37.871
  2026/02/17 19:16:41 orphan resource tracker initialized
  < Exit [BeforeSuite] TOP-LEVEL @ 02/17/26 19:16:41.969 (9.681s)
[BeforeSuite] PASSED [9.681 seconds]
------------------------------
Machine controllers test machine resource creation should not lead to any errors and add 1 more node in target cluster
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:649
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:16:41.969
  STEP: Checking machineController process is running @ 02/17/26 19:16:41.969
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:16:41.969
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:16:41.969
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:16:42.571 (602ms)
  > Enter [It] should not lead to any errors and add 1 more node in target cluster @ 02/17/26 19:16:42.572
  STEP: Checking for errors @ 02/17/26 19:16:42.767
  STEP: Waiting until number of ready nodes is 1 more than initial nodes @ 02/17/26 19:16:42.972
  < Exit [It] should not lead to any errors and add 1 more node in target cluster @ 02/17/26 19:18:19.925 (1m37.354s)
• [97.956 seconds]
------------------------------
Machine controllers test machine resource deletion when machines available should not lead to errors and remove 1 node in target cluster
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:678
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:18:19.926
  STEP: Checking machineController process is running @ 02/17/26 19:18:19.926
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:18:19.926
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:18:19.926
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:18:20.323 (398ms)
  > Enter [It] should not lead to errors and remove 1 node in target cluster @ 02/17/26 19:18:20.323
  STEP: Checking for errors @ 02/17/26 19:18:21.278
  STEP: Waiting until test-machine machine object is deleted @ 02/17/26 19:18:21.468
  STEP: Waiting until number of ready nodes is equal to number of initial nodes @ 02/17/26 19:18:50.053
  < Exit [It] should not lead to errors and remove 1 node in target cluster @ 02/17/26 19:18:50.639 (30.315s)
• [30.713 seconds]
------------------------------
Machine controllers test machine resource deletion when machines are not available should keep nodes intact
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:717
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:18:50.639
  STEP: Checking machineController process is running @ 02/17/26 19:18:50.639
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:18:50.639
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:18:50.639
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:18:51.034 (395ms)
  > Enter [It] should keep nodes intact @ 02/17/26 19:18:51.034
  STEP: Skipping as there are machines available and this check can't be performed @ 02/17/26 19:18:51.391
  < Exit [It] should keep nodes intact @ 02/17/26 19:18:51.391 (357ms)
• [0.752 seconds]
------------------------------
Machine controllers test machine deployment resource creation with replicas=0, scale up with replicas=1 should not lead to errors and add 1 more node to target cluster
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:745
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:18:51.391
  STEP: Checking machineController process is running @ 02/17/26 19:18:51.391
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:18:51.391
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:18:51.391
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:18:51.783 (392ms)
  > Enter [It] should not lead to errors and add 1 more node to target cluster @ 02/17/26 19:18:51.783
  STEP: Checking for errors @ 02/17/26 19:18:51.978
  STEP: Waiting for Machine Set to be created @ 02/17/26 19:18:52.16
  STEP: Updating machineDeployment replicas to 1 @ 02/17/26 19:18:54.88
  STEP: Checking if machineDeployment's status has been updated with correct conditions @ 02/17/26 19:18:55.243
  STEP: Checking number of ready nodes==1 @ 02/17/26 19:20:49.904
  STEP: Fetching initial number of machineset freeze events @ 02/17/26 19:20:51.253
  < Exit [It] should not lead to errors and add 1 more node to target cluster @ 02/17/26 19:20:52.154 (2m0.372s)
• [120.764 seconds]
------------------------------
Machine controllers test machine deployment resource scale-up with replicas=6 should not lead to errors and add further 5 nodes to target cluster
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:813
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:20:52.155
  STEP: Checking machineController process is running @ 02/17/26 19:20:52.155
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:20:52.155
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:20:52.155
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:20:52.734 (579ms)
  > Enter [It] should not lead to errors and add further 5 nodes to target cluster @ 02/17/26 19:20:52.734
  STEP: Checking for errors @ 02/17/26 19:20:53.099
  STEP: Checking number of ready nodes are 6 more than initial @ 02/17/26 19:20:53.1
  < Exit [It] should not lead to errors and add further 5 nodes to target cluster @ 02/17/26 19:22:40.115 (1m47.381s)
• [107.961 seconds]
------------------------------
Machine controllers test machine deployment resource scale-down with replicas=2 should not lead to errors and remove 4 nodes from target cluster
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:843
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:22:40.115
  STEP: Checking machineController process is running @ 02/17/26 19:22:40.115
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:22:40.115
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:22:40.115
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:22:40.514 (399ms)
  > Enter [It] should not lead to errors and remove 4 nodes from target cluster @ 02/17/26 19:22:40.514
  STEP: Checking for errors @ 02/17/26 19:22:41.519
  STEP: Checking number of ready nodes are 2 more than initial @ 02/17/26 19:22:41.52
  < Exit [It] should not lead to errors and remove 4 nodes from target cluster @ 02/17/26 19:23:12.469 (31.955s)
• [32.354 seconds]
------------------------------
Machine controllers test machine deployment resource scale-down with replicas=2 should freeze and unfreeze machineset temporarily
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:872
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:23:12.469
  STEP: Checking machineController process is running @ 02/17/26 19:23:12.47
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:23:12.47
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:23:12.47
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:23:12.864 (394ms)
  > Enter [It] should freeze and unfreeze machineset temporarily @ 02/17/26 19:23:12.864
  < Exit [It] should freeze and unfreeze machineset temporarily @ 02/17/26 19:23:19.033 (6.169s)
• [6.563 seconds]
------------------------------
Machine controllers test machine deployment resource updation to v2 machine-class and replicas=4 should upgrade machines and add more nodes to target
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:881
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:23:19.033
  STEP: Checking machineController process is running @ 02/17/26 19:23:19.033
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:23:19.033
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:23:19.033
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:23:19.8 (767ms)
  > Enter [It] should upgrade machines and add more nodes to target @ 02/17/26 19:23:19.8
  STEP: Checking for errors @ 02/17/26 19:23:20.167
  STEP: UpdatedReplicas to be 4 @ 02/17/26 19:23:20.167
  STEP: AvailableReplicas to be 4 @ 02/17/26 19:23:26.886
  STEP: Number of ready nodes be 4 more @ 02/17/26 19:25:20.613
  < Exit [It] should upgrade machines and add more nodes to target @ 02/17/26 19:25:55.371 (2m35.58s)
• [156.347 seconds]
------------------------------
Machine controllers test machine deployment resource deletion When there are machine deployment(s) available in control cluster should not lead to errors and list only initial nodes
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:935
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:25:55.371
  STEP: Checking machineController process is running @ 02/17/26 19:25:55.371
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:25:55.371
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:25:55.371
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:25:55.775 (404ms)
  > Enter [It] should not lead to errors and list only initial nodes @ 02/17/26 19:25:55.775
  STEP: Checking for errors @ 02/17/26 19:25:55.955
  STEP: Waiting until number of ready nodes is equal to number of initial  nodes @ 02/17/26 19:25:56.14
  < Exit [It] should not lead to errors and list only initial nodes @ 02/17/26 19:26:34.778 (39.003s)
• [39.407 seconds]
------------------------------
Machine controllers test orphaned resources when the hyperscaler resources are queried should have been deleted
/Users/I759930/go/pkg/mod/github.com/gardener/machine-controller-manager@v0.61.1/pkg/test/integration/common/framework.go:972
  > Enter [BeforeEach] Machine controllers test @ 02/17/26 19:26:34.778
  STEP: Checking machineController process is running @ 02/17/26 19:26:34.779
  STEP: Checking machineControllerManager process is running @ 02/17/26 19:26:34.779
  STEP: Checking nodes in target cluster are healthy @ 02/17/26 19:26:34.779
  < Exit [BeforeEach] Machine controllers test @ 02/17/26 19:26:35.166 (387ms)
  > Enter [It] should have been deleted @ 02/17/26 19:26:35.166
  STEP: Querying and comparing @ 02/17/26 19:26:35.166
  < Exit [It] should have been deleted @ 02/17/26 19:26:38.839 (3.673s)
• [4.061 seconds]
------------------------------
[AfterSuite]
/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/test/integration/controller/controller_test.go:49
  > Enter [AfterSuite] TOP-LEVEL @ 02/17/26 19:26:38.839
  STEP: Running Cleanup @ 02/17/26 19:26:38.84
  2026/02/17 19:26:59 machinedeployments.machine.sapcloud.io "test-machine-deployment" not found
  2026/02/17 19:26:59 machines.machine.sapcloud.io "test-machine" not found
  2026/02/17 19:26:59 deleting test-mc-v1 machineclass
  2026/02/17 19:26:59 machineclass deleted
  2026/02/17 19:27:00 deleting test-mc-v2 machineclass
  2026/02/17 19:27:00 machineclass deleted
  STEP: Killing any existing processes @ 02/17/26 19:27:00.661
  2026/02/17 19:27:00 controller_manager --control-kubeconfig=/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/dev/kube-configs/kubeconfig_control.yaml --target-kubeconfig=/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/dev/kube-configs/kubeconfig_target.yaml --namespace=shoot--i759930--mcm-ca-int --safety-up=2 --safety-down=1 --machine-safety-overshooting-period=300ms --leader-elect=false --v=3
  2026/02/17 19:27:00 stopMCM killed MCM process(es) with pid(s): [94235]
  2026/02/17 19:27:00 main --control-kubeconfig=/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/dev/kube-configs/kubeconfig_control.yaml --target-kubeconfig=/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/dev/kube-configs/kubeconfig_target.yaml --namespace=shoot--i759930--mcm-ca-int --machine-creation-timeout=20m --machine-drain-timeout=5m --machine-health-timeout=10m --machine-pv-detach-timeout=2m --machine-safety-apiserver-statuscheck-timeout=30s --machine-safety-apiserver-statuscheck-period=1m --machine-safety-orphan-vms-period=30m --leader-elect=false --v=3
  2026/02/17 19:27:00 stopMCM killed MCM process(es) with pid(s): [93848]
  2026/02/17 19:27:00 make --directory=../../../dev/mcm start CONTROL_KUBECONFIG=/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/dev/kube-configs/kubeconfig_control.yaml TARGET_KUBECONFIG=/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws/dev/kube-configs/kubeconfig_target.yaml CONTROL_NAMESPACE=shoot--i759930--mcm-ca-int LEADER_ELECT=false MACHINE_SAFETY_OVERSHOOTING_PERIOD=300ms
  2026/02/17 19:27:00 stopMCM killed MCM process(es) with pid(s): [93828]
  STEP: Scale back the existing machine controllers @ 02/17/26 19:27:00.94
  < Exit [AfterSuite] TOP-LEVEL @ 02/17/26 19:27:01.604 (22.764s)
[AfterSuite] PASSED [22.764 seconds]
------------------------------

Ran 10 of 10 Specs in 629.326 seconds
SUCCESS! -- 10 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 10m41.050888s
Test Suite Passed
Integration tests completed successfully
/Users/I759930/go/src/github.com/gardener/machine-controller-manager-provider-aws

@takoverflow
Copy link
Member

/cherry-pick rel-v0.60

@gardener-ci-robot
Copy link

@takoverflow: new pull request created: #1073

Details

In response to this:

/cherry-pick rel-v0.60

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. kind/enhancement Enhancement, improvement, extension lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MCM creates a Machine and immediately deletes it

4 participants