Atop binary file corruption after the node recieved a hot shutdown
Bug #1401562 reported by
Bogdan Dobrelya
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Triaged
|
Medium
|
Fuel Documentation Team | ||
| 6.1.x |
Triaged
|
Medium
|
Fuel Documentation Team | ||
Bug Description
Then the node got unexpected shutdown, atop binary file could became corrupted. Then corrupted, it cannot be either greped with atop -P nor listed with atop -r *starting from some point of the time*. Beyond of this time point, atop will through an error:
"atop/atopsar - uncompress: failed due to corrupted/
Looks like the only solution is to remove this file or back it up and restat atop service to start a new one.
This is not a Fuel bug, but atop one, though it impacts any troubleshooting
| Changed in fuel: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| milestone: | none → 6.1 |
| assignee: | nobody → Fuel for Openstack (fuel) |
| Changed in fuel: | |
| assignee: | Fuel for Openstack (fuel) → MOS Linux (mos-linux) |
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #1 |
Revision history for this message
| Aleksander Mogylchenko (amogylchenko) wrote | #2 |
| tags: | added: release-notes |
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #3 |
| Changed in fuel: | |
| assignee: | MOS Linux (mos-linux) → Fuel Documentation Team (fuel-docs) |
| status: | Confirmed → Triaged |
| no longer affects: | fuel/6.1.x |
| no longer affects: | fuel/6.0.x |
| Changed in fuel: | |
| status: | Triaged → New |
| Changed in fuel: | |
| milestone: | 7.0 → 8.0 |
| tags: | added: area-docs |
To post a comment you must log in.
Please add this to 6.0 release notes as well