-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
None
-
False
-
False
-
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
Details
- Affected Upgrade paths: 7->8, 8->9, 9->10
- When should be doc. updated? ASYNC
- Docs to update (optional): main upgrade docs
- Describe what should be documented: After the boot the the upgraded system, leapp needs to perform last bits of the upgrade. However, in some cases the leapp execution can be delayed (waiting for the full system boot) and it could happen that user could start to perform manual post-upgrade steps before leapp finishes all actions. Add an instruction to post-upgrade tasks (or append to the upgrade chapter?.. somehow I feel that post-upgrade section is better, but let's discuss it yet) to check whether leapp finished all required actions. A possible command for that could be:
[ -e "/etc/systemd/system/leapp_resume.service" ] || ps -e | grep -q leapp && echo "Leapp has not finished the execution yet!"
Possibly we will add instruction for the manual start of the service as well, as in some cases it could be delayed too much. We will think about that yet.
This was initiated by automation to document a change for In-Place Upgrades that requires documentation updates or overview. You are able to edit any aspect of this issue as long as the documents issue link is preserved.
- documents
-
RHEL-116838 [LEAPP 8to9] Race window of leapp.workflow.FirstBoot vs Documentation
-
- New
-