Windows Charms are unable to raise error state

[Charles Butler]

When deploying a charm on windows, it appears the return code's are not being respected - and the charm never enters an "error state"

juju rev: 1.21.3

unit-win-service-0[240]: 2015-02-28 16:58:51 INFO unit.win-service/0.install logger.go:40 char:9
unit-win-service-0[240]: 2015-02-28 16:58:51 INFO unit.win-service/0.install logger.go:40 + Install-WindowsFeatures $WINDOWS_FEATURES
unit-win-service-0[240]: 2015-02-28 16:58:51 INFO unit.win-service/0.install logger.go:40 + ~~~~~~~~~~~~~~~~~~~~~~~
unit-win-service-0[240]: 2015-02-28 16:58:51 INFO unit.win-service/0.install logger.go:40 + CategoryInfo : ObjectNotFound: (Install-WindowsFeatures:String)
unit-win-service-0[240]: 2015-02-28 16:58:51 INFO unit.win-service/0.install logger.go:40 [], ParentContainsErrorRecordException
unit-win-service-0[240]: 2015-02-28 16:58:51 INFO unit.win-service/0.install logger.go:40 + FullyQualifiedErrorId : CommandNotFoundException
unit-win-service-0[240]: 2015-02-28 16:58:51 INFO unit.win-service/0.install logger.go:40

The following error was found in the logs, and the service was green. I believe this is due to juju-agent still expecting the return code to be > 0, and I'm not 100% sure how this actually interacts on windows.

[Joseph Phillips (manadart)]

Marked won't fix to age and the fact that Windows workloads are in line for deprecation.