Comment 5 for bug 1866828

If I read that correctly:

dummy-vhost is subordinate to apache
each unit of dummy-vhost does need to configure its /var/www/dummy-vhost
data

only the leader of dummy-vhost passes the relation data to apache.

However, is it correct for Apache/1 to have the config from vhost_rdata if
its associated dummy-vhost/1 hasn't actually started up yet? (If
dummy-vhost/1 hasn't had the opportunity to fire install and start yet,
then it doesn't actually have /var/www/dummy-vhost on machine-1 for
apache/1 to serve that data, so it shouldn't (?) be configured with it yet?

Thoughts?

On Mon, Mar 16, 2020 at 2:15 PM Dmitrii Shcherbakov <
<email address hidden>> wrote:

> An example that can be used for testing:
>
> https://github.com/dshcherb/charm-apache-httpd#charm-apache-httpd
>
> juju deploy cs:~dmitriis/apache-httpd-0
> juju deploy cs:~dmitriis/dummy-vhost-0
> juju relate apache-httpd dummy-vhost
> juju add-unit apache-httpd
>
>
> More specifically:
>
> https://github.com/dshcherb/charm-apache-
> httpd/blob/0e57286b3b9b4304201f5d8e815b874f72b3214d/src/charm.py#L173
>
> https://github.com/dshcherb/charm-dummy-
> vhost/blob/4875bbb1298645f4c65f7169277066d4e5b83579/src/charm.py#L85-L89
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1866828
>
> Title:
> [2.7.4] relation-changed events for container-scoped app relation data
> may fire for primary units before they see their own subordinate
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1866828/+subscriptions
>