Problem trying to install into a single AZ

[arnoldst]

Hi

I'm trying to install into a single AZ - but I get this error
Error: Error applying plan:

4 error(s) occurred:

• aws_efs_mount_target.icp-registry[0]: 1 error(s) occurred:

• aws_efs_mount_target.icp-registry.0: MountTargetConflict: mount target already exists in this AZ
  status code: 409, request id: 3afd04d5-b1b4-11e8-bc84-ad3cfcd0fd63

• aws_efs_mount_target.icp-audit[1]: 1 error(s) occurred:

• aws_efs_mount_target.icp-audit.1: MountTargetConflict: mount target already exists in this AZ
  status code: 409, request id: 4fa60564-b1b4-11e8-982f-47849fbf15e4

• aws_efs_mount_target.icp-registry[1]: 1 error(s) occurred:

• aws_efs_mount_target.icp-registry.1: MountTargetConflict: mount target already exists in this AZ
  status code: 409, request id: 3ad1126e-b1b4-11e8-ae1b-77ef2ec71548

• aws_efs_mount_target.icp-audit[0]: 1 error(s) occurred:

• aws_efs_mount_target.icp-audit.0: MountTargetConflict: mount target already exists in this AZ
  status code: 409, request id: 4fd552c9-b1b4-11e8-982f-47849fbf15e4

Any ideas what I'm doing wrong ? Here's my terraform.tfvars....
aws_region = "eu-west-1"
key_name = "ICP-shared-ire"
image_location = "s3://icpmedia/ibm-cloud-private-x86_64-2.1.0.3.tar.gz"
icp_inception_image = "ibmcom/icp-inception:2.1.0.3-ee"
azs = ["c"]

also change the bastion node count as below in the variables.tf file as below

EC2 instances

no bastion host by default. set to 1 if you want to debug

variable "bastion" {
type = "map"
default = {
nodes = "1"
type = "t2.micro"
ami = "" // Leave blank to let terraform search for Ubuntu 16.04 ami. NOT RECOMMENDED FOR PRODUCTION
disk = "10" //GB
}
}

Any help much appreciated.

Thanks

Steve

[jkwong888]

did you leave the number of masters to 3? the script doesnt' really support installing 3 masters to the same AZ ... we could support this case, but I am not sure why that would be desired. If you drop the number of masters to 1, it will not provision EFS at all and you can avoid this error.

[arnoldst]

Hi   So I've made some progress - basically I worked out that we need to have a single master - and thats fixed that issue.   But the icp install fails....with this FAILED - RETRYING: Waiting for iam apikey secret (1 retries left).fatal: [localhost]: FAILED! => {"attempts": 100, "changed": true, "cmd": "kubectl get secret icp-serviceid-apikey-secret -n kube-system", "delta": "0:00:00.149019", "end": "2018-09-06 14:14:27.328023", "msg": "non-zero return code", "rc": 1, "start": "2018-09-06 14:14:27.179004", "stderr": "Error from server (NotFound): secrets \"icp-serviceid-apikey-secret\" not found", "stderr_lines": ["Error from server (NotFound): secrets \"icp-serviceid-apikey-secret\" not found"], "stdout": "", "stdout_lines": []}   Any ideas ?  otherwise we can close this issue  with a response of just use a single master if you only have a single AZ.   Steve Steve Arnold MBCS CITP Consulting IT Specialist Technical Sales and Solutions | IBM Hybrid Cloud E-mail: steve.arnold@uk.ibm.com Phone: +44 (0) 7702677866                    ----- Original message -----From: Jeffrey Kwong <notifications@github.com>To: ibm-cloud-architecture/terraform-icp-aws <terraform-icp-aws@noreply.github.com>Cc: arnoldst <steve.arnold@uk.ibm.com>, Author <author@noreply.github.com>Subject: Re: [ibm-cloud-architecture/terraform-icp-aws] Problem trying to install into a single AZ (#2)Date: Thu, Sep 6, 2018 4:27 PM  did you leave the number of masters to 3? the script doesnt' really support installing 3 masters to the same AZ ... we could support this case, but I am not sure why that would be desired. If you drop the number of masters to 1, it will not provision EFS at all and you can avoid this error. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.  Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

[jkwong888]

this is actually a bug in ICP 2.1.0.3 and you will need to apply fixpack 1, which you can download from fixcentral.

https://www-945.ibm.com/support/fixcentral/

There's a patched installer image you can use that addresses installation when using a public loadbalancer.

here is some documentation on fixpack 1:
https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.3/getting_started/fix_pack1.html