I am able to upgrade with RHSM. Without RHSM, I am stock with /etc/leapp/files/leapp_upgrade_re positories.repo. It is not clear how/where to create this repo. Can you help?
Would you know how much of available space is required on / in order to in-place upgrade complete successfully? In my system I use LVM for most o filesystems and a 12G long partition for / + /usr and it failed due lack of space on / partition.... even after the pre upgrade step have finished in green state,
Hi David, this varies based on amount of needed space for the installed content and on your partitioning (everything is on / ? is /var separated? is /usr separated? ....). For minimal installations, ~7GB of free space on / (including /usr) should be enough (unless system contains XFS partitions formatted withou ftype attributes). In your case, I guess it failed during the Download phase - during the download of the target RHEL rpms or right after when DNF calculates there is enough space for the upgrade, correct? This usually happens on system containing partitions with XFS formatted **without ftype** attributes. (xfs_info ; if ftype=0, then it's without ftype attributes; speaking about any such a parition on the system!! not just about /). In such a case check leapp.readthedocs.io/en/latest/el7toel8/envars.html#leapp-ovl-size -- it's a trade off to be able to workaround the fact this FS does not support containter technologies. If this is not your case, open ticket on RH support (attaching sosreport + /var/lib/leapp/leapp.db file; all generated right the run of leapp). It helps with investigation + prioritisation.
![[LIVE] : ONE ลุมพินี 86 | คู่เอก "คมเพชร vs ชาติพยัคฆ์"](http://i.ytimg.com/vi/m3q_dRYDuU8/mqdefault.jpg)
Fantastic tool - our team just used this process with little to no issues.
😍👨🎓✍️ Thank you
I am able to upgrade with RHSM. Without RHSM, I am stock with /etc/leapp/files/leapp_upgrade_re
positories.repo. It is not clear how/where to create this repo. Can you help?
Would you know how much of available space is required on / in order to in-place upgrade complete successfully? In my system I use LVM for most o filesystems and a 12G long partition for / + /usr and it failed due lack of space on / partition.... even after the pre upgrade step have finished in green state,
Hi David, this varies based on amount of needed space for the installed content and on your partitioning (everything is on / ? is /var separated? is /usr separated? ....). For minimal installations, ~7GB of free space on / (including /usr) should be enough (unless system contains XFS partitions formatted withou ftype attributes). In your case, I guess it failed during the Download phase - during the download of the target RHEL rpms or right after when DNF calculates there is enough space for the upgrade, correct? This usually happens on system containing partitions with XFS formatted **without ftype** attributes. (xfs_info ; if ftype=0, then it's without ftype attributes; speaking about any such a parition on the system!! not just about /). In such a case check leapp.readthedocs.io/en/latest/el7toel8/envars.html#leapp-ovl-size -- it's a trade off to be able to workaround the fact this FS does not support containter technologies. If this is not your case, open ticket on RH support (attaching sosreport + /var/lib/leapp/leapp.db file; all generated right the run of leapp). It helps with investigation + prioritisation.
2GB
Hi sir..will u pls help me with upgrade of rhel 7.6 to rhel7.8.
Take a backup or create a snapshot then run "yum update" then cat the version file.
Can we perform any online upgrade using dvd or some other source without using Leapp
Basically not. That's why leapp exists. The DNF package manager cannot handle the upgrade alone.
I have satellite server in my environment and I want rhel7 upgrade to rhel8 using this satellite
Does the applications version also get upgraded along with leapp upgrade.. 7 - 8
horrible audio quality