Skip to content

juju-controller r116 deployed as juju 3.6.14 still throws Ops warning fixed 2 year ago. #102

@taurus-forever

Description

@taurus-forever

Hi,

Today, on freshly deployed juju I still see this warning:

unit-controller-1: 16:27:14 DEBUG unit.controller/1.juju-log ops 2.17.0 up and running.
unit-controller-1: 16:27:14 DEBUG unit.controller/1.juju-log Emitting Juju event update_status.
unit-controller-1: 16:27:14 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-controller-2: 16:28:12 WARNING unit.controller/2.update-status /var/lib/juju/agents/unit-controller-2/charm/./src/charm.py:162: DeprecationWarning: Calling `ops.main.main()` is deprecated, call `ops.main()` instead
unit-controller-2: 16:28:12 WARNING unit.controller/2.update-status   main(JujuControllerCharm)

Hovewer the code with the fix has been committed 2 year ago:
98a8683

The charm revision 116 release date to 3.6/stable is 11 Nov 2024.
Please consider to release the new version of charm juju-controller to stable risk (3.6 is LTS):

Image
> juju status
Model       Controller  Cloud/Region         Version  SLA          Timestamp
controller  lxd         localhost/localhost  3.6.14   unsupported  16:19:51+01:00

App         Version  Status  Scale  Charm            Channel     Rev  Exposed  Message
controller           active      3  juju-controller  3.6/stable  116  yes      

Unit           Workload  Agent  Machine  Public address  Ports      Message
controller/0*  active    idle   0        10.46.207.55    17022/tcp  
controller/1   active    idle   1        10.46.207.44    17022/tcp  
controller/2   active    idle   2        10.46.207.155   17022/tcp  

Tnx!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions