Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

--resume after failed convert does not re-enable plesk-dist-upgrade-resume.service; finish phase not started

Aperta
  • Qualcosa non va?
#145 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, python
Ambito
cli, infrastructure

Direzione di ricerca

Start with the failure path that logs "Disable systemd 'plesk-dist-upgrade-resume.service' service after conversion failure" and the stage that logs "Prepare finishing systemd service", then compare how a normal run and a --resume run from "Repositories handling" reach them. Reproducing needs a test VM with a failed convert and resume.json set to that stage. Done means the resume service is enabled before the reboot after a --resume convert, or the failure path no longer disables it; the maintainer still has to choose between those two fixes.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Environment

  • cloudlinux7to8 v1.2.1
  • CloudLinux 7.9 (TuxCare ELS) -> CloudLinux 8.10, Plesk Obsidian 18.0.81.3

Describe the bug
The convert phase failed in leapp upgrade (transaction test, see #144). On failure the tool disables the resume service:

Disable systemd 'plesk-dist-upgrade-resume.service' service after conversion failure
Removed symlink /etc/systemd/system/multi-user.target.wants/plesk-dist-upgrade-resume.service.

After fixing the cause, I continued with ./cloudlinux7to8 --resume. resume.json had "stage": "Repositories handling", so the run continued from "Do convert": leapp upgrade succeeded, the server rebooted into the ELevate initramfs and came up as CloudLinux 8.10.

However, the finish phase never started. /var/log/plesk/cloudlinux7to8.log had no entries after the reboot, plesk-dist-upgrade-resume.service was still disabled, and resume.json showed "phase": "finish", "stage": null. The stage that enables the service ("Prepare finishing systemd service") runs before "Repositories handling", so it is skipped on --resume, and nothing re-enables the service that was disabled on failure.

The server was left on CloudLinux 8 with Plesk services stopped until the finish phase was started manually.

Expected behavior
When resuming the convert phase, make sure the resume service is enabled again before the reboot (regardless of the stage the run resumes from), or don't disable it on failures that can be resumed.

Workaround
After the reboot, run ./cloudlinux7to8 --resume manually. The finish phase then completed successfully.

Lingua principale
Python
Stelle
7
Fork
5
Merge medio
11m
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di plesk/cloudlinux7to8

Tutte le issue di plesk/cloudlinux7to8

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.