kubernetes/kops · error

error resuming processes: %v

Error message

error resuming processes: %v

What it means

ResumeProcesses failed while restoring previously suspended scaling processes on an existing ASG during RenderAWS; the ASG is left with processes suspended and the wrapped AWS error explains the API failure.

Source

Thrown at upup/pkg/fi/cloudup/awstasks/autoscalinggroup.go:637

			if len(toSuspend) > 0 {
				suspendProcessQuery := &autoscaling.SuspendProcessesInput{}
				suspendProcessQuery.AutoScalingGroupName = e.Name
				suspendProcessQuery.ScalingProcesses = aws.ToStringSlice(toSuspend)

				_, err := t.Cloud.Autoscaling().SuspendProcesses(ctx, suspendProcessQuery)
				if err != nil {
					return fmt.Errorf("error suspending processes: %v", err)
				}
			}
			if len(toResume) > 0 {
				resumeProcessQuery := &autoscaling.ResumeProcessesInput{}
				resumeProcessQuery.AutoScalingGroupName = e.Name
				resumeProcessQuery.ScalingProcesses = aws.ToStringSlice(toResume)

				_, err := t.Cloud.Autoscaling().ResumeProcesses(ctx, resumeProcessQuery)
				if err != nil {
					return fmt.Errorf("error resuming processes: %v", err)
				}
			}
			changes.SuspendProcesses = nil
		}

		if changes.InstanceProtection != nil {
			request.NewInstancesProtectedFromScaleIn = e.InstanceProtection
			changes.InstanceProtection = nil
		}

		if changes.CapacityRebalance != nil {
			request.CapacityRebalance = e.CapacityRebalance
			changes.CapacityRebalance = nil
		}

		empty := &AutoscalingGroup{}
		if !reflect.DeepEqual(empty, changes) {
			klog.Warningf("cannot apply changes to AutoScalingGroup: %v", changes)

View on GitHub (pinned to 4c8573c808)

Solutions

1. Wait for in-progress scaling activities to finish, then re-run `kops update cluster --yes`
2. Confirm the process names were valid when they were suspended
3. Check IAM permissions for autoscaling:ResumeProcesses
4. Inspect ASG activities (`aws autoscaling describe-scaling-activities`) for conflicts

Example fix

null

aws autoscaling describe-scaling-activities --auto-scaling-group-name nodes-<zone> \
  --query 'Activities[?StatusCode==`InProgress`]' # wait until clear before resuming

try {
  kops update cluster --name mycluster --yes
} catch (e) {
  if (/error resuming processes/.test(e.message)) {
    // wait for scaling activities to settle, then re-run apply
  }
}

When it happens

Trigger: Removing entries from suspendProcesses so toResume is non-empty, and ResumeProcesses fails — ASG busy with scaling activity, invalid process name, or throttling.

Common situations: Re-enabling scaling during an active instance refresh or AZ rebalance; AWS returns an error because the group is mid-operation.

Related errors

• error suspending processes: %v
• DIGITALOCEAN_ACCESS_TOKEN is required
• the image for the hook exec action not set
• IP version is incorrect
• ErrAlreadyExists

AI-assisted analysis of kubernetes/kops@4c8573c808 (2026-09-05). Data as JSON: /api/errors/1d30e935306bb138. Report an issue: GitHub.