[flake test] TestStartStop/group/old-k8s-version/serial/Pause - "sudo systemctl disable kubelet" failed

[ilya-zuyev]

There is at least one test flaking with error like below. It looks like it's related to minikube stop operation and kubelet service status.

	I0609 01:41:59.357566  373430 ssh_runner.go:149] Run: sudo systemctl disable kubelet
	I0609 01:41:59.480954  373430 retry.go:31] will retry after 276.165072ms: kubelet disable: sudo systemctl disable kubelet: Process exited with status 1
	stdout:
	
	stderr:
	Synchronizing state of kubelet.service with SysV service script with /lib/systemd/systemd-sysv-install.
	Executing: /lib/systemd/systemd-sysv-install disable kubelet
	update-rc.d: error: kubelet Default-Start contains no runlevels, aborting.
	I0609 01:41:59.757382  373430 ssh_runner.go:149] Run: sudo systemctl disable kubelet
	I0609 01:41:59.875735  373430 retry.go:31] will retry after 540.190908ms: kubelet disable: sudo systemctl disable kubelet: Process exited with status 1
	stdout:
	
	stderr:
	Synchronizing state of kubelet.service with SysV service script with /lib/systemd/systemd-sysv-install.
	Executing: /lib/systemd/systemd-sysv-install disable kubelet
	update-rc.d: error: kubelet Default-Start contains no runlevels, aborting.

For the full log please see https://storage.googleapis.com/minikube-builds/logs/11610/64a4182/Docker_Linux.html#fail_TestStartStop%2fgroup%2fold-k8s-version%2fserial%2fPause

[sharifelgamal]

update-rc.d: error: kubelet Default-Start contains no runlevels, aborting. makes it seems like the kubelet systemd service somehow got into a very bad state

[ilya-zuyev]

https://github.com/systemd/systemd/blob/8156422c8f0d94d3444043282f01551084271b22/src/systemctl/systemctl-sysv-compat.c#L183

somehow systemd thinks kubelet has a sysV part and tries to use it to stop the unit. Setting SYSTEMCTL_SKIP_SYSV env for systemctl stop should help

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sharifelgamal]

The Pause tests continue to flake, I'm upping the priority of this.