Terraform Challenge 1 bug?

rrwada · June 27, 2024, 9:56pm

When trying to running basic update commands to install terraform it is giving an error. Attached screenshot. Nothing mentioned regarding this in solution as well[1], hence I guess this is not part of the challenge. Can you please look into it and confirm?

[1] terraform-challenges/challenge-1 at master · kodekloudhub/terraform-challenges · GitHub

rob_kodekloud · June 28, 2024, 12:16am

I’m not sure what’s going on. Your output suggests that you have not added the hashicorp apt repos.

Problem is, I have done that, and I still can’t install terraform – I get the error

Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease                                               
Err:5 https://apt.releases.hashicorp.com bionic Release                 
  404  Not Found [IP: 18.154.185.57 443]
Hit:6 http://archive.ubuntu.com/ubuntu bionic-updates InRelease         
Hit:7 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Reading package lists... Done                     
E: The repository 'https://apt.releases.hashicorp.com bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

which is unexpected; it appears there’s some transient problem with their repos. I’d tell you to try to download binaries from their releases page, but 1.15 is so old they only have source code; you’d need to build terraform 1.1.5 from scratch, which is likely not what the intention is.

Try waiting a few hours and trying the install link to see if the situation has healed. If it hasn’t righted itself in a few hours, I’ll look into this again.

rrwada · June 28, 2024, 2:03am

Seems there is already an open issue

github.com/kubernetes/release

The legacy Kubernetes package repositories are removed as of 2024-03-04

opened 10:41AM - 04 Mar 24 UTC

xmudrii

kind/support needs-priority

[As announced previously](https://kubernetes.io/blog/2023/08/31/legacy-package-r…epository-deprecation/), the legacy Kubernetes package repositories (`apt.kubernetes.io` and `yum.kubernetes.io`, also known as `packages.cloud.google.com`) have been shut down (removed) as of 2024-03-04. ## What does this mean for me? If you use these legacy Kubernetes package repositories, you'll encounter errors upon using your package manager. In this case, you need to take steps outlined in this issue to resolve the problem. ## How can I recognize if I'm affected by this? If you use `apt` (`apt-get`), you're likely to get an error upon running `apt update` (`apt-get update`). Example errors include: ```shell Ign:9 https://packages.cloud.google.com/apt kubernetes-xenial InRelease Err:10 https://packages.cloud.google.com/apt kubernetes-xenial Release 404 Not Found [IP: xxx.xxx.xxx.xxx 443] Reading package lists... Done E: The repository ‘https://apt.kubernetes.io/ kubernetes-xenial Release’ no longer has a Release file. ``` If you use `yum` (or `dnf`), you're likely to get an error upon running any `yum` or `dnf` command. Example errors include: ```shell Error during downloading metadata for repository 'kubernetes': - Status code: 404 for https://packages.cloud.google.com/yum/repos/kubernetes-el7-x85_64/repodata/repomd.xml (IP: xxx.xxx.xxx.xxx) Error: Failed to download metadata for repo 'kubernetes': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried ``` ## How to mitigate? Please see the [deprecation announcement](https://kubernetes.io/blog/2023/08/31/legacy-package-repository-deprecation/) and the [pkgs.k8s.io announcement](https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/) blog posts for more details. In short, you need to: - [migrate to the Kubernetes official package repositories (`pkgs.k8s.io`)](https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/#how-to-migrate) - if you don't need Kubernetes repositories on your system any longer, or if there's no Kubernetes version that you need in the official Kubernetes package repositories, you can just delete the legacy Kubernetes repositories from your system - if you followed the official Kubernetes documentation to set up the legacy repositories, you'll likely find these repositories defined in `/etc/apt/sources.list.d/kubernetes.list` (for `apt` users) or `/etc/yum.repos.d/kubernetes.repo` (for `yum`/`dnf` users) ## Where can I get support for this? We'll be following up on potential mitigations for users affected by this in the coming days. Please keep an eye on this issue if you're affected.

I tried the steps mentioned in

Still same issue

rob_kodekloud · June 28, 2024, 4:07am

Actually not the issue you’re facing. Yes, those are obsolete repositories. But they don’t interfere with installing terraform. You’re not installing K8s; you don’t need a valid K8s repo for not installing it. You should be able to install terraform by:

adding the Hashicorp repository to APT
apt update
apt install terraform

I have doubts if it is possible to install v1.1.5 even under those circumstances, but right now, you can’t install anything newer either. Because apparently, there’s a problem with Hashicorp’s repo right now as well.

Alistair_KodeKloud · June 28, 2024, 4:23am

Or easier than that

{
apt update
apt install unzip -y
curl -L -o /tmp/terraform_1.1.5_linux_amd64.zip https://releases.hashicorp.com/terraform/1.1.5/terraform_1.1.5_linux_amd64.zip
unzip -d /usr/local/bin /tmp/terraform_1.1.5_linux_amd64.zip
}

root@controlplane ~ ✖ terraform version
Terraform v1.1.5
on linux_amd64

Your version of Terraform is out of date! The latest version
is 1.9.0. You can update by downloading from https://www.terraform.io/downloads.html

rob_kodekloud · June 28, 2024, 5:39am

Except I don’t think that a binary is available for 1.1.5 any more. I checked releases; all they have for 1.1.5 is source archives. You’d need to install make and a mess of other stuff, and golang to build it with.