[azure] can't bootstrap in Central US : no OS images found for location

Bug #1619682 reported by Junien F
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-images
Fix Released
Undecided
Unassigned
juju-core
Invalid
Undecided
Unassigned

Bug Description

Hi,

I'm trying to bootstrap in Central US, and :
ERROR juju.cmd supercommand.go:429 failed to bootstrap environment: cannot start bootstrap instance: no OS images found for location "Central US", series "xenial", architectures ["amd64" "arm64" "armhf" "i386" "ppc64el" "s390x"] (and endpoint: "https://management.core.windows.net/")

This is with juju 1.25.6

If I switch to "Central US EUAP" (because apparently that's what the Azure API is returning for cloud images) :
ERROR juju.cmd supercommand.go:429 failed to bootstrap environment: cannot get available role sizes: location "Central US EUAP" not found

Thank you

Revision history for this message
Junien F (axino) wrote :
Revision history for this message
Curtis Hovey (sinzui) wrote :

This config in my environments.yaml works for me. Note that juju
requires you to create a (classic) storage account in the region
you are bootstrapping in:

  azure-central-us:
    type: azure
    test-mode: true
    location: Central US
    management-subscription-id: <ME>
    management-certificate: |
      -----BEGIN PRIVATE KEY-----
      <FOO>
      -----END PRIVATE KEY-----
      -----BEGIN CERTIFICATE-----
      <BAR>
      -----END CERTIFICATE-----
    storage-account-name: juju0ci0central0us
    default-series: trusty

$ juju-1 version
1.25.6-xenial-amd64

$ juju-1 bootstrap -e azure-central-us
Bootstrapping environment "azure-central-us"
Starting new instance for initial state server
Launching instance
 - juju-azure-central-us-lg4ngzoco6-juju6wl4rycvq3x4vs5gzuouzzbp26gy2vzkalc1dbaw1b3auy
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to 10.0.0.4:22
Attempting to connect to juju-azure-central-us-lg4ngzoco6.cloudapp.net:22
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Installing package: tmux
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://jujutools.blob.core.windows.net/juju-tools/tools/agent/1.25.6/juju-1.25.6-trusty-amd64.tgz]>
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap agent installed
local -> azure-central-us
Bootstrap complete

Changed in juju-core:
status: New → Incomplete
Revision history for this message
Curtis Hovey (sinzui) wrote :

I see the issue is just xenial images. When I set default-series to xenial I reproduce the error:

Bootstrapping environment "azure-central-us"
Starting new instance for initial state server
Launching instance
Bootstrap failed, destroying environment
ERROR failed to bootstrap environment: cannot start bootstrap instance: no OS images found for location "Central US", series "xenial", architectures ["amd64" "arm64" "armhf" "i386" "ppc64el" "s390x"] (and endpoint: "https://management.core.windows.net/")

As seen in
    http://cloud-images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:azure.sjson
there are no xenial images published to "Central US", I see them for "US West" and "US East". I see "North Central US" and "West Central US"

Trusty does have "Central US". This is an issue with azure image streams. Either the image needs to be published for the region in streams, or Juju 1.25. need to learn about the newer azure regions.

Changed in juju-core:
status: Incomplete → Invalid
Changed in cloud-images:
milestone: none → y-2016-09-08
Dan Watkins (oddbloke)
Changed in cloud-images:
milestone: y-2016-09-08 → y-2016-09-22
Revision history for this message
Joshua Powers (powersj) wrote :

Given that xenial images are now present I am going to mark this fix released. Thanks!

Changed in cloud-images:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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