https://bugzilla.redhat.com/show_bug.cgi?id=1249314
Bug ID: 1249314
Summary: yumex-dnf is not following the install only_limit
config parameter default 3
Product: Fedora Documentation
Version: devel
Component: software-management-guide
Severity: medium
Assignee: docs(a)lists.fedoraproject.org
Reporter: totalitout(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs(a)lists.fedoraproject.org
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:39.0)
Gecko/20100101 Firefox/39.0
Build Identifier:
Using yumex-dnf when installing an updated kernel, the oldest kernel is not
removed. All kernels remain installed, apparently without limit. The default
to keep only the 3 newest kernels is ignored. Running: dnf update removes
excess kernels, the limit of 3 is observed.
Reproducible: Always
Steps to Reproduce:
1.Open yumex-dnf, run update.
2.Reboot to load updated kernel.
3.Kernel list displays more than 3 installed kernels.
Actual Results:
More than 3 kernels remain installed. The install only_limit config parameter
default 3 is ignored.
Expected Results:
Oldest kernel should be removed. No more than 3 kernels should remain
installed.
No error message. Didn't have any indication of a problem except when
rebooting noticed the excess kernels listed. This needs to be fixed. It could
cause unaware users to run out of space in their /boot partition.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1222305
Bug ID: 1222305
Summary: Release notes scattered with references to YUM. DNF
replaces yum
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: high
Assignee: relnotes(a)fedoraproject.org
Reporter: lsatenstein(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem:
The release notes on the web are not current and do not match the Fedora 22
release. The release notes within the Fedora 22 /usr/share/doc are also
refering to Fedora 19 in places.
In preparation for Fedora 22 release notes it looks like someone searched for
Fedora 21 and changed the 21 to 22.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1266636
Bug ID: 1266636
Summary: Link for update-crypto-policies needs updated.
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: medium
Assignee: relnotes(a)fedoraproject.org
Reporter: sheldon.corey(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem:
The anchor link for the update-crypto-policies referencing the rc4 ciphers
and such is dead.
Version-Release number of selected component (if applicable):
only found in 23
How reproducible:
Always in R/N for 23
Steps to Reproduce:
1. Navigate to
https://docs.fedoraproject.org/en-US/Fedora/23/html/Release_Notes/sect-Rele…
2. Click on the `update-crypto-policies' hyperlink
3. 404 page presented to you.
Actual results:
should redirect to
https://github.com/nmav/fedora-crypto-policies/blob/master/update-crypto-po…
Expected results:
presented with a github 404 error page
Additional info:
Merely needs fixing /updating of the reference link.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008149
Bug ID: 1008149
Summary: Contraficting info about the need of shared storage
for storing guest images to be migrated
Product: Fedora Documentation
Version: devel
Component: virtualization-getting-started-guide
Assignee: dayleparker(a)redhat.com
Reporter: jrodrigosm(a)yahoo.es
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dayleparker(a)redhat.com, docs(a)lists.fedoraproject.org
Hi,
In the Fedora 19 "Virtualization Getting Started Guide", section 2.2 ("What is
migration?"), URL
http://docs.fedoraproject.org/en-US/Fedora/19/html/Virtualization_Getting_S…
In the paragraph right before the 2.2.1 title, it is stated that "In Fedora 19,
shared storage is not necessary for storing guest images to be migrated. With
live storage migration [...]".
But in the last paragraph of the page, right before the note, it is stated that
"Shared, networked storage must be used for storing guest images to be
migrated. Without shared storage, migration is not possible."
These two statements seem contradictory to me. I just started learning about
virtualization, so I am unable to propose an alternative. But I do think some
clarification is needed.
Thanks,
Rodrigo
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1270597
Bug ID: 1270597
Summary: Systeam admin guide has wrong info for ssl certificate
generation
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: high
Assignee: swadeley(a)redhat.com
Reporter: pgaltieri(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Description of problem:
Section 9.1.7.4. Generating a New Key and Certificate of system admin user
guide has incorrect information on how to create SSL certificates. There are
several issues.
1) requires you to use yum to install packages
2) requires you to install package crypto-tools which does not exist
3) requires you to use program genkey which doesn't exist
Version-Release number of selected component (if applicable):
Edition 1 of online admin guide
https://docs.fedoraproject.org/en-US/Fedora/22/html/System_Administrators_G…
How reproducible:
Always
Steps to Reproduce:
1. Read
https://docs.fedoraproject.org/en-US/Fedora/22/html/System_Administrators_G…
2. goto section 9.1.7.4
3.
Actual results:
Provides wrong information
Expected results:
Correct infor on how to create an SSL certificate
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1206351
Bug ID: 1206351
Summary: dnf conversion tracker bug
Product: Fedora Documentation
Version: devel
Component: docs-requests
Assignee: nobody(a)fedoraproject.org
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Additional information:
Tracker for individual documentation blockers.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1206805
Bug ID: 1206805
Summary: convert yum commands to dnf commands - System
Administrators Guide
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: striker(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
External Bug ID: Red Hat Bugzilla 1206351
External Bug ID: Red Hat Bugzilla 1206351
Description of problem:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Sys…
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1193135
Bug ID: 1193135
Summary: Review Comments on Multiboot Guide version 0.1
Product: Fedora Documentation
Version: devel
Component: multiboot-guide
Severity: low
Assignee: chris.roberts(a)croberts.org
Reporter: scmccann2000(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: chris.roberts(a)croberts.org
Created attachment 992259
--> https://bugzilla.redhat.com/attachment.cgi?id=992259&action=edit
smccann comments to multiboot guide.
Attaching a pdf with a few comments from the perspective of a newbie to both
Fedora and multiboot. In general, very readable and understandable guide!
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1180202
Bug ID: 1180202
Summary: Overlap with uefi-secure-boot-guide
Product: Fedora Documentation
Version: devel
Component: multiboot-guide
Assignee: chris.roberts(a)croberts.org
Reporter: fweimer(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: chris.roberts(a)croberts.org
With the recent updates, there is now some overlap with the UEFI Secure Boot
guide.
I'm not sure the current state of Secure Boot is useful for non-dual-boot
systems, considering the feature loss and the lack of additional security due
to buggy kernels and permissive signed bootloaders from other vendors. Perhaps
merging the UEFI Secure Boot guide into the multiboot guide makes sense?
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1086052
Bug ID: 1086052
Summary: Include a section on using the Live media for rescue
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: sanjay.ankur(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
The install guide contains a section that documents how one can use the rescue
mode off the dvd. It doesn't document how one can use the live media for simple
rescue operations. The most common use case is when people install Window after
installing Fedora off a live media. They lose grub, and they can't figure out
how to use the live media to reinstall it.
There are a couple of blog posts that document it. For example:
http://thecreationist.expertscolumn.com/article/recover-grub-using-fedora-l…
It would maybe be a good idea to have a section in docs that provides hints on
how the live cd can be used for basic rescue operations.
Thanks,
Warm regards,
Ankur
--
You are receiving this mail because:
You are the QA Contact for the bug.