-
Notifications
You must be signed in to change notification settings - Fork 82
Open
Description
Hi,
This is a feedback from a complex company "grade" scenario for migrate some virtual machine from centos7 to centos8 to alma8 and i hope soon to alma9.
I try several things as for what i see things change in the wiki.
- https://wiki.almalinux.org/elevate/ELevate-quickstart-guide
- https://wiki.almalinux.org/documentation/migration-guide.html
In short several things not work as it. (probably because my env is sometimes a piece of junk).
What i think is missing/maybe should ask/go wrong :
- the change in the documentation (bad luck from my side)
- some issues with "old" kernel and some packages (dnf) that can't be remove/upgrade when alma is the os.(not fix for me today)
- the fact some package are not upgrade automaticly but have to be remove by hands and reinstall from alma (maybe i did wrong stuff at certain point of the upgrade)
- some proxy issues
- some gpg repositories key (dl and add but not see as it) issues (not fix for me today)
- need an automatic disable other repo and save for not centos/rhel repository list of package to reinstall (custom repo)
- a ask for reactivate custom repo after install is acheive and device reboot.
- some proxy issues (ask or provide a way to be sure proxy is set)
- check from the script failed but shouldn't (some issues already exist)
- remember users to reboot if needed
- Some upgrade issues with network card (not script fault)
- improve auto resolution in config file diff a least dump all file will be modify and create a file resume.lst for ei with the file list
- manage "lock" packages (rpm/dnf conf)
I probably miss several point and i'm not a dnf guy (more an apt one) so i did make mistake for sure. Be free to end me all your rtfm and other learning stuff ;)
thx for the work done.
Metadata
Metadata
Assignees
Labels
No labels