Azure: No availability zone set?

Bug #1982987 reported by Haw Loeung
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Wishlist
Unassigned

Bug Description

Hi,

When deploying VMs in Azure, there doesn't appear to be any availability zone information.

Juju status:

| Model Controller Cloud/Region Version SLA Timestamp
| mymodel-eastus-staging mycontroller-controller-us azure/eastus 2.9.32 unsupported 23:56:47Z
| ...
| Machine State DNS Inst id Series AZ Message
| 0 started 52.146.31.10 machine-0 focal
| 1 started 20.62.184.193 machine-1 focal
| 2 started 20.62.184.178 machine-2 focal

Even within the VM, there's no "JUJU_AVAILABILITY_ZONE". I mean, it's there, but empty.

Can we get that fixed to show the AZ? Maybe there's no concept of AZ within Azure, so instead can we get it to show the "location" / region name?

From within the VM, that looks available too:

| $ curl -H "Metadata:true" "http://169.254.169.254/metadata/instance/compute?api-version=2017-12-01"; echo
| {"location":"eastus","name":"machine-0","offer":"0001-com-ubuntu-server-focal", ... "vmSize":"Standard_D3_v2","zone":""}

Is that because of zone being "" above?

Haw Loeung (hloeung)
description: updated
Revision history for this message
Ian Booth (wallyworld) wrote :

The Azure provider uses availability sets which originally all that was available when the Azure provider was first developed several years ago.

There's now scale sets which can include availability zones, but we don't support that at the moment. Hence right now, for Azure, the AZ will always be "".

Ian Booth (wallyworld)
Changed in juju:
milestone: none → 3.1.0
importance: Undecided → High
status: New → Triaged
Changed in juju:
milestone: 3.1-beta1 → 3.1-rc1
Revision history for this message
Vitaly Antonenko (anvial) wrote :

This sounds more like feature requests. We need to discuss adding it to the next cycle roadmap.

tags: added: azure azure-provider fea
tags: added: feature
removed: fea
Changed in juju:
importance: High → Wishlist
Changed in juju:
milestone: 3.1-rc1 → 3.1-rc2
Changed in juju:
milestone: 3.1-rc2 → 3.1-rc3
Revision history for this message
Haw Loeung (hloeung) wrote :

Is this a feature request? The other clouds have this information present in Juju status output as well as the JUJU_AVAILABILITY_ZONE environment variable.

Revision history for this message
John A Meinel (jameinel) wrote :

So the original implementation on Azure didn't have zones. They had a different concept called Availability Sets, which was more the inverse (everything within one Availability Set would not be taken out simultaneously, vs everything in one Availability Zone goes down in the zone goes down).

Which meant that the original tracking definitely didn't want to pass the Set down as a Zone. However, I do believe with newer ARM logic on Azure (and within Juju) we did switch to a Zone based model, but it seems while the provisioner knows about it, we didn't actually add tracking for it.

Because of a different history for how Azure tracks this information, it is quite a bit more of an issue to start passing it through.

Revision history for this message
John A Meinel (jameinel) wrote :

Note that we'll do a quick audit to see if the information is easily accessible, or whether it requires deep modeling changes.

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.