Canonical Juju

juju status message: "resolver loop error"

Bug #1604915 reported by Jason Hobbs on 2016-07-20

This bug report is a duplicate of: Bug #1635664: Error causes deployments to fail. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Canonical Juju	Triaged	High	Unassigned	Canonical Juju 2.1-rc2

Bug Description

This is with 2.0 beta12.

A unit went to a juju-status of failed, with this status:
    units:
      nova-cloud-controller/0:
        workload-status:
          current: active
          message: Unit is ready
          since: 20 Jul 2016 10:25:57Z
        juju-status:
          current: failed
          message: resolver loop error
          since: 20 Jul 2016 11:57:24Z
          version: 2.0-beta12

From this run in OIL: http://10.245.162.43:8080/job/pipeline_deploy/8169/

Here's the full juju status:
http://paste.ubuntu.com/20209086/

I attached the logs from the failed unit, and from the controller.

See original description

Tags:

Revision history for this message

Jason Hobbs (jason-hobbs) wrote on 2016-07-20:

nova-cloud-controller_0-10.244.241.32.tar.gz Edit (869.3 KiB, application/x-tar)

description:	updated
description:	updated

Revision history for this message

Jason Hobbs (jason-hobbs) wrote on 2016-07-20:

bootstrap_logs (8).tgz Edit (1.3 MiB, application/x-tar)

Cheryl Jennings (cherylj) on 2016-07-21

Changed in juju-core:
status:	New → Triaged
importance:	Undecided → High
tags:	added: 2.0

Anastasia (anastasia-macmood) on 2016-08-03

Changed in juju-core:
milestone:	none → 2.0.0

Canonical Juju QA Bot (juju-qa-bot) on 2016-08-23

affects:	juju-core → juju
Changed in juju:
milestone:	2.0.0 → none
milestone:	none → 2.0.0

Alexis Bruemmer (alexis-bruemmer) on 2016-09-27

Changed in juju:
assignee:	nobody → Alexis Bruemmer (alexis-bruemmer)

Alexis Bruemmer (alexis-bruemmer) on 2016-09-30

Changed in juju:
milestone:	2.0.0 → 2.1.0

Revision history for this message

Larry Michel (lmic) wrote on 2016-09-30:

Marking as invalid per conversation with Alexis. I don't believe this has been recreated. We'll re-open if we find otherwise.

Changed in juju:
status:	Triaged → Invalid

Revision history for this message

Junien Fridrick (axino) wrote on 2016-10-20:

Hi,

I repro'ed this on a 2.0.0 environment, #1587644

Anastasia (anastasia-macmood) on 2016-10-20

Changed in juju:
status:	Invalid → Triaged

Revision history for this message

Aaron Bentley (abentley) wrote on 2016-10-21:

A resolver loop error appear here, but it may not be the root cause:
http://reports.vapour.ws/releases/4517/job/run-unit-tests-race/attempt/2002

Anastasia (anastasia-macmood) on 2017-02-02

Changed in juju:
assignee:	Alexis Bruemmer (alexis-bruemmer) → nobody

Revision history for this message

Anastasia (anastasia-macmood) wrote on 2017-02-13:

The original issues reported in this bug is no longer reproducible as per comment # 3.

"resolver loop error" seems to be a red herring as it shows on the systems under stress: both bug # 1587644 (comment # 4) and bug # 1635664 (alluded to in comment #5, test failure with race enabled) refer to heavily loaded system. The root causes for either are different.

As one bug is marked Fix Committed, I am marking this duplicate of test failure.

Note that for 2.0.x, the newer release - 2.0.3 specifically - contains a few performance improvements that should make a difference to stress Juju puts on the system.