`juju show-status-log --include-status-updates` does not show update-status history
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Anastasia | ||
2.3 |
Fix Released
|
Medium
|
Anastasia |
Bug Description
$ juju version
2.3.5-xenial-amd64
When I was troubleshooting LP: #1762431, I found that --include-
$ juju show-status-log -h
...
--include-
Inlcude update status hook messages in the returned logs
$ juju show-status-log neutron-api/1 --include-
...
09 Apr 2018 07:12:30Z juju-unit executing running amqp-relation-
09 Apr 2018 07:12:58Z juju-unit executing running neutron-
09 Apr 2018 07:13:23Z juju-unit executing running neutron-
09 Apr 2018 07:13:23Z juju-unit executing running shared-
09 Apr 2018 07:14:03Z juju-unit executing running neutron-
09 Apr 2018 07:14:31Z juju-unit executing running neutron-
09 Apr 2018 07:14:59Z juju-unit executing running neutron-
09 Apr 2018 07:14:59Z juju-unit idle
09 Apr 2018 07:15:05Z juju-unit executing running identity-
09 Apr 2018 07:15:41Z workload active Unit is ready
09 Apr 2018 07:15:43Z juju-unit idle
09 Apr 2018 07:15:49Z juju-unit executing running identity-
09 Apr 2018 07:16:26Z juju-unit idle
09 Apr 2018 07:19:54Z juju-unit executing running identity-
09 Apr 2018 07:20:55Z juju-unit idle
09 Apr 2018 11:57:21Z juju-unit executing running config-changed hook
09 Apr 2018 11:57:39Z workload maintenance Installing apt packages
09 Apr 2018 11:58:11Z workload active Unit is ready
09 Apr 2018 11:58:12Z juju-unit idle
09 Apr 2018 15:29:44Z juju-unit executing running config-changed hook
09 Apr 2018 15:30:02Z workload maintenance Installing apt packages
09 Apr 2018 15:30:34Z workload active Unit is ready
09 Apr 2018 15:30:35Z juju-unit idle
However, update-status hook is actually run multiple times.
$ juju debug-log -i neutron-api/1 --replay | grep 'ran "update-status" hook'
...
unit-neutron-api-1: 14:39:54 INFO juju.worker.
unit-neutron-api-1: 14:44:25 INFO juju.worker.
unit-neutron-api-1: 14:50:22 INFO juju.worker.
unit-neutron-api-1: 14:55:18 INFO juju.worker.
unit-neutron-api-1: 15:00:03 INFO juju.worker.
unit-neutron-api-1: 15:05:05 INFO juju.worker.
unit-neutron-api-1: 15:10:08 INFO juju.worker.
unit-neutron-api-1: 15:14:29 INFO juju.worker.
unit-neutron-api-1: 15:19:23 INFO juju.worker.
unit-neutron-api-1: 15:24:41 INFO juju.worker.
unit-neutron-api-1: 15:29:07 INFO juju.worker.
Changed in juju: | |
assignee: | nobody → Anastasia (anastasia-macmood) |
milestone: | none → 2.4-beta1 |
status: | Invalid → Triaged |
importance: | Undecided → Medium |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Ah... yes. The functionality was updated so the update-status hook is no longer recorded in the status-log. This is by design. It was really creating undue DB load for very little value given that it is run very regularly.
I believe the flag was left on the command to continue to work against older controllers. We should update the docs.