num_units log output on subordinate charms is confusing to new users

actually this was an after effect of a recent merge i believe which changed
default from None to 0 triggering the log msg

On Tue, Aug 18, 2015 at 3:38 PM, Charles Butler <
<email address hidden>> wrote:

> Public bug reported:
>
>
> juju deployer inherently appends a num_units: 0 line for each subordinate
> service (as i understand it) the warning output isn't really reflective of
> the behavior, and appears to be a byproduct of a symptom deployer has in
> surfacing weird error messages when its going astray or behaving as we
> expect it to.
>
> I dont know why the deployer is warning about num_units for the dependent
> charms as I haven't specified them.
> 2015-08-16 05:12:47 Config specifies num units for subordinate:
> neutron-api-plumgrid
> 2015-08-16 05:13:50 Config specifies num units for subordinate:
> plumgrid-edge
>
> I feel that we should ammend this to something like "generating
> num_units: 0 for subordinate service <service>"
>
> so the above error message makes more sense to the end user when
> following the breadcrumb trail of output deployer is feeding them.
>
> ** Affects: juju-deployer
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju-
> deployer.
> Matching subscriptions: deployer
> https://bugs.launchpad.net/bugs/1486214
>
> Title:
> num_units log output on subordinate charms is confusing to new users
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-deployer/+bug/1486214/+subscriptions
>

sounds good

On Tue, Aug 18, 2015 at 5:38 PM, Kapil Thangavelu <email address hidden> wrote:

> actually this was an after effect of a recent merge i believe which
> changed default from None to 0 triggering the log msg
>
> On Tue, Aug 18, 2015 at 3:38 PM, Charles Butler <
> <email address hidden>> wrote:
>
>> Public bug reported:
>>
>>
>> juju deployer inherently appends a num_units: 0 line for each subordinate
>> service (as i understand it) the warning output isn't really reflective of
>> the behavior, and appears to be a byproduct of a symptom deployer has in
>> surfacing weird error messages when its going astray or behaving as we
>> expect it to.
>>
>> I dont know why the deployer is warning about num_units for the dependent
>> charms as I haven't specified them.
>> 2015-08-16 05:12:47 Config specifies num units for subordinate:
>> neutron-api-plumgrid
>> 2015-08-16 05:13:50 Config specifies num units for subordinate:
>> plumgrid-edge
>>
>> I feel that we should ammend this to something like "generating
>> num_units: 0 for subordinate service <service>"
>>
>> so the above error message makes more sense to the end user when
>> following the breadcrumb trail of output deployer is feeding them.
>>
>> ** Affects: juju-deployer
>> Importance: Undecided
>> Status: New
>>
>> --
>> You received this bug notification because you are subscribed to juju-
>> deployer.
>> Matching subscriptions: deployer
>> https://bugs.launchpad.net/bugs/1486214
>>
>> Title:
>> num_units log output on subordinate charms is confusing to new users
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/juju-deployer/+bug/1486214/+subscriptions
>>
>
>