- Network Connection Sharing using NetworkManager – https://fedoraproject.org/wiki/Features/ConnectionSharing
- Installer (Anaconda) support for reporting errors in Bugzilla – https://fedoraproject.org/wiki/Anaconda/Features/SaveToBugzilla
Thanks to Chris Lumens and Dan Williams for hanging out in #fedora-qa, answering questions and helping diagnose issues. Special thanks to Jóhann Guðmundsson and others for helping shake out bugs with NetworkManager and anaconda. Stay tuned this week for another installment featuring VirtStorage and VirtRemoteInstall.
For those not able to join Test Day, I’ve included notes below.
Dan Williams added wireless connection sharing to the F10, F9 and F8 NetworkManager. This allows for the creation of ad-hoc wireless networks with various security settings (WEP key, WEP passphrase, WPA). Instructions and screenshots have been posted into the test plan for F10.
What I’ve been hoping for now for a few Test Days happened on this event. Jóhann Guðmundsson (aka viking_ice) discovered an issue during the day related to ad-hoc connections failing. Dan rebuilt NetworkManager with a fix and a few minutes later we were back on. Dan has asked folks with multiple operating systems to help test this feature.
If you have a Fedora system with wireless running NetworkManager-0.7.0-0.11.svn4022 (or newer) and have any of the following, this new feature could use your help.
- a windows laptop
- an Apple laptop
- a wireless capable mobile device
- a system with a 3g mobile broadband adapter
Test instructions are available on the wiki. Please add your thoughts and/or issues to the test matrix. To get the latest NetworkManager packages …
On F9 or F8, type:
$ yum --enablerepo=updates-testing update NetworkManager
On a rawhide system:
$ yum update NetworkManager
Also, be on the lookout for bug#461169.
The iterative devel+testing loop continued with Chris Lumens and anaconda’s ability to save problems directly to bugzilla (ala bug-buddy). Given the recent outage, rawhide has not been installable for some time. It is slowly getting back on it’s feet. While we weren’t able to fully exercise the test plan, we were able to shake out quite a few issues that will no doubt help make having installable beta possible. That list of issues includes an API mismatch between python-bugzilla and bugzilla version 3.1.4+ as well as the list of installer issues noted below (duplicates removed):
|461071||dbus exception in loader, org.freedesktop.NetworkManager not provided|
|461129||Traceback save screen shows ‘Local Disk" selection with no selectable options|
|461136||No shell present on tty2 during VNC install|
|461148||Installer fails while sending traceback to bugzilla.redhat.com|
|461182||Loader download screen does not progress past 1%, but completes|
|461203||Anaconda disk druid displays lock icon next to unencrypted LVM PV|
John Poelstra had a great suggestion for SaveToBugzilla testing. If you’d like to help test this feature, an updates.img was created that will force anaconda to break. For information on how to create or use an updates.img, please refer to the Anaconda/Updates wiki. An example of how I used the updates.img with snake is shown below.
$ yum install snake $ snake-install -c updates=http://jlaska.fedorapeople.org/traceback.img \ http://download.fedora.redhat.com/pub/fedora/linux/development/$(uname -i)/os Retrieving file vmlinuz... | 2.4 MB 00:00 Retrieving file initrd.img... | 16 MB 00:02 Updating bootloader | 2 B 00:00 Done. You may now reboot your system to start the install.
The snake-install tool will download the boot images and update your bootloader config. Once you reboot your system, you may need to answer a few networking details from the installation program. When you see the Welcome screen, click Next to trigger a failure. The failure will look like:
Go ahead and click Save, and you will be presented with several methods to save your traceback, including directly to http://bugzilla.redhat.com.
From here you can try different scenarios posted in the test plan. Happy testing!