profile::consul::acl_api_token
error + Other puppet errors in magic castle puppet v10.2
#148
-
Hello, I am running into a set of errors while using the latest release of magic castle puppet (v10.2). Here are the terraform configurations I am using:terraform {
required_version = ">= 0.14.5"
}
module "aws" {
source = "git::https://github.com/ComputeCanada/magic_castle.git//aws"
config_git_url = "https://github.com/ComputeCanada/puppet-magic_castle.git"
config_version = "10.2"
cluster_name = "....."
domain = "...."
image = "ami-0155c31ea13d4abd2" # CentOS 8 - https://wiki.centos.org/Cloud/AWS
instances = {
mgmt = { type = "t3.large", count = 1 },
login = { type = "t3.medium", count = 1 },
node = [{ type = "t3.medium", count = 2 }]
}
storage = {
type = "nfs"
home_size = 100
project_size = 50
scratch_size = 50
}
public_keys = [file("~/.ssh/id_rsa.pub")]
nb_users = 2
# Shared password, randomly chosen if blank
guest_passwd = ""
# AWS specifics
region = "us-west-2"
}
module "dns" {
#source = "git::https://github.com/ComputeCanada/magic_castle.git//dns/txt"
source = "./.terraform/modules/aws/dns/txt"
name = module.aws.cluster_name
domain = module.aws.domain
public_ip = module.aws.ip
rsa_public_key = module.aws.rsa_public_key
}
output "sudoer_username" {
value = module.aws.sudoer_username
}
output "guest_usernames" {
value = module.aws.guest_usernames
}
output "guest_passwd" {
value = module.aws.guest_passwd
}
output "public_ip" {
value = module.aws.ip
}
output "hostnames" {
value = module.dns.hostnames
}
I'm wondering whether this is a bug in magic castle puppet v10.2 or something wrong in my configurations? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Update:
I downgraded the |
Beta Was this translation helpful? Give feedback.
-
Hi Anderson,
Downgrading to v10.0 won't help in this case. |
Beta Was this translation helpful? Give feedback.
-
For anyone running into this same problem, re-running |
Beta Was this translation helpful? Give feedback.
For anyone running into this same problem, re-running
terraform apply
fixes this particular issue.