Kublet refuses to start because of hidden swap partition

I was experiencing issues where coredns refused to start even after I installed a CNI. Works, kubelet refused to start after a reboot. Logs stated that swap was still enabled, even after I'd removed it via normal means (run swapoff and edit /etc/fstab).

The problem turned out to be still having a swap partitiion in the file system. It was created as part of the OS install and deleting it from /etc/fstab didn't cause the partition to be removed. In other words, somewhere along the line the system is checking the partition table, and alerting on swap, even though it's not actually being used (e.g., it doesn't show up in the /etc/fstab or via "swapon --show").

You can view your disk table via the "blkid" command. Example:

root@cf1:~# blkid
/dev/nvme0n1p1: UUID="8F39-9A16" BLOCK_SIZE="512" TYPE="vfat" \
  PARTUUID="b218aaa5-0fe2-4c78-8962-08ef25d7a85c"
/dev/nvme0n1p2: UUID="0f363b61-a996-4a19-9bee-9280360a68b0" \
  BLOCK_SIZE="4096" TYPE="ext4" PARTUUID=\
  "b30c1cff-9030-4211-bd58-ba7b07c6ef96"
/dev/nvme0n1p3: UUID="71988c4b-914e-4022-8b47-7e90423c9e60" \
  TYPE="swap" PARTUUID="608469c4-05"

The fix is to edit the file system and remove the partition, using fdisk. Then reboot.

In my case, since the machine was NVME-only, I had to run:

fisk /dev/nvme0n1

and delete the /dev/nvmr0n1p3 particition.

Don't forget to press "w" at the end to write the new fs table to disk.

Note: this may be caused by deleting the line from /etc/fstab, instead of just commenting it out. When I just commented out the fstab line in the worker nodes, they did not experience the same problem.

Fix yer own jank, Google!

Just eff'in awesome. Google is sending me complaints that about how my blog is indexed. Since Google owns Blogger (which hosts this blog), you'd think that Google would recognize where the problem lies.

I've had enough. Between the new unfriendliness with email (new as in Cox moved their email to Yahoo and Google doesn't play nice with Yahoo), I'm looking at alternatives to Google's products. At this point, I'll pay for subscriptions rather than contribute any more time to develop work-arounds.

List me as: Meh.