Re: systemd-resolved and snaps

2017-03-20 Thread Kyle Fazzari
On 02/23/2017 02:26 PM, Steve Langasek wrote: > Hi Kyle, > > On Thu, Feb 23, 2017 at 01:58:07PM -0800, Kyle Fazzari wrote: >> Hey all. > >> I've received a bug report on a snap where the user was running a 16.10 >> Server install with the snap in question, and getting DNS errors. I've >> distil

Re: systemd-resolved and snaps

2017-02-23 Thread Steve Langasek
On Thu, Feb 23, 2017 at 02:39:27PM -0800, Kyle Fazzari wrote: > On 02/23/2017 02:26 PM, Steve Langasek wrote: > > acme-staging.api.letsencrypt.org is a CNAME. You are hitting bug #1647031, > > which we encountered when trying to roll out systemd-resolved by default for > > 17.04. This took a whi

Re: systemd-resolved and snaps

2017-02-23 Thread Kyle Fazzari
On 02/23/2017 02:26 PM, Steve Langasek wrote: > Hi Kyle, > > On Thu, Feb 23, 2017 at 01:58:07PM -0800, Kyle Fazzari wrote: >> Hey all. > >> I've received a bug report on a snap where the user was running a 16.10 >> Server install with the snap in question, and getting DNS errors. I've >> distil

Re: systemd-resolved and snaps

2017-02-23 Thread Steve Langasek
Hi Kyle, On Thu, Feb 23, 2017 at 01:58:07PM -0800, Kyle Fazzari wrote: > Hey all. > I've received a bug report on a snap where the user was running a 16.10 > Server install with the snap in question, and getting DNS errors. I've > distilled the problem as much as I can but I cannot for the life o

Re: systemd-resolved and snaps

2017-02-23 Thread Stéphane Graber
On Thu, Feb 23, 2017 at 01:58:07PM -0800, Kyle Fazzari wrote: > Hey all. > > I've received a bug report on a snap where the user was running a 16.10 > Server install with the snap in question, and getting DNS errors. I've > distilled the problem as much as I can but I cannot for the life of me > f