Canonical Juju

Deployed units using Oracle Cloud / OCI provider in wrong region

Bug #1864154 reported by Haw Loeung
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Vitaly Antonenko
Canonical Juju 3.3.1

Bug Description

Hi,

I'm trying to deploy units in oracle/us-phoenix-1, but looking at the dashboard, it seems these units end up in us-ashburn. See links below (sorry, company private):

Juju status output:

| https://pastebin.canonical.com/p/PfdZmBcPt2/

However, dashboard:

| https://private-fileshare.canonical.com/~hloeung/tmp/CcJLBjYl.png

Haw Loeung (hloeung)
summary: - Deployed units using Oracle / OCI provider in wrong region
+ Deployed units using Oracle Cloud / OCI provider in wrong region
Heather Lanigan (hmlanigan)
tags: added: oracle-provider
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

Do you have a 'default-region' or 'region' specified in your credentials.yaml? What regions are specified in your clouds.yaml?

How did you specify the region during bootstrap?

Changed in juju:
status: New → Triaged
Revision history for this message
Haw Loeung (hloeung) wrote :

Oh yes, there's a 'region' specified when I do 'juju show-credentials oracle oracle-oci':

| controller-credentials:
| oracle:
| oracle-oci:
| content:
| auth-type: httpsig
| validity-check: valid
| ...
| region: us-ashburn-1

I didn't put that there. Didn't specify one which I believe the default is ashburn. Also, any ideas why phoenix would show up in 'juju status'?

Revision history for this message
Haw Loeung (hloeung) wrote :

| $ juju status --format=yaml
| model:
| name: us-phoenix-1
| type: iaas
| controller: oracle-...-controller-1
| cloud: oracle
| region: us-phoenix-1
| version: 2.7.2
| model-status:
| current: available
| since: 20 Feb 2020 22:38:53Z
| sla: unsupported
| machines:
| "1":
| juju-status:
| current: started
| since: 21 Feb 2020 05:57:32Z
| version: 2.7.2
| dns-name: 150.136.239.201
| ip-addresses:
| - 150.136.239.201
| - 10.0.0.3
| instance-id: ocid1.instance.oc1.iad.anuwcljs5ai4gxycpj3sfhfqwgwzm6enrf46qglfk7jpg4uxg5jripxrxxba
| display-name: '...xrxxba'
| ...

Revision history for this message
Haw Loeung (hloeung) wrote :

But per Oracle's site[1], 150.136.0.0/16 is allocated to us-ashburn-1.

[1]https://docs.cloud.oracle.com/en-us/iaas/tools/public_ip_ranges.json

Revision history for this message
Heather Lanigan (hmlanigan) wrote :

With juju 2.9.24 (tip) I tried to bootstrap the us-ashburn-1 region, but the instance was in the us-phoenix-1 region instead...

$ juju bootstrap oci-canonical/us-ashburn-1
Creating Juju controller "oci-canonical-us-ashburn-1" on oci-canonical/us-ashburn-1
Looking for packaged Juju agent version 2.9.24 for amd64
No packaged binary found, preparing local Juju agent binary
Launching controller instance(s) on oci-canonical/us-ashburn-1...
 - ocid1.instance.oc1.phx.anyhqljtniwq6sychhhgozwxe4ekfaznlgy2eomvr7vuldskpf7tmlz5yxxa (arch=amd64)

Vitaly Antonenko (anvial)
no longer affects: juju/2.7
Changed in juju:
status: Triaged → Fix Committed
importance: Undecided → High
assignee: nobody → Vitaly Antonenko (anvial)
milestone: none → 3.3.1
Revision history for this message
Vitaly Antonenko (anvial) wrote :

https://github.com/juju/juju/pull/16393

Revision history for this message
Haw Loeung (hloeung) wrote :

Is this something we could backport to Juju 2.9.x? Thanks in advance.

Canonical Juju QA Bot (juju-qa-bot)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.