-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-7.9.z
-
leapp-repository-0.20.0-4.el7_9
-
None
-
None
-
1
-
rhel-sst-upgrades
-
20
-
None
-
False
-
-
None
-
Leapp: 9.5 & 10.0 public beta
-
Requested
-
RegressionOnly
-
None
M7a instances use custom AMD EPYC 9R14 (Genoa/Zen 4). IPU is inhibited because of that (from dddd json from CPU family 25 only model 1 is supported).
Inhibitor:
Risk Factor: high (inhibitor)
Title: Leapp detected a processor which is no longer supported in RHEL 9. Upgrade cannot proceed.
Summary: Support for the following processors has been removed in RHEL 9:
- Unsupported Family 19h
lscpu output:
Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: AuthenticAMD BIOS Vendor ID: Advanced Micro Devices, Inc. CPU family: 25 Model: 17 Model name: AMD EPYC 9R14 BIOS Model name: AMD EPYC 9R14 Stepping: 1 CPU MHz: 3698.389 BogoMIPS: 5199.99 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 4096K NUMA node0 CPU(s): 0 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf tsc_known_freq pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cr8_legacy abm sse4a misalignsse 3dnowprefetch topoext perfctr_core invpcid_single ssbd perfmon_v2 ibrs ibpb stibp ibrs_enhanced vmmcall fsgsbase bmi1 avx2 smep bmi2 invpcid avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves avx512_bf16 clzero xsaveerptr wbnoinvd arat avx512vbmi pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid flush_l1d
dddd.json excerpt from latest leapp-repository (leapp-repository-0.20.0-2):
{
"available_in_rhel": [],
"deprecation_announced": "",
"device_id": "x86_64:amd:25:[2-255]",
"device_name": "Unsupported Family 19h",
"device_type": "cpu",
"driver_name": "",
"maintained_in_rhel": []
}
- links to
-
RHBA-2024:131880
leapp and leapp-repository bug fix and enhancement update
- mentioned in
-
Page
No Confluence page found with the given URL.
[RHEL-34185] inhibited upgrade on M7a AWS insances
Christophe Besson
added a comment - The same problem can occur with VMWare (and also Oracle cloud), you can add 6 cases (at least) as per the below KCS that I have just updated
Christophe Besson
added a comment - The same problem can occur with VMWare (and also Oracle cloud), you can add 6 cases (at least) as per the below KCS that I have just updated
https://access.redhat.com/solutions/7052222 I can confirm that RUT no longer fails because of this with regenreated dddd json
rhn-support-mkluson will you please clone this ticket to the RHEL project?
So the fix is to regenerate the dddd.json data. Current source of truth is correct. Checking the convert script, it seems that everything is converted correctly.
Note that data currently contains also infomation about RHEL 10 HW maintainance/support.
In the meanwhile, I figured out that data has been changed in the meanwhile:
- readable output: https://redhat.gitlab.io/rhel/src/kernel/hardware-removal-support/cpus.html#x86-64-amd-25
- https://gitlab.com/redhat/rhel/src/kernel/hardware-removal-support/-/blob/main/hardware-removal-support.yaml?ref_type=heads#L2183
Checking the change in the leapp-repository, last data has been updated in Aug, and it switched from original (correct) field to the one presented above.
- Update: the json file has been generated internally in June. So I guess it was still before the switch to new format.
prarit@redhat.com jstancek@redhat.com are the device & driver deprecation data from kernel-hw team correct? regarding the data, it seems that such a family is not maintained / supported on any RHEL system, as `available_in_rhel` and `maintained_in_rhel` fields are empty.
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (leapp and leapp-repository bug fix and enhancement update), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2024:4214