Bug#881675: Bug#883890: nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted

org Sent: Friday, December 8, 2017 5:36 PM Subject: Re: Bug#883890: nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted Control: severity -1 important Control: tag -1 moreinfo On Fri, 2017-12-08 at 13:31 -0800, Duncan Hare wrote: > Package: nfs-common > Version: 1:1.3.

Bug#883890: nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted

Control: severity -1 important Control: tag -1 moreinfo On Fri, 2017-12-08 at 13:31 -0800, Duncan Hare wrote: > Package: nfs-common > Version: 1:1.3.4-2.1 > Severity: grave > Justification: renders package unusable > > File systems correctly mounted after "reached target network online" > > File

Processed: Re: Bug#883890: nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted

Processing control commands: > severity -1 important Bug #883890 [nfs-common] nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted Severity set to 'important' from 'grave' > tag -1 moreinfo Bug #883890 [nfs-common] nfs-common: Fully Qualified DNS Name mounts in fstab fail to b

Bug#883890: nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted

Package: nfs-common Version: 1:1.3.4-2.1 Severity: grave Justification: renders package unusable File systems correctly mounted after "reached target network online" File systema rw in both cases. Case 1 1. I deleted resolv.conf 2. Root fs rw in fstab 3. File systems mounted by IP address 4. re