[00:00] hazmat: Err... [00:00] I think you should just assume it [00:00] SpamapS, but we'll basically end up re-executing hooks is the only bad thing [00:00] Yeah exactly [00:00] all hooks should be able to be executed over and over and over [00:00] SpamapS, but we'll also miss changes, that the hook will need to detect when it gets the join event again [00:01] join+changed always comes together tho [00:01] SpamapS, and we'll miss departures [00:01] I've not found much use for those anyway ;) [00:02] But I see the point [00:03] seems to me that the model for those needs to be on join, each service unit gets its own node under the relation that means "I've been told about this" and then it must delete that node when it has been told about the departure [00:18] <_mup_> Bug #846129 was filed: After bootstrapping with a custom ensembe-branch, config-get no longer works. < https://launchpad.net/bugs/846129 > [03:39] <_mup_> Bug #846197 was filed: Opinionated driver for functional tests < https://launchpad.net/bugs/846197 > [04:12] <_mup_> Bug #846208 was filed: Provisioned nodes do not get a FQDN < https://launchpad.net/bugs/846208 > [16:05] negronjl: around? [16:49] can't seem to hit the archives [16:49] odd [16:49] it works from host not container [16:49] ah.. its the race condition around resolv.conf [17:21] <_mup_> ensemble/local-ubuntu-provider r350 committed by kapil.thangavelu@canonical.com [17:21] <_mup_> redo setup of containers, and formula extraction, always log to /var/log/ensemble [17:29] interesting the lxc cache captures the old dns server into /etc/resolv.conf which if its stale is toast [17:34] <_mup_> ensemble/local-ubuntu-provider r351 committed by kapil.thangavelu@canonical.com [17:34] <_mup_> update resolv.conf before attempting package installation in the container in the post-create script [17:44] hmm.. dangling symlink === wrtp_ is now known as wrtp