Comment 4 for bug 2032783

Revision history for this message
Chris (undrh2o) wrote :

I found a poor workaround - after the failure below I add the proxy to juju with

juju model-config http-proxy=http://10.158.100.3:8080
juju model-config https-proxy=http://10.158.100.3:8080

then when I re-run the "sunbeam cluster bootstrap" - it will proceed past that point but it fails later (still debugging why)

####Failure###
#>sunbeam cluster bootstrap --role control --role compute --role storage --accept-defaults
⠴ Deploying Sunbeam Machine ... terraform apply failed:
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # juju_application.sunbeam-machine will be created
  + resource "juju_application" "sunbeam-machine" {
      + constraints = (known after apply)
      + id = (known after apply)
      + model = "controller"
      + name = "sunbeam-machine"
      + placement = (known after apply)
      + principal = (known after apply)
      + trust = false
      + units = 0

      + charm {
          + channel = "latest/edge"
          + name = "sunbeam-machine"
          + revision = (known after apply)
          + series = "jammy"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.
juju_application.sunbeam-machine: Creating...
juju_application.sunbeam-machine: Still creating... [10s elapsed]
juju_application.sunbeam-machine: Still creating... [20s elapsed]
juju_application.sunbeam-machine: Still creating... [30s elapsed]

Error: resolving with preferred channel: Post "https://api.charmhub.io/v2/charms/refresh": dial tcp 185.125.188.58:443: i/o timeout

  with juju_application.sunbeam-machine,
  on main.tf line 29, in resource "juju_application" "sunbeam-machine":
  29: resource "juju_application" "sunbeam-machine" {

Error: Command '['/snap/openstack/316/bin/terraform', 'apply', '-auto-approve', '-no-color']' returned non-zero exit status 1.