** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646585
Title:
oem-config replaces /etc/resolv.conf symlink with a hard file
To manage notifications about this bug go
This has broken again in bionic. While the fix is still in there, the
netcfg-common.c file that ubiquity uses does NOT handle the systemd-
resolve.service case, where the symlink is to ../run/systemd/resolv
/stub-resolv.conf, and so running ubiquity during oem-config-firstboot
again breaks the
This bug was fixed in the package ubiquity - 2.21.63.4
---
ubiquity (2.21.63.4) xenial; urgency=medium
* src/panel/panel.c: set stricter size/extend rules for the panel so that it
looks nicer if its scaling is too great. (LP: #1622686)
* Automatic update of included source
Verification-done for xenial with ubiquity 2.21.63.4:
I verified that the resolv.conf file after running OEM mode is correctly
left around as a symlink to resolvconf.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this
Hello Newton, or anyone else affected,
Accepted ubiquity into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubiquity/2.21.63.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package netcfg - 1.135ubuntu4.5
---
netcfg (1.135ubuntu4.5) xenial; urgency=medium
* Add description for non-PCI platform network interfaces. LP:
#1697914
-- dann frazier Wed, 19 Jul 2017 15:15:12 -0600
** Changed in: netcfg (Ubuntu
The current issue is that ubiquity does NOT use the netcfg package, but
rather has its own copy of netcfg that still (as near as I can tell) has
the bug. Is there another bug tracking that? What is the timeframe
for that getting fixed in xenial?
--
You received this bug notification because
** Branch linked: lp:~ubuntu-installer/ubiquity/xenial-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646585
Title:
oem-config replaces /etc/resolv.conf symlink with a hard file
To manage
Verification-done for xenial, using netcfg 1.135ubuntu4.5:
I approximated the behavior of oem-config on a system after install
calling netcfg; it appears to properly handle the resolv.conf symlink on
the system.
** Tags removed: verification-needed verification-needed-xenial
** Tags added:
Hello Newton, or anyone else affected,
Accepted netcfg into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/netcfg/1.135ubuntu4.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Newton, or anyone else affected,
Accepted netcfg into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/netcfg/1.138ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Indeed, ubiquity has not been updated yet, because we should be able to
verify netcfg without it. Nevertheless, I have another SRU to land that
also needs to be applied to xenial, so I'll upload ubiquity along as
soon as netcfg lands in xenial-proposed.
** Description changed:
- The DGX server
The latest ubiquity I see for xenial is 2.21.63, and its netcfg-common.c
looks unfixed:
void reap_old_files (void)
{
static char* remove[] =
{ INTERFACES_FILE, HOSTS_FILE, HOSTNAME_FILE, NETWORKS_FILE,
RESOLV_FILE, DHCLIENT_CONF, DOMAIN_FILE, 0 };
char **ptr = remove;
Since we're hitting this during server install, and the netcfg
executable used is the one in the ubiquity package, All we need to
test this is the updated ubiquity package. I'm having trouble finding
a pointer to that...
--
You received this bug notification because you are a member of
Hello Newton, or anyone else affected,
Accepted netcfg into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/netcfg/1.135ubuntu4.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The ubiquity tasks should be Fix Released as well; ubiquity was updated
before the zesty release, artful is unaffected (fixed because zesty was
fixed before release).
I'm adding the tasks for Xenial by request from Stéphane.
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Fix Released
NVIDIA confirmed the Zesty fix works for them. Would it be possible to
backport to 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646585
Title:
oem-config replaces /etc/resolv.conf symlink
This bug was fixed in the package netcfg - 1.138ubuntu5
---
netcfg (1.138ubuntu5) zesty; urgency=medium
* Don't reap old resolv.conf if resolvconf is in use. Thanks Dariusz Gadomsky
for the patch. (LP: #1646585)
-- Mathieu Trudel-Lapierre Mon, 03 Apr
Seems like the most sensible fix is in netcfg after all; we should apply
the patch (minus the ubiquity bits), after properly testing that this
doesn't break server installs with only d-i, and that it doesn't break
non-OEM ubiquity installs.
** Changed in: ubiquity (Ubuntu Zesty)
Milestone:
This patch can't be applied as-is; netcfg comes from the standalone
package from the same name. Assuming we can fix this appropriately in
netcfg itself without breaking debian-installer-based installs, this
might work.
However, I suspect this can be appropriately handled directly in
ubiquity.
**
** Changed in: ubiquity (Ubuntu Zesty)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu Zesty)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646585
** Tags added: zesty
** Also affects: ubiquity (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646585
Title:
oem-config replaces
The attachment "zesty_ubiquity_17.04.8.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
Fix proposal for zesty.
** Tags added: sts sts-sponsor
** Patch added: "zesty_ubiquity_17.04.8.debdiff"
https://bugs.launchpad.net/nvidia/+bug/1646585/+attachment/4835373/+files/zesty_ubiquity_17.04.8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have tested this several times with different network settings and can
see that ubiquity plays quite nicely with resolvconf. That includes
static (e.g. dns-nameservers entries in /e/n/interfaces) and dhcp cases.
The only problem is the issue identified by Newton Liu above - the
resolv.conf gets
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646585
Title:
oem-config replaces /etc/resolv.conf symlink with a hard
26 matches
Mail list logo