Project

General

Profile

Bug #2426

Upgrade from F27 to F32

Added by bigfoot65 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
05/15/2020
Due date:
% Done:

0%


Description

I did an upgrade in 3 steps, two Fedora versions at a time. The steps below outline the process I completed:

#Upgrade F27 to F32
sudo dnf upgrade --refresh
#Reboot if anythng added
sudo dnf -y install dnf-plugin-system-upgrade
sudo dnf system-upgrade download --refresh --releasever=29 --nogpgcheck --allowerasing
sudo dnf system-upgrade reboot
#Once F29 working, next upgrade to F31
sudo dnf upgrade --refresh
#Reboot if anythng added
sudo dnf system-upgrade download --refresh --releasever=31 --nogpgcheck --allowerasing
sudo dnf system-upgrade reboot
#Once F31 is working, update to 32 
sudo dnf upgrade --refresh
#Reboot if anythng added
sudo dnf system-upgrade download --refresh --releasever=32 --nogpgcheck --allowerasing
sudo dnf system-upgrade reboot

I then noticed that since there aren't Amahi repos for F29 or F31, hda-ctl and hda-platform were removed. Once F32 upgrade was complete, I had to reinstall them. No other dependencies were installed and hda-ctl had to be started:
#Once F32 is working, install Amahi 12
sudo dnf install hda-ctl hda-platform
# Start hda-ctl
sudo systemctl start hda-ctl

I was able to access the dashboard and login initially. However, once the HDA rebooted, I received the following error:
Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Looking in /var/hda/platform/logs/error_log, I noticed the following error:
 [proxy_http:error] [pid 856:tid 140225528243968] [client ###.###.###.###:51694] AH01114: HTTP: failed to make connection to backend: localhost

I also tried to upgrade from F27 to F32 directly and the system upgrade would not work. The machine would reboot twice, then it'd be back to F27 login.

History

#1 Updated by bigfoot65 3 months ago

I think we need to have hda-ctl and hda-platform available in F29 and F31 repos for the upgrade.

Seems like the best path to F32 for upgrade.

#2 Updated by cpg 3 months ago

In Amahi 12, you also have to

sudo systemctl enable hda-platform
sudo systemctl start hda-platform

because the platform is running on a separate app server called puma and apache is just the web server (like when we use apache+php-fpm).

The issue will trying to do a light version of f29 and f31.

#3 Updated by bigfoot65 3 months ago

Yea when doing the first part of the upgrade to F29, the hda-ctl, hda-platform, and hda-suite are removed. This happens due to the --allowerasing option in the upgrade syntax. Since there is no F29 repo, the amahi.repo is disabled.

A light version should prevent that from happening.

Also available in: Atom