Bug 1272061
Summary: | WARNING: kernel version inconsistency between vmlinux and live memory | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Flavio Leitner <fleitner> | |
Component: | crash | Assignee: | Dave Anderson <anderson> | |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 22 | CC: | anderson | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | crash-7.1.3-1.fc22 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1274732 (view as bug list) | Environment: | ||
Last Closed: | 2015-10-26 13:23:03 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1274732 |
Description
Flavio Leitner
2015-10-15 11:48:24 UTC
No surprise there. Since Fedora doesn't have a consistent kernel, I can go through the update procedure today, and tomorrow's kernel can break it again. Using the rawhide version is always preferable, even if the released version still works. I built an f22 package, but I can't get fedpkg update to work: $ fedpkg update Creating a new update for crash-7.1.3-1.fc22 Password for crash: Creating a new update for crash-7.1.3-1.fc22 ServerError(https://admin.fedoraproject.org/updates/save, 404, Not Found) Traceback (most recent call last): File "/usr/bin/bodhi", line 217, in main data = bodhi.save(**update_args) File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py", line 111, in save 'bugs': bugs, File "/usr/lib/python2.7/site-packages/fedora/client/baseclient.py", line 344, in send_request auth_params=auth_params, retries=retries) File "/usr/lib/python2.7/site-packages/fedora/client/proxyclient.py", line 376, in send_request raise ServerError(url, http_status, msg) ServerError: ServerError(https://admin.fedoraproject.org/updates/save, 404, Not Found) Could not generate update request: Command 'bodhi --new --release f22 --file bodhi.template crash-7.1.3-1.fc22 --username crash' returned non-zero exit status 255 $ crash-7.1.3-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-b9c85dc537 The web interface worked... crash-7.1.3-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update crash' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-b9c85dc537 The "Push-to-Stable" operation failed: ============================================================ crash-7.1.3-1.fc22 into f22-updates ============================================================ [ OK ] f21 Latest package: crash-7.0.8-1.fc21 [ OK ] f21-updates Latest package: None [ OK ] f22 Latest package: crash-7.1.0-1.fc22 [--->] f22-updates Proposed package: crash-7.1.3-1.fc22 [FAIL] f23 + f23-updates Latest package: crash-7.1.2-1.fc23 Latest pending package: None Error: Condition not satisfied: crash-7.1.3-1.fc22 <= crash-7.1.2-1.fc23 Error: Proposed package version must be lesser than or equal to the latest (pending) package version. [ OK ] f24 Latest package: crash-7.1.3-1.fc24 Latest pending package: None RESULT: FAILED SUMMARY: 1 FAILED So I've cloned this BZ for f23, and will try the push in that release. I'm not sure sure whether the push-to-stable for f22 will get retried automatically once f23 is updated, but I note that the "push-to-stable" button is no longer visible. Then again, this BZ was automatically set as a blocker above, so maybe the push-to-stable will get retried. crash-7.1.3-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |