Welcome to the Linux Foundation Forum!

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

Posts: 5
edited February 19 in LFD259 Class Forum

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

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

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

  1. k8scp.sh: line 40: -y: command not found
  2. mkdir: cannot create directory ‘/etc/apt/keyrings’: File exists
  3. tee: deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.32/deb/ /
  4. /etc/apt/: Is a directory
  5. k8scp.sh: line 46: sources.list.d/kubernetes.list: No such file or directory
  6. Hit:1 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu noble InRelease
  7. Hit:2 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu noble-updates InRelease
  8. Hit:3 http://eu-north-1.ec2.archive.ubuntu.com/ubuntu noble-backports InRelease
  9. Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease
  10. Reading package lists...
  11. Reading package lists...
  12. Building dependency tree...
  13. Reading state information...
  14. E: Unable to locate package kubelet
  15. E: Unable to locate package kubeadm
  16. E: Unable to locate package kubectl
  17. E: Unable to locate package kubelet
  18. E: Unable to locate package kubeadm
  19. E: Unable to locate package kubectl
  20. E: No packages found
  21. 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

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • 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

  • Posts: 5

    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
  • 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

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training