From Fedora Project Wiki
No edit summary
(commonbugs cleanup lalala)
Line 1: Line 1:
<noinclude>{{tempdoc}}</noinclude>
<!--
This header (down to the first "Issues" section below) is generated by '''SUBSTITUTING''' [[Template:Common_bugs_header_prerelease]] at the time of page creation: <nowiki>{{subst:Common_bugs_header_prerelease}}</nowiki>. Please do this rather than copy/pasting. At the time a release goes stable, replace this entire header with a '''SUBSTITUTION''' of [[Template:Common_bugs_header_stable_release]]: <nowiki>{{subst:Common_bugs_header_stable_release}}</nowiki>.If you are making improvements to the header text, please make them also in the [[Template:Common_bugs_header_stable_release]], [[Template:Common_bugs_header_prerelease]] and [[Template:Common_bugs_header_shared]] templates as appropriate, so future pages will contain the same improvements.


This page records {{{testtype|'''$testtype'''}}} [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora {{{release|'''$release'''}}} {{{milestone|'''$milestone'''}}} {{{compose|'''$compose'''}}} release.
*** INSTRUCTIONS ON ADDING ENTRIES TO THIS PAGE. FOLLOW THIS FORMAT FOR ALL ENTRIES PLEASE. ***


== How to test ==
{{Anchor|Issue-Foo}}
=== Issue Foo (example) ===
<small>[[#Issue-Foo|link to this item]] - [[rhbug:XXXXXX|Bugzilla: #XXXXXXX]]</small>


<!--Please change the link in the first step to point to the appropriate subdirectory of http://dl.fedoraproject.org/pub/alt/stage/ for the candidate build under test.-->
Words words words. Blah blah blah. Include a good explanation of the problem, and any available workarounds.


# [https://dl.fedoraproject.org/pub/alt/stage/{{{release|}}}_{{{milestone|}}}_{{{compose|}}} Download the media for testing].
When adding issues to this page, ensure to add the CommonBugs keyword to the bug report, and add the anchor link to the entry on this page in the Whiteboard field on the bug report.
# Perform one or more of the [[:Category:Base_Acceptance_Test_Cases|test cases]] and add your results to the table below.
# If a test fails, [https://bugzilla.redhat.com/enter_bug.cgi file a bug report]. You may [https://qa.fedoraproject.org/blockerbugs/propose_bug propose the bug as a release blocker or freeze exception bug] for the appropriate release - see [[QA:SOP_blocker_bug_process|blocker bug process]] and [[QA:SOP_freeze_exception_bug_process|freeze exception bug process]].


Some tests must be run against particular Products or images - for example, the [[#Default boot and install]] tests. If no particular product or image is specified either in this page or the test case page, you can use any appropriate image. For example, you can run most of the [[#General Tests]] with the Workstation live image, or either of the Server install images.
If a build which may fix the problem is made available via updates-testing, add this text to the description (appropriately customized for the issue):


[[Delta_ISOs]] for Server offline installer images are available [http://dl.fedoraproject.org/pub/alt/stage/deltaisos/{{{release|}}}_{{{milestone|}}}_{{{compose|}}}_Server here]. If you have the Server offline install image for the previous TC/RC (or in the case of Alpha TC1, the previous stable release), you can generate the current install image with greatly reduced download size.
An updated [http://admin.fedoraproject.org/updates/(name)-(EVR) (name)] package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and [http://admin.fedoraproject.org/updates/(name)-EVR report to Bodhi] whether it solves the problem. To test the update, run this command:
<pre>su -c 'yum --enablerepo=updates-testing update (name)'</pre>


If you notice a problem during a test which does not constitute a complete failure of the test, you should still file a bug report, but it may not be appropriate to propose it as a release blocker bug. Use your judgment in deciding this, with reference to the [[Fedora_Release_Criteria]], which these tests are intended to verify. If you are unsure, err on the side of proposing the bug as a blocker.
If a scratch build which may fix the problem is made available via Koji (rather than in updates-testing), add this boilerplate paragraph (appropriately customized for the issue):


{{admon/important|Don't install updates|Don't install updates before performing any of the tests, as when you are testing pre-releases, available updates are not part of the proposed released package set.}}
A test build that should resolve this problem is available from Koji: [http://koji.fedoraproject.org/koji/taskinfo?taskID=XXXXXXX packagename-EVR]. If you are affected by this issue, please test this update and report your results to the [[rhbug:XXXXXX|bug report]].


{{admon/note|Virtual machine testing|In most cases, testing in a virtual machine is OK.}}
If the page is in pre-release state and a documented problem has been fixed in Branched repos but no newer pre-release has yet come out, add this boilerplate paragraph (appropriately customized for the issue):


== Add, Modify or Remove a Test Case ==
This issue was fixed in the updated ''(name)-(EVR)'' package. To solve the issue, update your (pre-release name, e.g. "{{<includeonly>safesubst:</includeonly>FedoraVersion|long|next}} Beta") installation as usual. You should no longer encounter this issue after updating to that version or later of {{package|(name)}}.
# Please request review for your changes by publishing your test case for review to  and/or the appropriate working group mailing list ().
# Once reviewed, make your changes to any current documents that use the template (e.g. [[Test_Results:Current_{{{testtype|$testtype}}}_Test]]).
# Lastly, update [[Template:{{{testtype|$testtype}}}_test_matrix]] with the same changes.


== Key ==
When the page is in pre-release state and a new pre-release becomes available, simply remove any issues that are now fixed from the page entirely.
-->


See the table below for a sample format for test results. All test results are posted using the [[Template:Result|result template]].
{{autolang|base=yes}}


This page documents common bugs in Fedora 22 and, if available, fixes or workarounds for these problems.  If you find your problem in this page, ''do not file a bug for it, unless otherwise instructed.''  Where appropriate, a reference to the current bug(s) in Bugzilla is included.


{| class="wikitable sortable" border="0"
{{admon/note|Pre-release version|Fedora 22 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 22 pre-releases. Issues that are fixed will be removed from the page once a fix is available (for instance, an issue that affects the Beta but is fixed in the final release will be removed at the time of that release).}}
! Test Result !! Explanation !! Code Entered
 
|-
== Release Notes ==
| {{result|none}}
Read the [[F22_Alpha_release_announcement]] <!--and the [http://fedorapeople.org/groups/docs/release-notes/en-US/ Fedora {{<includeonly>safesubst:</includeonly>#expr: {{<includeonly>safesubst:</includeonly>CurrentFedoraVersion}} + 1}} Beta Release Notes] <!--[http://docs.fedoraproject.org/en-US/Fedora/{{<includeonly>safesubst:</includeonly>#expr: {{<includeonly>safesubst:</includeonly>CurrentFedoraVersion}} + 1}}/html/Release_Notes/ Fedora {{<includeonly>safesubst:</includeonly>#expr: {{<includeonly>safesubst:</includeonly>CurrentFedoraVersion}} + 1}} release notes]--> for specific information about changes in Fedora 22 and other general information.
| ''Untested'' - This test has not been run, and is available for anyone to contribute feedback.
 
| <code><nowiki>{{result|none}}</nowiki></code>
{{Common_bugs_header_shared}}
|-
| {{result|pass|robatino}}
| ''Passed'' - The test has been run and the tester determine the test met the ''expected results''
| <code><nowiki>{{result|pass|robatino}}</nowiki></code>
|-
| {{result|inprogress|adamwill}}
| ''Inprogress'' - An inprogress result is often used for tests that take a long time to execute.  Inprogress results should be temporary and change to pass, fail or warn.
| <code><nowiki>{{result|inprogress|adamwill}}</nowiki></code>
|-
| {{result|fail|jlaska|XYZ|ZXY}}  
| ''Failed'' - Indicates a failed test.  A link to a bug must be provided.  See [[Template:Result]] for details on providing bug information. <references/>
| <code><nowiki>{{result|fail|jlaska|XYZ|ZXY}}</nowiki></code>
|-
| {{result|warn|rhe}} <ref>Brief description about the warning status</ref>
| ''Warning'' - This test completed and met the ''expected results'' of the test, but other issues were encountered during testing that warrant attention.<references/>
| <code><nowiki>{{result|warn|rhe}} <ref>Brief description about the warning status</ref></nowiki></code>
|-
| {{result|pass|hongqing}} {{result|warn|kparal}}
| ''Multiple results'' - More people can easily provide results to a single test case.
| <code><nowiki>{{result|pass|hongqing}} {{result|warn|kparal}}</nowiki></code>
|-
| {{result|pass|previous <build> run}}
| ''Result from previous test run'' - This test result is directly moved from the test run of previous ''<build>''.<references/>
| <code><nowiki>{{result|pass|previous <build> run}}</nowiki></code>
|-
| style="background:lightgrey;"|
| ''Unsupported'' - An unsupported test or configuration.  No testing is required.
|
|-
|}
<noinclude>
[[Category:QA Templates]]
</noinclude>

Revision as of 20:41, 9 March 2015


This page documents common bugs in Fedora 22 and, if available, fixes or workarounds for these problems. If you find your problem in this page, do not file a bug for it, unless otherwise instructed. Where appropriate, a reference to the current bug(s) in Bugzilla is included.

Note.png
Pre-release version
Fedora 22 has not yet been released. During this pre-release period, this page will cover known issues in the Fedora 22 pre-releases. Issues that are fixed will be removed from the page once a fix is available (for instance, an issue that affects the Beta but is fixed in the final release will be removed at the time of that release).

Release Notes

Read the F22_Alpha_release_announcement for specific information about changes in Fedora 22 and other general information.


My bug is not listed

Not every bug is listed in this page, but Bugzilla should be a comprehensive database of known bugs. This page is a sampling of the bugs most commonly discussed on our mailing lists and forums.

To see if your bug has already been reported, you can search Bugzilla. If it has not yet been reported, we encourage you to do so to help improve Fedora for yourself and others. A guide to Bugs and feature requests has been prepared to assist you.

If you believe an already-reported bug report should be added to this page because it is commonly encountered, you can:

  • Add it yourself, if you have wiki access. Common bugs instructions provides guidance on how to add an entry to the page correctly, but the most important thing is to make sure that the bug is listed - don't worry if you don't get the format quite right, we can clean it up later.
  • Or, add the CommonBugs keyword to the bug report. Someone from the QA team will then inspect the issue to determine whether the bug should be listed as a common bug. To expedite your request, please add a comment to the bug that includes
    1. a summary of the problem
    2. any known workarounds
    3. an assessment on the impact to Fedora users

For reference, you can query Bugzilla for bugs tagged CommonBugs:

  • CommonBugs? (bugs with CommonBugs keyword, but do not yet have a link to this page)
  • CommonBugs+(bugs with CommonBugs keyword and contain a link to this page)
Retrieved from "https://fedoraproject.org/w/index.php?title=User:Adamwill/Test_page&oldid=406009"