Activity log for bug #1747015

Date Who What changed Old value New value Message
2018-02-02 15:20:41 Adam Conrad bug added bug
2018-02-02 15:22:14 Adam Conrad description As discussed on IRC, rather that giving the lxd container a generic hostname of "lp-$series-$arch", it should get a hostname based on (or exactly the same) as the host running lp-buildd. Tail end of the IRC discussion: 07:09 < infinity> If the container has an /etc/hosts entry for lcy01-amd64-001.buildd that points to the container, it literally makes no difference that it's the same name as the outer host. 07:09 < cjwatson> Oh, if it points to the container, I see 07:09 < cjwatson> Right, that makes sense 07:10 < infinity> That only matters if the container wants to talk to the host or vice-versa, both of which are things we explicitly don't want anyway. 07:10 < cjwatson> Yeah 07:10 < cjwatson> Can I have a bug? It's a bit fiddly because we probably need to do hostname --fqdn or something to work out what to use 07:11 < cjwatson> I can sort it out, just want a reminder If there's some lxdish reason why it has a conniption if the host and container match (I can't see why, but hey, it could be), just prepending a subdomain of "lxd" or similar would make sense to me (ie: lxd.lcy01-amd64-001.buildd), which would be short enough to not be excessively icky, and handily also defeat the previous 'lp-*' glob in livecd-rootfs so that code magically stops being broken. ;) As discussed on IRC, rather that giving the lxd container a generic hostname of "lp-$series-$arch", it should get a hostname based on (or exactly the same as) the host running lp-buildd. Tail end of the IRC discussion: 07:09 < infinity> If the container has an /etc/hosts entry for lcy01-amd64-001.buildd that points to the container, it literally makes no difference that it's the same name as the outer host. 07:09 < cjwatson> Oh, if it points to the container, I see 07:09 < cjwatson> Right, that makes sense 07:10 < infinity> That only matters if the container wants to talk to the host or vice-versa, both of which are things we explicitly don't want anyway. 07:10 < cjwatson> Yeah 07:10 < cjwatson> Can I have a bug? It's a bit fiddly because we probably need to do hostname --fqdn or something to work out what to use 07:11 < cjwatson> I can sort it out, just want a reminder If there's some lxdish reason why it has a conniption if the host and container match (I can't see why, but hey, it could be), just prepending a subdomain of "lxd" or similar would make sense to me (ie: lxd.lcy01-amd64-001.buildd), which would be short enough to not be excessively icky, and handily also defeat the previous 'lp-*' glob in livecd-rootfs so that code magically stops being broken. ;)
2018-02-04 01:03:19 Colin Watson launchpad-buildd: importance Undecided High
2018-02-04 01:03:19 Colin Watson launchpad-buildd: status New In Progress
2018-02-04 01:03:19 Colin Watson launchpad-buildd: assignee Colin Watson (cjwatson)
2018-02-04 01:07:31 Launchpad Janitor branch linked lp:~cjwatson/launchpad-buildd/lxd-hostname
2018-05-08 09:38:32 Colin Watson launchpad-buildd: status In Progress Fix Committed
2018-06-14 10:16:16 Colin Watson launchpad-buildd: status Fix Committed Fix Released