Error in LFD259:2025-02-11 s_02/k8scp.sh

ivanr5

Lines 38-40 of k8scp.sh from https://cm.lf.training/LFD259/LFD259 V2025-02-11 SOLUTIONS.tar.xz look as follows:

# Install necessary software
sudo apt-get install curl apt-transport-https vim git wget gnupg2 software-properties-common apt-transport-https ca-certificates socat
-y

This leads to a number of failures further down the line, for example:

k8scp.sh: line 40: -y: command not found
mkdir: cannot create directory ‘/etc/apt/keyrings’: File exists
tee: deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.32/deb/ /
/etc/apt/: Is a directory
k8scp.sh: line 46: sources.list.d/kubernetes.list: No such file or directory
Hit:1 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu noble InRelease
Hit:2 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:3 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu noble-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package kubelet
E: Unable to locate package kubeadm
E: Unable to locate package kubectl
E: Unable to locate package kubelet
E: Unable to locate package kubeadm
E: Unable to locate package kubectl
E: No packages found
Failed to enable unit: Unit file kubelet.service does not exist.

ultimately resulting in a badly provisioned CP node.

---

Other bad lines:

• Lines 45-46
• Lines 120-122
• Lines 137-138

fazlur.khan

Hello @ivanr5 ,

The "-y" , assume yes flag for the package manager has been accidentally moved to a new line in the script causing the downstream errors. The emergency fix for this is underway and this will be fixed shortly. I will keep you posted.

Thanks,
Fazlur

ivanr5

I think I got the fixes sorted. Notice there are more issues present:

Other bad lines:

• Lines 45-46
• Lines 120-122
• Lines 137-138

fazlur.khan

Hello @ivanr5 ,

The script in the tar ball has been fixed.. We noticed that any line which was longer and spilled over to the next line, an automatic new line character was added resulting in shell to interpret that as another command and not the same and causing the errors...

Thank you for bringing this to our attention!! Much Appreciated!

Regards,
Fazlur