-
Notifications
You must be signed in to change notification settings - Fork 828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fallback networking doesn't handle IOError when reading sys/net/<iface>/carrier #2731
Comments
Launchpad user Scott Moser(smoser) wrote on 2016-12-23T17:35:27.725849+00:00 This is fixed in cloud-init 0.7.9. |
Launchpad user Brian Murray(brian-murray) wrote on 2017-01-12T19:45:10.390982+00:00 I'm accepting this cloud-init upload into yakkety-proposed but this particular bug is missing SRU bug information, could it please be added? |
Launchpad user Brian Murray(brian-murray) wrote on 2017-01-12T19:47:11.300080+00:00 Hello J, or anyone else affected, Accepted cloud-init into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.8-68-gca3ae67-0ubuntu1~16.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Scott Moser(smoser) wrote on 2017-01-20T17:04:37.691968+00:00 This code path is involved on each boot, but on Ubuntu we never triggered the failure case. Failure case happens when some drivers were in different state. I realize this is not great, but I'm marking this as verification-done based on: $ release=yakkety $ lxc file pull $name/etc/cloud/build.info - enable proposed, update$ m=http://archive.ubuntu.com/ubuntu; clean up to make it look like first boot.$ lxc exec $name -- sh -c 'cd /var/lib/cloud; for d in ; do [ "$d" = "seed" ] || rm -vRf "$d"; done' $ lxc exec $name -- grep WARN /var/log/cloud-init.log || echo no warn $ lxc lau |
Launchpad user Andy Whitcroft(apw) wrote on 2017-01-30T18:17:42.348509+00:00 The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-01-30T18:18:12.820305+00:00 This bug was fixed in the package cloud-init - 0.7.8-68-gca3ae67-0ubuntu1~16.10.1 cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium
-- Scott Moser smoser@ubuntu.com Mon, 19 Dec 2016 15:07:12 -0500 |
Launchpad user Brian Murray(brian-murray) wrote on 2017-02-06T15:44:06.880983+00:00 Hello J, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Brian Murray(brian-murray) wrote on 2017-02-06T21:33:09.438076+00:00 Hello J, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-0ubuntu1~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Scott Moser(smoser) wrote on 2017-02-09T02:24:14.670822+00:00 $ release=xenial $ lxc file pull $name/etc/cloud/build.info - enable proposed, update$ m=http://archive.ubuntu.com/ubuntu; clean up to make it look like first boot.$ lxc exec $name -- sh -c 'cd /var/lib/cloud; for d in ; do [ "$d" = "seed" ] || rm -vRf "$d"; done' $ lxc exec $name -- grep WARN /var/log/cloud-init.log || echo no warn |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-02-22T00:43:01.813488+00:00 This bug was fixed in the package cloud-init - 0.7.9-0ubuntu1~16.04.2 cloud-init (0.7.9-0ubuntu1~16.04.2) xenial-proposed; urgency=medium
cloud-init (0.7.9-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
-- Scott Moser smoser@ubuntu.com Mon, 06 Feb 2017 16:18:28 -0500 |
This bug was originally filed in Launchpad as LP: #1625766
Launchpad details
Launchpad user J(jwillx) wrote on 2016-09-20T18:29:38.627479+00:00
Sometimes reading from /sys/class/net//carrier returns an error and is unhangled causing fallback networking to not bring anything up.
[Original Description]
I am running Arch on a KVM vps provider. I installed using this template: Arch Linux 2016.03 64-bit (template). Everything was working fine until I decided to upgrade. I did pacman -Syu and everything upgraded without error until it restarted.
I had to manually install certain python packages. But, I kept getting more errors so I joined IRC.
Here's the log: https://irclogs.ubuntu.com/2016/09/20/%23cloud-init.html
Was told to post it Here to sum up everything
The text was updated successfully, but these errors were encountered: