[Bug 1956227] New: DNF System Upgrade page links to non-existent
component=dnf-plugin-system-upgrade
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1956227
Bug ID: 1956227
Summary: DNF System Upgrade page links to non-existent
component=dnf-plugin-system-upgrade
Product: Fedora Documentation
Version: devel
OS: Linux
Status: NEW
Component: install-guide
Severity: high
Assignee: pbokoc(a)redhat.com
Reporter: info(a)skierpage.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Target Milestone: ---
Classification: Fedora
(there's no Fedora Documentation component for Upgrading to a new release, or
Quick Docs)
Description of problem:
I followed https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/,
it went smoothly, well done!
But under "Frequently Asked Questions - How do I report issues with the
upgrade?", the step
Search Bugzilla for an existing bug report.
is a link to
https://bugzilla.redhat.com/buglist.cgi?component=dnf-plugin-system-upgra...
The bug list currently has one open bug 1767781 for the component
dnf-plugin-system-upgrade, but this doesn't seem to be a valid component any
more; it's not in the pop-up list when you enter a new bug. I'm not sure what
the correct component is for dnf system-upgrade bugs: some bugs are filed
against dnf, and others against dnf-plugins-extras.
Version-Release number of selected component (if applicable):
Not applicable.
How reproducible:
Every time.
Steps to Reproduce:
1. Read https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
2. Follow the link in "Search _Bugzilla for an existing bug report_."3
3. Try to file a bug.
Actual results:
Only one open bug for dnf-plugin-system-upgrade, and you can't choose this
Fedora component to enter a new bug.
Expected results:
Link should show a list of bugs with current system-update.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
5 months, 1 week
[Bug 2180561] New: Infinite loop after attempting recovery
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2180561
Bug ID: 2180561
Summary: Infinite loop after attempting recovery
Product: Fedora Documentation
Version: devel
Status: NEW
Component: selinux-user-guide
Assignee: pbokoc(a)redhat.com
Reporter: satensteinl(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: mprpic(a)redhat.com, pkennedy(a)redhat.com,
zach(a)oglesby.co
Target Milestone: ---
Classification: Fedora
Description of problem:
Here is a situation that has happened to a Fedora laptop workstation user
several times.
1) A modification is made to /etc/fstab (addition,correction,etc)
2) The individual fails to run sudo systemctl daemon-reload on laptop
3) On reboot, the system (presume it is selinux) blocks the boot of the
workstation
logon prompt is not reached. Linux wants user input.
4) The use than reruns the grub boot using recovery option.
5) The recovery option fails to add a ./autorelabel to /
6) The user reboots with no remedial action done.
7) User adds the ./autorelabel to / and reboots
8) The autorelabel takes effect, but then, all of
9) The file system's (parttions) are not in RW mode and...
The autorelabel is shutdown with a Reboot because
each filesystem is in RO mode for ./autorelabel.
9) Infinite loop on the laptop.
I have tried to do the recovery using the Everything.iso
as the recovery partition on that ISO was working up to version 36.
The keyword is "was".
Required
========
A recovery mode for the workstation iso that actually allows
autorelabel recovery. Workstation is way way more popular than Everything.iso
and
way way more popular than KDE version of Fedora.
Version-Release number of selected component (if applicable):
37.38. 39(rawhide)
How reproducible:
revise /etc/fstab without running sudo systemctl daemon-reload.
Steps to Reproduce:
1. See above.
2.
3.
Actual results:
Infinite loop, (for laptop, requires a reinstallation.
Expected results:
Autorelabel should somehow update RO file systems.
Additional info:
I was using the /everything.iso Recovery menu entry. Up to Fed 37, that was
working. But that recovery option has to be checked against Fedora 38, and also
provided for Gnome, KDE, and Cinnamon spins (or all spins).
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2180561
6 months, 2 weeks