Exiting from a debug-hook session puts hook in error state

[David Ames]

Snap version 2.3-beta2.1 of juju

When in a debug-hooks session after typing exit the hook is put in an error state.

All of the following exit strategies have the same outcome:

exit
exit 0
exit $(true)

There is no way to exit cleanly thus making debug-hooks less useful.

Log entries show exit status 1
2017-11-14 17:13:46 ERROR juju.worker.uniter.operation runhook.go:108 hook "update-status" failed: exit status 1
2017-11-14 17:18:54 ERROR juju.worker.uniter.operation runhook.go:108 hook "amqp-relation-joined" failed: exit status 1
2017-11-14 17:19:56 ERROR juju.worker.uniter.operation runhook.go:108 hook "identity-service-relation-joined" failed: exit status 1
2017-11-14 17:20:13 ERROR juju.worker.uniter.operation runhook.go:108 hook "amqp-relation-changed" failed: exit status 1
2017-11-14 17:20:52 ERROR juju.worker.uniter.operation runhook.go:108 hook "identity-service-relation-changed" failed: exit status 1
2017-11-14 17:21:46 ERROR juju.worker.uniter.operation runhook.go:108 hook "identity-service-relation-joined" failed: exit status 1
2017-11-14 17:24:03 ERROR juju.worker.uniter.operation runhook.go:108 hook "identity-service-relation-changed" failed: exit status 1

[Andrew Wilkins (axwalk)]

https://github.com/juju/juju/pull/8078

[John A Meinel (jameinel)]

Is there any way to have some sort of functional test for this so that we
know debug-hooks is useful for people?

On Wed, Nov 15, 2017 at 6:50 AM, Andrew Wilkins <
<email address hidden>> wrote:

> ** Changed in: juju
> Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1732233
>
> Title:
> Exiting from a debug-hook session puts hook in error state
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1732233/+subscriptions
>