Skip to content
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.

Could not create AWS cluster with multiple worker pools #1392

Closed
surajssd opened this issue Feb 22, 2021 · 1 comment
Closed

Could not create AWS cluster with multiple worker pools #1392

surajssd opened this issue Feb 22, 2021 · 1 comment
Labels
area/ux User Experience bug Something isn't working platform/aws AWS-related priority/P1 High priority

Comments

@surajssd
Copy link
Member

Description

Not able to create an AWS cluster with multiple worker pools. It fails with error as follows:

Unique ports required; 'worker_pool.wp2.lb_http_port' collides with 'worker_pool.wp1.lb_http_port'  args="[]" command="lokoctl cluster apply"

Environment and steps to reproduce

  1. Set-up:

Create a lokocfg file with following contents:

cluster "aws" {
  asset_dir    = "./assets"
  cluster_name = "foobar"
  dns_zone     = "foobar"
  dns_zone_id  = "foobar"
  ssh_pubkeys  = ["foo", "bar"]

  worker_pool "wp1" {
    count       = 1
    ssh_pubkeys = ["foo", "bar"]
  }

  worker_pool "wp2" {
    count       = 1
    ssh_pubkeys = ["foo", "bar"]
  }

  worker_pool "wp3" {
    count       = 1
    ssh_pubkeys = ["foo", "bar"]
  }
}
  1. Task:
$ lokoctl cluster apply
ERRO[0000] <nil>: Unique ports required; 'worker_pool.wp2.lb_http_port' collides with 'worker_pool.wp1.lb_http_port'  args="[]" command="lokoctl cluster apply"
ERRO[0000] <nil>: Unique ports required; 'worker_pool.wp2.lb_https_port' collides with 'worker_pool.wp1.lb_https_port'  args="[]" command="lokoctl cluster apply"
ERRO[0000] <nil>: Unique ports required; 'worker_pool.wp3.lb_http_port' collides with 'worker_pool.wp2.lb_http_port'  args="[]" command="lokoctl cluster apply"
ERRO[0000] <nil>: Unique ports required; 'worker_pool.wp3.lb_https_port' collides with 'worker_pool.wp2.lb_https_port'  args="[]" command="lokoctl cluster apply"
FATA[0000] Applying cluster failed: initializing: loading platform configuration  args="[]" command="lokoctl cluster apply"

Expected behavior

I expect either these variables be marked as compulsory in the code or in the docs. Also the error is not helpful not sure what is colliding with what, when I haven't provided anything.

Additional information

This is an error on current master and in last release (0.6.1).

@surajssd surajssd added bug Something isn't working priority/P1 High priority platform/aws AWS-related area/ux User Experience labels Feb 22, 2021
@surajssd
Copy link
Member Author

Oops saw this issue: #839 #1248

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/ux User Experience bug Something isn't working platform/aws AWS-related priority/P1 High priority
Projects
None yet
Development

No branches or pull requests

1 participant