Bug 1161366
| Summary: | wrong journalctl parameters in upgrade-post | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Serge Pavlovsky <pal666> |
| Component: | fedup-dracut | Assignee: | Will Woods <wwoods> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | awilliam, jgotts, jpazdziora, samuel-rhbugs, tflink, wwoods, zbyszek |
| Target Milestone: | --- | Keywords: | CommonBugs |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | https://fedoraproject.org/wiki/Common_F21_bugs#fedup-journald | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-09 19:50:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Serge Pavlovsky
2014-11-07 02:27:35 UTC
Hey, yeah, fixing the logging means that we're now dumping the entire journal. Whoops. Thanks for catching this.
Fixed in git:
https://github.com/wgwoods/fedup-dracut/commit/cde5f2d
Should be fixed for the F21 final release.
Please remove the -m too. Oh, hell. This missed F21, unfortunately. Still, I'll remove the '-m' upstream and rebuild to ensure this is fixed for F22. (In reply to Will Woods from comment #3) > Oh, hell. This missed F21, unfortunately. Majority of people do not have journals from other machines, and even if they do, those machines don't get a chance to run during fedup upgrade anyway, so it's mostly a cosmetic issue. > Still, I'll remove the '-m' upstream and rebuild to ensure this is fixed for > F22. Thanks! Can this fix be backported to F20 too? (The fedup instructions already tell users to make sure that they have the latest version) No, it can't. The script that writes out the journal is part of the upgrade.img in the boot media / install trees, which are frozen at release time. It's definitely not cosmetic. It added an additional 20 minutes to my fedup upgrade on a fairly new laptop. It's writing out logs dating back to February 21st. Sure, it's not cosmetic, but cannot be fixed (see comment #c6). This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Should this be CURRENTRELEASE with Fedora 22? I dislike to see bugs go EOLed ... No, it should be EOL, since fedup is EOL'd after F21. |