Manual provider jujud can fail to stop on clean-up

Bug #1651674 reported by Mick Gregg on 2016-12-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Medium
Unassigned

Bug Description

On occasion, the manual provider bootstrap node clean-up script can fail to stop the jujud process.

http://qa.jujucharms.com/releases/issue/57b1c1f9749a567693457040

This has been observed (@sinzui) on machines under load, and may be caused by an uninterruptible sleep state effectively blocking the abort and kill signals.

The fixes for bug 1642295 included some logging that may help diagnose this.

Mick Gregg (macgreagoir) wrote :

This was originally tracked in bug 1642295, but that bug was hijacked to track the clean-up of non-bootstrap nodes in the controller model.

Mick Gregg (macgreagoir) wrote :

I've just seen an example and am noting it here:
http://reports.vapour.ws/releases/4683/job/manual-deploy-xenial-arm64/attempt/772

The process is in S, not D, state but may still be waiting on IO... maybe.

Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.2.0
Curtis Hovey (sinzui) on 2017-03-24
Changed in juju:
milestone: 2.2-beta1 → 2.2-beta2
Curtis Hovey (sinzui) on 2017-03-30
Changed in juju:
milestone: 2.2-beta2 → 2.2-beta3
Changed in juju:
milestone: 2.2-beta3 → 2.2-beta4
Changed in juju:
milestone: 2.2-beta4 → 2.2-rc1
Tim Penhey (thumper) on 2017-06-01
Changed in juju:
importance: High → Medium
milestone: 2.2-rc1 → none
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers