Skip to content
This repository was archived by the owner on Jan 9, 2023. It is now read-only.
This repository was archived by the owner on Jan 9, 2023. It is now read-only.

S3 bucket existence from fresh Tarmak install #755

Open
@dippynark

Description

@dippynark

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened: Following the instructions from the docs: https://docs.tarmak.io/release-0.5/user-guide.html

tarmak init
tarmak clusters images build
tarmak clusters apply

I got an error:

$ tarmak clusters apply                                                                   (gke_jetstack-luke_europe-west1-b_argo/default)
INFO[0000] validating tarmak config                      app=tarmak
INFO[0000] verifying tarmak config                       app=tarmak
INFO[0003] writing SSH config                            app=tarmak
INFO[0003] ensuring remote resources                     app=tarmak
INFO[0004] generating terraform code                     app=tarmak module=terraform
DEBU[0004] created temporary directory: /var/folders/3k/xg9qp_d150l9kpp42_1yf0900000gn/T/tarmak-assets516421419
DEBU[0005] restored assets into directory: /var/folders/3k/xg9qp_d150l9kpp42_1yf0900000gn/T/tarmak-assets516421419
INFO[0005] initialising terraform                        app=tarmak module=terraform
DEBU[0006] Initializing modules...           app=tarmak module=terraform std=out
DEBU[0006] - module.state                                app=tarmak module=terraform std=out
DEBU[0006] - module.network                              app=tarmak module=terraform std=out
DEBU[0006] - module.bastion                              app=tarmak module=terraform std=out
DEBU[0006] - module.vault                                app=tarmak module=terraform std=out
DEBU[0006] - module.kubernetes                           app=tarmak module=terraform std=out
DEBU[0006]                                               app=tarmak module=terraform std=out
DEBU[0006] Initializing the backend...       app=tarmak module=terraform std=out
DEBU[0006] Backend configuration changed!  app=tarmak module=terraform std=out
DEBU[0006]                                               app=tarmak module=terraform std=out
DEBU[0006] Terraform has detected that the configuration specified for the backend  app=tarmak module=terraform std=out
DEBU[0006] has changed. Terraform will now check for existing state in the backends.  app=tarmak module=terraform std=out
DEBU[0006]                                               app=tarmak module=terraform std=out
DEBU[0006]                                           app=tarmak module=terraform std=out
DEBU[0008] Error inspecting states in the "s3" backend:  app=tarmak module=terraform std=err
DEBU[0008]     NoSuchBucket: The specified bucket does not exist  app=tarmak module=terraform std=err
DEBU[0008] 	status code: 404, request id: C70F073F40513F67, host id: kDCstTtLX5NTJ6IJJO0Wk/fh8rfJBmTqVm1aeGMueOCQ+xAkSXpEokqlV0G67qR6QQ/nwDErsUo=  app=tarmak module=terraform std=err
DEBU[0008]                                               app=tarmak module=terraform std=err
DEBU[0008] Prior to changing backends, Terraform inspects the source and destination  app=tarmak module=terraform std=err
DEBU[0008] states to determine what kind of migration steps need to be taken, if any.  app=tarmak module=terraform std=err
DEBU[0008] Terraform failed to load the states. The data in both the source and the  app=tarmak module=terraform std=err
DEBU[0008] destination remain unmodified. Please resolve the above error and try again.  app=tarmak module=terraform std=err
ERRO[0008] tarmak exited with an error: failed to prepare terraform: error running terraform init: exit status 1

Anything else we need to know?: The binary is from the GH releases page:

$ tarmak version                                                                          (gke_jetstack-luke_europe-west1-b_argo/default)
tarmak version: 0.5.4 builddate: 2019-02-14T15:13:44Z commit: 7d7bdf80697ed9664c0b2447627edeb387f3c810 winghash: unknown

An S3 bucket aws-tarmak-luke-eu-west-1-terraform-state does exist my inspecting the AWS console

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions