From Fedora Project Wiki

Revision as of 17:32, 10 February 2015 by Adamwill (talk | contribs) (add known issues section)

Fedora Test Days
Anaconda and Dnf

Date 2015-02-12
Time all day

Website Fedora Calendar
IRC #fedora-test-day (webirc)
Mailing list test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on DNF use in Anaconda, the Fedora installer. DNF is the package manager intended to replace yum as the default for Fedora soon: part of the goal of this test day is to decide if it is in good enough shape to replace yum for Anaconda for Fedora 22.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

Prerequisite for Test Day

  • Rawhide nightly image(s) (links to come)
  • Test system / drive or virtual machine (for this test day, you need something you can lose all the data from, non-destructive testing is not possible)
  • (Optional) a server for hosting kickstarts

How to test?

Known issues

For all testing described below, please note that there are some issues that are already known - no need to spend time reproducing these problems and filing new reports.

  • No proxy support. Proxies just won't be used
  • kickstart repos additionally do not implement --cost, --excludepkgs, --includepkgs, --ignoregroups
  • All of that, except proxy URL and cost, is also missing in the .repo files written with anaconda
  • %packages --multilib is not implemented
  • Language support selection is not saved in the dnf-langpacks configuration
  • Excluding packages in a kickstart does not work.

Planned testing

Download one of the nightly images to be used for testing, and run through one or more of the test cases listed on the results page. Report any bugs you encounter, and enter your results on the results page.

Exploratory testing

You can also do free form testing to exercise the package-related functions of the installer as much as possible: try different things in the INSTALLATION SOURCE and SOFTWARE SELECTION screens, and exercise the kickstart directives relating to repositories and package sets.

You can add test kickstarts and bugs you encounter in exploratory testing to the table below, following the example format. Please include all details and comments about the bug in the bug report and just include your name and the lists of bugs and kickstarts in the table. It's fine to only include bugs (if you only do interactive testing) or only kickstarts (if you tested kickstarts and didn't find any bugs). If you do not have access to a site or service to upload your kickstarts to, you can upload them to this Wiki.

Tester Bugs reported Kickstarts
Example RHBZ #123456 RHBZ #654321 groups.ks

Reporting bugs

If you have problems with any of the tests, report a bug to Bugzilla for the appropriate component. Likely choices are:

If you are unsure about which component to report a bug against, exactly how to file the report, or what other information to include, just ask on IRC and we will help you.

Test Results

Please enter results for the planned testing on the results page. The results will be transferred here some time after the Test Day concludes for the record.