| 2014-04-16 07:53:05 |
Timo Jyrinki |
bug |
|
|
added bug |
| 2014-04-16 08:28:04 |
Ubuntu QA Website |
tags |
dist-upgrade precise |
dist-upgrade iso-testing precise |
|
| 2014-04-16 08:47:32 |
Thomas Hood |
resolvconf (Ubuntu): status |
New |
Invalid |
|
| 2014-04-17 12:12:37 |
Timo Jyrinki |
summary |
No working network (= name resolving) after 12.04 LTS -> 14.04 LTS upgrade |
No working network after 12.04 LTS -> 14.04 LTS upgrade if no /etc/resolv.conf in precise |
|
| 2014-04-17 12:14:03 |
Timo Jyrinki |
description |
At least in my case, name resolving did not work after upgrading from precise to trusty.
I fixed it manually with:
cd /etc
sudo ln -s /run/resolvconf/resolv.conf .
There was no resolv.conf in /etc/ otherwise, but there was a /etc/resolv.conf.old which was a similar symlink to /run/.
In case this cannot be reproduced, it's possible I've created the problem myself, but I cannot say for sure if I've touched /etc/resolv.conf somehow. So please check /etc/resolv.conf* before and after dist-upgrade, and the functionality of the network. |
Name resolving did not work after upgrading from precise to trusty.
I fixed it manually with:
cd /etc
sudo ln -s /run/resolvconf/resolv.conf .
It turns out 12.04 LTS works fine without /etc/resolv.conf, so that increases the likelihoods that 12.04 LTS systems do not have that file. When such a system is upgraded to 14.04 LTS, network seemingly stops working to the user. |
|
| 2014-04-17 12:15:46 |
Launchpad Janitor |
branch linked |
|
lp:~timo-jyrinki/ubuntu/trusty/resolvconf/fix_lp_1308378 |
|
| 2014-04-17 12:16:03 |
Timo Jyrinki |
resolvconf (Ubuntu): status |
Invalid |
New |
|
| 2014-04-17 13:17:38 |
Timo Jyrinki |
description |
Name resolving did not work after upgrading from precise to trusty.
I fixed it manually with:
cd /etc
sudo ln -s /run/resolvconf/resolv.conf .
It turns out 12.04 LTS works fine without /etc/resolv.conf, so that increases the likelihoods that 12.04 LTS systems do not have that file. When such a system is upgraded to 14.04 LTS, network seemingly stops working to the user. |
[Impact]
Name resolving does not work after upgrading from 12.04 (precise) to 14.04 (trusty) in the corner case of not having /etc/resolv.conf in precise. precise however works fine with that file absent, while trusty does not, so it increases the likelihood of having these kind of machines (including some people from bug #1000244 probably).
[Test Case]
1. Install 12.04 LTS
2. rm /etc/resolv.conf and observe everything works fine
3. update-manager -c -d
4. Observe that in 14.04 LTS name resolving does not work.
[Test Case for testing the fix on 14.04]
1. wget http://de.archive.ubuntu.com/ubuntu/pool/main/r/resolvconf/resolvconf_1.63ubuntu16_all.deb
2. dpkg -i resolvconf_1.63ubuntu16_all.deb
3. Running that precise version, test the possible cases like rm /etc/resolv.conf (note you lose name resolving at this point in 14.04)
4. Run 'bzr bd' (apt-get install bzr-builddeb first) in the proposed branch, dpkg -i ../build-area/*.deb
5. Check how either, depending on the case being tested, /etc/resolv.conf is intact / non-touched or it's created when not-existing, restoring network connectivity
[Regression Potential]
Seems low considering the limiting of the proposed fix to 12.04 -> 14.04 upgrades only, and only in the case of the user/3rd party app/something intentionally removed /etc/resolv.conf (instead of just modifying it).
---
I fixed it manually with:
cd /etc
sudo ln -s /run/resolvconf/resolv.conf .
It turns out 12.04 LTS works fine without /etc/resolv.conf, so that increases the likelihoods that 12.04 LTS systems do not have that file. When such a system is upgraded to 14.04 LTS, network seemingly stops working to the user. |
|
| 2014-04-17 15:45:06 |
Thomas Hood |
description |
[Impact]
Name resolving does not work after upgrading from 12.04 (precise) to 14.04 (trusty) in the corner case of not having /etc/resolv.conf in precise. precise however works fine with that file absent, while trusty does not, so it increases the likelihood of having these kind of machines (including some people from bug #1000244 probably).
[Test Case]
1. Install 12.04 LTS
2. rm /etc/resolv.conf and observe everything works fine
3. update-manager -c -d
4. Observe that in 14.04 LTS name resolving does not work.
[Test Case for testing the fix on 14.04]
1. wget http://de.archive.ubuntu.com/ubuntu/pool/main/r/resolvconf/resolvconf_1.63ubuntu16_all.deb
2. dpkg -i resolvconf_1.63ubuntu16_all.deb
3. Running that precise version, test the possible cases like rm /etc/resolv.conf (note you lose name resolving at this point in 14.04)
4. Run 'bzr bd' (apt-get install bzr-builddeb first) in the proposed branch, dpkg -i ../build-area/*.deb
5. Check how either, depending on the case being tested, /etc/resolv.conf is intact / non-touched or it's created when not-existing, restoring network connectivity
[Regression Potential]
Seems low considering the limiting of the proposed fix to 12.04 -> 14.04 upgrades only, and only in the case of the user/3rd party app/something intentionally removed /etc/resolv.conf (instead of just modifying it).
---
I fixed it manually with:
cd /etc
sudo ln -s /run/resolvconf/resolv.conf .
It turns out 12.04 LTS works fine without /etc/resolv.conf, so that increases the likelihoods that 12.04 LTS systems do not have that file. When such a system is upgraded to 14.04 LTS, network seemingly stops working to the user. |
[Impact]
Name resolving using the NetworkManager-controlled nameserver discontinues working after upgrading from 12.04 (precise) to 14.04 (trusty) in the case where /etc/resolv.conf is absent.
Precise works fine with that file absent because the resolver defaults to using "nameserver 127.0.0.1" — so it is possible to run Precise for a long time without even noticing that the file is absent.
In Trusty, resolving does not work if /etc/resolv.conf is absent because the NetworkManager-controlled nameserver listens at 127.0.1.1.
People suffering from bug #1000244 may lack /etc/resolv.conf on upgrade.
[Test Case]
1. Install 12.04 LTS
2. rm /etc/resolv.conf and observe everything works fine
3. update-manager -c -d
4. Observe that in 14.04 LTS name resolving does not work.
[Test Case for testing the fix on 14.04]
1. wget http://de.archive.ubuntu.com/ubuntu/pool/main/r/resolvconf/resolvconf_1.63ubuntu16_all.deb
2. dpkg -i resolvconf_1.63ubuntu16_all.deb
3. Running that precise version, test the possible cases like rm /etc/resolv.conf (note you lose name resolving at this point in 14.04)
4. Run 'bzr bd' (apt-get install bzr-builddeb first) in the proposed branch, dpkg -i ../build-area/*.deb
5. Check how either, depending on the case being tested, /etc/resolv.conf is intact / non-touched or it's created when not-existing, restoring network connectivity
[Regression Potential]
Seems low considering the limiting of the proposed fix to 12.04 -> 14.04 upgrades only, and only in the case of the user/3rd party app/something intentionally removed /etc/resolv.conf (instead of just modifying it).
---
I fixed it manually with:
cd /etc
sudo ln -s /run/resolvconf/resolv.conf .
It turns out 12.04 LTS works fine without /etc/resolv.conf, so that increases the likelihoods that 12.04 LTS systems do not have that file. When such a system is upgraded to 14.04 LTS, network seemingly stops working to the user. |
|
| 2014-04-22 09:06:43 |
Timo Jyrinki |
nominated for series |
|
Ubuntu Trusty |
|
| 2014-04-22 09:07:56 |
Timo Jyrinki |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2014-04-23 15:01:30 |
Brian Murray |
bug task added |
|
resolvconf (Ubuntu Trusty) |
|
| 2014-04-23 15:01:40 |
Brian Murray |
resolvconf (Ubuntu Trusty): milestone |
|
trusty-updates |
|
| 2014-04-23 15:01:49 |
Brian Murray |
resolvconf (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2014-04-23 15:01:55 |
Brian Murray |
resolvconf (Ubuntu Trusty): status |
New |
Triaged |
|
| 2014-04-24 11:30:07 |
Thomas Hood |
summary |
No working network after 12.04 LTS -> 14.04 LTS upgrade if no /etc/resolv.conf in precise |
Name resolving not working after 12.04 LTS -> 14.04 LTS if /etc/resolv.conf was absent |
|
| 2014-06-13 13:12:39 |
Michael Vogt |
resolvconf (Ubuntu Trusty): status |
Triaged |
In Progress |
|
| 2014-06-13 13:12:48 |
Michael Vogt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2014-06-13 13:12:53 |
Michael Vogt |
resolvconf (Ubuntu): status |
Triaged |
Won't Fix |
|
| 2014-06-13 13:15:46 |
Michael Vogt |
nominated for series |
|
Ubuntu Utopic |
|
| 2014-06-13 13:15:46 |
Michael Vogt |
bug task added |
|
resolvconf (Ubuntu Utopic) |
|
| 2014-06-13 13:15:56 |
Michael Vogt |
resolvconf (Ubuntu): status |
Won't Fix |
In Progress |
|
| 2014-06-13 13:16:14 |
Michael Vogt |
resolvconf (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2014-06-17 14:08:54 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2014-06-17 14:09:04 |
Chris J Arges |
tags |
dist-upgrade iso-testing precise |
dist-upgrade iso-testing precise verification-needed |
|
| 2014-06-17 14:24:21 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/resolvconf |
|
| 2014-06-19 18:28:51 |
Timo Jyrinki |
tags |
dist-upgrade iso-testing precise verification-needed |
dist-upgrade iso-testing precise verification-done |
|
| 2014-06-24 18:18:30 |
Launchpad Janitor |
resolvconf (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2014-06-24 18:18:35 |
Stéphane Graber |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2014-06-30 08:32:12 |
Iain Lane |
resolvconf (Ubuntu): status |
In Progress |
Won't Fix |
|
| 2015-08-21 04:50:05 |
Mathew Hodson |
resolvconf (Ubuntu): milestone |
trusty-updates |
|
|
| 2015-08-21 04:50:09 |
Mathew Hodson |
resolvconf (Ubuntu Utopic): milestone |
trusty-updates |
|
|
