Scale reported as 1/0 after a juju deploy

Bug #1930444 reported by Tom Haddon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Ian Booth

Bug Description

I've just created a new 2.9.3 juju model, deployed `redis-k8s --channel=edge` into it and it's reporting a scale of 1/0.

https://pastebin.ubuntu.com/p/YNMBPTN285/

Tom Haddon (mthaddon)
tags: added: sidecar-charm
Revision history for this message
Colin Misare (cmisare) wrote :

I also see this when deploying with juju 2.9.3. The printed value under scale shows a couple of differing values when spinning up a unit:

"0/1" when the unit agent is allocating

"1" when the unit agent is executing

"1/0" when the unit agent is idle

When deploying with `--num-units 5`, the printed values also fluctuate between sensible values ("3/5") and non-sensible ones ("4/0", "5/0").

Revision history for this message
Pen Gale (pengale) wrote :

I think that this is related to the known issue around bundle scale defaulting to zero, which we are addressing w/ roadmap work this cycle.

@wallyworld: is there additional work that we need to do to address this, above and beyond what we discussed for the roadmap?

Revision history for this message
Ian Booth (wallyworld) wrote :

It's not bundle related. There appears to be a legitimate misreporting of the desired scale.

Changed in juju:
milestone: none → 2.9.5
importance: Undecided → High
status: New → Triaged
Ian Booth (wallyworld)
Changed in juju:
assignee: nobody → Ian Booth (wallyworld)
status: Triaged → In Progress
Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
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.

Other bug subscribers

Remote bug watches

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