Landscape Charm

hook "leader-settings-changed" failed: exit status 1

Bug #1603890 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Charm
New
Undecided
Unassigned

Bug Description

With a two-unit landscape-server deploy, killing the leader usually results in an error in the leader-settings-changed hook.

2016-07-15 11:38:59 INFO leader-settings-changed Job for landscape-package-search.service failed because the control process exited with error code. See "systemctl status landscape-package-search.service" and "journalctl -xe" for details.

Revision history for this message
Björn Tillenius (bjornt) wrote :
Revision history for this message
Björn Tillenius (bjornt) wrote :
Revision history for this message
Björn Tillenius (bjornt) wrote :
Revision history for this message
Björn Tillenius (bjornt) wrote :
Revision history for this message
Björn Tillenius (bjornt) wrote :

The deployment used r28 of lp:~landscape/landscape-charm/bundles-trunk

Revision history for this message
Chris Glass (tribaal) wrote :

An easy way to reproduce is, on Xenial:

- Make sure you use juju-1-default (well, juju 1)
- juju switch local
- juju bootstrap
- zope-testrunner3 -vv --path tests --tests-pattern basic --test LandscapeHATest

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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