View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
291 [AlmaLinux-8] -OTHER minor always 2022-08-06 12:57 2022-08-06 12:57
Reporter: ap8 Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Errata entry missing for httpd
Description: Advisory https://access.redhat.com/errata/RHSA-2022:5163 for CVE-2020-13950 is missing from AlmaLinux errata, but it is present in RockyLinux (https://errata.rockylinux.org/RLSA-2022:5163) and Oracle Linux (https://linux.oracle.com/errata/ELSA-2022-5163.html).
Tags:
Steps To Reproduce: In RockyLinux:
<code>
[root@rocky8 ~]# dnf updateinfo --info --all --cve CVE-2020-13950
Last metadata expiration check: 1:23:17 ago on Sat 06 Aug 2022 11:23:52 UTC.
===============================================================================
  Low: httpd:2.4 security update
===============================================================================
  Update ID: RLSA-2022:5163
       Type: security
    Updated: 2022-07-07 20:12:43
       CVEs: CVE-2020-13950
Description: For more information visit https://errata.rockylinux.org/RLSA-2022:5163
   Severity: Low
  Installed: true
[root@rocky8 ~]#
</code>

In AlmaLimux:
<code>
[root@alma8 ~]# dnf updateinfo --info --all --cve CVE-2020-13950
Last metadata expiration check: 1:25:21 ago on Sat 06 Aug 2022 11:20:58 UTC.

[root@alma8 ~]#
</code>
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
290 [AlmaLinux-8] osbuild-composer major always 2022-07-25 10:38 2022-07-25 10:38
Reporter: TulanKansen Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.6  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Impossible to create Installation ISO with osbuild-composer
Description: Hello,
I have discovered a blocking bug in osbuild-composer, who prevent at least creation of "installation ISO" file. In the upstream source package, the package "libreport-rhel-anaconda-bugzilla" is required during image creation.
Tags:
Steps To Reproduce: 1) Install osbuild-composer
2) create a blueprint with any package or configuration
3) create image with type "RHEL Installer (.iso)
4) creation fail because RPM package "libreport-rhel-anaconda-bugzilla" is not available in AlmaLinux
Additional Information: Proposed patch for the compilation of osbuild-composer RPM packages:
```Diff
diff -aruN osbuild-composer-46.3/internal/distro/rhel86/package_sets.go osbuild-composer-46.3_alma/internal/distro/rhel86/package_sets.go
--- osbuild-composer-46.3/internal/distro/rhel86/package_sets.go 2022-04-28 17:33:25.000000000 +0000
+++ osbuild-composer-46.3_alma/internal/distro/rhel86/package_sets.go 2022-07-22 16:29:43.048882567 +0000
@@ -748,7 +748,6 @@
                        "libibverbs",
                        "libreport-plugin-bugzilla",
                        "libreport-plugin-reportuploader",
- "libreport-rhel-anaconda-bugzilla",
                        "librsvg2",
                        "linux-firmware",
                        "lklug-fonts",
```
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
286 [AlmaLinux-8] -OTHER minor N/A 2022-07-20 18:11 2022-07-20 18:11
Reporter: toracat Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Add missing "AlmaLinux" to the mailing list subject line
Description: Currently, the subject line is set up as:

users@lists.almalinux.org [AlmaLinux Users]
devel@lists.almalinux.org [Devel]
security@lists.almalinux.org [Security]

Please change the latter two to [AlmaLinux Devel] and [AlmaLinux Security], respectively.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
274 [AlmaLinux-8] kernel major always 2022-07-01 06:37 2022-07-19 18:05
Reporter: dufgrinder Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: nvidia Legacy 390 does not compile
Description: I've tried to install nvidia driver for my graphic Card GeForce GT520:

Using the standard package: akmod-nvidia-390xx

The compilation fails (see attached log)

For information, it was working fine on CentOS7.
I've also tried with the NVIDIA-Linux-x86_64-390.151.sh (downloaded from the vendor site), it also failed.
Tags:
Steps To Reproduce: dnf install akmod-nvidia-390xx

# See the attached /var/cache/akmods/nvidia-390xx/390.144-3.el8-for-4.18.0-372.9.1.el8.x86_64.failed.log
Additional Information:
Attached Files: 390.144-3.el8-for-4.18.0-372.9.1.el8.x86_64.failed.log (511,249 bytes) 2022-07-01 06:39
https://bugs.almalinux.org/file_download.php?file_id=161&type=bug
akmods.log (5,536 bytes) 2022-07-01 06:39
https://bugs.almalinux.org/file_download.php?file_id=162&type=bug
Notes
(0000623)
dufgrinder   
2022-07-01 06:39   
The logs
(0000624)
toracat   
2022-07-01 10:41   
I recommend you give ELRepo's kmod package a try. To do this, you need to uninstall what you have installed so far and :

(1) Set up the ELRepo repository by following the instructions on https://www.elrepo.org/

sudo rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
sudo yum install https://www.elrepo.org/elrepo-release-8.el8.elrepo.noarch.rpm

(2) Then install the nvidia-detect package and run it ( see https://www.elrepo.org/tiki/nvidia-detect for details )

sudo yum install nvidia-detect
nvidia-detect -v
sudo yum install $(nvidia-detect)
(0000635)
dufgrinder   
2022-07-09 11:49   
Thanks toracat,

But it gives the same result (because nvidia-detect recommands to install the kmod-nvidia driver)

Read you soon, Olivier
(0000636)
toracat   
2022-07-09 16:34   
Are you sure nvidia-detect said "kmod-nvidia"? Not "kmod-nvidia-390xx" ? The latter is expected for the GT 520 card.
(0000637)
toracat   
2022-07-09 16:36   
Please copy the output of the command 'nvidia-detect -v' here. It should show the device IDs [xxxx:yyyy].
(0000642)
dufgrinder   
2022-07-13 04:13   
Hi,

nvidia-detect reports the following:
Probing for supported NVIDIA devices...
[10de:1040] NVIDIA Corporation GF119 [GeForce GT 520]
This device requires the legacy 390.xx NVIDIA driver kmod-nvidia-390xx
(0000643)
toracat   
2022-07-13 08:51   
So far, so good. Now all you have to do is to run the last command:

sudo yum install $(nvidia-detect)

Or you can run:

sudo yum install kmod-nvidia-390xx
(0000644)
dufgrinder   
2022-07-14 02:44   
Hi,

I did last week, that was I said " it gives the same result "
The akmods fails, compilation logs are uploaded in this ticket.
(0000645)
toracat   
2022-07-14 17:29   
Please note that ELRepo's kmod packages do NOT require compilation at all. They provide drivers that have been compiled for your kernel. Also, within a minor release (for example el 8.6), they do not need to be re-installed for each kernel update, thanks to their kABI-tracking nature.
(0000646)
toracat   
2022-07-14 17:32   
Make sure you run :

yum install kmod-nvidia-390xx

NOT:

yum install akmod-nvidia-390xx

(akmod is not an elrepo package)
(0000649)
dufgrinder   
2022-07-19 17:59   
Hello Toracat,

We found the root cause:
- On my install, I use RPM-Fusion
  yum install kmod-nvidia-390xx returns:
==============================================================================================================
 Paquet Architecture
                                                Version Dépôt Taille
==============================================================================================================
Installation:
 kmod-nvidia-390xx x86_64 3:390.144-3.el8 rpmfusion-nonfree-updates 55 k
Installation des dépendances:
 akmod-nvidia-390xx x86_64 3:390.144-3.el8 rpmfusion-nonfree-updates 89 k
 akmods noarch 0.5.6-24.el8 epel 27 k
 egl-wayland i686 1.1.9-3.el8 appstream 41 k
 egl-wayland x86_64 1.1.9-3.el8 appstream 39 k
 kernel-abi-stablelists noarch 4.18.0-372.16.1.el8_6 baseos 8.1 M
 kmodtool noarch 1-37.el8 epel 19 k
 nvidia-settings-390xx x86_64 390.144-2.el8 rpmfusion-nonfree-updates 1.7 M
 xorg-x11-drv-nvidia-390xx x86_64 3:390.144-2.el8 rpmfusion-nonfree-updates 2.6 M
 xorg-x11-drv-nvidia-390xx-kmodsrc x86_64 3:390.144-2.el8 rpmfusion-nonfree-updates 9.1 M
 xorg-x11-drv-nvidia-390xx-libs i686 3:390.144-2.el8 rpmfusion-nonfree-updates 16 M
 xorg-x11-drv-nvidia-390xx-libs x86_64 3:390.144-2.el8 rpmfusion-nonfree-updates 15 M

As you see, it also downloads the akmod.
Finally, I used
> yum install --disablerepo rpmfusion-nonfree-updates kmod-nvidia-390xx

And now it works fine.
I think we can close this ticket, many thanks for your help

KR, Olivier
(0000650)
toracat   
2022-07-19 18:05   
Glad to hear things are now working. Right, rpmfusion is a different beast.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
236 [AlmaLinux-8] kernel major always 2022-05-17 13:30 2022-07-17 18:57
Reporter: pmdumuid Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: The Simple Desktop Display Manager (sddm) fails to launch when using the default kernel that comes with Almalinux 8.6
Description: After upgrading to my AlmaLinux 8.6, I was unable to log in to a graphical environment (sddm). However when selecting an older version of the kernel from the grub screen, I am able to log in via the graphical environment (sddm).

I have since installed AlmaLinux 8.6 from scratch in a virtual machine and replicated this problem with a fresh install.

My colleages using different hardware are also experiencing this issue.

Given that sddm is a default desktop manager for KDE environments, I would presume this is major in severity.

My diagnosis so far:

Switching to a text terminal (Ctrl-Alt+F5) and logging in, I identified that sddm was freezing.

journalctl -b -u sddm.service

stops after showing:

May 17 20:25:50 linux-disp.kydlocal systemd[1]: Started Simple Desktop Display Manager.

when using the failing kernel, however for a working kernel, it shows a lot more:

-- Logs begin at Tue 2022-05-17 20:25:15 ACST, end at Tue 2022-05-17 22:49:48 ACST. --
May 17 20:25:50 linux-disp.kydlocal systemd[1]: Started Simple Desktop Display Manager.
May 17 20:25:58 linux-disp.kydlocal sddm[1933]: Could not setup default cursor
May 17 20:25:59 linux-disp.kydlocal sddm-helper[4193]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
May 17 20:26:32 linux-disp.kydlocal sddm-helper[11443]: pam_unix(sddm:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=xxxx

Tags:
Steps To Reproduce: Steps:

install a fresh Almalinux 8.6
Install sddm
Enable sddm (systemctl enable sddm.service)
Start sddm (systemctl start sddm.service)

What should occur:
A graphical login screen to show up .

What actually occurs:
A black screen with mouse visible upon movement, (i.e. Xorg started)
No text or graphics visible
Additional Information: Working kernel version - 4.18.0-348.23.1.el8_5.x86_64
Failing Kernel Version - 4.18.0-372.9.1.el8.x86_64
Attached Files:
Notes
(0000577)
alukoshko   
2022-05-24 00:23   
Hi.
Seems like upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=2082719
(0000595)
dfilonov   
2022-06-10 15:56   
Confirming the new kernel from Centos Stream ( kernel-4.18.0-394.el8.x86_64 ) fixes the issue.
(0000648)
toracat   
2022-07-17 18:57   
There was an update to the RHBZ quoted above:

" Troy Dawson 2022-07-13 14:26:47 UTC

There is progress on getting this fixed in RHEL 8.6, instead of just waiting for RHEL 8.7.
No expected date yet, but the work has started. "

Once it is fixed in RHEL, Alma will inherit it.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
277 [AlmaLinux-8] kernel major always 2022-07-05 01:14 2022-07-16 20:23
Reporter: amcrae42 Platform: x86_64  
Assigned To: OS: almalinux  
Priority: normal OS Version: 8.6  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: 8.6 kernel breaks program
Description: qbittorrent search hangs and locks up GUI.

Almalinux 8.4 kernel 305 works OK
Almalinux 8.5 kernel 348 works OK
Almalinux 8.6 kernel 372 hangs/locks up GUI
Almalinux 9.0 kernel 5.x works OK (recompiled for el9)
Tags:
Steps To Reproduce: Install virgin 8.6 system on test machine
install epel, run yum update
install qbittorrent
under View, tick the search Engine box
click on search tab, search plugins, check for updates, close
type anything in search field
GUI hangs

Manually install kernel vmlinuz-4.18.0-348.el8.x86_64 from Almalinux 8.5
(install kernel, kernel-core, kernel-modules rpms from 8.5 cd)
reboot
Repeat qbittorrent search test - all works OK
Additional Information:
Attached Files:
Notes
(0000647)
amcrae42   
2022-07-16 20:23   
This bug breaks multiple applications and is related to the handling of subprocesses.

Breaks seafile client, causes hangs in truecrypt.

Is probably the same bug as 000236.

I am now running centos stream kernel 4.18.0-394 which fixes all of the above.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
282 [AlmaLinux-8] -OTHER minor have not tried 2022-07-13 21:35 2022-07-13 21:35
Reporter: cPSloaneB Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Publicly document that ELevate is not currently compatible with system container environments
Description: ELevate is geared towards bare metal or virtual environments which allow the guest system to change the way the system boots. At least according to the migration room on chat.almalinux.org, system containers (e.g., OpenVZ) are not currently supported because of this, and a different way of accomplishing certain operations would need to be devised. This information should be made available in a more publicly visible location, perhaps such as somewhere in the ELevate section of wiki.almalinux.org.
Tags: elevate, leapp
Steps To Reproduce:
Additional Information: See https://chat.almalinux.org/almalinux/channels/migration/er4xdybfa7y5ixe18wqxizk59a, at or around the 18th of March 2022, for the start of the relevant conversation.
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
280 [AlmaLinux-8] dracut major always 2022-07-12 05:02 2022-07-12 17:08
Reporter: AstroTJP Platform: Opteron Servers running Linux  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5, 8.6, (9.0)  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Cannot install AlmaLinux 8.5 and 8.6 (nor 9.0) onto Opteron based servers
Description: Booting from AlmaLinux 8.5, 8.6, and 9.0 Live media (or Minimal install media), consistently fails to run or install operating systems.
Tags:
Steps To Reproduce: Using an Opteron 2216 based server (SunFire X4200) with LSI SAS1064-IR RAID controller, OR an Opteron 880 based server (Tyan S4882) with SiI-3114 SATA RAID controller, booting Live media fails to run or install for either server.
Additional Information: Both versions of AlmaLinux 8.5 and 8.6 will drop the attempted installation into "dracut" environment prompt. From there, I was able to copy (and include) the "rdsosreport.txt" files from each attempt, for each server. The AlmaLinux 9.0 Live install doesn't even get to the dracut environment, it just locks up at a "kernel panic" event. At this point, it would be nice to try and get the AlmaLinux 8.x issues resolved first, it may provide insight into the 9.0 issues.

For both server installs of version 8.6, both have a suspicious log message: "localhost kernel: random: 7 urandom warning(s) missed due to ratelimiting" in the respective rdsosreport.txt files. This warning appears just prior to dracut timeout messages. Doing internet searches, there is some mention that these messages occur prior to installing hard drive controller drivers; but, was unable to find a definitive fix for said issue. Attached are rdsosreport_*.txt files for each attempt at installs, along with some POST screen photos.

I can install Ubuntu 20.04 onto these servers, but my organization is standardizing on the use of AlmaLinux.

Server specs:
1) SunFire X4200 M2, Dual Opteron 2216 2.4Ghz CPU's, 4Gb RAM, LSI SAS1064-IR RAID controller configured with RAID-1E and 4 x 600Gb SAS drives.
2) Tyan S4882 Dual Opteron 880 2.4Ghz CPU's, 16Gb RAM, SiI 3114 SATA RAID controller with 1 x 256Gb SATA SSD.

Attached Files: rdsosreport_Alma86_SunFire_X4200_Opteron2216.txt (97,664 bytes) 2022-07-12 05:05
https://bugs.almalinux.org/file_download.php?file_id=167&type=bug
rdsosreport_Alma85_SunFire_X4200_Opteron2216.txt (99,770 bytes) 2022-07-12 05:05
https://bugs.almalinux.org/file_download.php?file_id=168&type=bug
SunFire_X4200_Opteron2216_LSI_SAS1064.jpg (82,492 bytes) 2022-07-12 05:05
https://bugs.almalinux.org/file_download.php?file_id=169&type=bug
SunFire_X4200_Opteron2216_POST01.jpg (132,472 bytes) 2022-07-12 05:05
https://bugs.almalinux.org/file_download.php?file_id=170&type=bug
SunFire_X4200_Opteron2216_POST02.jpg (144,887 bytes) 2022-07-12 05:05
https://bugs.almalinux.org/file_download.php?file_id=171&type=bug
rdsosreport_Alma86_Tyan_S4882_Opteron880.txt (90,755 bytes) 2022-07-12 05:07
https://bugs.almalinux.org/file_download.php?file_id=172&type=bug
rdsosreport_Alma85_Tyan_S4882_Opteron880.txt (97,727 bytes) 2022-07-12 05:07
https://bugs.almalinux.org/file_download.php?file_id=173&type=bug
Tyan_S4882_Opteron880_POST01.jpg (119,375 bytes) 2022-07-12 16:52
https://bugs.almalinux.org/file_download.php?file_id=174&type=bug
Tyan_S4882_Opteron880_SiI3114.jpg (84,793 bytes) 2022-07-12 16:52
https://bugs.almalinux.org/file_download.php?file_id=175&type=bug
Alma90_Kernel_Panic.jpg (177,687 bytes) 2022-07-12 17:08
https://bugs.almalinux.org/file_download.php?file_id=176&type=bug
Notes
(0000638)
AstroTJP   
2022-07-12 05:05   
The following rdsosreport_*.txt files are from the attempts to install AlmaLinux 8.5 and 8.6 onto SunFire X4200 server. Screen shots of POST screens are attached as well.
(0000639)
AstroTJP   
2022-07-12 05:07   
The following rdsosreport_*.txt files are from the attempts to install AlmaLinux 8.5 and 8.6 onto Tyan S4882 (Opteron 880) server. Screen shots of POST screens are attached as well.
(0000640)
AstroTJP   
2022-07-12 16:52   
Tyan S4882 screen shots that didn't make it into previous note...
(0000641)
AstroTJP   
2022-07-12 17:08   
Attached screen shot of kernel panic message, at point of lockup, when attempting to install AlmaLinux 9.0 (happens with both of the aforementioned servers)...


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
141 [AlmaLinux-8] -OTHER minor have not tried 2021-11-03 00:14 2022-07-08 14:16
Reporter: mjkelly Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: ELevate install: conflicts in /usr/lib/python3.6/site-packages/__pycache__
Description: I just did a CentOS 7 to AlmaLinux 8.4 conversion with ELevate (https://wiki.almalinux.org/elevate/ELevate-quickstart-guide.html). Following the quickstart guide, I ran `sudo leapp preupgrade` until the report showed no issues that inhibited an upgrade. I only had to make 2 of the 3 modifications listed in the quickstart guide:

1. Updating /etc/ssh/sshd_config (I explicitly disabled root login via ssh rather than enabling it)
2. sudo leapp answer --section remove_pam_pkcs11_module_check.confirm=True

When running `sudo leapp upgrade`, I got the following error from dnf:
```
2021-11-01 20:33:54.907 DEBUG PID: 41194 leapp.workflow.Download.dnf_package_download: file /usr/lib/python3.6/site-packages/__pycache__/six.cpython-36.opt-1.pyc from install of python3-six-1.11.0-8.el8.noarch conflicts with file from package python36-six-1.14.0-3.el7.noarch
```

My workaround was to remove python36 from the CentOS 7 system (and any packages that depended on it). The upgrade worked after that. There were no remediation steps after the upgrade, because my resulting Alma 8.4 came with Python 3.6 (as a side effect of the upgrade, perhaps?) My previously-installed packages that depended on python3 were from EPEL, so are unsupported in the new installation.

Let me know if there's more info I can collect, or if I should attempt a clean repro on a fresh CentOS 7 VM. Thank you!
Tags:
Steps To Reproduce: [I haven't tried this myself; this is a synthesis of what I believe happened based on looking at logs files]

1. Install `python36-six-1.14.0-3.el7.noarch` on a CentOS 7 system
2. Run `leapp upgrade`
3. It should fail with with the file conflict error mentioned above
Additional Information: I uploaded full logs (all archive tarballs from /var/log/leapp/archive) here: https://scratch.michaelkelly.org.s3-website-us-east-1.amazonaws.com/leapp-logs.tar.bz2. I collected all the logs in a single tarball. Each run is in a sequentially-numbered directory.

logs.5/var/log/leapp/leapp-upgrade.log is probably the best place to start -- that contains the error message mentioned above.
Attached Files:
Notes
(0000372)
mjkelly   
2021-11-03 03:28   
I was able to repro this with a fresh CentOS 7 install. The key is having python36 modules installed via EPEL. I'm not sure if upgrading a CentOS 7 host with EPEL packages installed is supported, but are the more specific repro steps either way!

1. Start from a fresh CentOS 7.9.2009 release
2. (install python 3.6 package from EPEL): yum update; yum install epel-release; install python36-six
3. yum install leapp-upgrade leapp-data-centos
4. (get CentOS set up for ELevate upgrade, from quickstart guide): rmmod pata_acpi; echo PermitRootLogin no | sudo tee -a /etc/ssh/sshd_config; leapp answer --section remove_pam_pkcs11_module_check.confirm=True
5. leapp preupgrade
6. leapp upgrade
 
Step 5 should show the system is ready for an upgrade, and step 6 should fail with an error like this:

Error: Transaction test error:
  file /usr/lib/python3.6/site-packages/__pycache__/six.cpython-36.opt-1.pyc from install of python3-six-1
.11.0-8.el8.noarch conflicts with file from package python36-six-1.14.0-3.el7.noarch
  file /usr/lib/python3.6/site-packages/__pycache__/six.cpython-36.pyc from install of python3-six-1.11.0-
8.el8.noarch conflicts with file from package python36-six-1.14.0-3.el7.noarch
  file /usr/lib/python3.6/site-packages/six.py from install of python3-six-1.11.0-8.el8.noarch conflicts w
ith file from package python36-six-1.14.0-3.el7.noarch

I hope this helps! Thanks.
(0000374)
alukoshko   
2021-11-08 08:57   
Hi.
EPEL is not supported yet and it's not easy because we have to add many actions for EPEL packages to https://pes.almalinux.org.
For example python36-six should be replaced with python3-six during upgrade and we have to add action for this.
And the same for every package that have it's name changed in EPEL 8.
Please stay tuned. Or even better, join us.
(0000393)
mjkelly   
2021-11-16 17:32   
Gotcha! That makes sense. Thanks for the info.

I can't promise any contributions in the near future, but if I have some time I'll learn about Package Evolution Service.

Thanks for all your work, it's incredible that this works under any circumstances. :)
(0000401)
tjyang   
2021-11-17 13:03   
I want to express my kudos for elevate project members for bringing elevate to centos7. Although it is not as automated as it can be but I have use elevate to migrate a few of my centos 7 VMWare test/non-prod VMs with saltstack formula to get rid of manual commands. I will try to find way to see, from sysadmin perspective, if I can contribute after my RTFM of leapp/elevate.
(0000634)
ParadoxGuitarist   
2022-07-08 14:16   
I just ran into this and it looked like there was just a form that needed to be filled out for each of the conflicting packages? I can totally help out with that! (if it's more complicated, is there any other documentation that's needed for contribution? ) Thanks!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
80 [AlmaLinux-8] lorax crash always 2021-05-20 13:45 2022-07-08 10:04
Reporter: tiny Platform: X86_64  
Assigned To: alukoshko OS: Alma Linux  
Priority: normal OS Version: 8.4  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: OSbuild Crashes on startup
Description: I am not able to start the osbuild composer service on alma linux 8.4 or run any composer-cli command without it immediately crashing. I installed composer using redhat's documentation listed below. The issue does not exist inside of centos stream using the same instructions. both running 2cpu 4gb KVM virtual machines inside of proxmox

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/composing_a_customized_rhel_system_image/installing-composer_composing-a-customized-rhel-system-image
Tags:
Steps To Reproduce: 1. install almalinux 8.4
2. run sudo dnf install osbuild-composer composer-cli cockpit-composer bash-completion
3. sudo systemctl enable --now osbuild-composer.socket
4. run composer-cli blueprint list or try and start the image builder service in cockpit
Additional Information:
Attached Files: composer-bug.txt (6,272 bytes) 2021-05-21 02:20
https://bugs.almalinux.org/file_download.php?file_id=84&type=bug
os-build-error.txt (96,803 bytes) 2022-07-07 15:01
https://bugs.almalinux.org/file_download.php?file_id=165&type=bug
Notes
(0000206)
tiny   
2021-05-21 02:20   
Here is the stack trace I am gettng from sudo composer-cli blueprint list
(0000207)
alukoshko   
2021-05-21 18:09   
Hello and thanks.
Yes I can confirm it.
At the moment osbuild-composer code is only supports RHEL and CentOS and patch to add another distributions would not be trivial.
osbuild-composer developers know about this problem and going to implement support for RHEL based distros later.
(0000208)
tiny   
2021-05-21 23:13   
Linked below is the os-build issue from their GitHub
https://github.com/osbuild/osbuild/issues/644
(0000601)
alukoshko   
2022-06-21 14:53   
Hello.
We have a patched version that now looks working (at least "Steps To Reproduce"):
https://build.almalinux.org/pulp/content/builds/AlmaLinux-8-x86_64-2913-br/

Could you please test it before we'll release it for all?
(0000619)
tiny   
2022-06-29 21:16   
I have confirmed via following steps
1. create an amlalinux vm in cockpit on fedora
2. download all rpms from https://build.almalinux.org/pulp/content/builds/AlmaLinux-8-x86_64-2913-br/Packages/o/
3. ran sudo dnf install *.rpm
4. ran sudo systemctl enable --now cockpit.socket
5. ran sudo composer-cli blueprints list and returned an empty out as expected

I will test creating an image with cockpit-composer later today
(0000620)
tiny   
2022-06-29 22:35   
I was able to create blueprint in the cockpit-composer web interface but I was not able to build a qcow2 image and it failed with the following error

Pipeline build
Stage org.osbuild.rpm
Output:
bwrap: execvp /run/osbuild/lib/runners/org.osbuild.almalinux86: No such file or directory
(0000621)
tiny   
2022-06-29 22:43   
the output above is identical to the logs generated from creating the image on the cli and extracting them from the tar ball
(0000626)
eabdullin   
2022-07-05 10:28   
Hello.
We patched osbuild for almalinux. Could you please test it with previuos osbuild-composer build?
https://build.almalinux.org/pulp/content/builds/AlmaLinux-8-x86_64-3331-br/
(0000629)
tiny   
2022-07-07 13:12   
I downloaded and installed the additional packages you posted using the same process as in comment 619 and rebuilt the image from cockpit and it generated a qcow2 file and I was able to import and run it.
(0000630)
tiny   
2022-07-07 15:01   
this appears to affect alma9 as well let me know if I need to submit a separate bug report. I have also attached the output of journalctl -u osbuild-composer.service this was created using the same steps to reproduce in the inital bug report.
(0000631)
eabdullin   
2022-07-08 05:30   
Not necessary to create a separate bug report.
Thank you for your help!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
278 [AlmaLinux-8] php major always 2022-07-06 21:27 2022-07-08 10:03
Reporter: ap8 Platform: x86_64  
Assigned To: lkhn OS: AlmaLinux  
Priority: high OS Version: 8.6  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: After enabling the dnf modules nginx:1.20 and php:7.4, a conflict arises which says that php:7.4 requires nginx:1.14
Description: The exact error message is:

```
Modular dependency problems:

 Problem: module php:7.4:8060020220701053012:a4870ff1.x86_64 requires module(nginx:1.14), but none of the providers can be installed
  - module nginx:1.14:8030020210419100506:f8e95b4e.x86_64 conflicts with module(nginx:1.20) provided by nginx:1.20:8060020220421131139:9edba152.x86_64
  - module nginx:1.20:8060020220421131139:9edba152.x86_64 conflicts with module(nginx:1.14) provided by nginx:1.14:8030020210419100506:f8e95b4e.x86_64
  - conflicting requests
```

The issue does NOT seem to affect RHEL 8.6 nor RockyLinux 8.6, while it occurs in AlmaLinux 8.6.
I noticed this for the first time on July 3rd (on July 2nd I had applied several updates to the OS).
Tags:
Steps To Reproduce: In a clean VM/container:

* `dnf module switch-to nginx:1.20`
* `dnf module switch-to php:7.4`
Additional Information:
Attached Files:
Notes
(0000632)
eabdullin   
2022-07-08 05:36   
Thank you for the report. The issue is fixed!
(0000633)
ap8   
2022-07-08 09:57   
Thank you very much for fixing it so promptly, all my servers were patched successfully this morning. Cheers!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
234 [AlmaLinux-8] -OTHER major always 2022-05-12 15:25 2022-07-06 10:34
Reporter: Eden Platform: AWS  
Assigned To: lkhn OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: AWS Systems Manager integration not complete.
Description: From here you can see that the SSM Agent has been included in AlmaLinux AMIs https://almalinux.org/blog/almalinux-cloud-images-updates-september-2021/

I've tried it , and since it is not officially supported by AWS yet, unlike RockyLinux, there are a few major issues.
https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-manual-agent-install.html

The OS is not detected. See excerpt of /var/log/amazon/ssm/amazon-ssm-agent.log

2022-05-12 14:46:19 INFO [ssm-agent-worker] [StartupProcessor] Write to serial port: Amazon SSM Agent v3.1.338.0 is running
2022-05-12 14:46:19 INFO [ssm-agent-worker] [StartupProcessor] Write to serial port: OsProductName: NotAvailable
2022-05-12 14:46:19 INFO [ssm-agent-worker] [StartupProcessor] Write to serial port: OsVersion: NotAvailable

And because of that, Systems Manager operations that require knowing which Operating System is running, will fail.

Failed with run commands:
AWS-RunPatchBaseline
AWS-UpdateSSMAgent

Request to liaise with AWS to make it officially supported.
Tags: AlmaLinux, almalinux8, aws, cloud, incomplete
Steps To Reproduce: 1 - Launch AlmaLinux instance with appropriate Instance Profile role for Systems Manager.
2 - Wait for it to fully boot.
3 - Use Systems Manager Run Command to run these documents against the instance: AWS-RunPatchBaseline AWS-UpdateSSMAgent
Additional Information: Inventory works but is not able to identify OS.
Features that do not require identifying the OS work, like Session Manager and AWS-RunShellScript.
Attached Files:
Notes
(0000628)
lkhn   
2022-07-06 10:34   
Hi Eden,

Thanks for the help in making the cloud integration of AlmaLinux OS better.

You can track the status of AlmaLinux OS support from this Pull Request: https://github.com/aws/amazon-ssm-agent/pull/448


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
262 [AlmaLinux-8] rpm crash random 2022-06-07 09:09 2022-07-06 02:04
Reporter: gabor567 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: recurring issue: base and appstream repositories cannot be synchronized using pulp-rpm
Description: I use pulp-rpm (v3) to synchronize the base and appstream repos from http://repo.almalinux.org/almalinux/8/BaseOS/x86_64/os/ and https://repo.almalinux.org/almalinux/8/AppStream/x86_64/os/ respectively.

I try to run the sync script once a week. Sometimes it works, sometimes it fails with the following error:
"Incoming and existing advisories have the same id and timestamp but different and intersecting package lists, and neither package list is a proper subset of the other. At least one of the advisories is wrong. To allow this behavior, set ALLOW_AUTOMATIC_UNSAFE_ADVISORY_CONFLICT_RESOLUTION = True (q.v.) in your configuration. Advisory id: ALSA-2019:2720"

(This advisory ID may not always be the same.)
I have learnt that deleting and recreating the pulp repository "solves" the problem but I lose the previous versions - keeping these would be one of the purposes of pulp.
Tags: almalinux8, appstream
Steps To Reproduce: - create repository and remote in pulp-rpm (like this: https://docs.pulpproject.org/pulp_rpm/workflows/create_sync_publish.html )
- synchronize the repository with the remote once a week
- sometimes it works, sometimes it fails. I failed at least 5 times in the last 12 months. It failed twice in the last month.
Additional Information: I have several other (non-AlmaLinux) repositories in pulp and they do work.
I only have seen this type of error with AlmaLinux repos.
Attached Files:
Notes
(0000627)
dralley   
2022-07-06 02:02   
I work on Pulp and a few other users have complained about this as well, both in the past and recently with this specific advisory (hence why I'm here).

This warning gets triggered when the advisory in the remote repo was changed at least once *after* being pushed but without changing the updated date metadata, and doing some weird things with the package list that make it difficult to decide what to make of it. I'm not sure what the specifics are in this case, however.

If someone has access to figure out what changed between the first and second revision of that advisory, I can try to provide some guidance on what ought to be done on your side (or if it seems reasonable, try to relax the restriction a bit on our side).


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
259 [AlmaLinux-8] dnf minor sometimes 2022-06-04 23:47 2022-07-02 12:00
Reporter: imtek Platform: x86_64  
Assigned To: alukoshko OS: 8  
Priority: normal OS Version: 8.6  
Status: confirmed Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Unable to update listed dnf updates on a lot of servers
Description: DNF lists that there are updates available but they are not able to be installed:
ALBA-2020:1673 bugfix perl-IO-Socket-SSL-2.066-4.module_el8.6.0+2851+6d072db5.noarch
FEDORA-EPEL-2019-6adf1e0ef3 newpackage python3-psutil-5.6.3-5.el8.x86_64

We tried to solve this with updating all bugfix/security/enhancement package and reboot server(s) but they keep getting listed. This only happens on AlmaLinux not on CloudLinux for instance or related projects.

Release:
AlmaLinux release 8.6 (Sky Tiger)

Kernel:
4.18.0-372.9.1.el8.x86_64 #1 SMP Tue May 10 08:57:35 EDT 2022 x86_64 x86_64
Tags: dnf, updates
Steps To Reproduce: dnf updateinfo list
dnf upgrade --security --bugfix --enhancement --newpackage -y
Additional Information:
Attached Files:
Notes
(0000625)
imtek   
2022-07-02 12:00   
Are there any updates regarding this issue?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
276 [AlmaLinux-8] kernel minor always 2022-07-01 14:45 2022-07-01 14:45
Reporter: solidstate Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Raspberry Pi 4 Bluetooth Radio not functional on pre-built almalinux-8 image.
Description: Bluetooth radio is not recognized when using pre-built almalinux-8 image on raspberry pi 4, built 20220618.
Tags:
Steps To Reproduce: Load relevant kernel modules and attempt any operation involving the Bluetooth radio, the radio is not recognized.

[root@pi ~]# modprobe bluetooth
[root@pi ~]# modprobe brcmfmac
[root@pi ~]# rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
[root@pi ~]#
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
275 [AlmaLinux-8] kernel major always 2022-07-01 09:31 2022-07-01 09:31
Reporter: dufgrinder Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Screen Freeze - Driver Nouveau crahes
Description: When Using AlmaLinux with XFCE Desktop (X11 Server), after a while, the screen freezes.
The kernel is not crashed, but journalctl report errors in 'nouveau' module.
Data retrieved via ssh


Graphic Card: 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1)
See journalctl and dmesg dumps
Tags:
Steps To Reproduce: Just work either with firefox, thunderbird, today I provoque it with vlc looping on a short video
Additional Information:
Attached Files: dmesg.txt (78,679 bytes) 2022-07-01 09:31
https://bugs.almalinux.org/file_download.php?file_id=163&type=bug
journalctl.txt (171,982 bytes) 2022-07-01 09:31
https://bugs.almalinux.org/file_download.php?file_id=164&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
163 [AlmaLinux-8] kernel block always 2021-12-07 11:43 2022-06-27 13:16
Reporter: aklymov Platform:  
Assigned To: alukoshko OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Unable to install 8.5 on Intel motherboards S5500, SC2400, SC2600 - problem initializing video
Description: Hello,
We are having problem installing Almalinux 8.5 on Intel motherboards S5500, SC2400, SC2600, right from the start - boot iso does not initialize video. When installing from Almalinux 8.3 iso there is no such problem.
After selecting "Install" from GRUB menu screen goes dark.
Tags: intel, kernel, setup, video
Steps To Reproduce: Boot Almalinux 8.5 installation iso on Intel motherboard S5500, SC2400, SC2600CW, after selecting "Install" from GRUB menu, screen goes blank.
Additional Information:
Attached Files:
Notes
(0000449)
alukoshko   
2021-12-13 14:10   
Hello. Could you please try CentOS 8.5 on the same system?
We have to find out if this is upstream regression or AlmaLinux specific bug.
(0000452)
aklymov   
2021-12-13 17:42   
We tried RockyLinux 8.5 and RHEL8.5 - same symptoms, problem is most likely in kernel configuration difference between 4.18-240 (which was used in 8.3 release and 4.18-348 (8.5 correspondingly). The paradox is, that to report problem upstream we have to have paid subscription.
(0000453)
alukoshko   
2021-12-13 17:48   
Then the best option is to check it on CentOS Stream 8 iso:
http://mirror.centos.org/centos/8-stream/isos/

If it works then most likely it will work with 8.6.
If not then you should report to CentOS Stream bugzilla https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%208&version=CentOS%20Stream

BTW do you need graphics after install?
You can either install in text mode or start with AlmaLinux 8.3 and then upgrade it to 8.5.
(0000454)
toracat   
2021-12-13 19:48   
@aklymov

You can report RHEL-related problems upstream (Red Hat) without paid subscription. Just create an account at bugzilla.redhat.com and file a report.
(0000455)
aklymov   
2021-12-15 18:41   
Thank you, toracat, I will do that.
(0000617)
alukoshko   
2022-06-27 13:16   
aklymov could you confirm that video works on 8.6?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
269 [AlmaLinux-8] systemd minor always 2022-06-22 06:08 2022-06-22 19:46
Reporter: bogen85 Platform: aarch64  
Assigned To: OS: Almalinux  
Priority: normal OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: bootctl (systemd-boot) inconsistency
Description: This could be a RHEL issue?

AlmaLinux 8 has bootctl on aarch64, AlmaLinux 9 does not.

AlmaLinux 9 might not have it due to this:
2021-10-12 - systemd maintenance team <systemd-maint@redhat.com> - 249-8
- boot: don't build bootctl when -Dgnu-efi=false is set (#2003130)

Both have bootctl on x86_64.

Anyways, this is twofold:
1) AlmaLinux 9 is missing bootctl on aarch64
2) AlmaLinux 8 bootctl installs an efi loader that crashes parallels on the Apple M1.
Tags:
Steps To Reproduce: On an Apple M1 macbook with the parallels
$ prlctl --version
prlctl version 17.1.4 (51567)

Create partition at least 64MiB as type EF00

format it as fat32: mkfs.vfat -F32 -n EFI-BOOT /dev/sdXY
mount it on /boot: mount /dev/sdXY /boot
install systemd-boot efi loader: bootctl install
reboot

results (on aarch64)
on Fedora 34: systemd-boot menu is present, can go into firmware
on Fedora 35: systemd-boot menu is present, can go into firmware
on Fedora 36: systemd-boot menu is present, can go into firmware
AlmaLinux 8: parallels crashes and wants to send a bug report
AlmaLinux 9: could not test as bootctl is missing

results (on x86_64)
on Fedora 35: systemd-boot menu is present, can go into firmware
on Fedora 36: systemd-boot menu is present, can go into firmware
AlmaLinux 8: systemd-boot menu is present, can go into firmware
AlmaLinux 9: systemd-boot menu is present, can go into firmware







Additional Information:
Attached Files:
Notes
(0000602)
bogen85   
2022-06-22 06:11   
ArchLinux aarch64 on the Apple M1 macbook in parallels passes the above test.

$ bootctl --version
systemd 251 (251.2-1-arch)
(0000603)
bogen85   
2022-06-22 06:20   
on each of the above tests I did sync and unmount /boot before rebooting.
(0000604)
bogen85   
2022-06-22 12:33   
secure boot is not enabled for this
(0000605)
bogen85   
2022-06-22 13:31   
fedora 34 bootctl (systemd) version 248 (v248.10-1.fc34)
fedora 35 bootctl (systemd) version 249 (v249.12-5.fc35)
fedora 36 bootctl (systemd) version 250 (v250.7-1.fc36)

almalinux 8 bootctl (systemd) version 239 (v239-58.el8)

---------

For Fedora 35-36 I used https://getfedora.org/en/workstation/download/ for each release

For AlmaLinux (x86_64 and aarch64) I used arch-chroot from arch-install-scripts on the Fedora 36 livecd and the 8 or 9 AlmaLinux default rootfs from https://us.lxd.images.canonical.com/images/almalinux/
(refreshed and upgraded before proceeding, but those are already up to date when downloaded fresh)
(0000606)
bogen85   
2022-06-22 13:44   
oh, I see bootctl is on AlmaLinux 9 aarch64

$ dnf provides bootctl
Last metadata expiration check: 18:19:30 ago on Tue 21 Jun 2022 02:20:16 PM CDT.
systemd-boot-250.3-1.el9.aarch64 : Simple UEFI boot manager to execute configured EFI images
Repo : epel
Matched from:
Filename : /usr/bin/bootctl

I will try it.
(0000607)
bogen85   
2022-06-22 13:58   
On AlmaLinux 9 x86_64 and aarch64:
$ dnf provides bootctl
systemd-boot-250.3-1.el9.x86_64 : Simple UEFI boot manager to execute configured EFI images
Repo : @System
Matched from:
Filename : /usr/bin/bootctl

systemd-boot-250.3-1.el9.x86_64 : Simple UEFI boot manager to execute configured EFI images
Repo : epel
Matched from:
Filename : /usr/bin/bootctl

All my AlmaLinux installs (8 and 9) on X86_64 use systemd-boot. They work fine.

-----------
bootctl on AlmaLinux9 aarch64 works fine.
(0000608)
bogen85   
2022-06-22 14:03   
So, the only inconsistency is that the systemd-boot on AlmaLinux 8 is older (239) than the bootctl on all the other releases I tried (248, 249, 250) and while 239 works on x86_64, it does not work on Apple aarch64 M1 in parallels.

systemd-boot 248, 249, 250 all work on x86_64 (non parallels, not on an Apple machine) and on Apple aarch64 M1 (parallels)
(0000609)
bogen85   
2022-06-22 14:27   
My AlmaLinux 8 and 9 installs on x86_64 are all custom and semi-automated via scripts.

I guess I missed noting the bootctl coming from EPEL 9 for AlmaLinux 9 as EPEL was already enabled before that, and when bootctl was missing I must have done a "dnf provides boot" and adding systemd-boot to an earlier package list.

Oh well.

So the only issue here is systemd-boot not working with AlmaLinux 8 on aarch64 Apple M1 in parallels, but working everywhere else in the above scenarios.
(0000610)
bogen85   
2022-06-22 15:14   
Looks like centos-8-stream bootctl is the same version as that in AlmaLinux 8.

I will try with centos-8-stream as well...

[root@rootfs-centos-8-stream ~]# bootctl --version
systemd 239 (239-58.el8)
(0000611)
bogen85   
2022-06-22 19:46   
Also crashes with centos-8 stream the same way it does with AlmaLinux 8

bootctl --version
systemd 239 (239-58.el8)

So this is issue is not specific to AlmaLinux.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
184 [AlmaLinux-8] osbuild-composer crash always 2022-02-08 05:53 2022-06-21 14:53
Reporter: Naranthiran Platform: X86_64  
Assigned To: alukoshko OS: Alma Linux  
Priority: urgent OS Version: 8.5  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Failed to start OSBuild Composer
Description: I am not able start the OS build compose. When I try to start osbuild-composer.service its stops immediately.

[root@localhost ~]# systemctl status osbuild-composer.service
● osbuild-composer.service - OSBuild Composer
   Loaded: loaded (/usr/lib/systemd/system/osbuild-composer.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2022-02-08 00:18:43 EST; 32min ago
  Process: 1657 ExecStart=/usr/libexec/osbuild-composer/osbuild-composer (code=exited, status=1/FAILURE)
 Main PID: 1657 (code=exited, status=1/FAILURE)

Feb 08 00:18:43 localhost.localdomain systemd[1]: osbuild-composer.service: Failed with result 'exit-code'.
Feb 08 00:18:43 localhost.localdomain systemd[1]: osbuild-composer.service: Service RestartSec=100ms expired, schedu>
Feb 08 00:18:43 localhost.localdomain systemd[1]: osbuild-composer.service: Scheduled restart job, restart counter i>
Feb 08 00:18:43 localhost.localdomain systemd[1]: Stopped OSBuild Composer.
Feb 08 00:18:43 localhost.localdomain systemd[1]: osbuild-composer.service: Start request repeated too quickly.
Feb 08 00:18:43 localhost.localdomain systemd[1]: osbuild-composer.service: Failed with result 'exit-code'.
Feb 08 00:18:43 localhost.localdomain systemd[1]: Failed to start OSBuild Composer.
Feb 08 00:18:45 localhost.localdomain systemd[1]: osbuild-composer.service: Start request repeated too quickly.
Feb 08 00:18:45 localhost.localdomain systemd[1]: osbuild-composer.service: Failed with result 'exit-code'.
Feb 08 00:18:45 localhost.localdomain systemd[1]: Failed to start OSBuild Composer.
Tags:
Steps To Reproduce: 1. install almalinux 8.4 and updated to 8.5
2. run sudo dnf install osbuild-composer composer-cli cockpit-composer bash-completion
3. sudo systemctl enable --now osbuild-composer.socket
4. run composer-cli blueprint list or try and start the image builder service in cockpit
Additional Information:
Attached Files: osbuild composer.JPG (57,974 bytes) 2022-02-08 05:53
https://bugs.almalinux.org/file_download.php?file_id=115&type=bug
Notes
(0000488)
alukoshko   
2022-02-08 20:39   
Hello. Unfortunately it's an upstream issue.
More details here: https://github.com/osbuild/osbuild-composer/issues/1411#issuecomment-853712989
(0000600)
alukoshko   
2022-06-21 14:53   
Hello.
We have a patched version that now looks working (at least "Steps To Reproduce"):
https://build.almalinux.org/pulp/content/builds/AlmaLinux-8-x86_64-2913-br/

Could you please test it before we'll release it for all?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
266 [AlmaLinux-8] anaconda crash always 2022-06-15 03:01 2022-06-15 15:54
Reporter: ggiesen Platform: x86_64  
Assigned To: OS: AlmaLinux 8  
Priority: high OS Version: 8.6  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Anaconda fails after typing in passphrase for encrypted disk with "TypeError: Argument 1 does not allow None as a value"
Description: Anaconda fails after typing in the passphrase for an encrypted disk, and clicking "Save Passphase". May take happen almost immediately or may take a minute. This happens even before your accept the changes for the disk layout.

Tags:
Steps To Reproduce: Create a VM in VMware Workstation Pro 16.2.1 with the following attributes:

2 GB RAM
1 vCPU
55 GB Disk
1 Network Adapter

Remove Sound Card
Remove Printer

Boot AlmaLinux 8.6 DVD, Configure Networking, Select Time Zone, Disable KDUMP, Enter Root Password.

Select Manual Partitioning, "I want to encrypt my disks" with the following disk layout:

/boot - 1 GiB
/swap - 2 GiB
/root - 20 GiB
/home - 10 GiB
/tmp - 5 GiB
/var - 10 GiB
/var/log - 5 GiB

Click done, and enter encryption passphrase. Click "Accept Passphrase". Within 5-60 seconds, the crash report will appear.
Additional Information: Screenshot and crash report attached
Attached Files: anaconda-2022-06-14-224631.338516-1827.tar.gz (524,095 bytes) 2022-06-15 03:01
https://bugs.almalinux.org/file_download.php?file_id=144&type=bug
anaconda_error.png (90,383 bytes) 2022-06-15 03:01
https://bugs.almalinux.org/file_download.php?file_id=145&type=bug
CentOS 8 64-bit-2022-06-14-23-17-32.png (69,721 bytes) 2022-06-15 03:20
https://bugs.almalinux.org/file_download.php?file_id=146&type=bug
CentOS 8 64-bit-2022-06-14-23-12-27.png (65,909 bytes) 2022-06-15 03:20
https://bugs.almalinux.org/file_download.php?file_id=147&type=bug
CentOS 8 64-bit-2022-06-14-23-13-18.png (43,094 bytes) 2022-06-15 03:20
https://bugs.almalinux.org/file_download.php?file_id=148&type=bug
CentOS 8 64-bit-2022-06-14-23-13-26.png (35,270 bytes) 2022-06-15 03:20
https://bugs.almalinux.org/file_download.php?file_id=149&type=bug
CentOS 8 64-bit-2022-06-14-23-13-39.png (81,221 bytes) 2022-06-15 03:20
https://bugs.almalinux.org/file_download.php?file_id=150&type=bug
CentOS 8 64-bit-2022-06-14-23-13-58.png (129,822 bytes) 2022-06-15 03:20
https://bugs.almalinux.org/file_download.php?file_id=151&type=bug
CentOS 8 64-bit-2022-06-14-23-14-24.png (20,013 bytes) 2022-06-15 15:54
https://bugs.almalinux.org/file_download.php?file_id=152&type=bug
CentOS 8 64-bit-2022-06-14-23-14-36.png (53,423 bytes) 2022-06-15 15:54
https://bugs.almalinux.org/file_download.php?file_id=153&type=bug
CentOS 8 64-bit-2022-06-14-23-15-03.png (47,307 bytes) 2022-06-15 15:54
https://bugs.almalinux.org/file_download.php?file_id=154&type=bug
CentOS 8 64-bit-2022-06-14-23-16-16.png (73,049 bytes) 2022-06-15 15:54
https://bugs.almalinux.org/file_download.php?file_id=155&type=bug
CentOS 8 64-bit-2022-06-14-23-16-41.png (58,301 bytes) 2022-06-15 15:54
https://bugs.almalinux.org/file_download.php?file_id=156&type=bug
CentOS 8 64-bit-2022-06-14-23-17-13.png (81,325 bytes) 2022-06-15 15:54
https://bugs.almalinux.org/file_download.php?file_id=157&type=bug
VM_settings.png (33,936 bytes) 2022-06-15 15:54
https://bugs.almalinux.org/file_download.php?file_id=158&type=bug
Notes
(0000596)
ggiesen   
2022-06-15 03:20   
More screenshots of all settings
(0000597)
ggiesen   
2022-06-15 15:54   
More settings screenshots since Mantis thinks I'm spamming, it won't let me attach them all at once.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
263 [AlmaLinux-8] NetworkManager minor always 2022-06-07 11:47 2022-06-09 09:55
Reporter: OscarCS Platform:  
Assigned To: OS:  
Priority: normal OS Version: 8.6  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: /etc/resolv.conf not correctly updated after sleep
Description: /etc/resolv.conf keeps older dns servers when ethernet is removed after a sleep
Tags: NetworkManager;/etc/resolve.conf;Laptop;sleep
Steps To Reproduce: In a laptop, in a place "X" whit a USB-C ethernet adapter "A" close the laptop and put it to sleep
Go to place Y
open the laptop and recover from sleep
connect a USB-C ethernet adapter "B"
plug the LAN cable to the adapter "B"
now you have a new ethernet connected to internet with a new IP adress
your /etc/resolve.conf has NEW "nameserver" lines, but the old ones are still there in the first positions
as result, name resolution becomes extremely slow since, until timeouts for the old and unreachable dns servers are completed, the new dns servers are not use.

Example of /etc/resolve.conf in place A

; generated by /sbin/dhclient-script
search XXXXXX # Not sure about this line, I don't have access to it
nameserver 192.168.100.1

Example of /etc/resolve.conf in place B:

; generated by /sbin/dhclient-script
search uab.cat
nameserver 192.168.100.1
nameserver 158.109.0.1
nameserver 158.109.0.9



Additional Information:
Attached Files:
Notes
(0000594)
OscarCS   
2022-06-09 09:55   
More information in the topic.
A workaround is:
systemctl restart NetworkManager.service

Below I'm paste the "nmcli" output of the laptop before and after "systemctl restart NetworkManager.service"

The laptop arrived from "home" to the workplace.
The user plugged in the Network Cable
It received the IP address from the workplace dhcp (158.109.XX.XXX)
It received the DNSs from the workplace (158.109.0.1 158.109.0.9) but the old DNS was not removed (192.168.100.1) so every new connection takes ages.
the user restarted NetworkManager.service
then the old DNS was removed (192.168.100.1) and everything works fine.

I can see that hw address from the wifi changed from E6:92:53:5D:FA:B6 to A0:CE:C8:3B:2F:3E after the restart, but after a bit of googling I found that this is perfectly normal.

This was not happening 1 month ago

I hope this helps to understand the problem and fixing it


#################################################
* BEFORE restart NetworkManager.service :
]$ nmcli
enp0s13f0u3u3u1: connected to Wired connection 1
        "Realtek RTL8153"
        ethernet (r8152), A0:CE:C8:3B:2F:3E, hw, mtu 1500
        ip4 default
        inet4 158.109.XX.XXX/23
        route4 158.109.XX.0/23 metric 100
        route4 default via 158.109.XX.1 metric 100
        inet6 fe80::3f70:8c7d:70e8:a48d/64
        route6 fe80::/64 metric 1024

virbr0: connected (externally) to virbr0
        "virbr0"
        bridge, 52:54:00:56:BF:32, sw, mtu 1500
        inet4 192.168.122.1/24
        route4 192.168.122.0/24 metric 0

wlp0s20f3: disconnected
        "Intel Ice Lake-LP PCH CNVi"
        2 connections available
        wifi (iwlwifi), E6:92:53:5D:FA:B6, hw, mtu 1500

p2p-dev-wlp0s20f3: disconnected
        "p2p-dev-wlp0s20f3"
        wifi-p2p, hw

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 192.168.100.1

        servers: 158.109.0.1 158.109.0.9
        domains: uab.cat
        interface: enp0s13f0u3u3u1

* AFTER restart NetworkManager.service :
$ nmcli
enp0s13f0u3u3u1: connected to Wired connection 1
        "Realtek RTL8153"
        ethernet (r8152), A0:CE:C8:3B:2F:3E, hw, mtu 1500
        ip4 default
        inet4 158.109.XX.XXX/23
        route4 default via 158.109.XX.1 metric 100
        route4 158.109.XX.0/23 metric 100
        inet6 fe80::3f70:8c7d:70e8:a48d/64
        route6 fe80::/64 metric 1024

virbr0: connected (externally) to virbr0
        "virbr0"
        bridge, 52:54:00:56:BF:32, sw, mtu 1500
        inet4 192.168.122.1/24
        route4 192.168.122.0/24 metric 0

wlp0s20f3: disconnected
        "Intel Ice Lake-LP PCH CNVi"
        2 connections available
        wifi (iwlwifi), 3E:C9:F9:3E:FE:27, hw, mtu 1500

p2p-dev-wlp0s20f3: disconnected
        "p2p-dev-wlp0s20f3"
        wifi-p2p, hw

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 158.109.0.1 158.109.0.9
        domains: uab.cat
        interface: enp0s13f0u3u3u1


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
252 [AlmaLinux-8] zstd minor always 2022-05-30 12:42 2022-06-07 20:27
Reporter: pawan Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.6  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Unable to decompress qcow.zst file
Description: Unable to decompress the filename.qcow2.zst
It says unsupported format.



Tags: zstd
Steps To Reproduce: Zstd version is
*** zstd command line interface 64-bits v1.4.4, by Yann Collet ***

compressed a file using following command
/usr/bin/zstd -c 'file.qcow2' > 'file.qcow2.zst'

decompressed a file using following command
/usr/bin/zstd -dc 'file.qcow2.zst' > 'file.qcow2'

It gives following error
zstd: file.qcow2.zst: unsupported format

Additional Information: This same steps worked on centos 7.9
without any issue
Attached Files:
Notes
(0000591)
maxihoster   
2022-06-07 20:26   
+1

We can't restore any backup! It's a big issue


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
261 [AlmaLinux-8] -OTHER minor always 2022-06-06 05:55 2022-06-06 06:03
Reporter: beaver6675 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: RFE: Issue a version of AlmaLinux 8 RPM GPG key with SHA256 hash
Description: RHEL 9 does not import RPM GPG keys with SHA1 in particular the AlmaLinux 8 key will not import on AlmaLinux 9.
This means that out-of-the-box you cannot build AlmaLinux 8 RPMs using mock on AlmaLinux 9 (unless gpgcheck is disabled in the mock templates which is not the default).
Tags:
Steps To Reproduce: On Almalinux 9, RHEL 9, CentOS Stream 9

rpm --import RPM-GPG-KEY-AlmaLinux-8
Additional Information: 1. 8 and 9 keys import on AlmaLinux 8
2 8 and 9 keys import on Fedora 36
Attached Files:
Notes
(0000588)
beaver6675   
2022-06-06 06:03   
My bad - it might be due to packages signed with SHA1 and not the key itself.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
258 [AlmaLinux-8] qemu-kvm crash sometimes 2022-06-03 05:25 2022-06-03 06:29
Reporter: jpbennett Platform: Amd Server  
Assigned To: OS: AlmaLinux  
Priority: high OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: qemu-kvm process goes to 100%, VM becomes unresponsive, Triggered by Creating a new VM
Description: Multiple times on two separate servers, qemu-kvm processes have suddenly spiked to 100% usage, and the VMs represented by those processes have become unresponsive to the point of needing force-power-cycled. Multiple VMs enter this state at the exact same moment. In two cases, the VM has recovered after multiple minutes, and in both cases, the VM's system clock was set in the future. It seems that the longer the hang goes on, the further in the future, as one machine thought it was the year 2217. Dates were correct before the hangs.

These servers were running CentOS 8 before converting to Alma, and didn't exhibit this bug on CentOS. The hanging VMs have also all been running Alma 8, though that's likely coincidence, as that's most of my VMs now. There hasn't been anything notable in the host machine's dmesg or logs that I have seen.
Tags: almalinux8, QEMU-KVM
Steps To Reproduce: Run multiple Alma 8 VMs on a server. Migrate an additional VM to that server using a command like virsh migrate --live --persistent --undefinesource --copy-storage-all --verbose Gitlab qemu+ssh://10.10.3.2/system. During the migration process, there is a chance that multiple running VMs will hang in the manner described. Oddly, not every VM hangs, nor does it happen on every migration, but when it occurs, all the affected VMs hang simultaneously.

Additionally, this has been reproduced when generating a new VM on a server. One of the other Alma VMs already running on that server entered this odd failure state.
Additional Information: Both servers are SuperMicro builds, one a AMD Opteron(TM) Processor 6272, the other a AMD EPYC 7302P 16-Core Processor. I'm using the Opteron_G3 processor type to host, as this allows live migration.
Attached Files: log2.png (85,648 bytes) 2022-06-03 06:29
https://bugs.almalinux.org/file_download.php?file_id=142&type=bug
log1.png (80,747 bytes) 2022-06-03 06:29
https://bugs.almalinux.org/file_download.php?file_id=143&type=bug
Notes
(0000585)
jpbennett   
2022-06-03 05:40   
Just reproduced this issue by *rebooting* a running VM, and a sistem VM jumped to 100% CPU and unresponsive.
(0000586)
jpbennett   
2022-06-03 06:29   
Dmesg from a VM as it hit this bug.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
257 [AlmaLinux-8] kernel minor always 2022-06-03 02:36 2022-06-03 02:36
Reporter: davemoniz Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: unchecked MSR access error on migration from Centos 8 to AL8.6
Description: I migrated 2 Centos 8 AWS EC2 servers to AlmaLinux 8.6. One was my production server and one was a fresh Centos 8 install. They both have this error in the log at boot and was not there prior to migration.

unchecked MSR access error: WRMSR to 0x199 (tried to write 0x0000000000000800) at rIP: 0xffffffffae66dcf4 (native_write_msr+0x4/0x20)

Kernel: Linux 4.18.0-372.9.1.el8.x86_64 on x86_64
Tags:
Steps To Reproduce: migrate from centos 8 to AL8.6. Reboot.

run
dmesg | egrep -i 'error|critical|warn'
Additional Information: Thank you.
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
251 [AlmaLinux-8] abrt crash always 2022-05-29 16:15 2022-05-29 16:15
Reporter: brianjmurrell Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: high OS Version: 8.6  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: 'report_AlmaLinuxBugTracker' exited with 1
Description: # abrt-cli report 74eaa4767c18c0d20c76df529377307f46fdcbcc
('report_uReport' completed successfully)
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). [y/N/f/e] n
Analyzing coredump 'coredump'
Coredump references 62 debuginfo files, 31 of them are not installed
Initializing package manager
Setting up repositories
Looking for needed packages in repositories
Can't find packages for 1 debuginfo files
Removing /var/tmp/abrt-tmp-debuginfo-2022-05-29-11:50:06.4131526
Missing debuginfo file: /usr/lib/debug/.build-id/f9/c39c0e3b76999296fde2908a6cc04b0b02559c.debug
Generating backtrace
Backtrace is generated and saved, 51206 bytes
AlmaLinux Bug Tracker User name: brianjmurrell
AlmaLinux Bug Tracker Password:

The report has been updated
Checking for duplicates
Creating a new issue
Can't generate stacktrace description (no crash thread?)
Adding External URL to issue
('report_AlmaLinuxBugTracker' exited with 1)
Tags:
Steps To Reproduce: See above.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
248 [AlmaLinux-8] sssd minor N/A 2022-05-25 19:31 2022-05-26 08:07
Reporter: schlitzered Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: why has alma linux more recent packages then centos stream?
Description: i just noticed that the alma linux 8 repos have more recent packages then centos 8-stream.

example:

http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/sssd-ipa-2.6.2-3.el8.x86_64.rpm
https://mirror.23m.com/almalinux/8.6/BaseOS/x86_64/os/Packages/sssd-ipa-2.6.2-4.el8_6.x86_64.rpm

i am sorry, but i have no access to a RHEL repo, so i could take a look there, but i was under the impression that 8-stream should have more recent packages then RHEL, and therefore also then ALMA linux.

not sure what is going on here, but this sounds strange, at least from the point what centos/redhat folks where telling about the stream stuff
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000580)
toracat   
2022-05-26 08:07   
RHEL 8 has sssd-ipa-2.6.2-4.el8_6. Alma Linux correctly matches it. You may want to file a report upstream at Red Hat.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
246 [AlmaLinux-8] abrt crash always 2022-05-24 11:33 2022-05-24 11:37
Reporter: brianjmurrell Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Failed to create a new issue: 'Error Type: SYSTEM NOTICE,
Description: Trying to use abrt-cli to report a bug results in:

Failed to create a new issue: 'Error Type: SYSTEM NOTICE,
Error Description: Object of class SoapFault could not be converted to int'
('report_AlmaLinuxBugTracker' exited with 1)
Tags:
Steps To Reproduce: # abrt-cli report 0158e1432033188b1a25aed3ef912a396d31033c
('report_uReport' completed successfully)
AlmaLinux Bug Tracker User name: [redacted]
AlmaLinux Bug Tracker Password: [redacted]

The report has been updated
Checking for duplicates
Creating a new issue
Adding External URL to issue
Failed to create a new issue: 'Error Type: SYSTEM NOTICE,
Error Description: Object of class SoapFault could not be converted to int'
('report_AlmaLinuxBugTracker' exited with 1)
Additional Information: Severity and Priority set quite high as this impedes filing of many other bugs.
Attached Files:
Notes
(0000579)
brianjmurrell   
2022-05-24 11:37   
I guess this is only intermittent as I was able to report a different bug with abrt-cli.

I don't see any way to edit the metadata on this ticket though.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
247 [AlmaLinux-8] ipa minor have not tried 2022-05-24 11:35 2022-05-24 11:35
Reporter: brianjmurrell Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 8.4  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash: b2136489ecd201d5a11f78a9dcecd5cec0b19390
URL: https://retrace.almalinux.org/faf/reports/bthash/03b7f2b3f746674128b45c64c4af5b916d81cc48
Summary: [abrt] ipa-client: run(): ipautil.py:599:run:ipapython.ipautil.CalledProcessError: CalledProcessError(Command ...
Description: Description of problem:
Not sure why this happene.

Version-Release number of selected component:
ipa-client-4.9.6-10.module_el8.5.0+2603+92118e57

Truncated backtrace:
#1 run in /usr/lib/python3.6/site-packages/ipapython/ipautil.py:599
0000002 disable_ldap_automount in /usr/lib/python3.6/site-packages/ipaplatform/redhat/tasks.py:776
0000003 uninstall in /usr/lib/python3.6/site-packages/ipaclient/install/ipa_client_automount.py:323
0000004 configure_automount in /usr/lib/python3.6/site-packages/ipaclient/install/ipa_client_automount.py:474
0000005 main in /usr/lib/python3.6/site-packages/ipaclient/install/ipa_client_automount.py:601
0000006 <module> in /usr/sbin/ipa-client-automount:27
Tags:
Steps To Reproduce:
Additional Information: cmdline: /usr/libexec/platform-python -I /usr/sbin/ipa-client-automount --uninstall --debug
crash_function: run
exception_type: ipapython.ipautil.CalledProcessError
executable: /usr/sbin/ipa-client-automount
interpreter: platform-python-3.6.8-39.el8_4.x86_64
kernel: 4.18.0-305.25.1.el8_4.x86_64
pkg_fingerprint: 51D6 647E C21A D6EA
pkg_vendor: AlmaLinux
runlevel: N 3
type: Python3
uid: 0
Attached Files: backtrace (7,408 bytes) 2022-05-24 11:35
https://bugs.almalinux.org/file_download.php?file_id=133&type=bug
cgroup (298 bytes) 2022-05-24 11:35
https://bugs.almalinux.org/file_download.php?file_id=134&type=bug
cpuinfo (1,352 bytes) 2022-05-24 11:35
https://bugs.almalinux.org/file_download.php?file_id=135&type=bug
environ (5,126 bytes) 2022-05-24 11:35
https://bugs.almalinux.org/file_download.php?file_id=136&type=bug
mountinfo (5,382 bytes) 2022-05-24 11:35
https://bugs.almalinux.org/file_download.php?file_id=137&type=bug
namespaces (129 bytes) 2022-05-24 11:35
https://bugs.almalinux.org/file_download.php?file_id=138&type=bug
open_fds (320 bytes) 2022-05-24 11:35
https://bugs.almalinux.org/file_download.php?file_id=139&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
238 [AlmaLinux-8] -OTHER text always 2022-05-17 15:33 2022-05-24 06:06
Reporter: akqroldhaber Platform: x68_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.6  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: RH Satellite 6 - Sync AlmaLinux 8 Appstream Repo "https://repo.almalinux.org/almalinux/8/AppStream/x86_64/os/" fails
Description: RH Satellite 6 - Sync AlmaLinux 8 Appstream Repo "https://repo.almalinux.org/almalinux/8/AppStream/x86_64/os/" fails with
"PLP0000: Importer indicated a failed response".

Sync Upstream https://repo.almalinux.org/almalinux/8.6/AppStream/ fails with "RPM1004: Error retrieving metadata: Not Found"
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000568)
Hitamashi   
2022-05-20 07:57   
Similar issue found on katello
Current version:
pulp-server-2.21.5-1.el7.noarch
katello-3.18.4-1.el7.noarch
foreman-2.3.5-1.el7.noarch

---
Output katello task:
{"pulp_tasks"=>
  [{"exception"=>nil,
    "task_type"=>"pulp.server.managers.repo.sync.sync",
    "_href"=>"/pulp/api/v2/tasks/de72077f-561c-4ff8-b6cf-ad47b90d6c34/",
    "task_id"=>"de72077f-561c-4ff8-b6cf-ad47b90d6c34",
    "tags"=>
     ["pulp:repository:f2ba1795-07bc-432d-9d87-95c9e5333310",
      "pulp:action:sync"],
    "finish_time"=>"2022-05-19T23:22:42Z",
    "_ns"=>"task_status",
    "start_time"=>"2022-05-19T23:21:08Z",
    "traceback"=>
     "Traceback (most recent call last):\n" +
     " File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 367, in trace_task\n" +
     " R = retval = fun(*args, **kwargs)\n" +
     " File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 688, in __call__\n" +
     " return super(Task, self).__call__(*args, **kwargs)\n" +
     " File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 110, in __call__\n" +
     " return super(PulpTask, self).__call__(*args, **kwargs)\n" +
     " File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 622, in __protected_call__\n" +
     " return self.run(*args, **kwargs)\n" +
     " File \"/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py\", line 860, in sync\n" +
     " raise pulp_exceptions.PulpExecutionException(_('Importer indicated a failed response'))\n" +
     "PulpExecutionException: Importer indicated a failed response\n",
    "spawned_tasks"=>[],
    "progress_report"=>
     {"yum_importer"=>
       {"content"=>
         {"items_total"=>0,
          "state"=>"FINISHED",
          "error_details"=>[],
          "details"=>
           {"rpm_total"=>0, "rpm_done"=>0, "drpm_total"=>0, "drpm_done"=>0},
          "size_total"=>0,
          "size_left"=>0,
          "items_left"=>0},
        "comps"=>{"state"=>"NOT_STARTED"},
        "purge_duplicates"=>{"state"=>"NOT_STARTED"},
        "distribution"=>
         {"items_total"=>0,
          "state"=>"FINISHED",
          "error_details"=>[],
          "items_left"=>0},
        "modules"=>{"state"=>"FINISHED"},
        "errata"=>{"state"=>"FAILED", "error"=>"'arch'"},
        "metadata"=>{"state"=>"FINISHED"}}},
    "queue"=>"reserved_resource_worker-0@katello.ipa.pay-nxt.com.dq2",
    "state"=>"error",
    "worker_name"=>"reserved_resource_worker-0@katello.ipa.pay-nxt.com",
    "result"=>nil,
    "error"=>
     {"code"=>"PLP0000",
      "data"=>{},
      "description"=>"Importer indicated a failed response",
      "sub_errors"=>[]},
    "_id"=>{"$oid"=>"6286cc4234e7113fe908e1d0"},
    "id"=>"6286cc4234e7113fe908e1d0"}],
 "contents_changed"=>true,
 "poll_attempts"=>{"total"=>100, "failed"=>1}}
---

---
Log generated by pulp when katello task failed:
2022-05-20T04:24:55.689073+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:INFO: [fb39f8d5] Generating metadata databases.
2022-05-20T04:25:01.582925+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:INFO: [fb39f8d5] Determining which units need to be downloaded.
2022-05-20T04:25:21.044596+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:INFO: [fb39f8d5] Downloading 0 RPMs.
2022-05-20T04:25:25.041468+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.repomd.alternate:INFO: [fb39f8d5] The content container reported: {'downloads': {}, 'total_sou
rces': 0} for base URL: https://repo.almalinux.org/almalinux/8/PowerTools/x86_64/os/
2022-05-20T04:25:25.044808+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:INFO: [fb39f8d5] Downloading additional units.
2022-05-20T04:25:25.170243+00:00 myserver pulp: py.warnings:WARNING: (2485-60864) /usr/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py:852: InsecureR
equestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
2022-05-20T04:25:25.170424+00:00 myserver pulp: py.warnings:WARNING: (2485-60864) InsecureRequestWarning)
2022-05-20T04:25:25.170606+00:00 myserver pulp: py.warnings:WARNING: (2485-60864)
2022-05-20T04:25:25.201472+00:00 myserver pulp: nectar.downloaders.threaded:INFO: Download succeeded: https://repo.almalinux.org/almalinux/8/PowerTools/x86_64/os/.treeinfo.
2022-05-20T04:25:26.194570+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.parse.treeinfo:INFO: [fb39f8d5] upstream distribution unchanged and force_full not set; skippi
ng
2022-05-20T04:25:26.921826+00:00 myserver pulp: kombu.transport.qpid:INFO: Connected to qpid with SASL mechanism ANONYMOUS
2022-05-20T04:25:27.253469+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) 'arch'
2022-05-20T04:25:27.253675+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) Traceback (most recent call last):
2022-05-20T04:25:27.253870+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/
importers/yum/sync.py", line 316, in run
2022-05-20T04:25:27.254092+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) self.get_errata(metadata_files)
2022-05-20T04:25:27.254231+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/
importers/yum/sync.py", line 924, in get_errata
2022-05-20T04:25:27.254346+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) updateinfo.process_package_element, additive_type=True
)
2022-05-20T04:25:27.254459+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/
importers/yum/sync.py", line 1006, in save_fileless_units
2022-05-20T04:25:27.254585+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) for model in package_info_generator:
2022-05-20T04:25:27.254752+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/
importers/yum/repomd/packages.py", line 64, in package_list_generator
2022-05-20T04:25:27.254900+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) package_info = process_func(element)
2022-05-20T04:25:27.255022+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/
importers/yum/repomd/updateinfo.py", line 33, in process_package_element
2022-05-20T04:25:27.255196+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) pkglists = map(_parse_pkglist, element.findall('pkglis
t') or [])
2022-05-20T04:25:27.255321+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/
importers/yum/repomd/updateinfo.py", line 102, in _parse_pkglist
2022-05-20T04:25:27.255460+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) return map(_parse_collection, element.findall('collect
ion') or [])
2022-05-20T04:25:27.255631+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/
importers/yum/repomd/updateinfo.py", line 116, in _parse_collection
2022-05-20T04:25:27.255780+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) ret['module'] = _parse_module(module_elements[0])
2022-05-20T04:25:27.255947+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/
importers/yum/repomd/updateinfo.py", line 175, in _parse_module
2022-05-20T04:25:27.256096+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) 'arch': element.attrib['arch'],
2022-05-20T04:25:27.256212+00:00 myserver pulp: pulp_rpm.plugins.importers.yum.sync:ERROR: [fb39f8d5] (2485-05792) KeyError: 'arch'
2022-05-20T04:25:27.354490+00:00 myserver pulp: pulp.server.event.http:INFO: [fb39f8d5] (2485-05792) {"call_report": {"exception": null, "task_type": "pulp.server.managers.r
epo.sync.sync", "_href": "/pulp/api/v2/tasks/fb39f8d5-e4c4-45b1-aa75-b9bc177f2940/", "task_id": "fb39f8d5-e4c4-45b1-aa75-b9bc177f2940", "tags": ["pulp:repository:f2ba1795-07bc-432d-9d87-95c9e5333310", "pulp:action:sync"], "finish_time": null, "_ns": "task_status", "start_time": "2022-05-20T04:24:49Z", "traceback": null, "spawned_tasks": [], "progress_report": {"yum_importer": {"content": {"items_total": 0, "state": "FINISHED", "error_details": [], "details": {"rpm_total": 0, "rpm_done": 0, "drpm_total": 0, "drpm_done": 0}, "size_total": 0, "size_left": 0, "items_left": 0}, "comps": {"state": "NOT_STARTED"}, "purge_duplicates": {"state": "NOT_STARTED"}, "distribution": {"items_total": 0, "state": "FINISHED", "error_details": [], "items_left": 0}, "modules": {"state": "FINISHED"}, "errata": {"state": "FAILED", "error": "'arch'"}, "metadata": {"state": "FINISHED"}}}, "state": "running", "worker_name": "reserved_resource_worker-2@myserver", "result": null, "error": null, "_id": {"$oid": "6287181134e7113fe92e92f6"}, "id": "6287181134e7113fe92e92f6"}, "event_type": "repo.sync.finish", "payload": {"importer_id": "yum_importer", "exception": null, "repo_id": "f2ba1795-07bc-432d-9d87-95c9e5333310", "traceback": null, "started": "2022-05-20T04:24:49Z", "_ns": "repo_sync_results", "completed": "2022-05-20T04:25:27Z", "importer_type_id": "yum_importer", "error_message": null, "summary": {"modules": {"state": "FINISHED"}, "content": {"state": "FINISHED"}, "comps": {"state": "NOT_STARTED"}, "purge_duplicates": {"state": "NOT_STARTED"}, "distribution": {"state": "FINISHED"}, "errata": {"state": "FAILED"}, "metadata": {"state": "FINISHED"}}, "added_count": 0, "result": "failed", "updated_count": 52, "details": {"modules": {"state": "FINISHED"}, "content": {"size_total": 0, "items_left": 0, "items_total": 0, "state": "FINISHED", "size_left": 0, "details": {"rpm_total": 0, "rpm_do
2022-05-20T04:25:27.356141+00:00 myserver pulp: pulp.server.event.http:INFO: [fb39f8d5] (2485-05792) ne": 0, "drpm_total": 0, "drpm_done": 0}, "error_details": []}, "comps": {"state": "NOT_STARTED"}, "purge_duplicates": {"state": "NOT_STARTED"}, "distribution": {"items_total": 0, "state": "FINISHED", "error_details": [], "items_left": 0}, "errata": {"state": "FAILED", "error": "'arch'"}, "metadata": {"state": "FINISHED"}}, "id": "62871837320fa809b570ad68", "removed_count": 0}}
2022-05-20T04:25:27.386817+00:00 myserver pulp: pulp.server.event.http:ERROR: [fb39f8d5] Received HTTP 404 from HTTP notifier to https://myserver/katello/api/v2/repositories/sync_complete?token=mqtAbrNHxFMeUiqXLNk9SB3zWbV3vRQg.
2022-05-20T04:25:27.397559+00:00 myserver pulp: pulp.server.async.tasks:INFO: [fb39f8d5] Task failed : [fb39f8d5-e4c4-45b1-aa75-b9bc177f2940]
---
(0000573)
alukoshko   
2022-05-23 22:36   
Hi.
There was issue in updateinfo.xml metadata that prevented AppStream to be synced.
Could you try again?
(0000578)
akqroldhaber   
2022-05-24 06:06   
Hello alukoshko,

the problem is fixed, syncing AlmaLinux 8 Appstream Repo works now without any issues.
Thanks for fixing the promlem.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
213 [AlmaLinux-8] abrt major always 2022-04-10 11:19 2022-05-24 00:21
Reporter: brianjmurrell Platform:  
Assigned To: alukoshko OS:  
Priority: urgent OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: No workflow suitable for this problem was found!
Description: # abrt-cli report 3bac1664261a7e5ea668703a412dcc0afdc34ff9
No workflow suitable for this problem was found!

# rpm -q abrt
abrt-2.10.9-21.el8.alma.x86_64
Tags:
Steps To Reproduce: See above
Additional Information: Set to major/urgent as this impedes the ability to send any useful crash reports.
Attached Files:
Notes
(0000536)
brianjmurrell   
2022-04-10 12:07   
I guess technically the problem is in libreport:

https://github.com/abrt/libreport/blob/865db9ecd8f85e4ac50c87c63ee2062546ec74e8/src/cli/cli-report.c#L811-L819

And indeed, https://git.almalinux.org/rpms/libreport/src/commit/a3b5337005f0f2e7d8a1ac29471b2303e3808469/SPECS/libreport.spec indicates there is supposed to be a libreport-almalinux package with the workflows defined, but there does not appear to be any such package available:

# dnf search libreport
Last metadata expiration check: 4:52:40 ago on Sun 10 Apr 2022 02:56:15 AM EDT.
========================================================================= Name Exactly Matched: libreport ==========================================================================
libreport.x86_64 : Generic library for reporting various problems
libreport.i686 : Generic library for reporting various problems
======================================================================== Name & Summary Matched: libreport =========================================================================
libreport-cli.x86_64 : libreport's command line interface
libreport-filesystem.x86_64 : Filesystem layout for libreport
libreport-gtk.i686 : GTK front-end for libreport
libreport-gtk.x86_64 : GTK front-end for libreport
libreport-newt.x86_64 : libreport's newt interface
libreport-plugin-bugzilla.x86_64 : libreport's bugzilla plugin
libreport-plugin-kerneloops.x86_64 : libreport's kerneloops reporter plugin
libreport-plugin-logger.x86_64 : libreport's logger reporter plugin
libreport-plugin-mailx.x86_64 : libreport's mailx reporter plugin
libreport-plugin-reportuploader.x86_64 : libreport's reportuploader plugin
libreport-plugin-ureport.x86_64 : libreport's micro report plugin
libreport-web.x86_64 : Library providing network API for libreport
libreport-web.i686 : Library providing network API for libreport
============================================================================= Name Matched: libreport ==============================================================================
libreport-anaconda.x86_64 : Default configuration for reporting anaconda bugs
python3-libreport.x86_64 : Python 3 bindings for report-libs
(0000576)
alukoshko   
2022-05-24 00:21   
Thanks for report.
libreport-almalinux is now available in AppStream repo.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
173 [AlmaLinux-8] -OTHER major always 2022-01-13 10:02 2022-05-24 00:20
Reporter: alukoshko Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: %{MODULARITYLABEL} is missing in AlmaLinux module packages
Description: All module packages should have %{MODULARITYLABEL} rpm attribute.
But in AlmaLinux this attribute is always (none).
Tags:
Steps To Reproduce: https://github.com/aquasecurity/trivy/issues/1021#issuecomment-1011890917
Additional Information:
Attached Files:
Notes
(0000575)
alukoshko   
2022-05-24 00:20   
Thanks for report.
We've rebuilt a lot of modules for 8.6 release with a proper %{MODULARITYLABEL} macro and will continue to build with it.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
245 [AlmaLinux-8] -OTHER minor have not tried 2022-05-23 17:47 2022-05-23 17:47
Reporter: kashanlinux Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: CVM Core Patch Set for the Azure Images
Description: Please find the list of CVM Core patchset .

CVM Patch list:
HV/Storvsc: Add bounce buffer support for Storvsc - https://github.com/lantianyu/linux/commit/c46341863ba7cfaa11ed6c95d454769dcde57b84
HV/Netvsc: Add SNP support for netvsc driver - https://github.com/lantianyu/linux/commit/0026626dbc42bfcbe26d993bec104383f9d60e35
x86/Hyper-V: Copy data from/to bounce buffer during IO operation - https://github.com/lantianyu/linux/commit/5f948e69f2be44891af03d60b918a3bc0845f954
x86/Hyper-V: Add new parameter for vmbus_sendpacket_pagebuffer()/mpb_desc() - https://github.com/lantianyu/linux/commit/b484eebaf79340e29012a2dadb4518fa7d5d1284
x86/Hyper-V: Initialize bounce buffer page cache and list - https://github.com/lantianyu/linux/commit/8a437af5e4af945b28ba0071302dfa28a48df408
hv/vmbus: Initialize VMbus ring buffer for Isolated VM - https://github.com/lantianyu/linux/commit/45de7cff82cd6e99aedbd4cf2c44fa30298c0dea
HV/Vmbus: Add SNP support for VMbus channel initiate message - https://github.com/lantianyu/linux/commit/4bca8b9748dd17fb860a4528781932ade1825dd5
HV: Add ghcb hvcall support for SNP VM - https://github.com/lantianyu/linux/commit/bfb44533b884b08b639258f7150aa71dc148e221
HV: Add Write/Read MSR registers via ghcb - https://github.com/lantianyu/linux/commit/8cf6a0dea3189a654c41e16ad859c9ceb5bb940c
HV: Get Hyper-V Isolated VM capability - https://github.com/lantianyu/linux/commit/9290189014a1b231f70b5620338d61508da673df
x86/Hyper-V: Add new hvcall guest address host visibility support - https://github.com/lantianyu/linux/commit/deb6dc9bdbff7a6b16910ebe9aff266de9690cb2
x86/Hyper-V: Add visibility parameter for vmbus_establish_gpadl() - https://github.com/lantianyu/linux/commit/e697bc57e853f058eef9b2268b865aa8e574e233
x86/hyperv: Initialize clockevents earlier in CPU onlining - https://github.com/lantianyu/linux/commit/8815c2eec402080a4c5f2536668f6d5b7946ef8b
HV: Fix populating wrong point to vmbus_connection.monitor_pages_va - https://github.com/lantianyu/linux/commit/9fe9c74f4198b960f50b5dbec312aa2ad5d7bccc
HV: Fix wrong shared_gpa_boundary - https://github.com/lantianyu/linux/commit/cf4453885bfb39d74e79265505afd78587c128e0
HV/Netvsc: Fix dropping package during high network throughput - https://github.com/lantianyu/linux/commit/821d80739594d13a877eca719784bc8d9e8f21e6
Netvsc: Fix race condition with skb - https://github.com/lantianyu/linux/commit/6704c8cc1c4897b996fccb317ce34ab57f4f1954
HV/IVM: Add support for new AMD GHCB spec - https://github.com/lantianyu/linux/commit/4dc820b56e8bc689f56d4b800cbcf7532195d3ab
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0a76566595bfb242a7f4bedc77233e9194831ba3
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=44144185951a0ff9b50bf21c0cd1f79ff688e5ca
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e8b7db38449ac5b950a3f00519171c4be3e226ff
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=453de21c2b8281228173a7b689120b92929743d6
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4d18fcc95f50950a99bd940d4e61a983f91d267a
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=ab548fd21e1cbe601ce5f775254a6d042c6495f2
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=244808e0302953de11dba1f8a580cdd1df35843d
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=91b1b640b834b2d6f330baf04c0cc049eca9d689
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=206ad34d52a2f1205c84d08c12fc116aad0eb407
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=4424a8d1acc0a30542d4399e83c2a6cfcdd1eb71
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=6809ea1c570b40c9b2f139684784d6318d958011
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=46011a70c1c21a5dba02b38edeac16e667544361
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=5c0c26e7dca8f892cc342213e737494d8fd3384f
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=cbf0eda5de05545754540e0ad3173dca5737742e
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=f844988bde35e491507a1b9b7f84b810464cbf78
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=3f71d6b91e7e6fd594c0c8f18b8a1253fea0e093
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=0102eeedb71757d6589144cf019424f69b3ab289
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=8dff9808e9734fb5b4eddd0a5b1472fade215490
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=8190826e75cee9d9c008d24d557ef1ce06f5e3e2
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=0ba35fe91ce34f2d0feff626efd0062dac41781c
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=e5b180a1dd0cd0a8f8c3576eb032c7afda468dcc
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=5862347fd2b74bc00cd34828afae6dc21206a70a
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=ef6c74ee0d35122fde67f9af3758071374a31482
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=505e3f00c3f3648cb6260deb35e87fae1f64f5d8
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=3b8c72d076c42bf27284cda7b2b2b522810686f8
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: image.png (276,428 bytes) 2022-05-23 17:47
https://bugs.almalinux.org/file_download.php?file_id=132&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
224 [AlmaLinux-8] almalinux-release major always 2022-04-29 19:19 2022-05-20 13:12
Reporter: agompel Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Alma Linux 9.0 Beta does not recognize ISO on a Ventoy USB Drive
Description: Alma Linux 9.0 Beta does not recognize ISO on a Ventoy USB Drive.
The cause is obvious: a Ventoy (multiboot) uses the exfat format, and the fuse package (or driver( is missing in this BETA.
  So I could install from the network, but not from the ISO file on the USB.
Tags: ISO, VENTOY
Steps To Reproduce: Just tried to select the USB drive for install, and got an unrecoverable error.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
240 [AlmaLinux-8] almalinux-release block always 2022-05-20 13:04 2022-05-20 13:04
Reporter: agompel Platform: ALMA LINUX 9 Beta  
Assigned To: OS: LINUX  
Priority: high OS Version: 9  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Procedure "WordPress with Nginx, PHP 8.1, and MariaDB " on Web Site, does not work, is inadequate !
Description: On https://wiki.almalinux.org/Howto.html,
   Procedure "WordPress with Nginx, PHP 8.1, and MariaDB " is just completely inadequate with ALMA LINUX 9.0
    1) it uses yum, when dnf has been in use for a long time now.
    2) it just does work... it seems to be made for older versions, where config files are not in the same place
    3) There is just no procedure to debug it, when it does not work.
----
Note: NGNIX, dnf installed works "out of the box" there no need for more !
          The issues are in getting dnf installed Wordpress to work.
----
    My opinion is that the best would be to have separate dnf modules and/or groupInstall for
        Wordpress for LAMP/Apache and Wordpress for LEMP/NGINX
     Ideally the same should be applied for popular applications like Mediawiki, and Drupal, and more ....
     My expertise not being there I can only offer to test/validate these, if/when they come.
----
Thanks for the attention.

Andre Gompel
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
237 [AlmaLinux-8] dnf minor always 2022-05-17 14:31 2022-05-17 14:31
Reporter: jacp10 Platform: VMWare ESX  
Assigned To: OS: Alma Linux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: dnf updateinfo list --security --all is not listing an advisory I know is in the repository
Description: Security advisory ALSA-2022-0891 exists as evidenced by https://errata.almalinux.org/8/ALSA-2022-0891.html

The command 'dnf updateinfo list --security --all' does not display this in the list, on my system. Some example output (with positive control)

dnf updateinfo list --security --all | grep 'httpd'
  ALSA-2022:1915 Moderate/Sec. httpd-2.4.37-47.module_el8.6.0+2872+fe0ff7aa.1.alma.x86_64
  ALSA-2022:1915 Moderate/Sec. httpd-filesystem-2.4.37-47.module_el8.6.0+2872+fe0ff7aa.1.alma.noarch
  ALSA-2022:1915 Moderate/Sec. httpd-tools-2.4.37-47.module_el8.6.0+2872+fe0ff7aa.1.alma.x86_64

i.e you can see httpd is installed because a later security update for it is listed, but the 2022:0891 is not.
Tags:
Steps To Reproduce: I can reproduce this in the sense of it happens every time I run the command. I have run yum clean all then retried with the same result. I can see reference to ALSA-2022:0891 inside /var/cache/dnf/.
Additional Information: I find the documentation on dnf a little unclear, so it is possible I have overlooked something, but I think the '--all' switch means all updates should be listed regardless of age/installation status. 2022:0891 I believe to be actually installed on this system.
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
235 [AlmaLinux-8] -OTHER feature always 2022-05-14 05:41 2022-05-17 13:31
Reporter: pel Platform: x86_64  
Assigned To: OS: Sky Tiger  
Priority: high OS Version: 8.6 beta  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: no login possible
Description: I'm a simple user. After update from "Software" to 8.6 beta (why I get this offered?) I'm no longer to login (no login window, I've to reset and reboot with the former version). I don't know the reason.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000566)
pmdumuid   
2022-05-17 13:21   
I think this is the same problem I am facing.

I recently updated my Almalinux from 8.5 to 8.6, and when using the latest kernel (initramfs-4.18.0-372.9.1.el8.x86_64.img) sddm hangs when starting, however when selecting an older kernel at the grub menu (e.g. 4.18.0-348.23.1.el8_5.x86_64) it works again.

A notable difference when running each kernel is that the out of `journalctl -b -u sddm.service` using the failing kernel just shows:
```
May 17 20:25:50 linux-disp.kydlocal systemd[1]: Started Simple Desktop Display Manager.
```

however using an older kernel I get more:
```
May 17 20:25:50 linux-disp.kydlocal systemd[1]: Started Simple Desktop Display Manager.
May 17 20:25:58 linux-disp.kydlocal sddm[1933]: Could not setup default cursor
May 17 20:25:59 linux-disp.kydlocal sddm-helper[4193]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
May 17 20:26:32 linux-disp.kydlocal sddm-helper[11443]: pam_unix(sddm:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=xxxx
```
(0000567)
pmdumuid   
2022-05-17 13:31   
Possibly relates to https://bugs.almalinux.org/view.php?id=236


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
194 [AlmaLinux-8] -OTHER minor always 2022-03-03 17:32 2022-05-17 08:49
Reporter: rw Platform: AWS  
Assigned To: lkhn OS: AlmaLinux  
Priority: normal OS Version: 8.5.20211116  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 8.4  
    Target Version:  
abrt_hash:
URL:
Summary: Marketplace image does not support 6th-generation instance types
Description: When trying to launch the us-east-1 x86_64 marketplace AMI (ami-003d8719443bc8563) on an m6a instance, I get an error that it is not supported. Launching the community AMI from the Wiki (ami-0b4dad3b4322e5151) is fine. Is it possible to enable the marketplace AMIs to support those latest generation types?
Tags: aws, cloud
Steps To Reproduce: Try to launch an m6a.large instance in us-east-1 using the marketplace AMI.

Example sanitized command:
aws ec2 run-instances \
  --region us-east-1 \
  --instance-type m6a.large \
  --image-id ami-003d8719443bc8563 \
  --subnet-id subnet-<VPC subnet ID> \
  --security-group-ids sg-<VPC security group ID> \
  --key-name <SSH key name>

The same command succeeds using the community AMI ami-0b4dad3b4322e5151
Additional Information:
Attached Files:
Notes
(0000565)
lkhn   
2022-05-17 08:47   
Hey rw,

We've updated the supported instance type for both architectures. (x86_64 and AArch64) This update includes 3rd Generation Intel(M6i, C6i, R6i) and AMD ( M6a, C6a) instance types too.

Thanks for the reporting!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
209 [AlmaLinux-8] -OTHER minor always 2022-04-04 05:15 2022-05-11 03:49
Reporter: trex-thedog Platform:  
Assigned To: OS:  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: PXE Installer for 8.5 stuck at multipath
Description: PXE Installer for Almalinux that can install to either local hard drive or iscsi lun. On 8.4 it works ok but not on 8.5.

On 8.5 the bootup process gets stuck at "Started cancel waiting for multipath siblings of sda".
Tags: installation, installer, pxe
Steps To Reproduce: 1. With PXE infra already setup, boot up the vmlinuz and initrd from the images/pxeboot location.
Additional Information: I was able to resolve it (I think) by editing the initrd.img and removing the prefixdevname-tools from it. Once I repacked it, the pxe installer seems to work ok.
Attached Files: IMG-1304.jpg (648,917 bytes) 2022-04-04 05:15
https://bugs.almalinux.org/file_download.php?file_id=127&type=bug
Notes
(0000531)
alukoshko   
2022-04-04 10:16   
Hello. Have you seen curl errors and No free space left on device error?
Could you try the same with CentOS 8.5 images?
(0000532)
trex-thedog   
2022-04-04 19:43   
Forgot to mention, yes I'm seeing curl and 'No free space left on device' errors.

I've just tried the latest Centos8 Stream and it is affected with this same issue. I did not bother doing an initrd.img surgery this time. I'm pretty sure it will work if I did that.
(0000555)
patl   
2022-05-02 23:30   
I get this error when I copy the installation files to a USB stick (GPT formatted, bootable FAT32 partition) and boot it in UEFI mode.

I have no iSCSI; just regular sSATA disks. No multipath. Nevertheless the Kickstart bootup hangs with "started cancel waiting for mutipath siblings" on each of the sSATA disks.

Would love to know how to bypass this.
(0000556)
patl   
2022-05-03 01:18   
Addendum:

My volume label was 10 characters including a dash and some lower case letters. When I make it 8 upper-case letters, the installation still prints these messages (and stalls for a bit) but ultimately works. Not sure whether the length or the character set is making the difference.

Also I have no theory to explain any of this. Perhaps someone with more knowledge/patience than I can figure it out.
(0000561)
trex-thedog   
2022-05-11 02:32   
^ That's (GPT + FAT32) quite an uncommon setup you have there. Afaik, fat32 truncates filenames to 8.3 (8 chars for filenames + 3 for extension). Perhaps that is what's happening in your case?

I was wondering how your usb stick ended up with fat32 with gpt partitioning scheme? Is that a multi-distro usb?
(0000562)
patl   
2022-05-11 03:49   
GPT + FAT32 = UEFI boot partition.

I am pretty much following the procedure at https://askubuntu.com/a/395880/. It is working for me now. I had to restrict the volume label and be very explicit in the kernel command line (e.g. "linuxefi /isolinux/vmlinuz inst.repo=cdrom:LABEL=MYMEDIA inst.ks=cdrom:LABEL=MYMEDIA:/path/to/ks.cfg"). I am using "cdrom:" because this grub.cfg is shared with my .iso installation media. It works even though this is a USB stick. If I try to let Anaconda hunt for the repo, it locks up the install with "Started cancel waiting for multipath siblings of sda".


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
232 [AlmaLinux-8] anaconda minor always 2022-05-05 10:23 2022-05-05 20:53
Reporter: robbevl Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Anaconda can't mount XFS during kickstart installation
Description: We have a kickstart file that works great with RHEL8 but fails while trying to use with AL8.

The installation starts but then Anaconda throws an error after formatting the xfs filesystems,
apparently the mount program doesn't know xfs:

DEBUG:blivet: XFS.setup: device: /dev/mapper/almalinux -root ; type: xfs ; status: False
INFO:program:Running... mount -t xfs -o defaults /dev/mapper/almalinux-root /mnt/sysimage
INFO:program:stderr:
INFO:program:b"mount: /mnt/sysimage: unknown filesystem type 'xfs'."
DEBUG:program:Return code: 32
INFO:anaconda.threading:Thread Failed: AnaTaskThread-MountFilesystemsTask -1 (139983618381568)


Relevant lines in ks.cfs:

zerombr
ignoredisk --only-use=sda
clearpart --drives=sda --initlabel --disklabel=gpt
bootloader --append="crashkernel=auto" --location=mbr --boot-drive=sda
part /boot --fstype="xfs" --ondisk=sda --size=1024
part /boot/efi --fstype="efi" --ondisk=sda --size=600 --fsoptions="umask=0077,shortname=winnt"
part pv.1 --fstype="lvmpv" --ondisk=sda --size=5120 --grow
volgroup almalinux pv.1
logvol swap --fstype="swap" --recommended --name=swap --vgname=almalinux
logvol / --fstype="xfs" --size=8192 --name=root --vgname=almalinux
logvol /var --fstype="xfs" --percent=100 --name=var --vgname=almalinux


We're using the almalinux-8.5-x86_64-dvd.iso hosted on an NFS share as repo:
nfs --server=my-nfs-server.example.com --dir=/kickstart/iso/almalinux-8.5-x86_64-dvd.iso

We're booting from the dvd itself. We have a small iso that is bootable and has this line in grub,cfg:

linuxefi /isolinux/vmlinuz inst.stage2=nfs:my-nfs-server.example.com:/kickstart/iso/almalinux-8.5-x86_64-dvd.iso inst.ks=nfs:my-nfs-server.example.com:/kickstart/ks/ks.cfg

This is working with the rhel8.5 dvd so I was surprised to see this error. XFS is supposed to be the default fs, are the xfs drivers not loaded when booting from DVD?
Tags: anaconda, installation, kickstart, not-a-bug, xfs
Steps To Reproduce: Attempt kickstart installation while booting from almalinux-8.5-x86_64-dvd.iso and with almalinux-8.5-x86_64-dvd.iso as repo.
Additional Information:
Attached Files:
Notes
(0000558)
robbevl   
2022-05-05 20:52   
Found the problem. It's not a bug, please close.

Anaconda was unable to load the xfs module (Required key not available).
This is caused by EFI secure boot (which needs modules to be signed), or rather, because I used my modified rhel8 iso as stage 1 boot device and attempted to point it at the Almalinux dvd for stage 2.
Apparently the difference was noticed, and as a result some modules (like xfs) did not load.
I created a modified Almalinux 8.5 bootable iso to load the ks and all works as expected now.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
233 [AlmaLinux-8] -OTHER minor always 2022-05-05 14:36 2022-05-05 14:36
Reporter: ronan Platform: AlmaLinux  
Assigned To: OS: Linux  
Priority: normal OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Some rpm binaries from RPM group are missing
Description: In group define AlmaLinux, some package are define but are not present in AlmaLinux:

*base:
rhc

*core:
rhc

*standard:
rhc

*powertools:
Judy-devel
ant-junit
antlr-C++
antlr-tool
apache-commons-beanutils
apache-commons-compress
apache-commons-net
apache-ivy
aqute-bnd
aqute-bndlib
bcel
beust-jcommander
bsf
bsh
cglib
easymock
felix-utils
geronimo-jms
glassfish-jsp-api
glassfish-servlet-api
hamcrest
hamcrest-core
javamail
javapackages-local
jaxen
jsch
jsr-305
junit
jvnet-parent
jzlib
maven-archiver
maven-artifact
maven-artifact-manager
maven-artifact-resolver
maven-artifact-transfer
maven-common-artifact-filters
maven-compiler-plugin
maven-dependency-tree
maven-doxia-core
maven-doxia-logging-api
maven-doxia-module-apt
maven-doxia-module-fml
maven-doxia-module-xdoc
maven-doxia-module-xhtml
maven-doxia-sink-api
maven-doxia-sitetools
maven-enforcer-api
maven-enforcer-plugin
maven-enforcer-rules
maven-filtering
maven-invoker
maven-jar-plugin
maven-local
maven-model
maven-monitor
maven-plugin-annotations
maven-plugin-build-helper
maven-plugin-bundle
maven-plugin-registry
maven-plugin-testing-harness
maven-profile
maven-project
maven-remote-resources-plugin
maven-reporting-api
maven-reporting-impl
maven-resources-plugin
maven-settings
maven-shared-incremental
maven-source-plugin
maven-surefire
maven-surefire-plugin
maven-surefire-provider-junit
maven-surefire-provider-testng
maven-verifier
mockito
msv-msv
objectweb-asm
objenesis
osgi-annotation
osgi-compendium
osgi-core
plexus-archiver
plexus-build-api
plexus-compiler
plexus-component-api
plexus-containers-container-default
plexus-i18n
plexus-interactivity-api
plexus-io
plexus-languages
plexus-resources
plexus-velocity
python2-talloc
python3-javapackages
qdox
xbean
xmlunit
xmvn-api
xmvn-connector-aether
xmvn-core
xmvn-install
xmvn-minimal
xmvn-mojo
xmvn-resolve
xmvn-subst
xz-java
Tags:
Steps To Reproduce:
$ sudo dnf -v group info base
$ sudo dnf -v group info core
$ sudo dnf -v group info standard
$ sudo dnf -v group info powertools
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
231 [AlmaLinux-8] -OTHER minor always 2022-05-05 09:54 2022-05-05 09:54
Reporter: ronan Platform: AlmaLinux  
Assigned To: OS: Linux  
Priority: normal OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Binaries RPM do not have RPM source available.
Description: In AlmaLinux some binaries packages do not have valid source in any RPM source repositories.

ant-1.10.5-1.module_el8.0.0+6031+d80e135e.noarch . The src rpm wanted is ant-1.10.5-1.module_el8.0.0+6031+d80e135e.src.rpm
aopalliance-1.0-17.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is aopalliance-1.0-17.module_el8.0.0+6035+97aff910.src.rpm
apache-commons-cli-1.4-4.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is apache-commons-cli-1.4-4.module_el8.0.0+6035+97aff910.src.rpm
apache-commons-codec-1.11-3.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is apache-commons-codec-1.11-3.module_el8.0.0+6035+97aff910.src.rpm
apache-commons-io-1:2.6-3.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is apache-commons-io-2.6-3.module_el8.0.0+6035+97aff910.src.rpm
apache-commons-lang3-3.7-3.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is apache-commons-lang3-3.7-3.module_el8.0.0+6035+97aff910.src.rpm
apache-commons-logging-1.2-13.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is apache-commons-logging-1.2-13.module_el8.0.0+6035+97aff910.src.rpm
aspnetcore-runtime-3.1-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
aspnetcore-targeting-pack-3.1-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
atinject-1-28.20100611svn86.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is atinject-1-28.20100611svn86.module_el8.0.0+6035+97aff910.src.rpm
cdi-api-1.2-8.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is cdi-api-1.2-8.module_el8.0.0+6035+97aff910.src.rpm
dotnet-apphost-pack-3.1-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-hostfxr-3.1-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-runtime-3.1-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-sdk-3.1-3.1.120-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-targeting-pack-3.1-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-templates-3.1-3.1.120-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
geronimo-annotation-1.0-23.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is geronimo-annotation-1.0-23.module_el8.0.0+6035+97aff910.src.rpm
glassfish-el-api-3.0.1-0.7.b08.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is glassfish-el-3.0.1-0.7.b08.module_el8.0.0+6035+97aff910.src.rpm
google-guice-4.1-11.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is google-guice-4.1-11.module_el8.0.0+6035+97aff910.src.rpm
guava20-20.0-8.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is guava20-20.0-8.module_el8.0.0+6035+97aff910.src.rpm
hawtjni-runtime-1.16-1.module_el8.0.0+6044+f3cbc35d.noarch . The src rpm wanted is hawtjni-1.16-1.module_el8.0.0+6044+f3cbc35d.src.rpm
hawtjni-runtime-1.16-2.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is hawtjni-1.16-2.module_el8.0.0+6035+97aff910.src.rpm
httpcomponents-client-4.5.5-4.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is httpcomponents-client-4.5.5-4.module_el8.0.0+6035+97aff910.src.rpm
httpcomponents-core-4.4.10-3.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is httpcomponents-core-4.4.10-3.module_el8.0.0+6035+97aff910.src.rpm
jansi-1.17.1-1.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is jansi-1.17.1-1.module_el8.0.0+6035+97aff910.src.rpm
jansi-1.17.1-1.module_el8.0.0+6044+f3cbc35d.noarch . The src rpm wanted is jansi-1.17.1-1.module_el8.0.0+6044+f3cbc35d.src.rpm
jansi-native-1.7-5.module_el8.0.0+6044+f3cbc35d.x86_64 . The src rpm wanted is jansi-native-1.7-5.module_el8.0.0+6044+f3cbc35d.src.rpm
jansi-native-1.7-7.module_el8.0.0+6035+97aff910.x86_64 . The src rpm wanted is jansi-native-1.7-7.module_el8.0.0+6035+97aff910.src.rpm
javapackages-filesystem-5.3.0-2.module_el8.0.0+6004+2fc32706.noarch . The src rpm wanted is javapackages-tools-5.3.0-2.module_el8.0.0+6004+2fc32706.src.rpm
jboss-interceptors-1.2-api-1.0.0-8.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is jboss-interceptors-1.2-api-1.0.0-8.module_el8.0.0+6035+97aff910.src.rpm
jcl-over-slf4j-1.7.25-4.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is slf4j-1.7.25-4.module_el8.0.0+6035+97aff910.src.rpm
jline-2.14.6-2.module_el8.0.0+6044+f3cbc35d.noarch . The src rpm wanted is jline-2.14.6-2.module_el8.0.0+6044+f3cbc35d.src.rpm
jsoup-1.11.3-3.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is jsoup-1.11.3-3.module_el8.0.0+6035+97aff910.src.rpm
maven-1:3.5.4-5.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-3.5.4-5.module_el8.0.0+6035+97aff910.src.rpm
maven-lib-1:3.5.4-5.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-3.5.4-5.module_el8.0.0+6035+97aff910.src.rpm
maven-resolver-api-1:1.1.1-2.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-resolver-1.1.1-2.module_el8.0.0+6035+97aff910.src.rpm
maven-resolver-connector-basic-1:1.1.1-2.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-resolver-1.1.1-2.module_el8.0.0+6035+97aff910.src.rpm
maven-resolver-impl-1:1.1.1-2.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-resolver-1.1.1-2.module_el8.0.0+6035+97aff910.src.rpm
maven-resolver-spi-1:1.1.1-2.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-resolver-1.1.1-2.module_el8.0.0+6035+97aff910.src.rpm
maven-resolver-transport-wagon-1:1.1.1-2.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-resolver-1.1.1-2.module_el8.0.0+6035+97aff910.src.rpm
maven-resolver-util-1:1.1.1-2.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-resolver-1.1.1-2.module_el8.0.0+6035+97aff910.src.rpm
maven-shared-utils-3.2.1-0.1.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-shared-utils-3.2.1-0.1.module_el8.0.0+6035+97aff910.src.rpm
maven-wagon-file-3.1.0-1.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-wagon-3.1.0-1.module_el8.0.0+6035+97aff910.src.rpm
maven-wagon-http-3.1.0-1.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-wagon-3.1.0-1.module_el8.0.0+6035+97aff910.src.rpm
maven-wagon-http-shared-3.1.0-1.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-wagon-3.1.0-1.module_el8.0.0+6035+97aff910.src.rpm
maven-wagon-provider-api-3.1.0-1.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is maven-wagon-3.1.0-1.module_el8.0.0+6035+97aff910.src.rpm
plexus-cipher-1.7-14.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is plexus-cipher-1.7-14.module_el8.0.0+6035+97aff910.src.rpm
plexus-classworlds-2.5.2-9.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is plexus-classworlds-2.5.2-9.module_el8.0.0+6035+97aff910.src.rpm
plexus-containers-component-annotations-1.7.1-8.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is plexus-containers-1.7.1-8.module_el8.0.0+6035+97aff910.src.rpm
plexus-interpolation-1.22-9.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is plexus-interpolation-1.22-9.module_el8.0.0+6035+97aff910.src.rpm
plexus-sec-dispatcher-1.4-26.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is plexus-sec-dispatcher-1.4-26.module_el8.0.0+6035+97aff910.src.rpm
plexus-utils-3.1.0-3.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is plexus-utils-3.1.0-3.module_el8.0.0+6035+97aff910.src.rpm
scala-2.10.6-14.module_el8.0.0+6044+f3cbc35d.noarch . The src rpm wanted is scala-2.10.6-14.module_el8.0.0+6044+f3cbc35d.src.rpm
sisu-inject-1:0.3.3-6.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is sisu-0.3.3-6.module_el8.0.0+6035+97aff910.src.rpm
sisu-plexus-1:0.3.3-6.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is sisu-0.3.3-6.module_el8.0.0+6035+97aff910.src.rpm
slf4j-1.7.25-4.module_el8.0.0+6035+97aff910.noarch . The src rpm wanted is slf4j-1.7.25-4.module_el8.0.0+6035+97aff910.src.rpm
centos-release-advanced-virtualization-1.0-2.el8.noarch . The src rpm wanted is centos-release-advanced-virtualization-1.0-2.el8.src.rpm
centos-release-ansible-29-1-2.el8.noarch . The src rpm wanted is centos-release-ansible-29-1-2.el8.src.rpm
centos-release-ceph-nautilus-1.2-2.el8.noarch . The src rpm wanted is centos-release-ceph-nautilus-1.2-2.el8.src.rpm
centos-release-ceph-octopus-1.0-1.el8.noarch . The src rpm wanted is centos-release-ceph-octopus-1.0-1.el8.src.rpm
centos-release-ceph-pacific-1.0-1.el8.noarch . The src rpm wanted is centos-release-ceph-pacific-1.0-1.el8.src.rpm
centos-release-configmanagement-1-1.el8.noarch . The src rpm wanted is centos-release-configmanagement-1-1.el8.src.rpm
centos-release-gluster6-1.0-1.el8.noarch . The src rpm wanted is centos-release-gluster6-1.0-1.el8.src.rpm
centos-release-gluster7-1.0-2.el8.noarch . The src rpm wanted is centos-release-gluster7-1.0-2.el8.src.rpm
centos-release-gluster8-1.0-1.el8.noarch . The src rpm wanted is centos-release-gluster8-1.0-1.el8.src.rpm
centos-release-gluster9-1.0-1.el8.noarch . The src rpm wanted is centos-release-gluster9-1.0-1.el8.src.rpm
centos-release-messaging-1-2.el8.noarch . The src rpm wanted is centos-release-messaging-1-2.el8.src.rpm
centos-release-nfs-ganesha28-1.0-3.el8.noarch . The src rpm wanted is centos-release-nfs-ganesha28-1.0-3.el8.src.rpm
centos-release-nfs-ganesha30-1.0-2.el8.noarch . The src rpm wanted is centos-release-nfs-ganesha30-1.0-2.el8.src.rpm
centos-release-nfv-common-1-2.el8.noarch . The src rpm wanted is centos-release-nfv-1-2.el8.src.rpm
centos-release-openstack-train-2-1.el8.noarch . The src rpm wanted is centos-release-openstack-train-2-1.el8.src.rpm
centos-release-openstack-ussuri-1-4.el8.noarch . The src rpm wanted is centos-release-openstack-ussuri-1-4.el8.src.rpm
centos-release-openstack-victoria-1-1.el8.noarch . The src rpm wanted is centos-release-openstack-victoria-1-1.el8.src.rpm
centos-release-opstools-1-10.el8.noarch . The src rpm wanted is centos-release-opstools-1-10.el8.src.rpm
centos-release-ovirt44-1.0-1.el8.noarch . The src rpm wanted is centos-release-ovirt44-1.0-1.el8.src.rpm
centos-release-samba411-1.0-1.el8.noarch . The src rpm wanted is centos-release-samba411-1.0-1.el8.src.rpm
centos-release-samba412-1.0-1.el8.noarch . The src rpm wanted is centos-release-samba412-1.0-1.el8.src.rpm
centos-release-samba413-1.0-1.el8.noarch . The src rpm wanted is centos-release-samba413-1.0-1.el8.src.rpm
centos-release-samba414-1.0-1.el8.noarch . The src rpm wanted is centos-release-samba414-1.0-1.el8.src.rpm
centos-release-storage-common-2-2.el8.noarch . The src rpm wanted is centos-release-storage-common-2-2.el8.src.rpm
centos-release-virt-common-1-2.el8.noarch . The src rpm wanted is centos-release-virt-common-1-2.el8.src.rpm
dotnet-apphost-pack-3.1-debuginfo-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-hostfxr-3.1-debuginfo-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-runtime-3.1-debuginfo-3.1.20-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-sdk-3.1-debuginfo-3.1.120-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet3.1-debuginfo-3.1.120-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet3.1-debugsource-3.1.120-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
dotnet-sdk-3.1-source-built-artifacts-3.1.118-1.el8.x86_64 . The src rpm wanted is dotnet3.1-3.1.118-1.el8.src.rpm
dotnet-sdk-3.1-source-built-artifacts-3.1.120-2.el8_5.x86_64 . The src rpm wanted is dotnet3.1-3.1.120-2.el8_5.src.rpm
glassfish-jaxb-bom-2.2.11-11.module_el8.3.0+2058+6bf11631.noarch . The src rpm wanted is glassfish-jaxb-2.2.11-11.module_el8.3.0+2058+6bf11631.src.rpm
glassfish-jaxb-bom-ext-2.2.11-11.module_el8.3.0+2058+6bf11631.noarch . The src rpm wanted is glassfish-jaxb-2.2.11-11.module_el8.3.0+2058+6bf11631.src.rpm
glassfish-jaxb-codemodel-parent-2.2.11-11.module_el8.3.0+2058+6bf11631.noarch . The src rpm wanted is glassfish-jaxb-2.2.11-11.module_el8.3.0+2058+6bf11631.src.rpm
glassfish-jaxb-external-parent-2.2.11-11.module_el8.3.0+2058+6bf11631.noarch . The src rpm wanted is glassfish-jaxb-2.2.11-11.module_el8.3.0+2058+6bf11631.src.rpm
glassfish-jaxb-parent-2.2.11-11.module_el8.3.0+2058+6bf11631.noarch . The src rpm wanted is glassfish-jaxb-2.2.11-11.module_el8.3.0+2058+6bf11631.src.rpm
glassfish-jaxb-runtime-parent-2.2.11-11.module_el8.3.0+2058+6bf11631.noarch . The src rpm wanted is glassfish-jaxb-2.2.11-11.module_el8.3.0+2058+6bf11631.src.rpm
glassfish-jaxb-txw-parent-2.2.11-11.module_el8.3.0+2058+6bf11631.noarch . The src rpm wanted is glassfish-jaxb-2.2.11-11.module_el8.3.0+2058+6bf11631.src.rpm
python3-sip-4.19.12-3.el8.i686 . The src rpm wanted is sip-4.19.12-3.el8.src.rpm
python3-sip-debuginfo-4.19.12-3.el8.i686 . The src rpm wanted is sip-4.19.12-3.el8.src.rpm
sip-debuginfo-4.19.12-3.el8.i686 . The src rpm wanted is sip-4.19.12-3.el8.src.rpm
Tags:
Steps To Reproduce: e.g.: apache-commons-cli

sudo dnf search --enablerepo="*-source" apache-commons-cli
================================================================================================= Name Exactly Matched: apache-commons-cli ==================================================================================================
apache-commons-cli.noarch : Command Line Interface Library for Java
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
230 [AlmaLinux-8] -OTHER minor always 2022-05-05 09:36 2022-05-05 09:36
Reporter: ronan Platform: AlmaLinux  
Assigned To: OS: Linux  
Priority: normal OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Some source package provide no binary RPM.
Description: Some source RPM do not provides any binary RPM.
It's confusing when you want to know where the binaries coming from.


perl-DBD-SQLite-1.58-2.el8.src.rpm (baseos-source,http://mirror.almalinux.ikoula.com/8/BaseOS/Source/Packages/perl-DBD-SQLite-1.58-2.el8.src.rpm)
perl-DBI-1.641-1.el8.src.rpm (baseos-source,http://mirror.almalinux.ikoula.com/8/BaseOS/Source/Packages/perl-DBI-1.641-1.el8.src.rpm)
389-ds-base-1.4.3.23-10.module_el8.5.0+2538+47000435.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/389-ds-base-1.4.3.23-10.module_el8.5.0+2538+47000435.src.rpm)
389-ds-base-1.4.3.23-14.module_el8.5.0+2628+c731dc97.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/389-ds-base-1.4.3.23-14.module_el8.5.0+2628+c731dc97.src.rpm)
Judy-1.0.5-18.module_el8.4.0+2357+88cd7ba1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/Judy-1.0.5-18.module_el8.4.0+2357+88cd7ba1.src.rpm)
Judy-1.0.5-18.module_el8.5.0+2637+d11efe18.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/Judy-1.0.5-18.module_el8.5.0+2637+d11efe18.src.rpm)
apache-commons-collections-3.2.2-10.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/apache-commons-collections-3.2.2-10.module_el8.5.0+2577+9e95fe00.src.rpm)
apache-commons-compress-1.20-3.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/apache-commons-compress-1.20-3.module_el8.3.0+2043+807b4491.src.rpm)
apache-commons-jxpath-1.3-36.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/apache-commons-jxpath-1.3-36.module_el8.3.0+2043+807b4491.src.rpm)
apache-commons-lang-2.6-21.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/apache-commons-lang-2.6-21.module_el8.5.0+2577+9e95fe00.src.rpm)
apache-commons-net-3.6-3.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/apache-commons-net-3.6-3.module_el8.5.0+2577+9e95fe00.src.rpm)
apiguardian-1.1.0-4.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/apiguardian-1.1.0-4.module_el8.3.0+2043+807b4491.src.rpm)
batik-1.11-6.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/batik-1.11-6.module_el8.3.0+2043+807b4491.src.rpm)
bea-stax-1.2.0-16.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/bea-stax-1.2.0-16.module_el8.5.0+2577+9e95fe00.src.rpm)
bind-dyndb-ldap-11.6-2.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/bind-dyndb-ldap-11.6-2.module_el8.4.0+2501+94d209c1.src.rpm)
bind-dyndb-ldap-11.6-2.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/bind-dyndb-ldap-11.6-2.module_el8.5.0+2603+92118e57.src.rpm)
buildah-1.11.6-10.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/buildah-1.11.6-10.module_el8.5.0+2635+e4386a39.src.rpm)
buildah-1.11.6-9.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/buildah-1.11.6-9.module_el8.5.0+2566+ec01067b.src.rpm)
buildah-1.19.9-1.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/buildah-1.19.9-1.module_el8.5.0+2567+c988d830.src.rpm)
buildah-1.19.9-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/buildah-1.19.9-1.module_el8.5.0+2614+87221ce8.src.rpm)
buildah-1.19.9-2.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/buildah-1.19.9-2.module_el8.5.0+2636+8c48f0fc.src.rpm)
buildah-1.5-8.gite94b4f9.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/buildah-1.5-8.gite94b4f9.module_el8.3.0+2044+12421f43.src.rpm)
cjose-0.6.1-2.module_el8.3.0+2087+ac02cfd2.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/cjose-0.6.1-2.module_el8.3.0+2087+ac02cfd2.src.rpm)
cockpit-podman-11-1.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/cockpit-podman-11-1.module_el8.5.0+2566+ec01067b.src.rpm)
cockpit-podman-11-1.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/cockpit-podman-11-1.module_el8.5.0+2635+e4386a39.src.rpm)
cockpit-podman-29-2.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/cockpit-podman-29-2.module_el8.5.0+2567+c988d830.src.rpm)
cockpit-podman-29-2.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/cockpit-podman-29-2.module_el8.5.0+2614+87221ce8.src.rpm)
cockpit-podman-29-2.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/cockpit-podman-29-2.module_el8.5.0+2636+8c48f0fc.src.rpm)
conmon-2.0.15-1.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/conmon-2.0.15-1.module_el8.5.0+2566+ec01067b.src.rpm)
conmon-2.0.15-1.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/conmon-2.0.15-1.module_el8.5.0+2635+e4386a39.src.rpm)
conmon-2.0.26-1.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/conmon-2.0.26-1.module_el8.5.0+2567+c988d830.src.rpm)
conmon-2.0.26-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/conmon-2.0.26-1.module_el8.5.0+2614+87221ce8.src.rpm)
conmon-2.0.26-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/conmon-2.0.26-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
container-selinux-2.124.0-1.gitf958d0c.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/container-selinux-2.124.0-1.gitf958d0c.module_el8.3.0+2044+12421f43.src.rpm)
container-selinux-2.130.0-1.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/container-selinux-2.130.0-1.module_el8.5.0+2566+ec01067b.src.rpm)
container-selinux-2.130.0-1.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/container-selinux-2.130.0-1.module_el8.5.0+2635+e4386a39.src.rpm)
container-selinux-2.167.0-1.module_el8.5.0+2585+beaa716d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/container-selinux-2.167.0-1.module_el8.5.0+2585+beaa716d.src.rpm)
container-selinux-2.167.0-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/container-selinux-2.167.0-1.module_el8.5.0+2614+87221ce8.src.rpm)
container-selinux-2.167.0-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/container-selinux-2.167.0-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
containernetworking-plugins-0.7.4-4.git9ebe139.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/containernetworking-plugins-0.7.4-4.git9ebe139.module_el8.3.0+2044+12421f43.src.rpm)
containernetworking-plugins-0.8.3-4.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/containernetworking-plugins-0.8.3-4.module_el8.5.0+2566+ec01067b.src.rpm)
containernetworking-plugins-0.8.3-4.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/containernetworking-plugins-0.8.3-4.module_el8.5.0+2635+e4386a39.src.rpm)
containernetworking-plugins-0.9.1-1.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/containernetworking-plugins-0.9.1-1.module_el8.5.0+2567+c988d830.src.rpm)
containernetworking-plugins-0.9.1-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/containernetworking-plugins-0.9.1-1.module_el8.5.0+2614+87221ce8.src.rpm)
containernetworking-plugins-0.9.1-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/containernetworking-plugins-0.9.1-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
criu-3.12-9.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/criu-3.12-9.module_el8.3.0+2044+12421f43.src.rpm)
criu-3.12-9.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/criu-3.12-9.module_el8.5.0+2566+ec01067b.src.rpm)
criu-3.12-9.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/criu-3.12-9.module_el8.5.0+2635+e4386a39.src.rpm)
criu-3.15-1.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/criu-3.15-1.module_el8.5.0+2567+c988d830.src.rpm)
criu-3.15-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/criu-3.15-1.module_el8.5.0+2614+87221ce8.src.rpm)
criu-3.15-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/criu-3.15-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
crun-0.18-2.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/crun-0.18-2.module_el8.5.0+2567+c988d830.src.rpm)
crun-0.18-2.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/crun-0.18-2.module_el8.5.0+2614+87221ce8.src.rpm)
crun-0.18-2.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/crun-0.18-2.module_el8.5.0+2636+8c48f0fc.src.rpm)
custodia-0.6.0-3.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/custodia-0.6.0-3.module_el8.4.0+2501+94d209c1.src.rpm)
custodia-0.6.0-3.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/custodia-0.6.0-3.module_el8.5.0+2603+92118e57.src.rpm)
eclipse-4.16-7.module_el8.4.0+2105+766a6595.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/eclipse-4.16-7.module_el8.4.0+2105+766a6595.src.rpm)
eclipse-ecf-3.14.8-1.module_el8.4.0+2105+766a6595.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/eclipse-ecf-3.14.8-1.module_el8.4.0+2105+766a6595.src.rpm)
eclipse-emf-2.22.0-1.module_el8.4.0+2105+766a6595.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/eclipse-emf-2.22.0-1.module_el8.4.0+2105+766a6595.src.rpm)
felix-gogo-command-1.0.2-11.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/felix-gogo-command-1.0.2-11.module_el8.3.0+2043+807b4491.src.rpm)
felix-gogo-runtime-1.1.0-7.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/felix-gogo-runtime-1.1.0-7.module_el8.3.0+2043+807b4491.src.rpm)
felix-gogo-shell-1.1.0-5.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/felix-gogo-shell-1.1.0-5.module_el8.3.0+2043+807b4491.src.rpm)
felix-scr-2.1.16-6.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/felix-scr-2.1.16-6.module_el8.3.0+2043+807b4491.src.rpm)
fuse-overlayfs-0.3-5.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/fuse-overlayfs-0.3-5.module_el8.3.0+2044+12421f43.src.rpm)
fuse-overlayfs-0.7.8-1.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/fuse-overlayfs-0.7.8-1.module_el8.5.0+2566+ec01067b.src.rpm)
fuse-overlayfs-0.7.8-1.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/fuse-overlayfs-0.7.8-1.module_el8.5.0+2635+e4386a39.src.rpm)
fuse-overlayfs-1.4.0-2.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/fuse-overlayfs-1.4.0-2.module_el8.5.0+2567+c988d830.src.rpm)
fuse-overlayfs-1.4.0-2.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/fuse-overlayfs-1.4.0-2.module_el8.5.0+2614+87221ce8.src.rpm)
fuse-overlayfs-1.4.0-2.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/fuse-overlayfs-1.4.0-2.module_el8.5.0+2636+8c48f0fc.src.rpm)
galera-26.4.7-1.module_el8.4.0+2357+88cd7ba1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/galera-26.4.7-1.module_el8.4.0+2357+88cd7ba1.src.rpm)
galera-26.4.9-4.module_el8.5.0+2637+d11efe18.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/galera-26.4.9-4.module_el8.5.0+2637+d11efe18.src.rpm)
glassfish-annotation-api-1.3.2-3.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/glassfish-annotation-api-1.3.2-3.module_el8.3.0+2043+807b4491.src.rpm)
glassfish-fastinfoset-1.2.13-9.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/glassfish-fastinfoset-1.2.13-9.module_el8.5.0+2577+9e95fe00.src.rpm)
glassfish-jaxb-api-2.2.12-8.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/glassfish-jaxb-api-2.2.12-8.module_el8.5.0+2577+9e95fe00.src.rpm)
glassfish-jsp-2.3.4-6.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/glassfish-jsp-2.3.4-6.module_el8.3.0+2043+807b4491.src.rpm)
glassfish-jsp-api-2.3.3-3.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/glassfish-jsp-api-2.3.3-3.module_el8.3.0+2043+807b4491.src.rpm)
glassfish-servlet-api-3.1.0-19.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/glassfish-servlet-api-3.1.0-19.module_el8.3.0+2043+807b4491.src.rpm)
google-gson-2.8.6-5.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/google-gson-2.8.6-5.module_el8.3.0+2043+807b4491.src.rpm)
guava-28.1-3.module_el8.3.0+2039+157bd82e.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/guava-28.1-3.module_el8.3.0+2039+157bd82e.src.rpm)
hamcrest-1.3-29.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/hamcrest-1.3-29.module_el8.3.0+2043+807b4491.src.rpm)
icu4j-65.1-3.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/icu4j-65.1-3.module_el8.3.0+2043+807b4491.src.rpm)
ipa-4.9.6-10.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ipa-4.9.6-10.module_el8.5.0+2603+92118e57.src.rpm)
ipa-4.9.6-12.module_el8.5.0+2639+2137cc8f.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ipa-4.9.6-12.module_el8.5.0+2639+2137cc8f.src.rpm)
ipa-4.9.6-6.module_el8.5.0+2587+88e16a2c.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ipa-4.9.6-6.module_el8.5.0+2587+88e16a2c.src.rpm)
ipa-healthcheck-0.7-6.module_el8.5.0+2587+88e16a2c.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ipa-healthcheck-0.7-6.module_el8.5.0+2587+88e16a2c.src.rpm)
ipa-healthcheck-0.7-6.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ipa-healthcheck-0.7-6.module_el8.5.0+2603+92118e57.src.rpm)
jackson-annotations-2.10.0-1.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jackson-annotations-2.10.0-1.module_el8.5.0+2577+9e95fe00.src.rpm)
jackson-core-2.10.0-1.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jackson-core-2.10.0-1.module_el8.5.0+2577+9e95fe00.src.rpm)
jackson-databind-2.10.0-1.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jackson-databind-2.10.0-1.module_el8.5.0+2577+9e95fe00.src.rpm)
jackson-jaxrs-providers-2.9.9-1.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jackson-jaxrs-providers-2.9.9-1.module_el8.5.0+2577+9e95fe00.src.rpm)
jackson-module-jaxb-annotations-2.7.6-4.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jackson-module-jaxb-annotations-2.7.6-4.module_el8.5.0+2577+9e95fe00.src.rpm)
jakarta-commons-httpclient-3.1-28.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jakarta-commons-httpclient-3.1-28.module_el8.5.0+2577+9e95fe00.src.rpm)
javassist-3.18.1-8.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/javassist-3.18.1-8.module_el8.5.0+2577+9e95fe00.src.rpm)
jetty-9.4.30-2.v20200611.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jetty-9.4.30-2.v20200611.module_el8.3.0+2043+807b4491.src.rpm)
jsch-0.1.54-12.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jsch-0.1.54-12.module_el8.3.0+2043+807b4491.src.rpm)
jsr-305-0-0.25.20130910svn.module_el8.3.0+2039+157bd82e.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jsr-305-0-0.25.20130910svn.module_el8.3.0+2039+157bd82e.src.rpm)
jss-4.9.1-1.module_el8.5.0+2592+8eb38ccc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jss-4.9.1-1.module_el8.5.0+2592+8eb38ccc.src.rpm)
jss-4.9.1-1.module_el8.5.0+2616+5b1d191d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jss-4.9.1-1.module_el8.5.0+2616+5b1d191d.src.rpm)
junit-4.12-14.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/junit-4.12-14.module_el8.3.0+2043+807b4491.src.rpm)
junit5-5.6.2-2.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/junit5-5.6.2-2.module_el8.3.0+2043+807b4491.src.rpm)
jzlib-1.1.3-14.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/jzlib-1.1.3-14.module_el8.3.0+2043+807b4491.src.rpm)
ldapjdk-4.23.0-1.module_el8.5.0+2592+8eb38ccc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ldapjdk-4.23.0-1.module_el8.5.0+2592+8eb38ccc.src.rpm)
ldapjdk-4.23.0-1.module_el8.5.0+2616+5b1d191d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ldapjdk-4.23.0-1.module_el8.5.0+2616+5b1d191d.src.rpm)
libpmemobj-cpp-1.9-1.module_el8.4.0+2338+24dee5ba.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/libpmemobj-cpp-1.9-1.module_el8.4.0+2338+24dee5ba.src.rpm)
libserf-1.3.9-9.module_el8.4.0+2130+2150d1b0.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/libserf-1.3.9-9.module_el8.4.0+2130+2150d1b0.src.rpm)
libslirp-4.3.1-1.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/libslirp-4.3.1-1.module_el8.5.0+2567+c988d830.src.rpm)
libslirp-4.3.1-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/libslirp-4.3.1-1.module_el8.5.0+2614+87221ce8.src.rpm)
libslirp-4.3.1-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/libslirp-4.3.1-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
libzip-1.5.2-1.module_el8.3.0+2009+b272fdef.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/libzip-1.5.2-1.module_el8.3.0+2009+b272fdef.src.rpm)
libzip-1.6.1-1.module_el8.5.0+2578+cc873159.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/libzip-1.6.1-1.module_el8.5.0+2578+cc873159.src.rpm)
log4j12-1.2.17-22.module_el8.3.0+6179+5e9e3994.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/log4j12-1.2.17-22.module_el8.3.0+6179+5e9e3994.src.rpm)
lucene-8.4.1-5.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/lucene-8.4.1-5.module_el8.3.0+2043+807b4491.src.rpm)
mariadb-10.5.13-1.module_el8.5.0+2637+d11efe18.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/mariadb-10.5.13-1.module_el8.5.0+2637+d11efe18.src.rpm)
mariadb-10.5.9-1.module_el8.4.0+2357+88cd7ba1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/mariadb-10.5.9-1.module_el8.4.0+2357+88cd7ba1.src.rpm)
mod_auth_openidc-2.3.7-8.module_el8.4.0+2097+f2438af7.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/mod_auth_openidc-2.3.7-8.module_el8.4.0+2097+f2438af7.src.rpm)
nginx-1.16.1-2.module_el8.4.0+2470+68135136.1.alma.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nginx-1.16.1-2.module_el8.4.0+2470+68135136.1.alma.src.rpm)
nginx-1.18.0-3.module_el8.4.0+2472+f736ed63.1.alma.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nginx-1.18.0-3.module_el8.4.0+2472+f736ed63.1.alma.src.rpm)
nginx-1.20.0-2.module_el8.5.0+2575+1b759a19.alma.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nginx-1.20.0-2.module_el8.5.0+2575+1b759a19.alma.src.rpm)
nginx-1.20.1-1.module_el8.5.0+2611+ab304644.alma.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nginx-1.20.1-1.module_el8.5.0+2611+ab304644.alma.src.rpm)
nodejs-12.22.5-1.module_el8.4.0+2529+af52a4c7.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-12.22.5-1.module_el8.4.0+2529+af52a4c7.src.rpm)
nodejs-14.17.5-1.module_el8.4.0+2536+e2879e58.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-14.17.5-1.module_el8.4.0+2536+e2879e58.src.rpm)
nodejs-14.18.2-2.module_el8.5.0+2618+8d46dafd.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-14.18.2-2.module_el8.5.0+2618+8d46dafd.src.rpm)
nodejs-16.13.1-3.module_el8.5.0+2605+45d748af.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-16.13.1-3.module_el8.5.0+2605+45d748af.src.rpm)
nodejs-16.8.0-1.module_el8.5.0+2591+fdab02ff.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-16.8.0-1.module_el8.5.0+2591+fdab02ff.src.rpm)
nodejs-nodemon-2.0.15-1.module_el8.5.0+2605+45d748af.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-nodemon-2.0.15-1.module_el8.5.0+2605+45d748af.src.rpm)
nodejs-nodemon-2.0.15-1.module_el8.5.0+2618+8d46dafd.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-nodemon-2.0.15-1.module_el8.5.0+2618+8d46dafd.src.rpm)
nodejs-nodemon-2.0.3-1.module_el8.4.0+2521+c668cc9f.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-nodemon-2.0.3-1.module_el8.4.0+2521+c668cc9f.src.rpm)
nodejs-nodemon-2.0.3-1.module_el8.4.0+2522+3bd42762.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-nodemon-2.0.3-1.module_el8.4.0+2522+3bd42762.src.rpm)
nodejs-nodemon-2.0.7-1.module_el8.5.0+2591+fdab02ff.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-nodemon-2.0.7-1.module_el8.5.0+2591+fdab02ff.src.rpm)
nodejs-packaging-17-3.module_el8.4.0+2521+c668cc9f.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-packaging-17-3.module_el8.4.0+2521+c668cc9f.src.rpm)
nodejs-packaging-23-3.module_el8.4.0+2522+3bd42762.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-packaging-23-3.module_el8.4.0+2522+3bd42762.src.rpm)
nodejs-packaging-23-3.module_el8.5.0+2618+8d46dafd.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-packaging-23-3.module_el8.5.0+2618+8d46dafd.src.rpm)
nodejs-packaging-25-1.module_el8.5.0+2591+fdab02ff.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-packaging-25-1.module_el8.5.0+2591+fdab02ff.src.rpm)
nodejs-packaging-25-1.module_el8.5.0+2605+45d748af.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/nodejs-packaging-25-1.module_el8.5.0+2605+45d748af.src.rpm)
objectweb-asm-7.3.1-3.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/objectweb-asm-7.3.1-3.module_el8.3.0+2043+807b4491.src.rpm)
oci-seccomp-bpf-hook-1.2.0-3.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/oci-seccomp-bpf-hook-1.2.0-3.module_el8.5.0+2567+c988d830.src.rpm)
oci-seccomp-bpf-hook-1.2.0-3.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/oci-seccomp-bpf-hook-1.2.0-3.module_el8.5.0+2614+87221ce8.src.rpm)
oci-seccomp-bpf-hook-1.2.0-3.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/oci-seccomp-bpf-hook-1.2.0-3.module_el8.5.0+2636+8c48f0fc.src.rpm)
oci-systemd-hook-0.1.15-2.git2d0b8a3.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/oci-systemd-hook-0.1.15-2.git2d0b8a3.module_el8.3.0+2044+12421f43.src.rpm)
oci-umount-2.3.4-2.git87f9237.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/oci-umount-2.3.4-2.git87f9237.module_el8.3.0+2044+12421f43.src.rpm)
opendnssec-2.1.7-1.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/opendnssec-2.1.7-1.module_el8.4.0+2501+94d209c1.src.rpm)
opendnssec-2.1.7-1.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/opendnssec-2.1.7-1.module_el8.5.0+2603+92118e57.src.rpm)
opentest4j-1.2.0-2.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/opentest4j-1.2.0-2.module_el8.3.0+2043+807b4491.src.rpm)
parfait-0.5.4-2.module_el8.3.0+6179+5e9e3994.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/parfait-0.5.4-2.module_el8.3.0+6179+5e9e3994.src.rpm)
parfait-0.5.4-4.module_el8.5.0+2610+de2b8c0b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/parfait-0.5.4-4.module_el8.5.0+2610+de2b8c0b.src.rpm)
perl-5.24.4-404.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-5.24.4-404.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Algorithm-Diff-1.1903-10.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Algorithm-Diff-1.1903-10.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Algorithm-Diff-1.1903-10.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Algorithm-Diff-1.1903-10.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-App-cpanminus-1.7044-5.module_el8.3.0+2027+c8990d1d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-App-cpanminus-1.7044-5.module_el8.3.0+2027+c8990d1d.src.rpm)
perl-App-cpanminus-1.7044-5.module_el8.3.0+2079+c9af6707.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-App-cpanminus-1.7044-5.module_el8.3.0+2079+c9af6707.src.rpm)
perl-Archive-Tar-2.30-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Archive-Tar-2.30-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Archive-Tar-2.32-440.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Archive-Tar-2.32-440.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Archive-Zip-1.59-5.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Archive-Zip-1.59-5.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Archive-Zip-1.67-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Archive-Zip-1.67-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-B-Debug-1.24-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-B-Debug-1.24-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-CPAN-2.16-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-2.16-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-CPAN-2.27-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-2.27-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-CPAN-DistnameInfo-0.12-13.module_el8.3.0+2079+c9af6707.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-DistnameInfo-0.12-13.module_el8.3.0+2079+c9af6707.src.rpm)
perl-CPAN-DistnameInfo-0.12-13.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-DistnameInfo-0.12-13.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-CPAN-Meta-2.150010-397.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-Meta-2.150010-397.module_el8.1.0+6019+b22674e1.src.rpm)
perl-CPAN-Meta-2.150010-397.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-Meta-2.150010-397.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-CPAN-Meta-Check-0.014-6.module_el8.3.0+2027+c8990d1d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-Meta-Check-0.014-6.module_el8.3.0+2027+c8990d1d.src.rpm)
perl-CPAN-Meta-Check-0.014-6.module_el8.3.0+2079+c9af6707.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-Meta-Check-0.014-6.module_el8.3.0+2079+c9af6707.src.rpm)
perl-CPAN-Meta-Requirements-2.140-397.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-Meta-Requirements-2.140-397.module_el8.1.0+6019+b22674e1.src.rpm)
perl-CPAN-Meta-Requirements-2.140-397.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-Meta-Requirements-2.140-397.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-CPAN-Meta-YAML-0.018-1001.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-Meta-YAML-0.018-1001.module_el8.1.0+6019+b22674e1.src.rpm)
perl-CPAN-Meta-YAML-0.018-1001.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-CPAN-Meta-YAML-0.018-1001.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Carp-1.40-367.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Carp-1.40-367.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Carp-1.50-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Carp-1.50-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Compress-Bzip2-2.26-7.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Compress-Bzip2-2.26-7.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Compress-Bzip2-2.26-7.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Compress-Bzip2-2.26-7.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Compress-Raw-Bzip2-2.074-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Compress-Raw-Bzip2-2.074-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Compress-Raw-Bzip2-2.093-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Compress-Raw-Bzip2-2.093-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Compress-Raw-Zlib-2.074-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Compress-Raw-Zlib-2.074-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Compress-Raw-Zlib-2.093-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Compress-Raw-Zlib-2.093-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Config-Perl-V-0.27-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Config-Perl-V-0.27-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Config-Perl-V-0.32-441.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Config-Perl-V-0.32-441.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-DBD-MySQL-4.046-3.module_el8.3.0+2017+f5725bb6.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DBD-MySQL-4.046-3.module_el8.3.0+2017+f5725bb6.src.rpm)
perl-DBD-MySQL-4.046-3.module_el8.3.0+2066+72d3e39c.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DBD-MySQL-4.046-3.module_el8.3.0+2066+72d3e39c.src.rpm)
perl-DBD-Pg-3.7.4-4.module_el8.3.0+2016+c57d755d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DBD-Pg-3.7.4-4.module_el8.3.0+2016+c57d755d.src.rpm)
perl-DBD-Pg-3.7.4-4.module_el8.3.0+2073+7d8e397c.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DBD-Pg-3.7.4-4.module_el8.3.0+2073+7d8e397c.src.rpm)
perl-DBD-SQLite-1.58-2.module_el8.3.0+2012+2dd00f05.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DBD-SQLite-1.58-2.module_el8.3.0+2012+2dd00f05.src.rpm)
perl-DBD-SQLite-1.58-2.module_el8.3.0+2082+310d7fcb.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DBD-SQLite-1.58-2.module_el8.3.0+2082+310d7fcb.src.rpm)
perl-DBI-1.641-3.module_el8.3.0+2003+49275ac5.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DBI-1.641-3.module_el8.3.0+2003+49275ac5.src.rpm)
perl-DBI-1.641-3.module_el8.3.0+2055+a42b6048.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DBI-1.641-3.module_el8.3.0+2055+a42b6048.src.rpm)
perl-DB_File-1.842-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DB_File-1.842-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-DB_File-1.852-4.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-DB_File-1.852-4.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Data-Dump-1.23-7.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Data-Dump-1.23-7.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-Data-Dump-1.23-7.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Data-Dump-1.23-7.module_el8.3.0+2092+31ea7642.src.rpm)
perl-Data-Dumper-2.161-5.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Data-Dumper-2.161-5.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Data-Dumper-2.174-440.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Data-Dumper-2.174-440.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Data-OptList-0.110-7.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Data-OptList-0.110-7.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Data-OptList-0.110-7.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Data-OptList-0.110-7.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Data-Section-0.200006-9.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Data-Section-0.200006-9.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Data-Section-0.200007-8.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Data-Section-0.200007-8.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Devel-PPPort-3.36-6.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Devel-PPPort-3.36-6.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Devel-PPPort-3.56-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Devel-PPPort-3.56-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Devel-Size-0.81-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Devel-Size-0.81-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Devel-Size-0.83-3.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Devel-Size-0.83-3.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Digest-1.17-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Digest-1.17-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Digest-1.17-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Digest-1.17-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Digest-HMAC-1.03-17.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Digest-HMAC-1.03-17.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-Digest-HMAC-1.03-17.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Digest-HMAC-1.03-17.module_el8.3.0+2092+31ea7642.src.rpm)
perl-Digest-MD5-2.55-397.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Digest-MD5-2.55-397.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Digest-MD5-2.55-397.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Digest-MD5-2.55-397.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Digest-SHA-6.02-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Digest-SHA-6.02-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Digest-SHA-6.02-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Digest-SHA-6.02-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Encode-2.88-7.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Encode-2.88-7.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Encode-3.01-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Encode-3.01-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Encode-Locale-1.05-10.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Encode-Locale-1.05-10.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-Encode-Locale-1.05-10.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Encode-Locale-1.05-10.module_el8.3.0+2092+31ea7642.src.rpm)
perl-Env-1.04-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Env-1.04-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Env-1.04-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Env-1.04-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Exporter-5.72-1001.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Exporter-5.72-1001.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Exporter-5.73-440.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Exporter-5.73-440.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-ExtUtils-CBuilder-0.280225-367.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-CBuilder-0.280225-367.module_el8.1.0+6019+b22674e1.src.rpm)
perl-ExtUtils-CBuilder-0.280231-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-CBuilder-0.280231-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-ExtUtils-Install-2.04-368.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-Install-2.04-368.module_el8.1.0+6019+b22674e1.src.rpm)
perl-ExtUtils-Install-2.14-440.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-Install-2.14-440.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-ExtUtils-MakeMaker-7.24-4.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-MakeMaker-7.24-4.module_el8.1.0+6019+b22674e1.src.rpm)
perl-ExtUtils-MakeMaker-7.42-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-MakeMaker-7.42-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-ExtUtils-Manifest-1.70-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-Manifest-1.70-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-ExtUtils-Manifest-1.72-438.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-Manifest-1.72-438.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-ExtUtils-ParseXS-3.31-369.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-ParseXS-3.31-369.module_el8.1.0+6019+b22674e1.src.rpm)
perl-ExtUtils-ParseXS-3.40-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-ExtUtils-ParseXS-3.40-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-FCGI-0.78-11.module_el8.3.0+2001+ffc7987e.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-FCGI-0.78-11.module_el8.3.0+2001+ffc7987e.src.rpm)
perl-FCGI-0.78-11.module_el8.3.0+2043+244f5a46.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-FCGI-0.78-11.module_el8.3.0+2043+244f5a46.src.rpm)
perl-Fedora-VSP-0.001-10.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Fedora-VSP-0.001-10.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Fedora-VSP-0.001-10.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Fedora-VSP-0.001-10.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-File-Fetch-0.56-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Fetch-0.56-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-File-Fetch-0.56-3.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Fetch-0.56-3.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-File-HomeDir-1.00-14.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-HomeDir-1.00-14.module_el8.1.0+6019+b22674e1.src.rpm)
perl-File-HomeDir-1.004-6.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-HomeDir-1.004-6.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-File-Listing-6.04-17.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Listing-6.04-17.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-File-Listing-6.04-17.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Listing-6.04-17.module_el8.3.0+2092+31ea7642.src.rpm)
perl-File-Path-2.12-368.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Path-2.12-368.module_el8.1.0+6019+b22674e1.src.rpm)
perl-File-Path-2.16-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Path-2.16-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-File-Temp-0.230.600-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Temp-0.230.600-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-File-Temp-0.230.900-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Temp-0.230.900-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-File-Which-1.21-4.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Which-1.21-4.module_el8.1.0+6019+b22674e1.src.rpm)
perl-File-Which-1.23-4.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-Which-1.23-4.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-File-pushd-1.014-6.module_el8.3.0+2027+c8990d1d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-pushd-1.014-6.module_el8.3.0+2027+c8990d1d.src.rpm)
perl-File-pushd-1.014-6.module_el8.3.0+2079+c9af6707.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-File-pushd-1.014-6.module_el8.3.0+2079+c9af6707.src.rpm)
perl-Filter-1.58-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Filter-1.58-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Filter-1.59-440.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Filter-1.59-440.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Filter-Simple-0.92-367.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Filter-Simple-0.92-367.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Filter-Simple-0.95-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Filter-Simple-0.95-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Getopt-Long-2.49.1-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Getopt-Long-2.49.1-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Getopt-Long-2.51-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Getopt-Long-2.51-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-HTML-Parser-3.72-15.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTML-Parser-3.72-15.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-HTML-Parser-3.72-15.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTML-Parser-3.72-15.module_el8.3.0+2092+31ea7642.src.rpm)
perl-HTML-Tagset-3.20-34.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTML-Tagset-3.20-34.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-HTML-Tagset-3.20-34.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTML-Tagset-3.20-34.module_el8.3.0+2092+31ea7642.src.rpm)
perl-HTTP-Cookies-6.04-2.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Cookies-6.04-2.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-HTTP-Cookies-6.04-2.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Cookies-6.04-2.module_el8.3.0+2092+31ea7642.src.rpm)
perl-HTTP-Date-6.02-19.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Date-6.02-19.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-HTTP-Date-6.02-19.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Date-6.02-19.module_el8.3.0+2092+31ea7642.src.rpm)
perl-HTTP-Message-6.18-1.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Message-6.18-1.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-HTTP-Message-6.18-1.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Message-6.18-1.module_el8.3.0+2092+31ea7642.src.rpm)
perl-HTTP-Negotiate-6.01-19.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Negotiate-6.01-19.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-HTTP-Negotiate-6.01-19.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Negotiate-6.01-19.module_el8.3.0+2092+31ea7642.src.rpm)
perl-HTTP-Tiny-0.074-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Tiny-0.074-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-HTTP-Tiny-0.076-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-HTTP-Tiny-0.076-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-IO-Compress-2.074-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IO-Compress-2.074-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-IO-Compress-2.093-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IO-Compress-2.093-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-IO-HTML-1.001-11.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IO-HTML-1.001-11.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-IO-HTML-1.001-11.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IO-HTML-1.001-11.module_el8.3.0+2092+31ea7642.src.rpm)
perl-IO-Socket-IP-0.39-6.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IO-Socket-IP-0.39-6.module_el8.1.0+6019+b22674e1.src.rpm)
perl-IO-Socket-IP-0.39-6.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IO-Socket-IP-0.39-6.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-IO-Socket-SSL-2.066-4.module_el8.3.0+2018+449fe210.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IO-Socket-SSL-2.066-4.module_el8.3.0+2018+449fe210.src.rpm)
perl-IO-Socket-SSL-2.066-4.module_el8.3.0+2088+ac7a9534.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IO-Socket-SSL-2.066-4.module_el8.3.0+2088+ac7a9534.src.rpm)
perl-IPC-Cmd-0.98-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IPC-Cmd-0.98-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-IPC-Cmd-1.04-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IPC-Cmd-1.04-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-IPC-SysV-2.07-398.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IPC-SysV-2.07-398.module_el8.1.0+6019+b22674e1.src.rpm)
perl-IPC-SysV-2.07-398.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IPC-SysV-2.07-398.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-IPC-System-Simple-1.25-18.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IPC-System-Simple-1.25-18.module_el8.1.0+6019+b22674e1.src.rpm)
perl-IPC-System-Simple-1.25-18.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-IPC-System-Simple-1.25-18.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Importer-0.025-6.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Importer-0.025-6.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-JSON-PP-2.94000-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-JSON-PP-2.94000-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-JSON-PP-4.04-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-JSON-PP-4.04-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-LWP-MediaTypes-6.02-15.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-LWP-MediaTypes-6.02-15.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-LWP-MediaTypes-6.02-15.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-LWP-MediaTypes-6.02-15.module_el8.3.0+2092+31ea7642.src.rpm)
perl-LWP-Protocol-https-6.07-4.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-LWP-Protocol-https-6.07-4.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-LWP-Protocol-https-6.07-4.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-LWP-Protocol-https-6.07-4.module_el8.3.0+2092+31ea7642.src.rpm)
perl-Locale-Codes-3.42-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Locale-Codes-3.42-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Locale-Maketext-1.28-397.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Locale-Maketext-1.28-397.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Locale-Maketext-1.29-440.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Locale-Maketext-1.29-440.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-MIME-Base64-3.15-1001.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-MIME-Base64-3.15-1001.module_el8.1.0+6019+b22674e1.src.rpm)
perl-MIME-Base64-3.15-1001.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-MIME-Base64-3.15-1001.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-MRO-Compat-0.13-5.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-MRO-Compat-0.13-5.module_el8.1.0+6019+b22674e1.src.rpm)
perl-MRO-Compat-0.13-5.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-MRO-Compat-0.13-5.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Math-BigInt-1.9998.11-6.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Math-BigInt-1.9998.11-6.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Math-BigInt-1.9998.18-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Math-BigInt-1.9998.18-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Math-BigInt-FastCalc-0.500.600-7.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Math-BigInt-FastCalc-0.500.600-7.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Math-BigInt-FastCalc-0.500.900-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Math-BigInt-FastCalc-0.500.900-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Math-BigRat-0.2614-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Math-BigRat-0.2614-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Math-BigRat-0.2614-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Math-BigRat-0.2614-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Module-Build-0.42.24-6.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-Build-0.42.24-6.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Module-Build-0.42.29-4.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-Build-0.42.29-4.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Module-CPANfile-1.1002-7.module_el8.3.0+2027+c8990d1d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-CPANfile-1.1002-7.module_el8.3.0+2027+c8990d1d.src.rpm)
perl-Module-CPANfile-1.1002-7.module_el8.3.0+2079+c9af6707.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-CPANfile-1.1002-7.module_el8.3.0+2079+c9af6707.src.rpm)
perl-Module-CoreList-5.20180414-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-CoreList-5.20180414-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Module-CoreList-5.20191220-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-CoreList-5.20191220-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Module-Load-0.32-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-Load-0.32-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Module-Load-0.34-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-Load-0.34-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Module-Load-Conditional-0.68-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-Load-Conditional-0.68-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Module-Load-Conditional-0.70-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-Load-Conditional-0.70-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Module-Metadata-1.000033-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-Metadata-1.000033-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Module-Metadata-1.000037-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Module-Metadata-1.000037-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Mozilla-CA-20160104-7.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Mozilla-CA-20160104-7.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-Mozilla-CA-20160104-7.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Mozilla-CA-20160104-7.module_el8.3.0+2092+31ea7642.src.rpm)
perl-NTLM-1.09-17.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-NTLM-1.09-17.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-NTLM-1.09-17.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-NTLM-1.09-17.module_el8.3.0+2092+31ea7642.src.rpm)
perl-Net-HTTP-6.17-2.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Net-HTTP-6.17-2.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-Net-HTTP-6.17-2.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Net-HTTP-6.17-2.module_el8.3.0+2092+31ea7642.src.rpm)
perl-Net-SSLeay-1.88-1.module_el8.3.0+2018+449fe210.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Net-SSLeay-1.88-1.module_el8.3.0+2018+449fe210.src.rpm)
perl-Net-SSLeay-1.88-1.module_el8.3.0+2088+ac7a9534.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Net-SSLeay-1.88-1.module_el8.3.0+2088+ac7a9534.src.rpm)
perl-Object-HashBase-0.008-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Object-HashBase-0.008-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Package-Generator-1.106-12.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Package-Generator-1.106-12.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Package-Generator-1.106-12.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Package-Generator-1.106-12.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Params-Check-0.38-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Params-Check-0.38-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Params-Check-0.38-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Params-Check-0.38-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Params-Util-1.07-23.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Params-Util-1.07-23.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Params-Util-1.07-23.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Params-Util-1.07-23.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Parse-PMFile-0.41-7.module_el8.3.0+2027+c8990d1d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Parse-PMFile-0.41-7.module_el8.3.0+2027+c8990d1d.src.rpm)
perl-Parse-PMFile-0.41-7.module_el8.3.0+2079+c9af6707.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Parse-PMFile-0.41-7.module_el8.3.0+2079+c9af6707.src.rpm)
perl-PathTools-3.63-368.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-PathTools-3.63-368.module_el8.1.0+6019+b22674e1.src.rpm)
perl-PathTools-3.78-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-PathTools-3.78-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Perl-OSType-1.010-397.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Perl-OSType-1.010-397.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Perl-OSType-1.010-397.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Perl-OSType-1.010-397.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-PerlIO-via-QuotedPrint-0.08-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-PerlIO-via-QuotedPrint-0.08-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-PerlIO-via-QuotedPrint-0.08-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-PerlIO-via-QuotedPrint-0.08-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Pod-Checker-1.73-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Checker-1.73-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Pod-Checker-1.73-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Checker-1.73-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Pod-Escapes-1.07-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Escapes-1.07-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Pod-Escapes-1.07-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Escapes-1.07-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Pod-Parser-1.63-1001.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Parser-1.63-1001.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Pod-Parser-1.63-1001.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Parser-1.63-1001.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Pod-Perldoc-3.28-397.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Perldoc-3.28-397.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Pod-Perldoc-3.28.01-442.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Perldoc-3.28.01-442.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Pod-Simple-3.35-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Simple-3.35-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Pod-Simple-3.40-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Simple-3.40-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Pod-Usage-1.69-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Usage-1.69-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Pod-Usage-1.69-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Pod-Usage-1.69-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Scalar-List-Utils-1.48-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Scalar-List-Utils-1.48-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Scalar-List-Utils-1.53-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Scalar-List-Utils-1.53-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Socket-2.027-4.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Socket-2.027-4.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Socket-2.029-4.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Socket-2.029-4.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Software-License-0.103012-5.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Software-License-0.103012-5.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Software-License-0.103014-5.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Software-License-0.103014-5.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Storable-2.56-369.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Storable-2.56-369.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Storable-3.15-442.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Storable-3.15-442.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-String-ShellQuote-1.04-24.module_el8.3.0+2027+c8990d1d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-String-ShellQuote-1.04-24.module_el8.3.0+2027+c8990d1d.src.rpm)
perl-String-ShellQuote-1.04-24.module_el8.3.0+2079+c9af6707.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-String-ShellQuote-1.04-24.module_el8.3.0+2079+c9af6707.src.rpm)
perl-Sub-Exporter-0.987-16.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Sub-Exporter-0.987-16.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Sub-Exporter-0.987-16.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Sub-Exporter-0.987-16.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Sub-Install-0.928-15.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Sub-Install-0.928-15.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Sub-Install-0.928-15.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Sub-Install-0.928-15.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Sys-Syslog-0.35-398.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Sys-Syslog-0.35-398.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Sys-Syslog-0.36-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Sys-Syslog-0.36-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Term-ANSIColor-4.06-397.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Term-ANSIColor-4.06-397.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Term-ANSIColor-4.06-397.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Term-ANSIColor-4.06-397.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Term-Cap-1.17-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Term-Cap-1.17-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Term-Cap-1.17-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Term-Cap-1.17-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Term-Table-0.015-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Term-Table-0.015-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Test-Harness-3.42-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Test-Harness-3.42-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Test-Harness-3.42-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Test-Harness-3.42-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Test-Simple-1.302086-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Test-Simple-1.302086-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Test-Simple-1.302170-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Test-Simple-1.302170-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Text-Balanced-2.03-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Balanced-2.03-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Text-Balanced-2.03-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Balanced-2.03-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Text-Diff-1.44-4.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Diff-1.44-4.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Text-Diff-1.45-7.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Diff-1.45-7.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Text-Glob-0.11-5.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Glob-0.11-5.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Text-Glob-0.11-5.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Glob-0.11-5.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Text-ParseWords-3.30-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-ParseWords-3.30-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Text-ParseWords-3.30-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-ParseWords-3.30-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Text-Tabs+Wrap-2013.0523-396.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Tabs+Wrap-2013.0523-396.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Text-Template-1.47-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Template-1.47-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Text-Template-1.58-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Text-Template-1.58-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Thread-Queue-3.13-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Thread-Queue-3.13-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Thread-Queue-3.13-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Thread-Queue-3.13-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Time-HiRes-1.9753-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Time-HiRes-1.9753-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Time-HiRes-1.9760-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Time-HiRes-1.9760-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Time-Local-1.280-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Time-Local-1.280-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Time-Local-1.280-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Time-Local-1.280-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-TimeDate-2.30-15.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-TimeDate-2.30-15.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-TimeDate-2.30-15.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-TimeDate-2.30-15.module_el8.3.0+2092+31ea7642.src.rpm)
perl-Try-Tiny-0.30-7.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Try-Tiny-0.30-7.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-Try-Tiny-0.30-7.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Try-Tiny-0.30-7.module_el8.3.0+2092+31ea7642.src.rpm)
perl-URI-1.71-7.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-URI-1.71-7.module_el8.1.0+6019+b22674e1.src.rpm)
perl-URI-1.76-5.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-URI-1.76-5.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Unicode-Collate-1.20-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Unicode-Collate-1.20-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Unicode-Collate-1.27-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Unicode-Collate-1.27-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-Unicode-Normalize-1.25-1001.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Unicode-Normalize-1.25-1001.module_el8.1.0+6019+b22674e1.src.rpm)
perl-Unicode-Normalize-1.26-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-Unicode-Normalize-1.26-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-WWW-RobotRules-6.02-18.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-WWW-RobotRules-6.02-18.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-WWW-RobotRules-6.02-18.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-WWW-RobotRules-6.02-18.module_el8.3.0+2092+31ea7642.src.rpm)
perl-YAML-1.24-3.module_el8.3.0+2028+68ef8273.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-YAML-1.24-3.module_el8.3.0+2028+68ef8273.src.rpm)
perl-YAML-1.24-3.module_el8.3.0+2083+dc5fbb55.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-YAML-1.24-3.module_el8.3.0+2083+dc5fbb55.src.rpm)
perl-autodie-2.29-1001.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-autodie-2.29-1001.module_el8.1.0+6019+b22674e1.src.rpm)
perl-autodie-2.29-1001.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-autodie-2.29-1001.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-bignum-0.49-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-bignum-0.49-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-bignum-0.51-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-bignum-0.51-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-constant-1.33-1001.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-constant-1.33-1001.module_el8.1.0+6019+b22674e1.src.rpm)
perl-constant-1.33-1001.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-constant-1.33-1001.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-experimental-0.019-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-experimental-0.019-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-experimental-0.020-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-experimental-0.020-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-generators-1.10-10.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-generators-1.10-10.module_el8.1.0+6019+b22674e1.src.rpm)
perl-generators-1.11-4.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-generators-1.11-4.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-inc-latest-0.500-10.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-inc-latest-0.500-10.module_el8.1.0+6019+b22674e1.src.rpm)
perl-inc-latest-0.500-10.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-inc-latest-0.500-10.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-libnet-3.11-4.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-libnet-3.11-4.module_el8.1.0+6019+b22674e1.src.rpm)
perl-libnet-3.11-4.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-libnet-3.11-4.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-libwww-perl-6.34-1.module_el8.3.0+2020+fb59cb73.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-libwww-perl-6.34-1.module_el8.3.0+2020+fb59cb73.src.rpm)
perl-libwww-perl-6.34-1.module_el8.3.0+2092+31ea7642.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-libwww-perl-6.34-1.module_el8.3.0+2092+31ea7642.src.rpm)
perl-local-lib-2.000023-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-local-lib-2.000023-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-local-lib-2.000024-7.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-local-lib-2.000024-7.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-parent-0.237-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-parent-0.237-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-parent-0.237-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-parent-0.237-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-perlfaq-5.20180605-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-perlfaq-5.20180605-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-perlfaq-5.20191102-1.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-perlfaq-5.20191102-1.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-podlators-4.09-4.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-podlators-4.09-4.module_el8.1.0+6019+b22674e1.src.rpm)
perl-podlators-4.12-2.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-podlators-4.12-2.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-threads-2.21-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-threads-2.21-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-threads-2.22-439.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-threads-2.22-439.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-threads-shared-1.58-3.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-threads-shared-1.58-3.module_el8.1.0+6019+b22674e1.src.rpm)
perl-threads-shared-1.60-440.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-threads-shared-1.60-440.module_el8.3.0+6149+d2c5d96d.src.rpm)
perl-version-0.99.24-2.module_el8.1.0+6019+b22674e1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-version-0.99.24-2.module_el8.1.0+6019+b22674e1.src.rpm)
perl-version-0.99.24-441.module_el8.3.0+6149+d2c5d96d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/perl-version-0.99.24-441.module_el8.3.0+6149+d2c5d96d.src.rpm)
pg_repack-1.4.6-3.module_el8.5.0+2546+e924f9ed.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pg_repack-1.4.6-3.module_el8.5.0+2546+e924f9ed.src.rpm)
pg_repack-1.4.6-3.module_el8.5.0+2552+86306fc7.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pg_repack-1.4.6-3.module_el8.5.0+2552+86306fc7.src.rpm)
pg_repack-1.4.6-3.module_el8.5.0+2606+4554acc4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pg_repack-1.4.6-3.module_el8.5.0+2606+4554acc4.src.rpm)
pg_repack-1.4.6-3.module_el8.5.0+2607+8c0fd184.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pg_repack-1.4.6-3.module_el8.5.0+2607+8c0fd184.src.rpm)
pgaudit-1.4.0-5.module_el8.5.0+2552+86306fc7.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pgaudit-1.4.0-5.module_el8.5.0+2552+86306fc7.src.rpm)
pgaudit-1.4.0-5.module_el8.5.0+2606+4554acc4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pgaudit-1.4.0-5.module_el8.5.0+2606+4554acc4.src.rpm)
pgaudit-1.5.0-1.module_el8.4.0+2484+85259292.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pgaudit-1.5.0-1.module_el8.4.0+2484+85259292.src.rpm)
pgaudit-1.5.0-1.module_el8.5.0+2607+8c0fd184.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pgaudit-1.5.0-1.module_el8.5.0+2607+8c0fd184.src.rpm)
php-7.3.20-1.module_el8.3.0+2009+b272fdef.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-7.3.20-1.module_el8.3.0+2009+b272fdef.src.rpm)
php-7.4.19-1.module_el8.5.0+2578+cc873159.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-7.4.19-1.module_el8.5.0+2578+cc873159.src.rpm)
php-pear-1.10.12-1.module_el8.5.0+2578+cc873159.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pear-1.10.12-1.module_el8.5.0+2578+cc873159.src.rpm)
php-pear-1.10.9-1.module_el8.3.0+2009+b272fdef.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pear-1.10.9-1.module_el8.3.0+2009+b272fdef.src.rpm)
php-pecl-apcu-5.1.17-1.module_el8.3.0+2009+b272fdef.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pecl-apcu-5.1.17-1.module_el8.3.0+2009+b272fdef.src.rpm)
php-pecl-apcu-5.1.18-1.module_el8.5.0+2578+cc873159.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pecl-apcu-5.1.18-1.module_el8.5.0+2578+cc873159.src.rpm)
php-pecl-rrd-2.0.1-1.module_el8.3.0+2009+b272fdef.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pecl-rrd-2.0.1-1.module_el8.3.0+2009+b272fdef.src.rpm)
php-pecl-rrd-2.0.1-1.module_el8.5.0+2578+cc873159.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pecl-rrd-2.0.1-1.module_el8.5.0+2578+cc873159.src.rpm)
php-pecl-xdebug-2.8.0-1.module_el8.3.0+2009+b272fdef.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pecl-xdebug-2.8.0-1.module_el8.3.0+2009+b272fdef.src.rpm)
php-pecl-xdebug-2.9.5-1.module_el8.5.0+2578+cc873159.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pecl-xdebug-2.9.5-1.module_el8.5.0+2578+cc873159.src.rpm)
php-pecl-zip-1.15.4-1.module_el8.3.0+2009+b272fdef.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pecl-zip-1.15.4-1.module_el8.3.0+2009+b272fdef.src.rpm)
php-pecl-zip-1.18.2-1.module_el8.5.0+2578+cc873159.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/php-pecl-zip-1.18.2-1.module_el8.5.0+2578+cc873159.src.rpm)
pki-core-10.11.2-2.module_el8.5.0+2592+8eb38ccc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pki-core-10.11.2-2.module_el8.5.0+2592+8eb38ccc.src.rpm)
pki-core-10.11.2-4.module_el8.5.0+2616+5b1d191d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pki-core-10.11.2-4.module_el8.5.0+2616+5b1d191d.src.rpm)
pki-core-10.11.2-5.module_el8.5.0+2640+bc030dcc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pki-core-10.11.2-5.module_el8.5.0+2640+bc030dcc.src.rpm)
pki-servlet-engine-9.0.30-3.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pki-servlet-engine-9.0.30-3.module_el8.5.0+2577+9e95fe00.src.rpm)
pmdk-1.9.2-1.module_el8.4.0+2338+24dee5ba.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pmdk-1.9.2-1.module_el8.4.0+2338+24dee5ba.src.rpm)
podman-1.0.0-8.git921f98f.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/podman-1.0.0-8.git921f98f.module_el8.3.0+2044+12421f43.src.rpm)
podman-1.6.4-26.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/podman-1.6.4-26.module_el8.5.0+2566+ec01067b.src.rpm)
podman-1.6.4-28.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/podman-1.6.4-28.module_el8.5.0+2635+e4386a39.src.rpm)
podman-3.0.1-6.module_el8.5.0+2585+beaa716d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/podman-3.0.1-6.module_el8.5.0+2585+beaa716d.src.rpm)
podman-3.0.1-7.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/podman-3.0.1-7.module_el8.5.0+2614+87221ce8.src.rpm)
podman-3.0.1-8.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/podman-3.0.1-8.module_el8.5.0+2636+8c48f0fc.src.rpm)
postgres-decoderbufs-0.10.0-2.module_el8.4.0+2484+85259292.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgres-decoderbufs-0.10.0-2.module_el8.4.0+2484+85259292.src.rpm)
postgres-decoderbufs-0.10.0-2.module_el8.5.0+2552+86306fc7.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgres-decoderbufs-0.10.0-2.module_el8.5.0+2552+86306fc7.src.rpm)
postgres-decoderbufs-0.10.0-2.module_el8.5.0+2606+4554acc4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgres-decoderbufs-0.10.0-2.module_el8.5.0+2606+4554acc4.src.rpm)
postgres-decoderbufs-0.10.0-2.module_el8.5.0+2607+8c0fd184.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgres-decoderbufs-0.10.0-2.module_el8.5.0+2607+8c0fd184.src.rpm)
postgresql-12.7-2.module_el8.5.0+2552+86306fc7.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgresql-12.7-2.module_el8.5.0+2552+86306fc7.src.rpm)
postgresql-12.9-1.module_el8.5.0+2606+4554acc4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgresql-12.9-1.module_el8.5.0+2606+4554acc4.src.rpm)
postgresql-13.3-2.module_el8.5.0+2546+e924f9ed.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgresql-13.3-2.module_el8.5.0+2546+e924f9ed.src.rpm)
postgresql-13.5-1.module_el8.5.0+2607+8c0fd184.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgresql-13.5-1.module_el8.5.0+2607+8c0fd184.src.rpm)
postgresql-9.6.22-1.module_el8.4.0+2479+beebcf7e.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/postgresql-9.6.22-1.module_el8.4.0+2479+beebcf7e.src.rpm)
python-jwcrypto-0.5.0-1.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-jwcrypto-0.5.0-1.module_el8.4.0+2501+94d209c1.src.rpm)
python-jwcrypto-0.5.0-1.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-jwcrypto-0.5.0-1.module_el8.5.0+2603+92118e57.src.rpm)
python-kdcproxy-0.4-5.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-kdcproxy-0.4-5.module_el8.4.0+2501+94d209c1.src.rpm)
python-kdcproxy-0.4-5.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-kdcproxy-0.4-5.module_el8.5.0+2603+92118e57.src.rpm)
python-nss-1.0.1-10.module_el8.5.0+2577+9e95fe00.alma.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-nss-1.0.1-10.module_el8.5.0+2577+9e95fe00.alma.src.rpm)
python-podman-api-1.2.0-0.2.gitd0a45fe.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-podman-api-1.2.0-0.2.gitd0a45fe.module_el8.5.0+2566+ec01067b.src.rpm)
python-podman-api-1.2.0-0.2.gitd0a45fe.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-podman-api-1.2.0-0.2.gitd0a45fe.module_el8.5.0+2635+e4386a39.src.rpm)
python-qrcode-5.1-12.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-qrcode-5.1-12.module_el8.4.0+2501+94d209c1.src.rpm)
python-qrcode-5.1-12.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-qrcode-5.1-12.module_el8.5.0+2603+92118e57.src.rpm)
python-yubico-1.3.2-9.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-yubico-1.3.2-9.module_el8.4.0+2501+94d209c1.src.rpm)
python-yubico-1.3.2-9.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/python-yubico-1.3.2-9.module_el8.5.0+2603+92118e57.src.rpm)
pyusb-1.0.0-9.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pyusb-1.0.0-9.module_el8.4.0+2501+94d209c1.src.rpm)
pyusb-1.0.0-9.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/pyusb-1.0.0-9.module_el8.5.0+2603+92118e57.src.rpm)
redis-6.0.9-5.module_el8.4.0+2584+1bb0d2aa.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/redis-6.0.9-5.module_el8.4.0+2584+1bb0d2aa.src.rpm)
relaxngDatatype-2011.1-7.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/relaxngDatatype-2011.1-7.module_el8.5.0+2577+9e95fe00.src.rpm)
resteasy-3.0.26-6.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/resteasy-3.0.26-6.module_el8.5.0+2577+9e95fe00.src.rpm)
ruby-2.6.7-107.module_el8.4.0+2507+bbd85cce.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ruby-2.6.7-107.module_el8.4.0+2507+bbd85cce.src.rpm)
ruby-2.6.9-108.module_el8.5.0+2623+08a8ba32.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ruby-2.6.9-108.module_el8.5.0+2623+08a8ba32.src.rpm)
ruby-2.7.4-137.module_el8.4.0+2515+f744ca41.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ruby-2.7.4-137.module_el8.4.0+2515+f744ca41.src.rpm)
ruby-3.0.2-140.module_el8.5.0+2595+0c654ebc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/ruby-3.0.2-140.module_el8.5.0+2595+0c654ebc.src.rpm)
rubygem-abrt-0.3.0-4.module_el8.1.0+6018+ce4da579.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-abrt-0.3.0-4.module_el8.1.0+6018+ce4da579.src.rpm)
rubygem-abrt-0.3.0-4.module_el8.5.0+2623+08a8ba32.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-abrt-0.3.0-4.module_el8.5.0+2623+08a8ba32.src.rpm)
rubygem-abrt-0.4.0-1.module_el8.3.0+6147+d0dfc1e4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-abrt-0.4.0-1.module_el8.3.0+6147+d0dfc1e4.src.rpm)
rubygem-abrt-0.4.0-1.module_el8.5.0+2595+0c654ebc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-abrt-0.4.0-1.module_el8.5.0+2595+0c654ebc.src.rpm)
rubygem-bson-4.5.0-1.module_el8.1.0+6018+ce4da579.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-bson-4.5.0-1.module_el8.1.0+6018+ce4da579.src.rpm)
rubygem-bson-4.5.0-1.module_el8.5.0+2623+08a8ba32.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-bson-4.5.0-1.module_el8.5.0+2623+08a8ba32.src.rpm)
rubygem-bson-4.8.1-1.module_el8.3.0+6147+d0dfc1e4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-bson-4.8.1-1.module_el8.3.0+6147+d0dfc1e4.src.rpm)
rubygem-mongo-2.11.3-1.module_el8.3.0+6147+d0dfc1e4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-mongo-2.11.3-1.module_el8.3.0+6147+d0dfc1e4.src.rpm)
rubygem-mongo-2.8.0-1.module_el8.1.0+6018+ce4da579.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-mongo-2.8.0-1.module_el8.1.0+6018+ce4da579.src.rpm)
rubygem-mongo-2.8.0-1.module_el8.5.0+2623+08a8ba32.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-mongo-2.8.0-1.module_el8.5.0+2623+08a8ba32.src.rpm)
rubygem-mysql2-0.5.2-1.module_el8.1.0+6018+ce4da579.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-mysql2-0.5.2-1.module_el8.1.0+6018+ce4da579.src.rpm)
rubygem-mysql2-0.5.2-1.module_el8.5.0+2623+08a8ba32.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-mysql2-0.5.2-1.module_el8.5.0+2623+08a8ba32.src.rpm)
rubygem-mysql2-0.5.3-1.module_el8.3.0+6147+d0dfc1e4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-mysql2-0.5.3-1.module_el8.3.0+6147+d0dfc1e4.src.rpm)
rubygem-mysql2-0.5.3-1.module_el8.5.0+2595+0c654ebc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-mysql2-0.5.3-1.module_el8.5.0+2595+0c654ebc.src.rpm)
rubygem-pg-1.1.4-1.module_el8.1.0+6018+ce4da579.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-pg-1.1.4-1.module_el8.1.0+6018+ce4da579.src.rpm)
rubygem-pg-1.1.4-1.module_el8.5.0+2623+08a8ba32.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-pg-1.1.4-1.module_el8.5.0+2623+08a8ba32.src.rpm)
rubygem-pg-1.2.3-1.module_el8.3.0+6147+d0dfc1e4.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-pg-1.2.3-1.module_el8.3.0+6147+d0dfc1e4.src.rpm)
rubygem-pg-1.2.3-1.module_el8.5.0+2595+0c654ebc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/rubygem-pg-1.2.3-1.module_el8.5.0+2595+0c654ebc.src.rpm)
runc-1.0.0-56.rc5.dev.git2abd837.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/runc-1.0.0-56.rc5.dev.git2abd837.module_el8.3.0+2044+12421f43.src.rpm)
runc-1.0.0-66.rc10.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/runc-1.0.0-66.rc10.module_el8.5.0+2566+ec01067b.src.rpm)
runc-1.0.0-66.rc10.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/runc-1.0.0-66.rc10.module_el8.5.0+2635+e4386a39.src.rpm)
runc-1.0.0-72.rc92.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/runc-1.0.0-72.rc92.module_el8.5.0+2567+c988d830.src.rpm)
runc-1.0.0-72.rc92.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/runc-1.0.0-72.rc92.module_el8.5.0+2614+87221ce8.src.rpm)
runc-1.0.0-73.rc95.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/runc-1.0.0-73.rc95.module_el8.5.0+2636+8c48f0fc.src.rpm)
sat4j-2.3.5-19.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/sat4j-2.3.5-19.module_el8.3.0+2043+807b4491.src.rpm)
si-units-0.6.5-2.module_el8.3.0+6179+5e9e3994.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/si-units-0.6.5-2.module_el8.3.0+6179+5e9e3994.src.rpm)
si-units-0.6.5-2.module_el8.5.0+2610+de2b8c0b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/si-units-0.6.5-2.module_el8.5.0+2610+de2b8c0b.src.rpm)
skopeo-0.1.32-6.git1715c90.module_el8.4.0+2478+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/skopeo-0.1.32-6.git1715c90.module_el8.4.0+2478+12421f43.src.rpm)
skopeo-0.1.41-4.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/skopeo-0.1.41-4.module_el8.5.0+2566+ec01067b.src.rpm)
skopeo-0.1.41-4.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/skopeo-0.1.41-4.module_el8.5.0+2635+e4386a39.src.rpm)
skopeo-1.2.2-10.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/skopeo-1.2.2-10.module_el8.5.0+2567+c988d830.src.rpm)
skopeo-1.2.4-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/skopeo-1.2.4-1.module_el8.5.0+2614+87221ce8.src.rpm)
skopeo-1.2.4-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/skopeo-1.2.4-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
slapi-nis-0.56.6-4.module_el8.5.0+2587+88e16a2c.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slapi-nis-0.56.6-4.module_el8.5.0+2587+88e16a2c.src.rpm)
slapi-nis-0.56.6-4.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slapi-nis-0.56.6-4.module_el8.5.0+2603+92118e57.src.rpm)
slf4j-1.7.25-4.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slf4j-1.7.25-4.module_el8.5.0+2577+9e95fe00.src.rpm)
slirp4netns-0.1-5.dev.gitc4e1bc5.module_el8.3.0+2044+12421f43.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slirp4netns-0.1-5.dev.gitc4e1bc5.module_el8.3.0+2044+12421f43.src.rpm)
slirp4netns-0.4.2-3.git21fdece.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slirp4netns-0.4.2-3.git21fdece.module_el8.5.0+2566+ec01067b.src.rpm)
slirp4netns-0.4.2-3.git21fdece.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slirp4netns-0.4.2-3.git21fdece.module_el8.5.0+2635+e4386a39.src.rpm)
slirp4netns-1.1.8-1.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slirp4netns-1.1.8-1.module_el8.5.0+2567+c988d830.src.rpm)
slirp4netns-1.1.8-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slirp4netns-1.1.8-1.module_el8.5.0+2614+87221ce8.src.rpm)
slirp4netns-1.1.8-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/slirp4netns-1.1.8-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
softhsm-2.6.0-5.module_el8.4.0+2501+94d209c1.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/softhsm-2.6.0-5.module_el8.4.0+2501+94d209c1.src.rpm)
softhsm-2.6.0-5.module_el8.5.0+2603+92118e57.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/softhsm-2.6.0-5.module_el8.5.0+2603+92118e57.src.rpm)
stax-ex-1.7.7-8.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/stax-ex-1.7.7-8.module_el8.5.0+2577+9e95fe00.src.rpm)
subversion-1.14.1-1.module_el8.4.0+2130+2150d1b0.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/subversion-1.14.1-1.module_el8.4.0+2130+2150d1b0.src.rpm)
swig-4.0.2-3.module_el8.4.0+2100+4bdcb5c6.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/swig-4.0.2-3.module_el8.4.0+2100+4bdcb5c6.src.rpm)
tomcatjss-7.7.0-1.module_el8.5.0+2592+8eb38ccc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/tomcatjss-7.7.0-1.module_el8.5.0+2592+8eb38ccc.src.rpm)
tomcatjss-7.7.0-1.module_el8.5.0+2616+5b1d191d.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/tomcatjss-7.7.0-1.module_el8.5.0+2616+5b1d191d.src.rpm)
toolbox-0.0.7-1.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/toolbox-0.0.7-1.module_el8.5.0+2566+ec01067b.src.rpm)
toolbox-0.0.7-1.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/toolbox-0.0.7-1.module_el8.5.0+2635+e4386a39.src.rpm)
toolbox-0.0.99-1.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/toolbox-0.0.99-1.module_el8.5.0+2567+c988d830.src.rpm)
toolbox-0.0.99.3-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/toolbox-0.0.99.3-1.module_el8.5.0+2614+87221ce8.src.rpm)
toolbox-0.0.99.3-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/toolbox-0.0.99.3-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
udica-0.2.1-2.module_el8.5.0+2566+ec01067b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/udica-0.2.1-2.module_el8.5.0+2566+ec01067b.src.rpm)
udica-0.2.1-2.module_el8.5.0+2635+e4386a39.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/udica-0.2.1-2.module_el8.5.0+2635+e4386a39.src.rpm)
udica-0.2.4-1.module_el8.5.0+2567+c988d830.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/udica-0.2.4-1.module_el8.5.0+2567+c988d830.src.rpm)
udica-0.2.4-1.module_el8.5.0+2614+87221ce8.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/udica-0.2.4-1.module_el8.5.0+2614+87221ce8.src.rpm)
udica-0.2.4-1.module_el8.5.0+2636+8c48f0fc.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/udica-0.2.4-1.module_el8.5.0+2636+8c48f0fc.src.rpm)
unit-api-1.0-5.module_el8.3.0+6179+5e9e3994.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/unit-api-1.0-5.module_el8.3.0+6179+5e9e3994.src.rpm)
unit-api-1.0-5.module_el8.5.0+2610+de2b8c0b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/unit-api-1.0-5.module_el8.5.0+2610+de2b8c0b.src.rpm)
univocity-parsers-2.8.4-3.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/univocity-parsers-2.8.4-3.module_el8.3.0+2043+807b4491.src.rpm)
uom-lib-1.0.1-6.module_el8.3.0+6179+5e9e3994.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/uom-lib-1.0.1-6.module_el8.3.0+6179+5e9e3994.src.rpm)
uom-lib-1.0.1-6.module_el8.5.0+2610+de2b8c0b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/uom-lib-1.0.1-6.module_el8.5.0+2610+de2b8c0b.src.rpm)
uom-parent-1.0.3-3.module_el8.3.0+6179+5e9e3994.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/uom-parent-1.0.3-3.module_el8.3.0+6179+5e9e3994.src.rpm)
uom-parent-1.0.3-3.module_el8.5.0+2610+de2b8c0b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/uom-parent-1.0.3-3.module_el8.5.0+2610+de2b8c0b.src.rpm)
uom-se-1.0.4-3.module_el8.3.0+6179+5e9e3994.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/uom-se-1.0.4-3.module_el8.3.0+6179+5e9e3994.src.rpm)
uom-se-1.0.4-3.module_el8.5.0+2610+de2b8c0b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/uom-se-1.0.4-3.module_el8.5.0+2610+de2b8c0b.src.rpm)
uom-systems-0.7-1.module_el8.3.0+6179+5e9e3994.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/uom-systems-0.7-1.module_el8.3.0+6179+5e9e3994.src.rpm)
uom-systems-0.7-1.module_el8.5.0+2610+de2b8c0b.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/uom-systems-0.7-1.module_el8.5.0+2610+de2b8c0b.src.rpm)
utf8proc-2.1.1-5.module_el8.4.0+2130+2150d1b0.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/utf8proc-2.1.1-5.module_el8.4.0+2130+2150d1b0.src.rpm)
velocity-1.7-24.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/velocity-1.7-24.module_el8.5.0+2577+9e95fe00.src.rpm)
xalan-j2-2.7.1-38.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xalan-j2-2.7.1-38.module_el8.5.0+2577+9e95fe00.src.rpm)
xerces-j2-2.11.0-34.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xerces-j2-2.11.0-34.module_el8.5.0+2577+9e95fe00.src.rpm)
xml-commons-apis-1.4.01-25.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xml-commons-apis-1.4.01-25.module_el8.5.0+2577+9e95fe00.src.rpm)
xml-commons-apis-1.4.01-31.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xml-commons-apis-1.4.01-31.module_el8.3.0+2043+807b4491.src.rpm)
xml-commons-resolver-1.2-26.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xml-commons-resolver-1.2-26.module_el8.5.0+2577+9e95fe00.src.rpm)
xmlgraphics-commons-2.3-4.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xmlgraphics-commons-2.3-4.module_el8.3.0+2043+807b4491.src.rpm)
xmlstreambuffer-1.5.4-8.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xmlstreambuffer-1.5.4-8.module_el8.5.0+2577+9e95fe00.src.rpm)
xsom-0-19.20110809svn.module_el8.5.0+2577+9e95fe00.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xsom-0-19.20110809svn.module_el8.5.0+2577+9e95fe00.src.rpm)
xz-java-1.8-8.module_el8.3.0+2043+807b4491.src.rpm (appstream-source,http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/xz-java-1.8-8.module_el8.3.0+2043+807b4491.src.rpm)
Cython-0.29.21-5.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/Cython-0.29.21-5.module_el8.5.0+2574+e91fd823.src.rpm)
asio-1.10.8-7.module_el8.1.0+6015+efe6ed09.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/asio-1.10.8-7.module_el8.1.0+6015+efe6ed09.src.rpm)
byaccj-1.15-17.module_el8.0.0+6004+2fc32706.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/byaccj-1.15-17.module_el8.0.0+6004+2fc32706.src.rpm)
pybind11-2.6.1-2.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/pybind11-2.6.1-2.module_el8.5.0+2574+e91fd823.src.rpm)
pytest-4.6.6-3.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/pytest-4.6.6-3.module_el8.4.0+2510+cb4d423d.src.rpm)
pytest-6.0.2-2.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/pytest-6.0.2-2.module_el8.5.0+2574+e91fd823.src.rpm)
python-atomicwrites-1.3.0-8.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-atomicwrites-1.3.0-8.module_el8.4.0+2510+cb4d423d.src.rpm)
python-attrs-19.3.0-3.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-attrs-19.3.0-3.module_el8.4.0+2510+cb4d423d.src.rpm)
python-attrs-20.3.0-2.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-attrs-20.3.0-2.module_el8.5.0+2574+e91fd823.src.rpm)
python-iniconfig-1.1.1-2.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-iniconfig-1.1.1-2.module_el8.5.0+2574+e91fd823.src.rpm)
python-more-itertools-7.2.0-5.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-more-itertools-7.2.0-5.module_el8.4.0+2510+cb4d423d.src.rpm)
python-more-itertools-8.5.0-2.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-more-itertools-8.5.0-2.module_el8.5.0+2574+e91fd823.src.rpm)
python-packaging-19.2-3.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-packaging-19.2-3.module_el8.4.0+2510+cb4d423d.src.rpm)
python-packaging-20.4-4.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-packaging-20.4-4.module_el8.5.0+2574+e91fd823.src.rpm)
python-pluggy-0.13.0-3.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-pluggy-0.13.0-3.module_el8.4.0+2510+cb4d423d.src.rpm)
python-pluggy-0.13.1-3.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-pluggy-0.13.1-3.module_el8.5.0+2574+e91fd823.src.rpm)
python-py-1.10.0-1.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-py-1.10.0-1.module_el8.5.0+2574+e91fd823.src.rpm)
python-py-1.8.0-8.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-py-1.8.0-8.module_el8.4.0+2510+cb4d423d.src.rpm)
python-wcwidth-0.1.7-16.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-wcwidth-0.1.7-16.module_el8.4.0+2510+cb4d423d.src.rpm)
python-wcwidth-0.2.5-3.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python-wcwidth-0.2.5-3.module_el8.5.0+2574+e91fd823.src.rpm)
python3x-pyparsing-2.4.5-3.module_el8.4.0+2510+cb4d423d.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python3x-pyparsing-2.4.5-3.module_el8.4.0+2510+cb4d423d.src.rpm)
python3x-pyparsing-2.4.7-5.module_el8.5.0+2574+e91fd823.src.rpm (powertools-source,http://mirror.almalinux.ikoula.com/8/PowerTools/Source/Packages/python3x-pyparsing-2.4.7-5.module_el8.5.0+2574+e91fd823.src.rpm)
Tags:
Steps To Reproduce: e.g. For "perl-DBD-SQLite":

$ sudo dnf search -v --enablerepo="*-source" perl-DBD-SQLite

=================================================================================================== Name Exactly Matched: perl-DBD-SQLite ===================================================================================================
perl-DBD-SQLite.x86_64 : SQLite DBI Driver
Repo : appstream
Matched from:
Provide : perl-DBD-SQLite = 1.58-2.module_el8.3.0+2074+0df5c3bb

perl-DBD-SQLite.src : SQLite DBI Driver
Repo : appstream-source
Matched from:
Other : perl-DBD-SQLite


$ sudo dnf search -v --repo baseos-source perl-DBD-SQLite
...
=================================================================================================== Name Exactly Matched: perl-DBD-SQLite ===================================================================================================
perl-DBD-SQLite.src : SQLite DBI Driver
Repo : baseos-source
Matched from:
Other : perl-DBD-SQLite

The package used in AlmaLinux coming from repo "appstream" but a source package is present in repo "baseos-source" providing nothing.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
229 [AlmaLinux-8] -OTHER minor always 2022-05-05 09:01 2022-05-05 09:01
Reporter: ronan Platform: AlmaLinux  
Assigned To: OS: Linux  
Priority: normal OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Can't find RPM source
Description: Some rpm src can't be find in AlmaLinux in the usual way.

e.g.: aopalliance
Tags:
Steps To Reproduce:
Let's take a working package: ansible-pcp
#sudo dnf search -v --enablerepo="*-source" ansible-pcp
===================================================================================================== Name Exactly Matched: ansible-pcp =====================================================================================================
ansible-pcp.noarch : Ansible Metric collection for Performance Co-Pilot
Repo : appstream
Matched from:
Provide : ansible-pcp = 2.2.1-1.el8

ansible-pcp.src : Ansible Metric collection for Performance Co-Pilot
Repo : appstream-source
Matched from:
Other : ansible-pcp

But with aopalliance
#sudo dnf search -v --enablerepo="*-source" aopalliance
===================================================================================================== Name Exactly Matched: aopalliance =====================================================================================================
aopalliance.noarch : Java/J2EE AOP standards
Repo : appstream
Matched from:
Provide : aopalliance = 1.0-17.module_el8.0.0+6035+97aff910

But if you query the specific repo you've got:
#sudo dnf search -v --repo appstream-source aopalliance
==================================================================================================== Name Exactly Matched: aopalliance =====================================================================================================
aopalliance.src : Java/J2EE AOP standards
Repo : appstream-source
Matched from:
Other : aopalliance


Note:
1) The package is in source repository
http://mirror.almalinux.ikoula.com/8/AppStream/Source/Packages/

2) The primary.xml.gz is OK
http://mirror.almalinux.ikoula.com/8/AppStream/Source/repodata/

3) It's not comming from dnf (same result with dnf from fedora)

4) The same command work in fedora and centos



Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
228 [AlmaLinux-8] nginx minor always 2022-05-05 04:13 2022-05-05 04:13
Reporter: davidlai Platform:  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: nginx config file has a typo
Description: Minor issue

After installing nginx, there is a config file /etc/nginx/nginx.conf. At approx line 50 is:

        error_page 404 /404.html;
            location = /40x.html {
        }

I believe this is a typo there, the /40x.html should be /404.html

I think the correct lines should read:

        error_page 404 /404.html;
            location = /404.html {
        }

I suspect this problem is introduced upstream of Alma, but downstream of Nginx. Possibly a typo introduced by Redhat?
Tags:
Steps To Reproduce: Just install nginx
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
227 [AlmaLinux-8] systemd major always 2022-05-05 01:44 2022-05-05 01:45
Reporter: m4 Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: System will not boot if raid goes into degraded mode while system is down, and "root" is not physically on those drives.
Description: If a raid1 (or other) that is not on the physical disks that 'root' is on, goes degraded while system is powered down -- and it is required for system to run (/etc/fstab listed), the system goes into dracut emergency mode, and "mdadm -R /dev/mdXYZ" needs to be run manually.

If both the root disk(s) and a raid on a non-root physical disk goes degraded at the same time -- then "perhaps" both will go into degraded mode.

See Additional information.
Tags:
Steps To Reproduce: System testing setup:
1) root raid1 on two SAS disks (sda/sdb ) and other raids on those too (home,var,etc.).
2) two other disks with a required (/etc/fstab) raid1 - say /media/private_date, lets say /dev/nvme0n1p1, and nvme1n1p1.
Test cases to see if system runs with disks degraded:
A) system running:
    a) unplug one SAS. cat /proc/mdstat, etc. Plug it back in. Fix if needed via mdadm. Repeat with other.
    b) unplug one NVMe. Etc. per "a)".
B) Everything running nicely, powerdown:
   c) unplug one SAS. Power up, etc.
   d) everything is running nicely, then power down, unplug one NVMe. Power up, etc.

With B)d) - the system will go into dracut emergency recovery mode - every time. Remember to have system running nicely before powerdown. :)
Additional Information: When root from initramfs layout is running and it is looking for the 'real root', the various raids are discovered, and systemd rules cause "mdadm -I /dev/ABCDWYXZ --export to be run" the first (and only FIRST) time that a software raid is created, which sets up a last-resort timer in case all members of the raid are not present -- while continuing to process udev devices to find disks/partitions. As soon as "root" is found and active (could be degraded when system went down, which is no different that having all disks present), the real root is setup for pivot root, systemd is taken down, the pivot root occurs, and at this time all the last-resort timers outstanding are lost. The real systemd starts and redoes the device discovery udev stuff -- but, any raid already known to the kernel already (root is important!), no last-resort timers are set.

Any raid on the same physical devices as the root raid, "may" (most likely) will already have all it's devices found and last-resort timers will have gone off -- if one goes off for root. With the long time for a raid to become active -- most likely those raids are also active.

Continuing thought process (ignoring side tracking paragraph above), when systemd is busy processing /etc/fstab for mounting file systems (asynchronously), everything is nice -- except for the mandatory raid that went into degraded mode while powered off. There is no last-resort timer to go off, and it will sit there inactive.

I am attaching a work-around. Possible fixes: 1) clean out all md raids from kernel data structures (except root -- nested raids, etc. present complexity) when systemd goes down to restart up on the real root file system. 2) copy the last-resort timers into the real root structure before shutting systemd down -- and make sure they will still be run when the real systemd comes up. 3) Always have mdadm --export return the environment style variables -- not just when a /dev/mdXYZ is created for the first device found. 4) Eliminate the use of initramfs and taking systemd down and replaying the device discovery (udev) process.

I don't know, all of this is convoluted ... and I expect other similar situations exist with all the messiness involved.
Attached Files: 65-md-incremental.rules (3,840 bytes) 2022-05-05 01:44
https://bugs.almalinux.org/file_download.php?file_id=129&type=bug
dracut.conf (207 bytes) 2022-05-05 01:44
https://bugs.almalinux.org/file_download.php?file_id=130&type=bug
md-run-timer (728 bytes) 2022-05-05 01:44
https://bugs.almalinux.org/file_download.php?file_id=131&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
225 [AlmaLinux-8] -OTHER minor always 2022-04-29 23:45 2022-04-29 23:45
Reporter: grandparoach Platform: Azure  
Assigned To: OS: almalinux-hpc  
Priority: normal OS Version: 8_5-hpc-gen2  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: The Azure Marketplace image for the almalinux-hpc 8_5-gen2 is missing the NFS Utilities
Description: The Azure Marketplace image for almalinux-hpc 8_5-hpc-gen2 is missing the NFS Utilities.
There are so many other things which are pre-installed on this image, it would be much more convenient if the NFS Utilities were pre-installed as well.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
190 [AlmaLinux-8] selinux-policy major always 2022-02-22 15:04 2022-04-29 10:07
Reporter: Blackclaws Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: k3s selinux not working on Almalinux
Description: The k3s selinux package does not work correctly on Almalinux in contrast to CentOS 8.5.

By my understanding this should work out of the box as Almalinux is more or less a drop in replacement. Is this something the package has to address or is this something that Almalinux has to address?

There is a related bug on github:

https://github.com/k3s-io/k3s-selinux/issues/27
Tags:
Steps To Reproduce: See github bug.
Additional Information: Works on CentOS 8.5 not tested on RHEL so far
Attached Files:
Notes
(0000496)
Blackclaws   
2022-02-22 15:06   
The reason why I classified this as major is because the update to Almalinux 8.5 broke my k3s cluster due to this issue. I had to deactivate SELinux in the meantime to resolve.

As stated above it might not actually be Almalinux fault but I don't understand enough about how the policy systems might differ to correctly pin down the source of the problem.
(0000523)
srbala   
2022-03-26 10:48   
@Blackclaws, GitHub issue indicates that this has been resolved on package update. Please verify.
(0000550)
Blackclaws   
2022-04-29 10:07   
Unfortunately that doesn't seem to be the case. I still need to run with setenforce 0 in order to be able to run most containers.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
221 [AlmaLinux-8] dnf block always 2022-04-26 16:22 2022-04-29 08:57
Reporter: thony62410 Platform: Google cloud plateform  
Assigned To: OS: AlmaLinux  
Priority: high OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: TLS problem when i use DNF
Description: Hello,

We encounter a problem during a fresh deployment of alma linux with openssl, I specify that we use the image provided on the Google marcketplace, it seems that there is a problem with the ciphers configured on openssl, i have this error when we try to update the server with dnf:

[root@admny1ano01 ssl]# dnf update
AlmaLinux 8 - BaseOS 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'baseos':
  - Curl error (35): SSL connect error for https://mirrors.almalinux.org/mirrorlist/8/baseos [OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mirrors.almalinux.org:443 ]
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: Curl error (35): SSL connect error for https://mirrors.almalinux.org/mirrorlist/8/baseos [OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mirrors.almalinux.org:443 ]

When i try to pass an connection with openssl, i have this error:

SSL_connect:SSLv3/TLS write client hello
read from 0x55ef7f703ea0 [0x55ef7f70e723] (5 bytes => -1 (0xFFFFFFFFFFFFFFFF))
SSL_connect:error in SSLv3/TLS write client hello
write:errno=104



I have also the problem with an other site and curl command(i think that it's du to openssl) :

[root@admny1ano01 ssl]# curl https://rpmfind.net/linux/RPM/centos/8-stream/appstream/x86_64/Packages/bind-utils-9.11.36-3.el8.x86_64.html --output bind-utils-9.11.36-3.el8.x86_64.rpm
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to rpmfind.net:443


Thanks a lot for your time.
Regards

Tags: cloud, gcp
Steps To Reproduce: dnf update or curl command...
Additional Information: nss-3.67.0-7.el8_5.x86_64


[root@admny1ano01 ssl]# curl --version
curl 7.61.1 (x86_64-redhat-linux-gnu) libcurl/7.61.1 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.6 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.2.0) libssh/0.9.4/openssl/zlib nghttp2/1.33.0


uname -a
Linux admny1ano01.nl.gcp.dktinfra.cloud 4.18.0-348.20.1.el8_5.x86_64 #1 SMP Thu Mar 10 11:31:47 EST 2022 x86_64 x86_64 x86_64 GNU/Linux
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
222 [AlmaLinux-8] openldap feature always 2022-04-26 17:46 2022-04-26 17:46
Reporter: jeriedel24 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Request for package openldap-servers to be added to the repository
Description: Our software developers need an installation of OpenLDAP server (in addition to 389-ds server) for their unit tests, because they have to test their LDAP client software against both kinds of LDAP server.
Would it be possible that you add the package openldap-servers to the AlmaLinux repository? The version of openldap-servers should match the version of the packages openldap and openldap-clients that are part of AlmaLinux.
Tags:
Steps To Reproduce:
Additional Information: The package openldap-servers is available in RockyLinux 8 (in the "plus" repository) and in CentOS 8.5 and in Centos 8-stream (in the "PowerTools" repository).
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
102 [AlmaLinux-8] NetworkManager major always 2021-06-20 17:53 2022-04-26 08:50
Reporter: adontz Platform: AWS  
Assigned To: lkhn OS: AlmaLinux  
Priority: normal OS Version: 8.4  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 8.4  
    Target Version:  
abrt_hash:
URL:
Summary: Incorrect SELinux label on /etc/sysconfig/network-scripts/ifcfg-eth0
Description: Incorrect SELinux label on

    /etc/sysconfig/network-scripts/ifcfg-eth0

which is "system_u:object_r:unlabeled_t:s0" instead of "system_u:object_r:net_conf_t:s0" renders nmcli unusable.
Try to update connection configuration logs similar error message

NetworkManager[783]: <info> [1624210442.3384] audit: op="connection-update" uuid="5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03" name="eth0" args="ipv4.dns-search,connection.timestamp" pid=9325 uid=0 result="fail" reason="failed to update connection: Could not open file '/etc/sysconfig/network-scripts/ifcfg-eth0' for writing: Permission denied"
Tags:
Steps To Reproduce: Execute

    nmcli connection modify "eth0" ipv4.dns-search 'example.com'

on a a fresh AWS image.
Additional Information: Executing

    chcon -t net_conf_t /etc/sysconfig/network-scripts/ifcfg*

completely fixes the problem.
Attached Files:
Notes
(0000295)
alukoshko   
2021-06-30 18:58   
Hello and thank you! Nice catch.
We are investigating it.
(0000298)
ezamriy   
2021-07-05 21:22   
The problem is confirmed. I've created a GitHub issue https://github.com/AlmaLinux/cloud-images/issues/23 for it and wrote up my investigation results. We need to change our build pipeline to avoid Amazon's vmimport execution.
(0000549)
lkhn   
2022-04-26 08:50   
Fixed by: https://github.com/AlmaLinux/cloud-images/commit/37958232da8f387f4bf5bb5ecd65e006b9eb71cb


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
93 [AlmaLinux-8] -OTHER minor always 2021-06-02 12:05 2022-04-26 08:47
Reporter: obarrios Platform: AWS  
Assigned To: lkhn OS: AlmaLinux  
Priority: normal OS Version: 8.4  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 8.4  
    Target Version:  
abrt_hash:
URL:
Summary: The UUID is always the same in the AWS official image of AlmaLinux 8.4
Description: In my software, we identify instances by /etc/machine-id but in AWS the value is always the same.

AMI Location:
aws-marketplace/AlmaLinux OS 8.4 x86_64-c076b20a-2305-4771-823f-944909847a05
Tags: aws, cloud
Steps To Reproduce: cat /etc/machine-id
68eb8fb9b4544a189870301b79618f1d
Additional Information: I'm temporary workaround it by performing this just after create the instance:
rm /etc/machine-id
dbus-uuidgen --ensure=/etc/machine-id
Attached Files:
Notes
(0000547)
lkhn   
2022-04-26 08:44   
(Last edited: 2022-04-26 08:45)
Hey,

Thanks for making AlmaLinux Better.

This issue fixed by: https://github.com/AlmaLinux/cloud-images/commit/37958232da8f387f4bf5bb5ecd65e006b9eb71cb
(0000548)
lkhn   
2022-04-26 08:47   
https://github.com/AlmaLinux/cloud-images/commit/37958232da8f387f4bf5bb5ecd65e006b9eb71cb


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
215 [AlmaLinux-8] -OTHER trivial always 2022-04-21 05:51 2022-04-24 08:58
Reporter: fiberkill Platform: HP Proliant  
Assigned To: OS: Almalinux  
Priority: high OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Problem beim updaten ein frischen installation mit "yum update"
Description: Ich teste gerade unsere Kickstart-Umgebung mit Almalinux. Hiemit kann ich eine frische Installation ohne Probleme herstellen.
Nach der Installation werden die .repo Dateien via Ansible auf unseren lokalen Mirror von BaseOS, AppStream, Extra usw. umgestellt.
Diese Mirror habe kurz vorher aktualisiert. Danach kann ich ohne Problem Pakete über die lokalen Paketquellen installieren.
Wenn ich nun auf den eben frisch installierten Server "yum udpdate" ausführe, bekommen folgende Fehlermeldung:

Last metadata expiration check: 0:39:11 ago on Thu 21 Apr 2022 07:09:24 AM CEST.
Error:
 Problem 1: package perl-Net-SSLeay-1.88-1.module_el8.3.0+2086+72f2d257.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - cannot install the best update candidate for package perl-libs-4:5.26.3-420.el8.x86_64
  - cannot install the best update candidate for package perl-Net-SSLeay-1.88-1.module_el8.3.0+2086+72f2d257.x86_64
 Problem 2: package net-snmp-agent-libs-1:5.8-22.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - package perl-Carp-1.50-439.module_el8.3.0+6149+d2c5d96d.noarch requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - cannot install the best update candidate for package perl-Carp-1.42-396.el8.noarch
  - cannot install the best update candidate for package net-snmp-agent-libs-1:5.8-22.el8.x86_64
 Problem 3: package net-snmp-1:5.8-22.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - package perl-Data-Dumper-2.174-440.module_el8.3.0+6149+d2c5d96d.x86_64 requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - package perl-Data-Dumper-2.174-440.module_el8.3.0+6149+d2c5d96d.x86_64 requires libperl.so.5.30()(64bit), but none of the providers can be installed
  - cannot install the best update candidate for package perl-Data-Dumper-2.167-399.el8.x86_64
  - cannot install the best update candidate for package net-snmp-1:5.8-22.el8.x86_64
 Problem 4: perl-libs-4:5.26.3-420.el8.i686 has inferior architecture
  - package perl-Mozilla-CA-20160104-7.module_el8.3.0+2091+9eecfe51.noarch requires perl(:MODULE_COMPAT_5.26.3), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - package perl-Digest-1.17-396.module_el8.3.0+6149+d2c5d96d.noarch requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - cannot install the best update candidate for package perl-Mozilla-CA-20160104-7.module_el8.3.0+2091+9eecfe51.noarch
  - cannot install the best update candidate for package perl-Digest-1.17-395.el8.noarch
 Problem 5: package perl-IO-Socket-SSL-2.066-4.module_el8.3.0+2086+72f2d257.noarch requires perl(Net::SSLeay) >= 1.46, but none of the providers can be installed
  - package perl-Net-SSLeay-1.88-1.module_el8.3.0+2086+72f2d257.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - package perl-Digest-MD5-2.55-397.module_el8.3.0+6149+d2c5d96d.x86_64 requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - package perl-Digest-MD5-2.55-397.module_el8.3.0+6149+d2c5d96d.x86_64 requires libperl.so.5.30()(64bit), but none of the providers can be installed
  - cannot install the best update candidate for package perl-IO-Socket-SSL-2.066-4.module_el8.3.0+2086+72f2d257.noarch
  - cannot install the best update candidate for package perl-Digest-MD5-2.55-396.el8.x86_64
  - package perl-Net-SSLeay-1.88-1.module_el8.3.0+2018+449fe210.x86_64 is filtered out by modular filtering
  - package perl-Net-SSLeay-1.88-1.module_el8.3.0+2088+ac7a9534.x86_64 is filtered out by modular filtering
 Problem 6: problem with installed package perl-Net-SSLeay-1.88-1.module_el8.3.0+2086+72f2d257.x86_64
  - package perl-Net-SSLeay-1.88-1.module_el8.3.0+2086+72f2d257.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - package perl-Encode-4:3.01-439.module_el8.3.0+6149+d2c5d96d.x86_64 requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - package perl-Encode-4:3.01-439.module_el8.3.0+6149+d2c5d96d.x86_64 requires libperl.so.5.30()(64bit), but none of the providers can be installed
  - cannot install the best update candidate for package perl-Encode-4:2.97-3.el8.x86_64
 Problem 7: problem with installed package net-snmp-agent-libs-1:5.8-22.el8.x86_64
  - package net-snmp-agent-libs-1:5.8-22.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - package perl-Errno-1.30-452.module_el8.4.0+2179+01326e37.x86_64 requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - package perl-Errno-1.30-452.module_el8.4.0+2179+01326e37.x86_64 requires perl-libs(x86-64) = 4:5.30.1-452.module_el8.4.0+2179+01326e37, but none of the providers can be installed
  - cannot install the best update candidate for package perl-Errno-1.28-420.el8.x86_64
 Problem 8: problem with installed package net-snmp-1:5.8-22.el8.x86_64
  - package net-snmp-1:5.8-22.el8.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - package perl-Exporter-5.73-440.module_el8.3.0+6149+d2c5d96d.noarch requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - cannot install the best update candidate for package perl-Exporter-5.72-396.el8.noarch
 Problem 9: problem with installed package perl-IO-Socket-SSL-2.066-4.module_el8.3.0+2086+72f2d257.noarch
  - package perl-IO-Socket-SSL-2.066-4.module_el8.3.0+2086+72f2d257.noarch requires perl(Net::SSLeay) >= 1.46, but none of the providers can be installed
  - package perl-Net-SSLeay-1.88-1.module_el8.3.0+2086+72f2d257.x86_64 requires libperl.so.5.26()(64bit), but none of the providers can be installed
  - cannot install both perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 and perl-libs-4:5.26.3-420.el8.x86_64
  - package perl-File-Path-2.16-439.module_el8.3.0+6149+d2c5d96d.noarch requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
  - cannot install the best update candidate for package perl-File-Path-2.15-2.el8.noarch
  - package perl-Net-SSLeay-1.88-1.module_el8.3.0+2018+449fe210.x86_64 is filtered out by modular filtering
  - package perl-Net-SSLeay-1.88-1.module_el8.3.0+2088+ac7a9534.x86_64 is filtered out by modular filtering
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Tags: ansible, kickstart, yum update
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000537)
alukoshko   
2022-04-21 11:31   
Hello.
Do you have the same issue with original AlmaLinux repos?
(0000545)
fiberkill   
2022-04-24 08:58   
I'll try but i have to download the repo. What is in your opinion the best URL for this mirror?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
218 [AlmaLinux-8] dhcp major always 2022-04-22 10:21 2022-04-22 10:22
Reporter: godzillante Platform: x86_64  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: network service removes IP from ethernet configured as DHCP after 24 hours
Description: I noticed this pattern on three different VMs hosted on Scaleway and Hetzner, which use DHCP for IP assignment.

After I installed AlmaLinux 8.5 successfully, I installed cPanel DNSOnly, which disables NetworkManager (it does during the installation phase, I guess because it conflicts with cPanel's management of IPs).
Then after 24 hours I lost all three VMs at the same time, and the only way to have them reachable again was to disable the "network" service and re-enable NetworkManager.
On another, similar VM which uses static IP addressing I have no problem.

Latest updates are installed via dns.
Tags:
Steps To Reproduce: 1. Set up DHCP network
2. Disable NetworkManager and enable the old network daemon
3. Wait 24 hours
4. Notice there's no IP address on the main network interface
Additional Information:
Attached Files:
Notes
(0000541)
godzillante   
2022-04-22 10:22   
typo on last line of description: "Latest updates are installed via dnf"


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
112 [AlmaLinux-8] anaconda minor always 2021-07-06 04:29 2022-04-22 05:08
Reporter: lee Platform: Linux  
Assigned To: alukoshko OS: Alma Linux  
Priority: normal OS Version: 8.3  
Status: feedback Product Version:  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Closest Mirror while installing
Description: Hi,

It would be great if the installation source were the closest mirror, like in CentOS 8.
We could install the latest version of the OS with all the patches in a fresh install.

Thanks
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000299)
alukoshko   
2021-07-07 18:09   
Unfortunately it's not possible without rebuilding the ISO images.
aarch64 version was released a bit later and includes this feature.
x86_64 will have to wait for 8.5 I believe or some emergency rebuild.
(0000301)
lee   
2021-07-08 09:22   
Thanks �. We will wait.
(0000345)
alukoshko   
2021-10-14 14:43   
Yesterday we've released 8.5-beta with automatic closest mirror choosing during install
https://wiki.almalinux.org/release-notes/8.5-beta
Please try it.
(0000419)
alukoshko   
2021-11-22 20:10   
8.5 stable is out with automatic closest mirror choosing during netinstall.
(0000538)
lee   
2022-04-22 05:08   
Hi,

Tested and working on install iso.
Please enable on the Live media install also.
Thanks


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
212 [AlmaLinux-8] systemd minor have not tried 2022-04-10 09:13 2022-04-11 13:52
Reporter: vk Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: systemd permission denied due to assigned context
Description: Tried to create a service that executes a binary. The binary was downloaded to /tmp/mybinary/mybinary then moved to /usr/bin/mybinary and its permissions were changed to:

-rwxr-xr-x. 1 mybinary_user mybinary_user 14049280 Apr 2 02:43 /usr/bin/mybinary

The I created a unit file to execute the "mybinary" by User=mybinary_user Group=mybinary_user

Systemctl was failing with permission denied

journalctl snippet:

systemd[1]: Starting MyBinary...
systemd[1745]: mybinary.service: Failed to execute command: Permission denied
systemd[1745]: mybinary.service: Failed at step EXEC spawning /usr/bin/mybinary.: Permission denied
systemd[1]: mybinary.service: Control process exited, code=exited status=203
systemd[1]: mybinary.service: Failed with result 'exit-code'.
systemd[1]: Failed to start MyBinary.

But the mybinary_user and root were both able to run the binary.

After a lot of digging around I found out that my issue was similar to this one bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1177202

I checked my binary had this context output
# ls -Z /usr/bin/mybinary
unconfined_u:object_r:user_tmp_t:s0 /usr/bin/mybinary

so I "chcon" the type to from "user_tmp_t" to "bin_t" (same as most of the /usr/bin/* files)

Systemd then was able to run the binary.

I am new to linux so I am not sure if this is expected but I thought I should let you know.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
214 [AlmaLinux-8] dnf minor always 2022-04-11 09:54 2022-04-11 09:54
Reporter: kiwi Platform: All  
Assigned To: OS: Alma Linux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Alma Linux repository uses too weak certificate for enhanched security
Description: If you security harden your serverusing RedHats proposed method (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening):

update-crypto-policies --set FUTURE

...you can no longer use dnf (with underlying curl) since it reports that the repository certificate is too weak:

[root@server~]# dnf update
AlmaLinux 8 - BaseOS 0.0 B/s | 0 B 00:07
Errors during downloading metadata for repository 'baseos':
  - Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.almalinux.org/mirrorlist/8/baseos?countme=3 [SSL certificate problem: EE certificate key too weak]
  - Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.almalinux.org/mirrorlist/8/baseos [SSL certificate problem: EE certificate key too weak]
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.almalinux.org/mirrorlist/8/baseos [SSL certificate problem: EE certificate key too weak]
[root@server~]#
Tags:
Steps To Reproduce: update-crypto-policies --set FUTURE

dnf update
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
211 [AlmaLinux-8] asciidoc minor always 2022-04-06 13:48 2022-04-06 13:48
Reporter: wadeh Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: a2x conversion to PDF or PS broken
Description: The a2x command (part of asciidoc) fails to create PDF or PS documents from text files due to a Python error.

Note that this worked fine on CentOS 6 and 7.

I suspect this is broken upstream but have not tested it yet on RHEL or CentOS 8 Stream.
Tags:
Steps To Reproduce: 1. Create test document "test.txt"
2. Run "a2x -d article -f pdf test.txt"
3. It fails each time with and error (note, this should keep the test.xml temp file)
4. Manually run dblatex to see the details of the error:

dblatex -t pdf -p "/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s "/etc/asciidoc/dblatex/asciidoc-dblatex.sty" "./test.xml"

Errors reported:
Build the book set list...
Build the listings...
XSLT stylesheets DocBook - LaTeX 2e (0.3.10)
===================================================
Image 'dblatex' not found
Unexpected error occured
Error: %b requires a bytes-like object, or an object that implements __bytes__# , not 'str'
Additional Information: RPMS:
    asciidoc-8.6.10-0.5.20180627gitf7c2274.el8.noarch
    dblatex-0.3.10-8.el8.noarch

test.txt, a simple test document:

Test Document
=============
Joe Blo <joeblo@example.com>
1.0, 4/6/2022: created as a test document

Synopsis:
---------

This is a test document using asciidoc "The asciidoc(1) command
translates the AsciiDoc text file FILE to DocBook or HTML.
If FILE is - then the standard input is used."

Notes:
------

1. This would be a list of notes.
2. And some more notes.

Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
210 [AlmaLinux-8] -OTHER crash always 2022-04-05 12:17 2022-04-05 13:57
Reporter: olahaye74 Platform: x86_64  
Assigned To: OS: CentOS  
Priority: normal OS Version: 7  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Leapp preupgrade crashes UnicodeDecodeError: 'utf8' codec can't decode byte 0xef in position 3: invalid continuation byte
Description: # LC_ALL=C leapp preupgrade
==> Processing phase `configuration_phase`
====> * ipu_workflow_config
        IPU workflow config actor
==> Processing phase `FactsCollection`
====> * scan_kernel_cmdline
        No documentation has been provided for the scan_kernel_cmdline actor.
====> * removed_pam_modules_scanner
        Scan PAM configuration for modules that are not available in RHEL-8.
====> * scan_sap_hana
        Gathers information related to SAP HANA instances on the system.
====> * scan_subscription_manager_info
        Scans the current system for subscription manager information
====> * system_facts
        Provides data about many facts from system.
====> * udevadm_info
        Produces data exported by the "udevadm info" command.
Process Process-187:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 258, in _bootstrap
    self.run()
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 114, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/python2.7/site-packages/leapp/repository/actor_definition.py", line 72, in _do_run
    actor_instance.run(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/leapp/actors/__init__.py", line 335, in run
    self.process(*args)
  File "/usr/share/leapp-repository/repositories/system_upgrade/common/actors/udev/udevadminfo/actor.py", line 18, in process
    out = run(['udevadm', 'info', '-e'])['stdout']
  File "/usr/lib/python2.7/site-packages/leapp/libraries/stdlib/__init__.py", line 181, in run
    stdin=stdin, env=env, encoding=encoding)
  File "/usr/lib/python2.7/site-packages/leapp/libraries/stdlib/call.py", line 179, in _call
    **extra
  File "/usr/lib/python2.7/site-packages/leapp/libraries/stdlib/call.py", line 59, in _multiplex
    linebufs[fd] += decoders[fd].decode(read)
  File "/usr/lib64/python2.7/codecs.py", line 296, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xef in position 3: invalid continuation byte


=============================================================================================
Actor udevadm_info unexpectedly terminated with exit code: 1 - Please check the above details
=============================================================================================

Debug output written to /var/log/leapp/leapp-preupgrade.log

============================================================
                           REPORT
============================================================

A report has been generated at /var/log/leapp/leapp-report.json
A report has been generated at /var/log/leapp/leapp-report.txt

============================================================
                       END OF REPORT
============================================================

Answerfile has been generated at /var/log/leapp/answerfile
Tags:
Steps To Reproduce: sudo Leapp preupgrade
Additional Information:
Attached Files: udevadm_info-e.txt (303,641 bytes) 2022-04-05 12:50
https://bugs.almalinux.org/file_download.php?file_id=128&type=bug
Notes
(0000533)
olahaye74   
2022-04-05 12:50   
Attachment: the output of udevadm info -e
as you will notice, some output is written in Chinese. (example: line 3089).
This is obviously not ASCII, thus the crash.
(0000534)
olahaye74   
2022-04-05 13:27   
It seems to crash when decoding this line:
E: HID_UNIQ=香晦晦香香晦晦香

(added a print(read) at line 59 in /usr/lib/python2.7/site-packages/leapp/libraries/stdlib/call.py (just before the crash).
(0000535)
olahaye74   
2022-04-05 13:57   
It seems that the device that raises the problem is a Belkin USB+VGA KVM adapter-module (need to physically check)
# lsusb -t -d 3032:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
        |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
        |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M
[root@drtcloud leapp]# lsusb -v -d 3032:

Bus 002 Device 003: ID 3032:1b1c
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x3032
  idProduct 0x1b1c
  bcdDevice dd.28
  iManufacturer 4 ???
  iProduct 70 ????????????????????????????????
  iSerial 136 ??????????????????????????????
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 59
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 3 Human Interface Device
      bInterfaceSubClass 1 Boot Interface Subclass
      bInterfaceProtocol 1 Keyboard
      iInterface 0
        HID Device Descriptor:
          bLength 9
          bDescriptorType 33
          bcdHID 1.00
          bCountryCode 33 US
          bNumDescriptors 1
          bDescriptorType 34 Report
          wDescriptorLength 63
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 64
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 3 Human Interface Device
      bInterfaceSubClass 1 Boot Interface Subclass
      bInterfaceProtocol 2 Mouse
      iInterface 0
        HID Device Descriptor:
          bLength 9
          bDescriptorType 33
          bcdHID 1.00
          bCountryCode 0 Not supported
          bNumDescriptors 1
          bDescriptorType 34 Report
          wDescriptorLength 52
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0004 1x 4 bytes
        bInterval 10
Device Status: 0x0002
  (Bus Powered)
  Remote Wakeup Enabled


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
206 [AlmaLinux-8] kernel minor have not tried 2022-03-28 17:50 2022-03-29 10:53
Reporter: kashanlinux Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: PMU to ignore in linux “initcall_blacklist=arm_pmu_acpi_init” in ARM64 Support
Description: There’s a quick fix in Linux for the PMU problem: on the Linux kernel boot line, add “initcall_blacklist=arm_pmu_acpi_init”. This option will keep the PMU driver from loading, and should avoid all the PMU problems.
Tags: aarch64
Steps To Reproduce:
Additional Information:
Attached Files: image.png (1,736 bytes) 2022-03-28 17:50
https://bugs.almalinux.org/file_download.php?file_id=120&type=bug
image-2.png (1,376 bytes) 2022-03-28 17:50
https://bugs.almalinux.org/file_download.php?file_id=121&type=bug
image-3.png (7,171 bytes) 2022-03-28 17:50
https://bugs.almalinux.org/file_download.php?file_id=122&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
192 [AlmaLinux-8] -OTHER tweak always 2022-02-24 05:16 2022-03-26 10:46
Reporter: lee Platform: x86_64  
Assigned To: OS: Linux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Enable Content trust in Alma Linux Docker images
Description: docker trust inspect --pretty almalinux:latest
gives
“No signatures or cannot access almalinux:latest”

docker trust inspect --pretty centos:8
gives

"
SIGNED TAG DIGEST SIGNERS
8 76d24f3ba3317fa945743bb3746fbaf3a0b752f10b10376960de01da70685fbd (Repo Admin)

Administrative keys for centos:8

Repository Key: f4880e657b5b47e2a5eec7d7c5700245e9fde28754c84faada67115c523f7488
Root Key: 95eadfb9877a06161261e4ebed7c8c9f1cbc49ab7f0a5ab246dfcce0d20c3e8c
"

Kindly look into this.
Tags: Docker
Steps To Reproduce: docker trust inspect --pretty almalinux:latest
Additional Information: https://docs.docker.com/engine/reference/commandline/trust_inspect/
https://docs.docker.com/engine/security/trust/
Attached Files: alma-dct.txt (1,370 bytes) 2022-03-26 10:46
https://bugs.almalinux.org/file_download.php?file_id=119&type=bug
Notes
(0000522)
srbala   
2022-03-26 10:46   
It looks like our March release resolved `almalinux:latest` tag. Other tags 8, 8.5, minimal, still have issues.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
204 [AlmaLinux-8] almalinux-release minor always 2022-03-24 01:28 2022-03-24 01:28
Reporter: karlberry Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: 8.5 boot.iso too big for CD media?
Description: AlmaLinux-8.5-x86_64-boot.iso has size 773,849,088 bytes. I tried to burn it to a blank CD with cdrecord -dev=... (I still have old systems where CD is the most convenient way to install), but it bailed out with:

Blocks total: 359849 Blocks current: 359849 Blocks remaining: -18009
wodim: WARNING: Data may not fit on current disk.

And when I tried overburning the media anyway, it could not be read correctly.

Any chance of reducing the size? The 8.4 *boot.iso is considerably smaller: 709,885,952.

Thanks.
Tags: boot
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
203 [AlmaLinux-8] passwd major random 2022-03-22 07:40 2022-03-23 17:23
Reporter: elialum Platform: Almalinux  
Assigned To: OS: Almalinux  
Priority: urgent OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: User level permissionts/settings randomly destroyed (su: failed to execute /bin/bash: No such file or directory)
Description: We are getting hit by random system-level user errors in which the user is completely unable to function, nothing basically works, here is one simple example of trying to SU to the user -

su username
su: failed to execute /bin/bash: No such file or directory

As these are mostly users that related to websites, everything is dead obviously (websites, crons, anything)

Our quick & dirty workaround currently is to recreate the user -

userdel username
useradd username
chown -R username.username userhomedir

One thing we noted is that "nobody" user on this server is different from than usual system:

~>grep nobody /etc/passwd
nobody:x:65534:65534:Kernel Overflow User:/:/sbin/nologin

usually, it's like

~>grep nobody /etc/passwd
nobody:x:99:99:Nobody:/:/sbin/nologin


nobody uid=65534, pid=65534 is unusual as far as I can tell? Not sure if it's related though




Thanks,
Eli.


Tags:
Steps To Reproduce:
Additional Information: Kernel: 4.18.0-348.20.1.el8_5.x86_64
Attached Files:
Notes
(0000519)
alukoshko   
2022-03-22 08:12   
Hello. Both nobody users are correct but for different os versions.

RHEL8:
~>grep nobody /etc/passwd
nobody:x:65534:65534:Kernel Overflow User:/:/sbin/nologin

RHEL7:
~>grep nobody /etc/passwd
nobody:x:99:99:Nobody:/:/sbin/nologin

Is it possible that your server OS was attacked or unintentionally damaged by someone?
AlmaLinux itself doesn't modify users or their dirs in any way.
Does /bin/bash actually present in system?
(0000520)
danielsan   
2022-03-22 08:26   
Hello alukosho,

Thank you for your reply,
/bin/bash is present in the system.

Do you have any clue how can we investigate that issue?
(0000521)
elialum   
2022-03-23 17:23   
Found the issue, an internal script that runs daily on the users and doing something on their group ownership (security-wise) if some conditions are met.
Worked perfectly on COS7, so we didn't catch it initially when upgraded to ALM8

We can close this one


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
202 [AlmaLinux-8] almalinux-release text always 2022-03-21 15:51 2022-03-21 15:51
Reporter: squinky86 Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: low OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Installer implies that a DISA STIG exists for AlmaLinux
Description: During installation, the installer implies that a DISA STIG for AlmaLinux exists (at V1R3) instead of referencing DISA's RHEL STIG.
Tags:
Steps To Reproduce: Select the DISA STIG profile during installation.
Additional Information: DISA has released STIGs for RHEL and Oracle Linux, but not for AlmaLinux. The language of this profile suggests that one has been approved for AlmaLinux when it has not. The language of this profile during installation should be changed back to the (now V1R5) RHEL STIG.
Attached Files: alma.png (48,003 bytes) 2022-03-21 15:51
https://bugs.almalinux.org/file_download.php?file_id=118&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
201 [AlmaLinux-8] dnf major always 2022-03-21 09:49 2022-03-21 11:49
Reporter: Fozzy Admins Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: high OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Error: Failed to download metadata for repo «centos-openstack-train»: Cannot prepare internal mirrorlist: No URLs in mirrorlist
Description: Openstack-Train repository installed via dnf does not work due to the end of life of CentOS 8.
For its correct operation, it is required to specify the Vault repositories in yum.repos.d configs.

Tags:
Steps To Reproduce: Install centos-release-openstack-train repo via dnf/yum and make cache.
Additional Information: I see 2 solutions: creating an openstack repo for Alma Linux 8, or replacing the repo with vault.
Attached Files:
Notes
(0000518)
sboldyreva   
2022-03-21 11:49   
Hello! There's a related bug, you may want to check it: https://bugs.almalinux.org/view.php?id=186


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
200 [AlmaLinux-8] pulseaudio major always 2022-03-18 20:08 2022-03-18 20:08
Reporter: dufgrinder Platform: ASUS 55A - Intel Pentium B970  
Assigned To: OS: AlmanLinux 8.5  
Priority: normal OS Version: 4.18.0-348.20.1  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Speakers always Mute
Description: Hi,

On a quite old laptop, Speakers never play.

Knowing that:
* They worked may years under Centos 7 and always work with Fedora 35 and Centos 9
* Headphones are working

KR, Olivier

Tags:
Steps To Reproduce: Just play a movie:
- Try to mute / unmute with pulseaudio
Additional Information: lspci -v | grep -B1 -A12 -i audio

00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
    Subsystem: ASUSTeK Computer Inc. Device 1c33
    Flags: bus master, fast devsel, latency 0, IRQ 30
    Memory at f7e10000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: <access denied>
    Kernel driver in use: snd_hda_intel
    Kernel modules: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0, IRQ 24
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
    I/O behind bridge: [disabled]
    Memory behind bridge: [disabled]
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
198 [AlmaLinux-8] kernel major always 2022-03-07 19:23 2022-03-15 10:35
Reporter: leyland Platform: Intel 12100  
Assigned To: OS: Alma Linux  
Priority: immediate OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Intel(R) 2.5G Ethernet Linux Driver (IGC) will not load properly
Description: Alma Linux 8.5 will not load igc perperly

[ 0.922651] igc 0000:02:00.0: enabling device (0000 -> 0002)
[ 0.952132] igc: probe of 0000:02:00.0 failed with error -2

02:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)

I tested centos stream 9 with the lastest kernel, it is working fine
Tags: 2.5G, igc, intel
Steps To Reproduce:
Additional Information:
Attached Files: 8cd92ac447e730bdae96ffb05fef4f5.jpg (374,945 bytes) 2022-03-10 02:45
https://bugs.almalinux.org/file_download.php?file_id=117&type=bug
Notes
(0000503)
leyland   
2022-03-07 19:25   
[ 0.921966] Intel(R) 2.5G Ethernet Linux Driver
[ 1.268381] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1)
(0000504)
alukoshko   
2022-03-09 08:48   
Hello.
Could you please check RHEL or CentOS 8.5 on the same hardware?
Most likely the adapter is just not properly supported in 8.5.
(0000506)
toracat   
2022-03-09 19:54   
@leyland

Can you show us the output from:

$ lspci -nn | grep -i net

That should display the device IDs.
(0000508)
leyland   
2022-03-10 02:15   
Ethernet controller [0200]: Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 03)
(0000509)
toracat   
2022-03-10 02:41   
I do confirm that device [8086:15f3] is supported by the igc driver in the EL8.5 kernel.

$ grep 8086 /lib/modules/`uname -r`/modules.alias | grep -i 15f3
alias pci:v00008086d000015F3sv*sd*bc*sc*i* igc

You indicated that the latest kernel in CentOS Stream 9 worked. If a newer version of the driver works, you could also try ELRepo's kernel-ml. It is currently at kernel-5.16.13.

https://elrepo.org/linux/kernel/el8/x86_64/RPMS/
(0000510)
leyland   
2022-03-10 02:45   
(0000511)
leyland   
2022-03-10 04:47   
Because I need to use ZFS as production, so Kernel 5.16.13 is unstable for ZFS
(0000512)
leyland   
2022-03-10 04:48   
This is why I gave up Centos Stream 9 and move to RHEL compatible Alma Linux 8.5
(0000515)
leyland   
2022-03-15 08:43   
Centos Stream 8 Kernel 4.18.0-365.el8.x86_64 solved Intel IGC Driver issue
(0000516)
alukoshko   
2022-03-15 09:08   
Good. Then it most likely will work with 8.6 stable release.
(0000517)
leyland   
2022-03-15 10:35   
uname -a
4.18.0-365.el8.x86_64 #1 SMP Thu Feb 10 16:11:23 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

dmesg|grep Intel
[ 0.922076] igc 0000:01:00.0: enabling device (0000 -> 0002)
[ 0.922407] igc 0000:01:00.0: PCIe PTM not supported by PCIe bus/controller
[ 0.971467] igc 0000:01:00.0 (unnamed net_device) (uninitialized): PHC added
[ 1.030147] igc 0000:01:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x1 link)
[ 1.030375] igc 0000:01:00.0 eth0: MAC: 88:c9:b3:bf:71:59
[ 7.023201] igc 0000:01:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

[ 0.921356] Intel(R) 2.5G Ethernet Linux Driver
[ 0.921690] Copyright(c) 2018 Intel Corporation.

lspci -nn
01:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 03)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
199 [AlmaLinux-8] dnf major always 2022-03-11 04:44 2022-03-11 08:39
Reporter: chris hutchinson Platform:  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: /etc/yum.repos.d/almalinux-resilientstorage.repo has repeated [resilientstorage] entries
Description: /etc/yum.repos.d/almalinux-resilientstorage.repo contains repeated entries for [resilientstorage] and causes puppet v7 to fail.

Manually editing the repo file to give the entries unique names fixed things.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000514)
alukoshko   
2022-03-11 08:39   
Hi. There was a bug in released AlmaLinux 8.5 that was then quickly fixed by almalinux-release version 8.5-3.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
197 [AlmaLinux-8] firefox major have not tried 2022-03-07 19:04 2022-03-10 22:05
Reporter: repulsive-gravity Platform: el8  
Assigned To: OS:  
Priority: urgent OS Version: 8.5 ArcticSphinx  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: CVE-2022-26485 and CVE-2022-26486 Use-After-Free memory exploits;
Description: I'm relatively new to Linux, I hope I've brought this to the proper place. I'm sure everyone is aware of this; but, I am wondering if Alma is working on adding these patches to the official repository?

Those being : Firefox 91.6.1 esr ; Firefox 97.0.2

Currently, dnf thinks Firefox 91.6.0 is up to date.

CVE-2022-26485 and CVE-2022-26486 are the use-after-free memory exploits.

Cheers
Tags: cve-2022-26485, cve-2022-26486, firefox, zeroday
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000505)
sboldyreva   
2022-03-09 10:28   
Hello! As AlmaLinux is 1:1 compatible with RHEL, we release updates after Red Hat. For now, there's not such an update yet.
(0000513)
alukoshko   
2022-03-10 22:05   
Hello.
firefox-91.7.0-3.el8_5.alma was just released with the following vulnerabilities closed:
CVE-2022-25235
CVE-2022-25236
CVE-2022-25315
CVE-2022-26381
CVE-2022-26383
CVE-2022-26384
CVE-2022-26386
CVE-2022-26387
CVE-2022-26485
CVE-2022-26486


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
165 [AlmaLinux-8] -OTHER block always 2021-12-21 02:58 2022-03-09 20:17
Reporter: edb Platform: M1 Max (aarm64)  
Assigned To: OS: macOS  
Priority: immediate OS Version: 12.1  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Unable to install Alma Linux 8.x aarm64 macOS 12.1 M1
Description: Unable to install Alma Linux 8.x aarm64 macOS 12.1 M1 Max

Virtualization platforms: Parallels, VMware Fusion, QEMU

Description: The ISO's boot into the install select menu. Selecting any of the options brings you right back to the same menu of selecting the media verification or going straight to the install.
Tags:
Steps To Reproduce: With M1 based Mac, using Parallels, or VMware Fusion or QEMU, boot the iso for install with default settings or other settings.
Additional Information:
Attached Files:
Notes
(0000456)
alukoshko   
2021-12-21 19:07   
RHEL8 (and all its derivatives) doesn't support Apple M1.
RHEL9 will do.
(0000457)
edb   
2021-12-22 04:27   
How soon to see this supported? My organization is standardizing with Alma Linux and the added support for Apple M1 Arm would be great.
(0000458)
edb   
2021-12-22 04:29   
Specifically this is to run as a VM, not necessarily on M1 bare metal.
Thanks advance!
(0000464)
akdev   
2021-12-31 02:48   
What happens when you try to boot from a Centos 8 Stream image? does it work? unfortunately this is difficult to troubleshoot as it requires special hardware - are you using an aarch64 image or x86 image? does the x86-64 work?
(0000500)
edb   
2022-03-04 01:41   
Checking in. What would be the expected timing for this?

Regards.
(0000507)
toracat   
2022-03-09 20:17   
As @alukoshko noted, you have to wait for EL9, which *might* be out around May (but please don't quote me :)

https://access.redhat.com/solutions/6545411
"Can I run RHEL in a VM in a Mac using the Apple M1 processor?"


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
196 [AlmaLinux-8] -OTHER trivial always 2022-03-05 05:16 2022-03-05 05:16
Reporter: aboschke Platform:  
Assigned To: OS: Arctic Sphynx  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Group 'Additional Development' has EL7 artifact package hmaccalc should now be libkcapi-hmaccalc
Description: Package name change from EL7 to EL8 (see A.2. Package replacements):
[ https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/considerations_in_adopting_rhel_8/index ]
Tags:
Steps To Reproduce: # dnf install \@"Additional Development"

No match for group package "hmaccalc"
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
195 [AlmaLinux-8] crypto-policies major always 2022-03-04 21:51 2022-03-04 21:51
Reporter: hirschQ Platform: vmware virtual machine  
Assigned To: OS: Almalinux  
Priority: high OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: crypto mismatch: baseos mirrolist SSL certificate problem: EE certificate key too weak
Description: It is not possible to use the almalinux baseos mirrorlist when crypto policy set = FUTURE

Errors during downloading metadata for repository 'baseos':
  - Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.almalinux.org/mirrorlist/8/baseos [SSL certificate problem: EE certificate key too weak]
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.almalinux.org/mirrorlist/8/baseos [SSL certificate problem: EE certificate key too weak]
Tags: installation, selinux
Steps To Reproduce: I installed minimal Almalinux with Security Profile: CIS Benchmark Level 2 for Server and tried to update or install.
But changing crypto-policy to future will reproduce the error, too:

update-crypto-policies --set FUTURE
reboot
dnf install nano
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
193 [AlmaLinux-8] -OTHER minor have not tried 2022-02-25 12:02 2022-02-25 20:55
Reporter: Pietergroot21 Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Repository ‘baseos’
Description:     I installed Almalinux.

When I ran the yum update -y command after a clean install, I saw this warning:

 [root@~]# yum update -y

AlmaLinux 8 - BaseOS 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'baseos':

  - Curl error (6): Couldn't resolve host name for https://mirrors.almalinux.org/mirrorlist/8/baseos [Could not resolve host: mirrors.almalinux.org]
Error: Failed to download metadata for repo 'baseos': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.almalinux.org/mirrorlist/8/baseos [Could not resolve host: mirrors.almalinux.org]
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000497)
alukoshko   
2022-02-25 15:14   
Hi. Looks like something is wrong with DNS settins.
Please try:
nslookup mirrors.almalinux.org

What's in /etc/resolv.conf ?
(0000498)
Pietergroot21   
2022-02-25 17:30   
when I enter that it says "file or folder does not exist"
(0000499)
alukoshko   
2022-02-25 20:55   
then you should properly setup your network first


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
191 [AlmaLinux-8] cronie minor always 2022-02-23 13:19 2022-02-23 13:19
Reporter: domen Platform: Vmware  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Mail on error not sent from cron files
Description: I have following lines in root crontab file:

MAILTO="domen.setar@izum.si"

0 10 * * * /tmp/nonexistent_file.sh

Error message about non existent file is not sent via mail but is written into /var/log/cron:

Feb 23 14:07:01 testsrv CROND[2503686]: (root) CMDOUT (/bin/sh: /tmp/nonexistent_file.sh: No such file or directory)

Mail system on testsrv works fine, because I can send mail from the command line.

This functionality works in Centos 7 and 8 releases.
Tags: cron
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
186 [AlmaLinux-8] almalinux-release major always 2022-02-11 14:55 2022-02-21 15:57
Reporter: pete Platform: x68_64  
Assigned To: OS: Almalinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: centos-release-openstack-train repos are broken
Description: I was using the centos-release-openstack-train repos for the installation of, among others, etcd.

Some days after CentOS 8 went EOL the Cloud SIG repo seems to have gone offline (or moved elsewhere) as well. As a result, the repos installed with the centos-release-openstack-train package are broken now.
Tags:
Steps To Reproduce: Using a fresh install of Almalinux 8.5 (Vagrant box "almalinux/8"):

[root@localhost ~]# dnf install centos-release-openstack-train
AlmaLinux 8 - BaseOS 2.0 MB/s | 5.9 MB 00:03
AlmaLinux 8 - AppStream 2.0 MB/s | 9.1 MB 00:04
AlmaLinux 8 - Extras 17 kB/s | 12 kB 00:00
Dependencies resolved.
====================================================================================================================================
 Package Architecture Version Repository Size
====================================================================================================================================
Installing:
 centos-release-openstack-train noarch 2-1.el8 extras 11 k
Installing dependencies:
 centos-release-messaging noarch 1-2.el8 extras 9.2 k
 centos-release-rabbitmq-38 noarch 1-2.el8 extras 8.1 k
 centos-release-storage-common noarch 2-2.el8 extras 9.2 k

Transaction Summary
====================================================================================================================================
Install 4 Packages

Total download size: 37 k
Installed size: 8.2 k
Is this ok [y/N]: y
Downloading Packages:
(1/4): centos-release-messaging-1-2.el8.noarch.rpm 88 kB/s | 9.2 kB 00:00
(2/4): centos-release-openstack-train-2-1.el8.noarch.rpm 101 kB/s | 11 kB 00:00
(3/4): centos-release-rabbitmq-38-1-2.el8.noarch.rpm 71 kB/s | 8.1 kB 00:00
(4/4): centos-release-storage-common-2-2.el8.noarch.rpm 223 kB/s | 9.2 kB 00:00
------------------------------------------------------------------------------------------------------------------------------------
Total 52 kB/s | 37 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing : 1/1
  Installing : centos-release-storage-common-2-2.el8.noarch 1/4
  Installing : centos-release-messaging-1-2.el8.noarch 2/4
  Installing : centos-release-rabbitmq-38-1-2.el8.noarch 3/4
  Installing : centos-release-openstack-train-2-1.el8.noarch 4/4
  Verifying : centos-release-messaging-1-2.el8.noarch 1/4
  Verifying : centos-release-openstack-train-2-1.el8.noarch 2/4
  Verifying : centos-release-rabbitmq-38-1-2.el8.noarch 3/4
  Verifying : centos-release-storage-common-2-2.el8.noarch 4/4

Installed:
  centos-release-messaging-1-2.el8.noarch centos-release-openstack-train-2-1.el8.noarch
  centos-release-rabbitmq-38-1-2.el8.noarch centos-release-storage-common-2-2.el8.noarch

Complete!
[root@localhost ~]# dnf makecache
CentOS-8 - RabbitMQ 38 83 B/s | 38 B 00:00
Error: Failed to download metadata for repo 'centos-rabbitmq-38': Cannot prepare internal mirrorlist: No URLs in mirrorlist
Additional Information: Looking at http://mirror.centos.org/centos/8/, the "cloud" and "messaging" directories have gone, which explains the problem.

Unfortunately I could not figure out yet where they have moved, so it's not trivial to fix. Anyway, the -release RPMs should be updated to reflect that change.
Attached Files:
Notes
(0000492)
pete   
2022-02-20 12:12   
The issue has obviously been caused by the SIG repositories moving over to the CentOS Stream mirrors, at least some of them.

As for the repositories I require (mainly Centos-OpenStack), the following workaround seems to do the trick:

<code>
[root@localhost ~]# sed -i 's/\$releasever/8-stream/g' /etc/yum.repos.d/CentOS-Ceph-Nautilus.repo
[root@localhost ~]# sed -i 's/\$releasever/8-stream/g' /etc/yum.repos.d/CentOS-OpenStack-victoria.repo
[root@localhost ~]# sed -i 's/\$releasever/8-stream/g' /etc/yum.repos.d/CentOS-Messaging-rabbitmq.repo
[root@localhost ~]# sed -i 's/\$releasever/8-stream/g' /etc/yum.repos.d/CentOS-NFV-OpenvSwitch.repo
[root@localhost ~]# yum makecache
CentOS-8 - Advanced Virtualization 5.0 kB/s | 3.0 kB 00:00
CentOS-8-stream - Ceph Nautilus 16 kB/s | 3.0 kB 00:00
CentOS-8 - RabbitMQ 38 17 kB/s | 3.0 kB 00:00
CentOS-8-stream - NFV OpenvSwitch 377 kB/s | 111 kB 00:00
CentOS-8-stream - OpenStack victoria 17 kB/s | 3.0 kB 00:00
AlmaLinux 8 - BaseOS 5.9 kB/s | 4.3 kB 00:00
AlmaLinux 8 - AppStream 7.9 kB/s | 4.7 kB 00:00
AlmaLinux 8 - Extras 1.7 kB/s | 3.9 kB 00:02
Metadata cache created.
</code>

Disclaimer: If the SIGs actually build against Centos Stream, there might be incompatibilities with plain AlmaLinux 8/Rocky Linux 8. This is something that might need to be resolved on a different level.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
189 [AlmaLinux-8] dnf block have not tried 2022-02-18 13:35 2022-02-21 15:57
Reporter: pomichel Platform:  
Assigned To: OS: AlmaLinux release 8.5  
Priority: urgent OS Version: Arctic Sphynx  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Cant't update OS via yum or dnf
Description: Get an error :

CentOS-8 - Ceph Nautilus 1.1 kB/s | 38 B 00:00
Erreur : Échec du téléchargement des métadonnées pour le dépôt « centos-ceph-nautilus » : Cannot prepare internal mirrorlist: No URLs in mirrorlist

Problem can be reproduced on any of my 6 production servers.

Please urgently help !
Tags:
Steps To Reproduce: Run yum update
of dnf install net-tools for instance
Additional Information:
Attached Files:
Notes
(0000493)
pete   
2022-02-20 12:13   
This is the same issue as https://bugs.almalinux.org/view.php?id=186

See my latest updaten to that issue for an at least partial workaround.
(0000494)
pomichel   
2022-02-21 09:28   
OK, thanks. The workaround is working though I don't feel secure to work with Centos Stream repositories.
(0000495)
pete   
2022-02-21 15:56   
I also don't think this is an ideal situation, for the reasons mentioned in 0000186. I strongly hope it can be solved in a reasonable way rather sooner than later.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
142 [AlmaLinux-8] kernel major always 2021-11-04 05:43 2022-02-17 21:17
Reporter: sbhat Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Intermittent I/O block, timeout of disks in ZFS on Almalinux8
Description: I have two servers A & B and both the servers intermittently rejecting IO, aborting IO commands & causing hiccup in the IO. zpool status turns to warning due to this incident.
Server A:
[root@server-A]$/opt/MegaRAID/storcli/storcli64 /c0 show
CLI Version = 007.1907.0000.0000 Sep 13, 2021
Operating system = Linux 4.18.0-305.el8.x86_64
Controller = 0
Status = Success
Description = None

Product Name = LSI3008-IR
Serial Number = 500304801cca7901
SAS Address = 500304801cca7901
PCI Address = 00:01:00:00
System Time = 11/03/2021 10:43:37
FW Package Build = 00.00.00.00
FW Version = 13.00.00.00
BIOS Version = 08.31.00.00
NVDATA Version = 11.02.49.39
Driver Name = mpt3sas
Driver Version = 35.101.00.00
Bus Number = 1
Device Number = 0
Function Number = 0
Domain ID = 0
Vendor Id = 0x1000
Device Id = 0x97
SubVendor Id = 0x15D9
SubDevice Id = 0x808
Board Name = LSI3008-IR
Board Assembly = N/A
Board Tracer Number = N/A
Security Protocol = None
Physical Drives = 14


Server A Intermittent Errors:
[Wed Nov 3 03:25:16 2021] mpt3sas_cm0: log_info(0x31120b10): originator(PL), code(0x12), sub_code(0x0b10)
[Wed Nov 3 03:25:16 2021] mpt3sas_cm0: log_info(0x31120b10): originator(PL), code(0x12), sub_code(0x0b10)
[Wed Nov 3 03:25:16 2021] mpt3sas_cm0: log_info(0x31120b10): originator(PL), code(0x12), sub_code(0x0b10)
[Wed Nov 3 03:25:16 2021] sd 0:0:10:0: [sdk] tag#2497 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=0s
[Wed Nov 3 03:25:16 2021] sd 0:0:10:0: [sdk] tag#2498 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=0s
[Wed Nov 3 03:25:16 2021] sd 0:0:10:0: [sdk] tag#2547 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=0s
[Wed Nov 3 03:25:16 2021] sd 0:0:10:0: [sdk] tag#2498 CDB: Write(16) 8a 00 00 00 00 01 52 7f 81 a2 00 00 00 11 00 00
[Wed Nov 3 03:25:16 2021] sd 0:0:10:0: [sdk] tag#2547 CDB: Write(16) 8a 00 00 00 00 01 52 7f 81 91 00 00 00 11 00 00
[Wed Nov 3 03:25:16 2021] sd 0:0:10:0: [sdk] tag#2497 CDB: Write(16) 8a 00 00 00 00 01 52 7f 81 b3 00 00 00 11 00 00
[Wed Nov 3 03:25:16 2021] blk_update_request: I/O error, dev sdk, sector 5679055249 op 0x1:(WRITE) flags 0x700 phys_seg 1 prio class 0
[Wed Nov 3 03:25:16 2021] blk_update_request: I/O error, dev sdk, sector 5679055283 op 0x1:(WRITE) flags 0x700 phys_seg 1 prio class 0
[Wed Nov 3 03:25:16 2021] blk_update_request: I/O error, dev sdk, sector 5679055266 op 0x1:(WRITE) flags 0x700 phys_seg 1 prio class 0
[Wed Nov 3 03:25:16 2021] zio pool=backups vdev=/dev/sdk1 error=5 type=2 offset=2907675256320 size=8704 flags=180880
[Wed Nov 3 03:25:16 2021] zio pool=backups vdev=/dev/sdk1 error=5 type=2 offset=2907675247616 size=8704 flags=180880
[Wed Nov 3 03:25:16 2021] zio pool=backups vdev=/dev/sdk1 error=5 type=2 offset=2907675238912 size=8704 flags=180880
[Wed Nov 3 03:25:17 2021] sd 0:0:10:0: Power-on or device reset occurred





Server B:
[root@server-B]$ /opt/MegaRAID/storcli/storcli64 /c0 show
CLI Version = 007.1907.0000.0000 Sep 13, 2021
Operating system = Linux 4.18.0-305.10.2.el8_4.x86_64
Controller = 0
Status = Success
Description = None

Product Name = SAS9300-4i
Serial Number = SP83910736
SAS Address = 500605b00e807090
PCI Address = 00:01:00:00
System Time = 11/03/2021 04:31:03
FW Package Build = 00.00.00.00
FW Version = 16.00.01.00 <--------<
BIOS Version = 08.37.00.00_18.00.00.00
NVDATA Version = 14.01.00.07
Driver Name = mpt3sas
Driver Version = 35.101.00.00
Bus Number = 1
Device Number = 0
Function Number = 0
Domain ID = 0
Vendor Id = 0x1000
Device Id = 0x96
SubVendor Id = 0x1000
SubDevice Id = 0x3110
Board Name = SAS9300-4i
Board Assembly = H3-25473-00G
Board Tracer Number = SP83910736
Security Protocol = None
Physical Drives = 12

Server B Intermittent Errors:
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5085 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: handle(0x0006), sas_address(0x50030480180ec340), phy(0)
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: enclosure logical id(0x50030480180ec37f), slot(0)
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: enclosure level(0x0000), connector name( )
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: task abort: SUCCESS scmd(0x000000004e58e27c)
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: attempting task abort!scmd(0x00000000e6d2bb01), outstanding for 30408 ms & timeout 30000 ms
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5117 CDB: Write(16) 8a 00 00 00 00 02 a2 c0 e1 f8 00 00 00 40 00 00
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: handle(0x0006), sas_address(0x50030480180ec340), phy(0)
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: enclosure logical id(0x50030480180ec37f), slot(0)
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: enclosure level(0x0000), connector name( )
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: No reference found at driver, assuming scmd(0x00000000e6d2bb01) might have completed
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: task abort: SUCCESS scmd(0x00000000e6d2bb01)
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5117 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5117 CDB: Write(16) 8a 00 00 00 00 02 a2 c0 e1 f8 00 00 00 40 00 00
[Wed Nov 3 06:41:07 2021] blk_update_request: I/O error, dev sdc, sector 11320484344 op 0x1:(WRITE) flags 0x700 phys_seg 8 prio class 0
[Wed Nov 3 06:41:07 2021] zio pool=backups vdev=/dev/sdc1 error=5 type=2 offset=5796086935552 size=32768 flags=180880
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: attempting task abort!scmd(0x00000000c1d8d569), outstanding for 30408 ms & timeout 30000 ms
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5116 CDB: Write(16) 8a 00 00 00 00 02 a2 c0 e2 78 00 00 00 40 00 00
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: handle(0x0006), sas_address(0x50030480180ec340), phy(0)
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: enclosure logical id(0x50030480180ec37f), slot(0)
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: enclosure level(0x0000), connector name( )
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: No reference found at driver, assuming scmd(0x00000000c1d8d569) might have completed
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: task abort: SUCCESS scmd(0x00000000c1d8d569)
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5116 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5116 CDB: Write(16) 8a 00 00 00 00 02 a2 c0 e2 78 00 00 00 40 00 00
[Wed Nov 3 06:41:07 2021] blk_update_request: I/O error, dev sdc, sector 11320484472 op 0x1:(WRITE) flags 0x700 phys_seg 8 prio class 0
[Wed Nov 3 06:41:07 2021] zio pool=backups vdev=/dev/sdc1 error=5 type=2 offset=5796087001088 size=32768 flags=180880
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: attempting task abort!scmd(0x000000000a3a05e3), outstanding for 30533 ms & timeout 30000 ms
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5115 CDB: Write(16) 8a 00 00 00 00 02 a2 c0 e2 38 00 00 00 40 00 00
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: handle(0x0006), sas_address(0x50030480180ec340), phy(0)
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: enclosure logical id(0x50030480180ec37f), slot(0)
[Wed Nov 3 06:41:07 2021] scsi target0:0:0: enclosure level(0x0000), connector name( )
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: No reference found at driver, assuming scmd(0x000000000a3a05e3) might have completed
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: task abort: SUCCESS scmd(0x000000000a3a05e3)
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5115 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
[Wed Nov 3 06:41:07 2021] sd 0:0:0:0: [sdc] tag#5115 CDB: Write(16) 8a 00 00 00 00 02 a2 c0 e2 38 00 00 00 40 00 00
[Wed Nov 3 06:41:07 2021] blk_update_request: I/O error, dev sdc, sector 11320484408 op 0x1:(WRITE) flags 0x700 phys_seg 8 prio class 0
[Wed Nov 3 06:41:07 2021] zio pool=backups vdev=/dev/sdc1 error=5 type=2 offset=5796086968320 size=32768 flags=180880
[Wed Nov 3 06:41:08 2021] sd 0:0:0:0: Power-on or device reset occurred
Tags: almalinux8, disk, io-abort, megaraidsas, mpt3sas, smartctl, zfs
Steps To Reproduce: Supermicro Almalinux8 Server with ZFS
Additional Information: 1. Both servers A,B are Broadcom HBA controllers communicate to kernel via mpt3sas driver.
2. We have another server C which has megaraid_sas as driver & not seeing this issue.
3. We have 5 OmniOS (solaris based) servers with both mpt3sas/megaraid_sas drivers but not seeing any IO/disk hiccups at all.
4. smartctl says drives are all good.
5. The IO isn't for one disk but for all the disks randomly.
6. Server has no special IO write or anything, the timing is random too, as if disks are waking up from sleep.

Any suggestions will be very greatly appreciated.
Attached Files:
Notes
(0000377)
sbhat   
2021-11-09 14:13   
Anyone? help
(0000435)
alukoshko   
2021-12-01 08:32   
Hello. Have you tried AlmaLinux 8.5? It has updated kernel.
And it would be great to try to reproduce the same on CentOS or RHEL to understand if it's AlmaLinux specific or upstream issue.
(0000437)
sbhat   
2021-12-01 12:01   
The current OS is Alma 8.4. We haven't tried to reproduce it on centos/rhel since this happens on a zfs storage with large data sets. It doesn't happen on OmniOS though. Anyway, thanks!
(0000444)
toracat   
2021-12-12 18:22   
Another thing you can do is to test-install ELRepo's kernel-ml. With this, you'll be testing the latest stable kernel from kernel.org.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
187 [AlmaLinux-8] general major always 2022-02-14 22:59 2022-02-14 22:59
Reporter: bhnysu Platform: x86-64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: minimal ISO missing rsyslog and plymouth packages from Core package group
Description: AlmaLinux-8.5-x86_64-minimal.iso

The above does not include rsyslog and (less importantly) plymouth RPMs which are listed as mandatory for the 'core' package group. The core group is mandatory for the 'minimal-environment' group, which I would expect the minimal.iso to be able to fully install.

I gather this is due to those packages being in the Appstream repo and the minimal iso including only the BaseOS repo. But nonetheless I think rsyslog would be an expected part of any minimal install. Plymouth not as much.
Tags: installation, minimal-install
Steps To Reproduce: Install from AlmaLinux-8.5-x86_64-minimal.iso

After installing, find that rsyslog (and plymouth) are not present in the system.
Additional Information: Simply doing

dnf install group minimal-environment

after the fact will pull in the missing packages but that shouldn't be necessary.
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
185 [AlmaLinux-8] gnome-shell major always 2022-02-09 01:39 2022-02-09 01:39
Reporter: amcrae42 Platform: x86_64  
Assigned To: OS: Almalinux  
Priority: high OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Severe memory leak eventually causes processes to hang/crash
Description: top shows gnome-shell grows over time until swap starts to get used up.

Difficult to say what I am doing that causes it. I am using Xwayland. I have to logout/in
every 2-3 days to reset the memory use. I am using three screens over two graphics cards
if that is relevant.

System patched to current yum update.

Probably caused by a relatively recent update. Did not have problems last year (Dec 2021).
Tags:
Steps To Reproduce: Run logged in session. Run top.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
27 [AlmaLinux-8] open-vm-tools major always 2021-02-24 15:17 2022-02-08 14:02
Reporter: corporategadfly Platform:  
Assigned To: alukoshko OS:  
Priority: high OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Guest customization fails in vmware when using AlmaLinux 8.3 RC as source template
Description: In an enterprise setting, it is typical to use a source VM template and then deploy multiple VMs using that template. Unfortunately, guest customizations (e.g., setting of hostname, interface settings, DNS, etc.) fails during VM deploy.

See https://github.com/vmware/open-vm-tools/issues/497 for some investigative work.

To help adoption of AlmaLinux, deployment using vmware (with templates) is essential.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: almalinux-bug-27-almalinux-8.4-failed-toolsDeployPkg.log (29,059 bytes) 2021-05-07 20:23
https://bugs.almalinux.org/file_download.php?file_id=75&type=bug
almalinux-bug-27-centos-8-toolsDeployPkg.log (25,435 bytes) 2021-05-07 20:23
https://bugs.almalinux.org/file_download.php?file_id=76&type=bug
open-vm-tools-11.1.0-2.el8.alma.x86_64.rpm (732,076 bytes) 2021-05-07 21:13
https://bugs.almalinux.org/file_download.php?file_id=77&type=bug
open-vm-tools-sdmp-11.1.0-2.el8.alma.x86_64.rpm (37,804 bytes) 2021-05-07 21:13
https://bugs.almalinux.org/file_download.php?file_id=78&type=bug
open-vm-tools-desktop-11.1.0-2.el8.alma.x86_64.rpm (196,964 bytes) 2021-05-07 21:13
https://bugs.almalinux.org/file_download.php?file_id=79&type=bug
almalinux-bug-27-almalinux-8.3-with-patched-open-vm-tools-failed-toolsDeployPkg.log (29,622 bytes) 2021-05-13 01:46
https://bugs.almalinux.org/file_download.php?file_id=80&type=bug
toolsDeployPkg.log (30,717 bytes) 2021-10-25 09:58
https://bugs.almalinux.org/file_download.php?file_id=99&type=bug
toolsDeployPkg-2.log (8,181 bytes) 2021-11-25 20:29
https://bugs.almalinux.org/file_download.php?file_id=107&type=bug
Notes
(0000092)
corporategadfly   
2021-03-31 14:17   
Identical experience with AlmaLinux 8.3.
(0000093)
alukoshko   
2021-03-31 16:10   
Please provide steps to reproduce.
What VMware version are you using? What should be customized?
(0000094)
corporategadfly   
2021-03-31 16:14   
vSphere Client version 6.7.0.46000

So, we typically customize the following:
* hostname
* domain
* DNS entries
* assignment for interfaces (typically two)

Works in RHEL8 and CentOS8 (as long as perl and open-vm-tools is installed).
(0000095)
corporategadfly   
2021-03-31 16:15   
Our VSS folks use a custom CLI for initiating the VM creation so I don't know the internal details but generic details are available at: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-EB5F090E-723C-4470-B640-50B35D1EC016.html
(0000107)
corporategadfly   
2021-04-02 01:29   
Here is an example of a customization which sets hostname, ip addresses, DNS, etc.:
<code>
{
  "hostname": "hostname-1",
  "dhcp": false,
  "domain": "x.y.z",
  "dns": [
    "128.x.x.x",
    "128.y.y.y"
  ],
  "interfaces": [
    {
      "dhcp": false,
      "ip": "10.192.228.58",
      "mask": "255.255.255.128",
      "gateway": [
        "10.192.228.1"
      ]
    },
    {
      "dhcp": false,
      "ip": "10.192.228.186",
      "mask": "255.255.255.128",
      "gateway": [
        "10.192.228.129"
      ]
    }
  ]
}
</code>
(0000180)
corporategadfly   
2021-05-06 23:08   
Any updates?
(0000181)
alukoshko   
2021-05-07 18:19   
Hi! I wasn't able to reproduce the problem but I haven't tried via CLI.
Could you help a bit with this issue?
Please attach open-vm-tools logs from AlmaLinux and from RHEL/CentOS with the same customization if you can.
I'll try to find out what goes wrong and what's the difference.

Also will you able to help with testing of patched open-vm-tools package if I attach it here? I have an idea how to modify it.
(0000182)
corporategadfly   
2021-05-07 18:40   
Absolutely willing to help with testing if I get a patched open-vm-tools package.

I will gather the logs as soon as I'm able to setup a new AlmaLinux template and a new VM deploy (using that template).
(0000183)
corporategadfly   
2021-05-07 20:23   
added toolsDeployPkg.log (one from successful Centos 8 and one from failed AlmaLinux).
(0000184)
alukoshko   
2021-05-07 20:47   
(Last edited: 2021-05-07 20:49)
Well I see the difference:

CentOS:
INFO: Customization instance RHEL7Customization loaded.

AlmaLinux:
INFO: Customization instance RedHatCustomization loaded.

Errors at the end of logs actually the same for both OS.
(0000185)
alukoshko   
2021-05-07 21:13   
(0000186)
alukoshko   
2021-05-07 21:13   
(0000187)
alukoshko   
2021-05-07 21:16   
Attached files are for 8.3 stable actually but may work on 8.4 beta too I believe.
Please attach log even if customization will fail again as I wanna check the difference.
(0000191)
corporategadfly   
2021-05-13 01:46   
Here is the procedure to create a new template VM from 8.3 stable. After installing 8.3 AlmaLinux, I executed the following commands:

yum remove open-vm-tools --noautoremove
rpm -ivh /tmp/open-vm-tools-11.1.0-2.el8.alma.x86_64.rpm

Installed perl:

yum install perl

After that shutdown VM and converted VM to template. Then, I used this template to create a new VM with multiple NICs. Find attached the toolsDeployPkg.log (Same detection of RedHat family as earlier - no difference).
(0000192)
corporategadfly   
2021-05-13 01:47   
And I apologize for the delay in responding.
(0000212)
alukoshko   
2021-05-25 23:07   
Hello.
Looks like nothing can be done on open-vm-tools side. We have to wait for support from VMware.
(0000357)
jordane fillatre   
2021-10-22 08:58   
Hi,

I've just encountered the issue on the AlmaLinux release 8.4 (Electric Cheetah) and open-vm-tools.x86_64 11.2.0-2.el8
In my mind the issue is resolved by following: https://github.com/vmware/open-vm-tools/blob/master/ReleaseNotes.md#resolved-issues
But Im currently unable to build package in 11.3.5 to comfirm. Where is the roadmap for package update, either for AlmaLinux or the upstream?

Regards
(0000358)
alukoshko   
2021-10-22 09:13   
Hi.

RHEL 8.5 beta has version 11.2.5
CentOS Stream 8 has 11.3.5 https://koji.mbox.centos.org/koji/buildinfo?buildID=19617

Actually we don't know what version will be included in RHEL 8.5 stable.
But you can try CentOS Stream 8 package to confirm.
(0000360)
jordane fillatre   
2021-10-22 12:22   
Ok,
I'm able to use the CentOS Stream 11.3.5 build as you suggested.
I had to temporary update the /etc/redhat-release file content to "CentOS Linux release 8.4 (Electric Cheetah)" in order to succeed.

Regards
(0000361)
alukoshko   
2021-10-22 12:37   
What happens if you don't update /etc/redhat-release?
(0000366)
jordane fillatre   
2021-10-25 09:58   
Hi,
In the context of use of vsphere_virtual_machine terraform resource, the customisation still fail without redhat-release.

In attachment the toolsDeployPkg.log file

Regard
(0000415)
drazenk   
2021-11-22 14:19   
FWIW, I had the same issue and I've worked around it by installing cloud-init (with a suitable configuration) on the template VM.

Without cloud-init VmWare will run some Perl script(s) which will correctly figure out that it's running on something which is RHEL compatible, but won't find the distro name in its list. And then it falls back to the wrong configuration mechanism. It could have tried to use the same configuration mechanism as for the equivalent RHEL release and that would have probably worked fine. But instead it falls back to some other mechanism which doesn't work. I think (but am not 100% sure) it's trying to use the mechanism for the oldest RHEL release it knows about, but that doesn't work on a RHEL 8 clone. Maybe it would with some compatibility packages installed, but I wouldn't go that route.

I don't know from where are those Perl scripts coming. I don't see anything Perlish in the open-vm-tools package (or its dependencies). If the Perl code is coming from VmWare hypervisor then there's nothing Alma Linux (or any other) distribution can do.

But in any case, cloud-init is the new official way to configure cloned VMs and it does work once you manage to figure out how to configure it. Also doesn't have dependencies on the code which is not in the distribution.
(0000417)
alukoshko   
2021-11-22 14:56   
Thank you drazenk for this update.
I think we should add an article to wiki about that.
(0000428)
drazenk   
2021-11-25 20:29   
I had to debug something with this, so I have more info to share. VmWare will put the relevant logs into /var/log/vmware-imc directory.
I'm attaching my log when cloud-init is in use. But you can see (more or less) that VmWare tools are getting a Perl script out of thin air. :-)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
125 [AlmaLinux-8] -OTHER minor N/A 2021-09-02 20:59 2022-02-07 14:46
Reporter: fdr Platform: azure  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: It's harder to reference images on Azure than necessary
Description: I have a prototype switching from Microsoft's "endorsed" CentOS images
from RogueWave/OpenLogic as indicated by the portal's drop-down and
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/endorsed-distros
to AlmaLinux.

It's harder to use AlmaLinux for some reason.

With the "endorsed" images, all I need to do is set the ImageReference, https://docs.microsoft.com/en-us/rest/api/compute/virtual-machines/create-or-update#imagereference.

With AlmaLinux, I need to do two more things:

Most annoyingly, I need to enable AlmaLinux on my subscriptions at
https://portal.azure.com/#blade/Microsoft_Azure_Marketplace/GalleryItemDetailsBladeNopdl/id/almalinux.almalinux/product/.
This is troublesome when setting up new subscriptions. Also the error
message given by Azure to do this is not very good.

Secondly, the API call needs more stuff in it, namely, the "Plan"
field:
(https://docs.microsoft.com/en-us/rest/api/compute/virtual-machines/create-or-update#plan).

Neither are necessary with the "endorsed" CentOS images.
Tags: azure, cloud
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000330)
fdr   
2021-09-03 18:40   
I was messing around with my API calls and it seems there is some way to make a non-marketplace image "offer":

"Creating a virtual machine from a non-Marketplace image does not need Plan information. Please remove the Plan information from VM..."
(0000487)
abo1787   
2022-02-07 14:46   
Thanks for reporting this one we're hitting this one here with our automated pipelines. Were hoping it would be a simple swap from centos to alma, but have to rebuild off alma base image instead of converting.

Hope this helps as a plus 1 to this ticket as I cannot find a way to do so. Also Azure support sent me this way, there may be other coming, and maybe they see this comment.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
183 [AlmaLinux-8] open-vm-tools major always 2022-02-07 08:35 2022-02-07 08:41
Reporter: Mover Platform: AMD Ryzen 7 4800U with Radeon  
Assigned To: OS: Windows 10 专业工作站版  
Priority: urgent OS Version: 21H2 v19044.1387  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Copy file from win10 to almalinux have bug
Description: 很高兴贵公司开发了如此优秀而且免费的Linux,他非常稳定非常实用和华丽,谢谢。同时我也很机智,继centos后,在RockyLinux 与AlmaLinux与openEuler与openAnolis中选择了AlmaLinux,哈哈。AlmaLinux太过于完美,这不得使我介绍给我的 同学 学校 老师 网友 朋友。

我把AlmaLinux通过VMware16 Pro安装到了电脑,在使用过程中想要复制文件到虚拟机,这似乎是件很平常的事,但是在AlmaLinux中失败了,我尝试重新安装了open-vm-tools也是不可以,依然显示错误。但是可以从AlmaLinux复制文件到Windows10.


I am very pleased that your company developed such excellent and free Linux, it is very stable, very useful and gorgeous, thank you. I chose AlmaLinux between RockyLinux and AlmaLinux and openEuler and openAnolis after centos. AlmaLinux is too perfect for me to introduce to my classmates, school teachers, online friends.

I installed AlmaLinux on my computer using VMware16 Pro and it seems to be normal to try to copy files to the virtual machine during use, but it failed in AlmaLinux and I tried to reinstall open-vm-tools and it still failed. But you can copy files from AlmaLinux to Windows10.
Tags: open-vm-tools
Steps To Reproduce: 复制任意文件到虚拟机AlmaLinux即可复现

Copy any file to virtual machine AlmaLinux
Additional Information:
Attached Files: QQ截图20220207163530.png (39,021 bytes) 2022-02-07 08:35
https://bugs.almalinux.org/file_download.php?file_id=113&type=bug
QQ图片20220207155021.png (173,652 bytes) 2022-02-07 08:35
https://bugs.almalinux.org/file_download.php?file_id=114&type=bug
Notes
(0000486)
Mover   
2022-02-07 08:41   
I make a video show error :AlmaLinux copy file error.mp4
url:https://hub.ficc.cc/hub2/video/AlmaLinux%20copy%20file%20error.mp4?preview


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
164 [AlmaLinux-8] -OTHER minor N/A 2021-12-12 18:15 2022-02-05 16:44
Reporter: toracat Platform:  
Assigned To: alukoshko OS:  
Priority: normal OS Version:  
Status: confirmed Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: "Announce" mailing list is not announcing errata
Description: According to :

https://lists.almalinux.org/mailman3/lists/

The description for the "Announce mailing list" is :

AlmaLinux Announcements. This is a low volume list for announcements and notifications of project updates, errata, etc.

However no errata has been sent to this mailing list.
Tags:
Steps To Reproduce:
Additional Information: Also, it is desirable to have "AlmaLinux announce" (or some such) rather than the current "Announce" on the subject line of each mail.
Attached Files:
Notes
(0000450)
alukoshko   
2021-12-13 14:12   
Hello.
We're working on updates email announcements now.
(0000475)
toracat   
2022-01-11 18:14   
Any news?
(0000485)
toracat   
2022-02-05 16:44   
*bump*


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
182 [AlmaLinux-8] -OTHER minor always 2022-02-04 19:42 2022-02-04 19:42
Reporter: gtb Platform: x86_64  
Assigned To: OS: Alma  
Priority: normal OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Almalinux devel repo causes mock install failures
Description: Running mock (on a Fedora system with the latest mock-core-configs) and enabling the devel repo in almalinux (necessary to build some software) results in uninstallable packages due to conflicts.

Tags:
Steps To Reproduce: mock --root /etc/mock/alma+epel-8-x86_64.cfg --enablerepo=devel install perl-IO-Socket-INET6
Additional Information: Expected result:

  perl-IO-Socket-INET6 installed

Actual result:

  Error:
   Problem: package perl-IO-Socket-INET6-2.72-12.module_el8.3.0+2009+2dd00f05.noarch requires perl(:MODULE_COMPAT_5.30.1), but none of the providers can be installed
    - cannot install the best candidate for the job
    - package perl-libs-4:5.30.1-452.module_el8.4.0+2179+01326e37.x86_64 is filtered out by modular filtering
  (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)





I am not sure if this is an issue with mock, the mock core configs, or the alma repo, but the equivalent request works with the centos-stream+epel-next-8 mock cfg (i.e. mock --root /etc/mock/centos-stream+epel-next-8-x86_64.cfg --enablerepo=Stream-Devel install perl-IO-Socket-INET6 )

Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
181 [AlmaLinux-8] grub2 major always 2022-02-01 14:19 2022-02-01 14:19
Reporter: spomata Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: grub.cfg generated under /boot/efi/EFI/centos
Description: While upgrading from CentOS 7 to Alma Linux 8 through the leapp/elevate solution, during the initrd phase the grub.cfg file will be generated under the centos EFI directory rather than under almalinux causing the successive reboot to fail.

Booting with a usb stick and copying the file to the proper location will allow to boot correctly using the "insmod blscfg" method as per the autogenerated grub.cfg file.

Mattermost link: https://chat.almalinux.org/almalinux/pl/gae885ubfjbu7bmwxpspitj73r
Tags: elevate, grub, leapp
Steps To Reproduce: - Start from a CentOS 7.9.2009
- Install leapp and elevate packages for migration to AlmaLinux
- Complete the migration process
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
180 [AlmaLinux-8] libselinux minor always 2022-02-01 10:12 2022-02-01 10:12
Reporter: p-fruck Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: selinux python bindings missing for python3.9
Description: Not quite sure whether this is on purpose, but when using python 3.6 the selinux bindings are preinstalled whereas when using python 3.9 they are not. I'd love to see python-selinux bindings for python 3.9 out of the box.



Tags: python, selinux
Steps To Reproduce: # Make sure both python versions are installed
sudo dnf install python36 python39

# Check for selinux packages with python 3.9, no output is returned for me
/usr/bin/pip3.9 freeze | grep '^se'

# Check for selinux packages with python 3.6, the below output is returned for me
/usr/bin/pip3.6 freeze | grep '^se'
selinux==2.9
sepolicy==1.1
setools==4.3.0
setroubleshoot==1.1
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
179 [AlmaLinux-8] jq minor always 2022-01-24 22:18 2022-01-25 07:55
Reporter: Znuff Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: jq doesn't depend on libonig
Description: [root@cpdev ~]# yum install jq
Last metadata expiration check: 1:31:16 ago on Mon 24 Jan 2022 10:41:39 PM EET.
Dependencies resolved.
===========================================================================================================================================================================================================================================================================================================================================================================
 Package Architecture Version Repository Size
===========================================================================================================================================================================================================================================================================================================================================================================
Installing:
 jq x86_64 1.5-12.el8 appstream 161 k

Transaction Summary
===========================================================================================================================================================================================================================================================================================================================================================================
Install 1 Package

Total download size: 161 k
Installed size: 359 k
Is this ok [y/N]: y
Downloading Packages:
jq-1.5-12.el8.x86_64.rpm 3.6 MB/s | 161 kB 00:00
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 212 kB/s | 161 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing : 1/1
  Installing : jq-1.5-12.el8.x86_64 1/1
  Running scriptlet: jq-1.5-12.el8.x86_64 1/1
  Verifying : jq-1.5-12.el8.x86_64 1/1

Installed:
  jq-1.5-12.el8.x86_64

Complete!
[root@cpdev ~]# jq .user.allow.json
jq: error while loading shared libraries: libonig.so.5: cannot open shared object file: No such file or directory
Tags:
Steps To Reproduce: - yum install jq
- no libonig being installed
- jq will complain about missing libonig

Additional Information:
Attached Files:
Notes
(0000483)
alukoshko   
2022-01-25 07:55   
Hi. How to reproduce this? For me jq is installing with dependency:

sh-4.4# dnf install jq
AlmaLinux 8 - BaseOS 1.8 MB/s | 5.8 MB 00:03
AlmaLinux 8 - AppStream 1.9 MB/s | 8.7 MB 00:04
AlmaLinux 8 - Extras 9.6 kB/s | 12 kB 00:01
Dependencies resolved.
================================================================================
 Package Architecture Version Repository Size
================================================================================
Installing:
 jq x86_64 1.5-12.el8 appstream 161 k
Installing dependencies:
 oniguruma x86_64 6.8.2-2.el8 appstream 187 k

Transaction Summary
================================================================================
Install 2 Packages

Total download size: 348 k
Installed size: 1.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): jq-1.5-12.el8.x86_64.rpm 321 kB/s | 161 kB 00:00
(2/2): oniguruma-6.8.2-2.el8.x86_64.rpm 319 kB/s | 187 kB 00:00
--------------------------------------------------------------------------------
Total 287 kB/s | 348 kB 00:01

...

sh-4.4# jq . 1.json
{
  "name": "John",
  "age": 30,
  "car": null
}


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
176 [AlmaLinux-8] rsync major always 2022-01-22 18:11 2022-01-24 10:05
Reporter: slayerduck Platform:  
Assigned To: OS: Almalinux  
Priority: urgent OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Rsync memleak percpu
Description: I’m using lsyncd to keep folders up to date between servers. This calls upon rsync and thus I’m doing a lot of rsyncs, a couple 1000 per hour. After upgrading from C8 to Almalinux my ram is filling up on destination servers and that eventually crashes the entire server. When i check /proc/meminfo the “percpu” is the one that fills up.

I tried swtiching kernel to elrepo’s and this did not fix the issue. It has to be some lib that was replaced when i converted. I can reproduce this on all servers i update to alma, the more rsyncs i do the faster it fills up. Cloudlinux also has the issue.

Munin mem attached of two production servers, one was actually crashed the other one with 256GB ram nearly when this issue was found.
Tags:
Steps To Reproduce: #! /bin/bash
# Example test for percpu/rsync memleak. Needs two servers, source can be any linux with rsync. Destination with CD or Alma will leak percpu.
# Can reproduce in Cloudlinux and AlmaLinux

# STEP 1: Generate random files for rsync. CD into any empty DIR
workdir=/opt/test3/
cd $workdir

for n in {1..5000}; do
    dd if=/dev/urandom of=file$( printf %03d "$n" ).bin bs=1 count=$(( RANDOM + 1024 ))
done

# STEP 2: Generate SSH keys and make sure you can SSH into remote machine (Alma or Cloud)
ls $workdir | xargs -n1 -P10 -I% rsync -Pa % 192.168.0.212:$workdir

# Open new window, check: cat /proc/meminfo | grep Percpu
# running rm -rf on dir with tranfered files will lower Percpu again. Otherwise no other way i know of so far to reduce mem besides reboot. Dropping caches does not work.
Additional Information:
Attached Files: memory-week.png (48,859 bytes) 2022-01-22 18:11
https://bugs.almalinux.org/file_download.php?file_id=111&type=bug
memory-week-crashed.png (54,778 bytes) 2022-01-22 18:11
https://bugs.almalinux.org/file_download.php?file_id=112&type=bug
Notes
(0000480)
alukoshko   
2022-01-24 08:40   
Hello. Have you tried the same with RHEL or CentOS 8.5?
(0000481)
slayerduck   
2022-01-24 10:05   
I have today, and rhel 8.5 is showing the same symptoms. If i replace rsync with scp the bug occurs still to. So this doesn't seem like an rsync issue.
It also seems like it takes some time for it to go all the way up, if i try to do it on a small VM with 2gb ram it fills up the whole server then somehow does drops back down. So it might only be an issue with machines with larger amounts of ram or over a longer time.

scp or rsyncing 100k files/2gb data with 8 threads, server with 128GB ram: Percpu: 8447616 kB


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
178 [AlmaLinux-8] -OTHER trivial have not tried 2022-01-24 02:12 2022-01-24 02:12
Reporter: d1ng1383rry Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Total system RAM differs
Description: When using free -m

Centos7 shows 32009 total
AlmaLinux 8.5 shows 31890 total

Same system, standalone installations within 24 hours of each other. Wouldn't have caught it, but server software I was installing does a RAM check and refuses to work on AL 8.5, so had to go back to CentOS on that machine.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
177 [AlmaLinux-8] almalinux-release minor always 2022-01-22 21:15 2022-01-22 21:15
Reporter: ayuri Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: don't include repo config into release package
Description: Project states it's 1:1 compatible with CentOS while the first and foremost important package is obviously not. It includes hard-coded repos instead of doing what CentOS does (which is absolutely the right thing) of depending on another package that in its turn supplies the repo info.

Why you came up with this "brilliant" idea is beyond me.

We customize our repos and don't use "upstream" URIs to fetch the repo info, as we sync from our repo server to avoid unnecessary hassle and to have special configuration like repo priority settings.
Tags:
Steps To Reproduce: # rpm -qR centos-linux-release |grep repo | head -1
centos-repos(8)
#
# rpm -qlv centos-linux-release |grep yum.repo
#
# rpm -qlv -p almalinux-release-8.5-4.el8.x86_64.rpm |grep yum.repo
warning: almalinux-release-8.5-4.el8.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID c21ad6ea: NOKEY
-rw-r--r-- 1 root root 951 Dec 21 19:51 /etc/yum.repos.d/almalinux-ha.repo
-rw-r--r-- 1 root root 893 Dec 21 19:51 /etc/yum.repos.d/almalinux-plus.repo
-rw-r--r-- 1 root root 971 Dec 21 19:51 /etc/yum.repos.d/almalinux-powertools.repo
-rw-r--r-- 1 root root 1049 Dec 21 19:51 /etc/yum.repos.d/almalinux-resilientstorage.repo
-rw-r--r-- 1 root root 2690 Dec 21 19:51 /etc/yum.repos.d/almalinux.repo
#
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
175 [AlmaLinux-8] -OTHER feature always 2022-01-22 08:35 2022-01-22 08:35
Reporter: gattadoit Platform: Raspberry pi  
Assigned To: OS: Almalinux  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Raspberry pi 400 WiFi issue
Description: Almalinux and GUI load with no issue. The WiFi shows enabled. I do not see any networks.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
174 [AlmaLinux-8] -OTHER trivial always 2022-01-17 15:01 2022-01-18 16:51
Reporter: adstak Platform:  
Assigned To: OS: AlmaLinux  
Priority: low OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: I believe I have found an miss assigned ID in the updateinfo in the BaseOs repo
Description: So long story short as this is either an easy fix or intended and I simply miss understand.

So we have a a tool I wrote at my company which parses updateinfo in the repo and reports security info to a central place for patch reporting etc.

As part of this I recently added alma info as we moved away from centos. As part of this I stumbled across the id --> ALBA-2019:3693

This seems to be labelled ALBA in the updateinfo but from my understanding this should be an ALSA as it applies a fix for CVE-2018-18074 going from its own description.

My understanding to add context is ALBA is the Alma Linux Bug Announce and ALSA is the ALMA Linux Security Announce. ( This is a guess going from centos's CESA and other updateinfo formats from other providers)

So put simply is ALBA-2019:3693 correct or should this be ALSA-2019:3693 or does it not matter?
Tags:
Steps To Reproduce: Read the updateinfo file from the BaseOS almalinux8 repo
Additional Information:
Attached Files:
Notes
(0000479)
alukoshko   
2022-01-18 16:36   
Hello. ALBA is correct. Original bulletin is RHBA-2019:3693 - Bug Fix Advisory https://access.redhat.com/errata/RHBA-2019:3693
This update doesn't fix vulnerability. It fixes bug that was added in previous security update of this package. So it's bugfix release.

Bug fix:
The fix CVE-2018-18074 leads to a regression (BZ#1758261)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
171 [AlmaLinux-8] dnf minor always 2022-01-05 13:47 2022-01-14 09:48
Reporter: mvrk Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Unable to lock release version
Description: I'm unable to lock release version.

I tried with different ways:

1 - echo "8.4" > /etc/dnf/vars/releasever
2 - Modify the /etc/dnf.conf and add distroverpkg=8.4 to main section

Every time i run dnf upgrade i still get all packages updates to 8.5

If i run: python3 -c 'import dnf, json; db = dnf.dnf.Base(); print(json.dumps(db.conf.substitutions, indent=2))'
Always shows 8 instead of 8.4:

{
  "arch": "x86_64",
  "basearch": "x86_64",
  "releasever": "8"
}

I also tried with: dnf --releasever=8.4 upgrade
but i still get the 8.5 packages.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000477)
eabdullin   
2022-01-14 09:48   
Hello. Thank you, for your question.
It is expected behavior, version 8.4 is no longer supported because 8.5 is released.
If you want to use 8.4, you can uncomment and change 'baseurl' in config files from '/etc/yum.repos.d/' to 'https://repo.almalinux.org/vault/8.4/{BaseOS\AppStream\etc}/{x86_64\aarch64}/os', and comment 'mirrorlist' line.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
167 [AlmaLinux-8] -OTHER major always 2021-12-31 09:38 2022-01-11 18:17
Reporter: sabas3dgh Platform: X86_64  
Assigned To: OS: Amlalinux  
Priority: immediate OS Version: 8  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: rtl8192eu (USB WIFI Dongle) drivers - DKMS build - From Github - Fails [related Bug_ID 0000047]
Description: ============================
Linux localhost.localdomain 4.18.0-348.7.1.el8_5.x86_64 #1 SMP Tue Dec 21 13:57:48 EST 2021 x86_64 x86_64 x86_64 GNU/Linux

AlmaLinux release 8.5 (Arctic Sphynx)
=============================



 rtl8192eu (USB WIFI Dongle) drivers - DKMS build - From Github - Fails
I used the modified driver repository and I can't build the driver/module;

→ make
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.18.0-348.7.1.el8_5.x86_64/build M=/home/admin/Downloads/rtl8192eu-linux-driver modules
make[1]: Entering directory '/usr/src/kernels/4.18.0-348.7.1.el8_5.x86_64'
  CC [M] /home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.o
In file included from /home/admin/Downloads/rtl8192eu-linux-driver/include/drv_types.h:30,
                 from /home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c:17:
/home/admin/Downloads/rtl8192eu-linux-driver/include/wifi.h:1038: warning: "IEEE80211_MAX_AMPDU_BUF" redefined
 #define IEEE80211_MAX_AMPDU_BUF 0x40
 
In file included from /home/admin/Downloads/rtl8192eu-linux-driver/include/osdep_service_linux.h:83,
                 from /home/admin/Downloads/rtl8192eu-linux-driver/include/osdep_service.h:50,
                 from /home/admin/Downloads/rtl8192eu-linux-driver/include/drv_types.h:27,
                 from /home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c:17:
./include/linux/ieee80211.h:1660: note: this is the location of the previous definition
 #define IEEE80211_MAX_AMPDU_BUF 0x100
 
/home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_ch_switch_notify’:
/home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c:445:3: error: too few arguments to function ‘cfg80211_ch_switch_started_notify’
   cfg80211_ch_switch_started_notify(adapter->pnetdev, &chdef, 0);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/admin/Downloads/rtl8192eu-linux-driver/include/osdep_service_linux.h:93,
                 from /home/admin/Downloads/rtl8192eu-linux-driver/include/osdep_service.h:50,
                 from /home/admin/Downloads/rtl8192eu-linux-driver/include/drv_types.h:27,
                 from /home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c:17:
./include/net/cfg80211.h:7673:6: note: declared here
 void cfg80211_ch_switch_started_notify(struct net_device *dev,
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c: At top level:
/home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c:9952:3: error: ‘struct cfg80211_ops’ has no member named ‘mgmt_frame_register’
  .mgmt_frame_register = cfg80211_rtw_mgmt_frame_register,
   ^~~~~~~~~~~~~~~~~~~
/home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c:9952:25: error: initialization of ‘int (*)(struct wiphy *, struct wireless_dev *, u64)’ {aka ‘int (*)(struct wiphy *, struct wireless_dev *, long long unsigned int)’} from incompatible pointer type ‘void (*)(struct wiphy *, struct wireless_dev *, u16, bool)’ {aka ‘void (*)(struct wiphy *, struct wireless_dev *, short unsigned int, _Bool)’} [-Werror=incompatible-pointer-types]
  .mgmt_frame_register = cfg80211_rtw_mgmt_frame_register,
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.c:9952:25: note: (near initialization for ‘rtw_cfg80211_ops.mgmt_tx_cancel_wait’)
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:316: /home/admin/Downloads/rtl8192eu-linux-driver/os_dep/linux/ioctl_cfg80211.o] Error 1
make[1]: *** [Makefile:1571: _module_/home/admin/Downloads/rtl8192eu-linux-driver] Error 2
make[1]: Leaving directory '/usr/src/kernels/4

the same error (more or less would happen when building from original repositories)
Tags:
Steps To Reproduce:
Additional Information: related to this bug
https://bugs.almalinux.org/view.php?id=47

lsusb: >>>
[87939.234099] Code: 1f 44 00 00 f3 0f 1e fa 55 48 89 f5 53 48 89 fb 48 83 ec 08 e8 4b ff ff ff 48 8b 3b 48 89 c6 e8 e0 a7 f8 ff 48 89 ee 48 89 df <48> 8b 40 10 48 83 c4 08 5b 5d ff e0 66 66 2e 0f 1f 84 00 00 00 00
[301735.457109] usb 7-1: USB disconnect, device number 2
[301742.027067] usb 2-3: new high-speed USB device number 4 using ehci-pci
[301742.157244] usb 2-3: New USB device found, idVendor=2357, idProduct=0109, bcdDevice= 2.00
[301742.157249] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[301742.157253] usb 2-3: Product: 802.11n NIC
[301742.157256] usb 2-3: Manufacturer: Realtek
[301742.157258] usb 2-3: SerialNumber: 00e04c000001
[301742.636990] usb 2-3: Vendor: Realtek
[301742.636993] usb 2-3: Product: 802.11n NI
[301742.636994] usb 2-3: Serial:
[301742.636996] usb 2-3: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes):
[301742.636998] usb 2-3: 00: 29 81 00 7c 01 40 03 00
[301742.637000] usb 2-3: 08: 40 74 04 50 14 00 00 00
[301742.637013] usb 2-3: 10: 27 27 28 29 29 29 2b 2b
[301742.637014] usb 2-3: 18: 2b 2c 2c f2 ef ef ff ff
[301742.637016] usb 2-3: 20: ff ff ff ff ff ff ff ff
[301742.637017] usb 2-3: 28: ff ff ff ff ff ff ff ff
[301742.637018] usb 2-3: 30: ff ff ff ff ff ff ff ff
[301742.637020] usb 2-3: 38: ff ff 2b 2b 2b 2b 2b 2b
[301742.637021] usb 2-3: 40: 2d 2d 2d 2c 2c f2 ef ef
[301742.637023] usb 2-3: 48: ff ff ff ff ff ff ff ff
[301742.637025] usb 2-3: 50: ff ff ff ff ff ff ff ff
[301742.637026] usb 2-3: 58: ff ff ff ff ff ff ff ff
[301742.637027] usb 2-3: 60: ff ff ff ff ff ff ff ff
[301742.637029] usb 2-3: 68: ff ff ff ff ff ff ff ff
[301742.637030] usb 2-3: 70: ff ff ff ff ff ff ff ff
[301742.637032] usb 2-3: 78: ff ff ff ff ff ff ff ff
[301742.637033] usb 2-3: 80: ff ff ff ff ff ff ff ff
[301742.637035] usb 2-3: 88: ff ff ff ff ff ff ff ff
[301742.637036] usb 2-3: 90: ff ff ff ff ff ff ff ff
[301742.637038] usb 2-3: 98: ff ff ff ff ff ff ff ff
[301742.637039] usb 2-3: a0: ff ff ff ff ff ff ff ff
[301742.637041] usb 2-3: a8: ff ff ff ff ff ff ff ff
[301742.637042] usb 2-3: b0: ff ff ff ff ff ff ff ff
[301742.637044] usb 2-3: b8: a1 1f 1e 00 00 00 ff ff
[301742.637045] usb 2-3: c0: ff 01 00 10 00 00 00 ff
[301742.637047] usb 2-3: c8: 00 00 ff ff ff ff ff ff
[301742.637048] usb 2-3: d0: 57 23 09 01 e7 47 02 50
[301742.637049] usb 2-3: d8: 3e aa 83 f2 4b 0a 03 52
[301742.637051] usb 2-3: e0: 65 61 6c 74 65 6b 20 0e
[301742.637052] usb 2-3: e8: 03 38 30 32 2e 31 31 6e
[301742.637054] usb 2-3: f0: 20 4e 49 43 20 00 00 ff
[301742.637055] usb 2-3: f8: ff ff ff ff ff ff ff ff
[301742.637057] usb 2-3: 100: ff ff ff ff ff ff ff ff
[301742.637058] usb 2-3: 108: ff ff ff ff ff ff ff ff
[301742.637060] usb 2-3: 110: ff ff ff ff ff ff ff 0d
[301742.637061] usb 2-3: 118: 03 00 05 00 30 00 00 00
[301742.637063] usb 2-3: 120: 00 93 ff ff ff ff ff ff
[301742.637064] usb 2-3: 128: ff ff ff ff ff ff ff ff
[301742.637066] usb 2-3: 130: f6 a8 98 2d 03 92 98 00
[301742.637067] usb 2-3: 138: fc 8c 00 11 9b 44 02 0a
[301742.637069] usb 2-3: 140: ff ff ff ff ff ff ff ff
[301742.637070] usb 2-3: 148: ff ff ff ff ff ff ff ff
[301742.637072] usb 2-3: 150: ff ff ff ff ff ff ff ff
[301742.637073] usb 2-3: 158: ff ff ff ff ff ff ff ff
[301742.637074] usb 2-3: 160: ff ff ff ff ff ff ff ff
[301742.637076] usb 2-3: 168: ff ff ff ff ff ff ff ff
[301742.637077] usb 2-3: 170: ff ff ff ff ff ff ff ff
[301742.637079] usb 2-3: 178: ff ff ff ff ff ff ff ff
[301742.637080] usb 2-3: 180: ff ff ff ff ff ff ff ff
[301742.637082] usb 2-3: 188: ff ff ff ff ff ff ff ff
[301742.637083] usb 2-3: 190: ff ff ff ff ff ff ff ff
[301742.637085] usb 2-3: 198: ff ff ff ff ff ff ff ff
[301742.637086] usb 2-3: 1a0: ff ff ff ff ff ff ff ff
[301742.637088] usb 2-3: 1a8: ff ff ff ff ff ff ff ff
[301742.637089] usb 2-3: 1b0: ff ff ff ff ff ff ff ff
[301742.637091] usb 2-3: 1b8: ff ff ff ff ff ff ff ff
[301742.637093] usb 2-3: 1c0: ff ff ff ff ff ff ff ff
[301742.637094] usb 2-3: 1c8: ff ff ff ff ff ff ff ff
[301742.637096] usb 2-3: 1d0: ff ff ff ff ff ff ff ff
[301742.637097] usb 2-3: 1d8: ff ff ff ff ff ff ff ff
[301742.637098] usb 2-3: 1e0: ff ff ff ff ff ff ff ff
[301742.637100] usb 2-3: 1e8: ff ff ff ff ff ff ff ff
[301742.637101] usb 2-3: 1f0: ff ff ff ff ff ff ff ff
[301742.637103] usb 2-3: 1f8: ff ff ff ff ff ff ff ff
[301742.637106] usb 2-3: RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
[301742.637108] usb 2-3: RTL8192EU MAC: 50:3e:aa:83:f2:4b
[301742.637110] usb 2-3: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
[301742.664017] usb 2-3: Firmware revision 19.0 (signature 0x92e1)
[301743.708628] usbcore: registered new interface driver rtl8xxxu
[301743.777950] rtl8xxxu 2-3:1.0 wlp0s29f7u3: renamed from wlan0
[301743.806331] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u3: link is not ready
[301743.840926] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u3: link is not ready
[301743.946174] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u3: link is not ready
[301743.966340] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u3: link is not ready
[301745.272812] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u3: link is not ready
[301746.480838] wlp0s29f7u3: authenticate with 5c:6a:80:48:ea:d8
[301746.505111] wlp0s29f7u3: send auth to 5c:6a:80:48:ea:d8 (try 1/3)
[301746.712442] wlp0s29f7u3: send auth to 5c:6a:80:48:ea:d8 (try 2/3)
[301746.920260] wlp0s29f7u3: send auth to 5c:6a:80:48:ea:d8 (try 3/3)
[301747.128056] wlp0s29f7u3: authentication with 5c:6a:80:48:ea:d8 timed out
[301748.624730] wlp0s29f7u3: authenticate with 5c:6a:80:48:ea:d8
[301748.651316] wlp0s29f7u3: send auth to 5c:6a:80:48:ea:d8 (try 1/3)
[301748.856053] wlp0s29f7u3: send auth to 5c:6a:80:48:ea:d8 (try 2/3)
[301749.065199] wlp0s29f7u3: send auth to 5c:6a:80:48:ea:d8 (try 3/3)
[301749.273067] wlp0s29f7u3: authentication with 5c:6a:80:48:ea:d8 timed out
Attached Files: rtl8192eu.patch (1,258 bytes) 2022-01-02 20:07
https://bugs.almalinux.org/file_download.php?file_id=110&type=bug
Notes
(0000467)
sabas3dgh   
2021-12-31 16:00   
it seems that it won't build under 4.18 alma linux kernel. Need a fix; thanks.
(0000469)
toracat   
2022-01-02 20:07   
@sabas3dgh

I uploaded a patch file that will allow compiling the code. I don't have the relevant device, so have no idea if the driver actually works.
(0000476)
toracat   
2022-01-11 18:17   
@sabas3dgh

Did the patch work? If so, could you confirm it so that this ticket can be closed as 'resolved'?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
172 [AlmaLinux-8] dnf minor always 2022-01-06 06:17 2022-01-06 06:17
Reporter: kfujinaga Platform: XenServer  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Did not update grub.cfg automatically after kernel update in AlmaLinux 8.5
Description: In the AlmaLinux 8.5 enviroment created from 8.5 install media, I executed "dnf upgrade".
In this action, new kernel "4.18.0-348.7.1.el8_5.x86_64" was installed.
But /boot/grub2/grub.cfg was not updated.

If I execute "grub2-mkconfig -o /boot/grub2/grub.cfg" manually, boot/grub2/grub.cfg is updated.

I can not find this problem in AlmaLinux 8.4,
Tags:
Steps To Reproduce: 1. Install AlmaLinux 8.5 (AlmaLinux-8.5-x86_64-dvd.iso, Server(GUI) mode)
2. Check kernel version

# uname -r
4.18.0-348.el8.x86_64
# rpm -qa |grep kernel |sort
kernel-4.18.0-348.el8.x86_64
kernel-core-4.18.0-348.el8.x86_64
kernel-modules-4.18.0-348.el8.x86_64
kernel-tools-4.18.0-348.el8.x86_64
kernel-tools-libs-4.18.0-348.el8.x86_64

2. Check boot settings.

(grubby)
# grubby --info=ALL | grep -E "^kernel|^index"
index=0
kernel="/boot/vmlinuz-4.18.0-348.el8.x86_64"
index=1
kernel="/boot/vmlinuz-0-rescue-f2cfcd79b1db49188a987dffe9c4ee73"

(grub.cfg)
# grep "^menuentry" /boot/grub2/grub.cfg
menuentry 'AlmaLinux (4.18.0-348.el8.x86_64) 8.5 (Arctic Sphynx)' --class almalinux --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.18.0-348.el8.x86_64-advanced-9a24da02-c767-4dad-a0f4-05bbd22909c7' {
menuentry 'AlmaLinux (0-rescue-f2cfcd79b1db49188a987dffe9c4ee73) 8.5 (Arctic Sphynx)' --class almalinux --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-f2cfcd79b1db49188a987dffe9c4ee73-advanced-9a24da02-c767-4dad-a0f4-05bbd22909c7' {

4. system update (kernel "4.18.0-348.7.1.el8_5.x86_64" was installed)

Update all packages.

# dnf upgrade

5. check kernel verson

kernel 4.18.0-348.7.1.el8_5.x86_64 was installed.

# uname -r
4.18.0-348.el8.x86_64
# rpm -qa |grep kernel |sort
kernel-4.18.0-348.7.1.el8_5.x86_64
kernel-4.18.0-348.el8.x86_64
kernel-core-4.18.0-348.7.1.el8_5.x86_64
kernel-core-4.18.0-348.el8.x86_64
kernel-modules-4.18.0-348.7.1.el8_5.x86_64
kernel-modules-4.18.0-348.el8.x86_64
kernel-tools-4.18.0-348.7.1.el8_5.x86_64
kernel-tools-libs-4.18.0-348.7.1.el8_5.x86_64

6. Check boot settings.
gubby return new setting, but grub.conf was not updated.

(grubby)
# grubby --info=ALL | grep -E "^kernel|^index"
index=0
kernel="/boot/vmlinuz-4.18.0-348.7.1.el8_5.x86_64"
index=1
kernel="/boot/vmlinuz-4.18.0-348.el8.x86_64"
index=2
kernel="/boot/vmlinuz-0-rescue-f2cfcd79b1db49188a987dffe9c4ee73"

(grub.cfg)
# grep "^menuentry" /boot/grub2/grub.cfg
menuentry 'AlmaLinux (4.18.0-348.el8.x86_64) 8.5 (Arctic Sphynx)' --class almalinux --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.18.0-348.el8.x86_64-advanced-9a24da02-c767-4dad-a0f4-05bbd22909c7' {
menuentry 'AlmaLinux (0-rescue-f2cfcd79b1db49188a987dffe9c4ee73) 8.5 (Arctic Sphynx)' --class almalinux --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-f2cfcd79b1db49188a987dffe9c4ee73-advanced-9a24da02-c767-4dad-a0f4-05bbd22909c7' {

7. Reboot.

# reboot

8. Check booted kernel version

Old kernel was booted.

# uname -r
4.18.0-348.el8.x86_64
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
57 [AlmaLinux-8] -OTHER feature always 2021-04-06 16:10 2022-01-03 17:56
Reporter: enigma131 Platform: Server - Desktop  
Assigned To: OS: Amalinux  
Priority: normal OS Version: 8.3  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: rtl8188eu (USB WIFI Dongle) drivers - build fails- From Github
Description: I have a popular wifi usb dongle (a Realtek TL-WN725N), and I try to make it work under Alama.
When i insert dongle after system boot, i got, from dmesg :

[ 90.432685] usb 1-5: new high-speed USB device number 7 using xhci_hcd
[ 90.559175] usb 1-5: New USB device found, idVendor=0bda, idProduct=8179, bcdDevice= 0.00
[ 90.559176] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 90.559177] usb 1-5: Product: 802.11n NIC
[ 90.559178] usb 1-5: Manufacturer: Realtek

Since kernel module isn't include in Kernel 4.18, I have try to compile it following this :

https://tutorialforlinux.com/2020/06/05/step-by-step-centos-8-realtek-rtl8188eu-driver-installation

Then I got error at make stage :

/home/alma/rtl8188eu/os_dep/ioctl_linux.c:7814:3: error: « struct iw_handler_def » no member « private »
  .private = rtw_private_handler,
   ^~~~~~~

I it possible to make it work ? I need to transfer the internet trafic to the dongle and use RJ45 for the server part.
Tags: not-a-bug
Steps To Reproduce:
Additional Information:
Attached Files: dmesg (69,610 bytes) 2021-04-07 11:19
https://bugs.almalinux.org/file_download.php?file_id=70&type=bug
Notes
(0000127)
alukoshko   
2021-04-06 17:13   
Hello.
Have a look at the following issue: https://github.com/lwfinger/rtl8188eu/issues/302
Looks like it's impossible with stock kernel.
(0000128)
enigma131   
2021-04-06 17:35   
Hi, yes I see, the author don't seems want to make changes for CentOs 8 series..
I have found a other github here : https://github.com/aircrack-ng/rtl8188eus
I will try it tomorrow and tell you informed
(0000131)
enigma131   
2021-04-07 11:19   
I've tested the aircrak one, I had to modify 3 files:

grep -r almalinux
os_dep/linux/rtw_android.c:#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4, 18, 0)) // almalinux ex 5,0
os_dep/linux/os_intfs.c: #if LINUX_VERSION_CODE < KERNEL_VERSION(4, 18, 0) // almalinux ex 4,19
core/rtw_mlme_ext.c: /* fallthrough */ // almalinux

And after then it compiles and isntalls:

lsmod | grep 80211
cfg80211 806912 1 8188eu
rfkill 28672 4 cfg80211

But there is a but.
After inserting the usb dongle, i get error message in dmesg and no wifi, see attached file at the end
(0000134)
enigma131   
2021-04-08 16:45   
So if I understand well, there is no way to correct this ?
I'm frustrating because this dongle is working everywhere else ( Debian 11, Ubuntu 20.04, Fedora 33, Windows 10 ...) without compiling / installing a piece of code / driver.

My understanding for solving the issue : changing kernel or changing dongle.

1) In case of changing dongle, where could I find certified hardware compatibility list ?
2) In case of changing kernel, which one would be a good target ? (I don't want a 'rolling' type kernel, I'm searching a LTS type which doesn't increment each week) .
And according to https://www.kernel.org/category/releases.html, standard kernel LTS have EOL previous to 2029.
(0000135)
alukoshko   
2021-04-08 16:50   
1) We're compatible with RHEL8 so supported hardware is the same: https://catalog.redhat.com/hardware
2) http://elrepo.org provides newer kernels for RHEL-based distros. I believe kernel-lt (Long Term) package will fit your needs.
(0000136)
enigma131   
2021-04-08 17:25   
This one gives only 1 response https://catalog.redhat.com/hardware/components/search?q=wifi&p=1 and seems not really a dongle.
I think a internet search engine will give better responses, or Redhat have definitivelly bad wifi support (it's possible!). I will continue to search this way, but I don't want buy and buy without be sure of result.
I will look too for elrepo and kernels, thanks for the trick!
(0000137)
enigma131   
2021-04-09 07:42   
Following your link http://elrepo.org/tiki/HomePage , I discover "latest stable mainline kernels" . Are theses related to my link from kernel.org?
If yes I don't see the real benefit over Debian , because I'm searching a long term Kernel like the one from Redhat (4.18) -> support up to 2019.

Concerning searching a other Wifi dongle, i discover the other thread you have solved https://bugs.almalinux.org/view.php?id=47 with rtl8192, I found one here : https://www.amazon.fr/KuWFi-300Mbps-Realtek-RTL8192-Adaptateur/dp/B01D2L1U4S
But not sure for me it will work in future for kernel 4.18 and Alma 8.x. (x >=4)
Take my example witk rtl8188eu, It was compiling with early stages of CenntOs8 , and now we are at stage 8.3 and compiles fails.
(0000138)
alukoshko   
2021-04-09 07:56   
Of course if you going to buy another dongle you should buy the one supported out of the box. Unofficial drivers from github are always kind of lottery.

kernel-lt from elrepo.org will stay on 5.4 version for long time and then someday will change to 5.10.
If you need the same kernel version till 2029 then yes, elrepo's kernel doesn't fit your needs.
(0000139)
enigma131   
2021-04-09 10:39   
I don't know where are located Alma's kernel sources, but if they are same as Centos I've look at vault's site. In drivers/staging there are 5 Realtek drivers sources including rtl8192 and rtl8188eu's one and no one is working from the begining without compilation/modifications/adaptation !
Strange situation!
(0000140)
enigma131   
2021-04-09 18:12   
I've finally make it work.
How I did it?
First I've look with modinfo, all other distros (Fedora, Debian unbuntu) are based on version 4.14 from feb. 2013 and are fully fonctionnal.
I'll go back to lwfinger and see 4 branches, including Master.
I've git clone branch v4.1.8_9499 (this one is from dec. 2013)
Made modifications:
os_dep/rtw_android.c:#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4, 18, 0)) // 5,0 alma line 359
os_dep/os_intfs.c:#elif (LINUX_VERSION_CODE >= KERNEL_VERSION(4, 18, 0)) // 4,19 alma line 419
Then it compiles and WORKS !
Package includes dkms install.
ps: branch v5.2.2.4 compiles too but haven't try, but Master and branch kernel_code didn't compile

Could be closed, but I would be great if method could be sticked for other peoples (or would it be better to post solution at lwfinger git ?)
(0000141)
alukoshko   
2021-04-09 18:22   
I've found that elrepo-testing repo contain that driver:
http://mirror.rc.usf.edu/elrepo/testing/el8/x86_64/RPMS/kmod-r8188eu-0.0-1.el8_3.elrepo.x86_64.rpm
Maybe you should try it too, it won't require dkms.
(0000142)
enigma131   
2021-04-09 19:10   
Hum this one is stamped with first -240 serie and not with latest -240.15 , so it can't load.
It's the problem with testing, compilations are not always made every kernel upgrades.
I prefer have a dkms build, until source is compatible with upcoming kernels of course.
Thanks for the link in case of ...
(0000143)
enigma131   
2021-04-09 20:07   
I have added the solution to lwfinger's git bug track 302, but if he don't react i will fork the correct branch on my git.
(0000156)
toracat   
2021-04-23 17:58   
Please note that ELRepo's kmod packages are kABI-tracking, meaning they survive kernel updates. This is the main point that is different from the dkms method which requires rebuilding upon every kernel update.

So, usually kmods are built against the first (GA) kernel of a major release (for example RHEL 8.0) and they should continue to work withing that release (8.x). However there could be a kABI breakage withing a point release. In this case ELRepo will rebuild and update the kmod. If you encounter this situation, you can file a report at their bug tracker, https://elrepo.org/bugs .
(0000157)
toracat   
2021-04-23 18:18   
@enigma131

By the way why kmod-r8188eu-0.0-1.el8_3.elrepo.x86_64.rpm is in the testing repository is the following. Someone requested to provide a kmod-rtl8188eu package in:

https://elrepo.org/bugs/view.php?id=1062#c7541

As you can see, ELRepo fulfilled the request within a day and asked the submitter to test it. However there was no response. Without feedback, the package has to stay in the testing repo.

If you could give it a try and report the result, that would be much appreciated. It you'd rather not open an account there, you could reply here, too.
(0000158)
toracat   
2021-04-23 18:20   
@enigma131

Also, the source code can be found here:

https://github.com/elrepo/packages/tree/master/r8188eu-kmod/el8
(0000161)
toracat   
2021-04-23 21:49   
OK, I just found out that there was indeed a kABI breakage in RHEL 8 and kmod-r8188eu-0.0-1.el8_3 (which was built for kernel-4.18.0-240.el8) does not work for newer kernels. It will need to be rebuilt against the latest kernel. I will update the status here with any progress.
(0000162)
enigma131   
2021-04-24 06:26   
Ok toracat, thanks for report. As I'm a Github regitered user, I will try to compile the kmod package next week and report there if error(s).
Yes of course it would be great if we can have working kmod modules for our wireless devices for all 8.x kernel updates
Concerning DKMS, I was looking at the Lwfinger's source, it is very complete and was (and is still) updated since many years. The branch v4.1.8_9499 is updated now and is fully functionnal now without errors (I had posted there my compile errors). I have some experience concerning dkms and my DVB cards, but no experience for kmod building.
(0000163)
toracat   
2021-04-24 07:39   
@enigma131

Since you have been successfully building and using the Lwfinger's source, it's probably a good idea for you to stick with it. The kmod method is a better choice [only] when the kABI is stable. It looks to me like the code being used in ELRepo's kmod keeps breaking with kernel updates. In a situation like this, dkms would be the way to go.
(0000174)
enigma131   
2021-04-27 16:38   
I've tested the kmod driver today:

sudo dnf --enablerepo="elrepo-testing" install kmod-r8188eu
...
depmod: WARNING: /lib/modules/4.18.0-240.el8.x86_64/extra/r8188eu/r8188eu.ko needs unknown symbol iwe_stream_add_event
depmod: WARNING: /lib/modules/4.18.0-240.el8.x86_64/extra/r8188eu/r8188eu.ko needs unknown symbol lib80211_get_crypto_ops
depmod: WARNING: /lib/modules/4.18.0-240.el8.x86_64/extra/r8188eu/r8188eu.ko needs unknown symbol wireless_send_event
depmod: WARNING: /lib/modules/4.18.0-240.el8.x86_64/extra/r8188eu/r8188eu.ko needs unknown symbol iwe_stream_add_point

But installed. Removing dkms, pulled out the dongle, rebooting,
then : dmesg -w , Pull in the dongle I got:

[ 454.338365] usb 1-5: new high-speed USB device number 8 using xhci_hcd
[ 454.464961] usb 1-5: New USB device found, idVendor=0bda, idProduct=8179, bcdDevice= 0.00
[ 454.464963] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 454.464964] usb 1-5: Product: 802.11n NIC
[ 454.464965] usb 1-5: Manufacturer: Realtek
[ 454.464966] usb 1-5: SerialNumber: 00xxxxxxxx
[ 454.479010] r8188eu: loading out-of-tree module taints kernel.
[ 454.479156] r8188eu: module verification failed: signature and/or required key missing - tainting kernel
[ 454.479267] r8188eu: Unknown symbol iwe_stream_add_event (err 0)
[ 454.479442] r8188eu: Unknown symbol lib80211_get_crypto_ops (err 0)
[ 454.479476] r8188eu: Unknown symbol wireless_send_event (err 0)
[ 454.479529] r8188eu: Unknown symbol iwe_stream_add_point (err 0)

Conclusion kmod module did not work , yes. I will post this on Kmod's git next days
(0000175)
toracat   
2021-04-27 16:44   
Thanks for testing and reporting the result.
(0000177)
enigma131   
2021-04-30 06:37   
Bug posted on elrepo's Git : https://github.com/elrepo/packages/issues/238
(0000189)
enigma131   
2021-05-10 11:11   
Package removed from elrepo, and maintainer didn't want to investigate more work.
So DKMS is the only solution that work.
(0000190)
toracat   
2021-05-11 00:38   
It is not that we (ELRepo) do not want to investigate more work but rather the source code for this particular driver does not make using kmod packages practical.

As noted earlier here or in this link:

https://github.com/elrepo/packages/issues/238#issuecomment-832336150

I was able to build the kmod package from the source code in the Lwfinger's branch v4.1.8_9499. However it contains many kernel symbols that cause kABI breakage. To take advantage the kmod method, it is critically important the code does not break at each kernel update. There is nothing we (ELrepo) can do about it, unfortunately.
(0000462)
akdev   
2021-12-31 02:34   
this looks very off-topic for this issue tracker. I presume the linked module never built for RHEL8 to begin with.

In any case - the only thing to do is to file an issue with the owner of the github repo.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
168 [AlmaLinux-8] -OTHER crash always 2022-01-02 15:05 2022-01-02 15:05
Reporter: Arbich Platform: x86_64  
Assigned To: OS: almalinux kde plasma 5  
Priority: high OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: After updating the KDE Plasma 5 components, the operating system is not loaded.
Description:
Installed Almalinux KDE Plasma 5 8.4 on a Lenovo G550 (Core 2 Duo) laptop. Executed a package update in the terminal. The update ended up freezing the laptop. Performed hardreset. Loading the laptop ended with the issuance of a diagnostic message:

"The current theme cannot be loaded due to the errors below, please select another theme.

file:///usr/share/sddm/themes/01-breeze-fedora/Main.qml:14:1: plugin cannot be loaded
for module "org.kde.plasma.core": Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/
core/libcorebindingsplugin.so: (/lib64/libKF5XmlGui.so.5: undefined symbol:
_ZN19KeySequenceRecorder16recordingChangedEv)"

  and laptop freezing. The laptop is not operational at this time. Sorry for the bad english.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: IMG_20220101_193052483_m.jpg (452,549 bytes) 2022-01-02 15:05
https://bugs.almalinux.org/file_download.php?file_id=108&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
30 [AlmaLinux-8] selinux-policy minor have not tried 2021-02-24 21:37 2021-12-31 03:05
Reporter: wadeh Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Launched firefox and tried to play a video, got SELinux alert
Description: SELinux alert displayed while playing audio on youtube in firefox.
Tags:
Steps To Reproduce: 1. Loaded AlmaLinux RC1 in a VM on Fedora 33.
2. in background installed epel and installed some packages:
       dnf install marble marble-astro marble-qt
3. Launched firefox and opened a tab, entered youtube.com
4. Selected some classical music and it started playing
5. The selinux alert was displayed
       
Additional Information: See attached
Attached Files: selinuxaltert.txt (2,447 bytes) 2021-02-24 21:37
https://bugs.almalinux.org/file_download.php?file_id=58&type=bug
Notes
(0000446)
akdev   
2021-12-13 04:03   
>Loaded AlmaLinux RC1 in a VM on Fedora 33.

It's been a while since RC1 was released. I will have to check if this alert happens on latest release.
(0000466)
akdev   
2021-12-31 03:05   
installed AlmaLinux 8.5, installed firefox, played music on youtube - no SELinux alerts and no avc denials in the logs


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
120 [AlmaLinux-8] flatpak minor always 2021-08-24 16:35 2021-12-31 03:00
Reporter: nahumcastro Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: KDE flatpak apps do not show any text
Description: Install QGIS as advised here https://qgis.org/es/site/forusers/alldownloads.html#flatpak
and the app shows no text, just buttons, there are no menus, dialogs, all text is missing

The same behavior happened with KDevelop.
Tags: not-a-bug
Steps To Reproduce: Install QGIS as advised here https://qgis.org/es/site/forusers/alldownloads.html#flatpak
and the app shows no text, just buttons, there are no menus, dialogs, all text is missing
Additional Information: QGIS version 3.16LTS
Attached Files:
Notes
(0000465)
akdev   
2021-12-31 03:00   
this works fine for me - the application crashes on Wayland as it probably a Qt version that doesn't support Wayland fully.

I was able to execute the application on a fresh AlmaLinux 8.5 instance with `QT_QPA_PLATFORM=xcb flatpak --user run org.qgis.qgis`


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
91 [AlmaLinux-8] glusterfs minor always 2021-06-01 15:41 2021-12-31 02:44
Reporter: figless Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: glusterfs packages are built from incorrect sources
Description: The versions of glusterfs, glusterfs-client, glusterfs-fuse, glusterfs-libs, glusterfs-rdma (BaseOS), and glusterfs-api, glusterfs-cli (AppStream) are all version 6.0:56 which does not match what exists in RHEL (BaseOS, AppStream), which is version 6.0:49.1.

It seems that the srpm for gluster has been rebuilt from "Red Hat Storage Native Client for RHEL 8" rather than BaseOS/AppStream
Tags: not-a-bug
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000463)
akdev   
2021-12-31 02:44   
[akdev@virt0 ~]$ cat /etc/redhat-release
CentOS Stream release 8
[akdev@virt0 ~]$ sudo dnf info glusterfs | awk '/Version/ || /Release/'
Version : 6.0
Release : 56.4.el8

[akdev@almalinux8 ~]$ cat /etc/redhat-release
AlmaLinux release 8.5 (Artic Sphynx)
[akdev@virt0 ~]$ sudo dnf info glusterfs | awk '/Version/ || /Release/'
Version : 3.12.2
Release : 40.2.el8
Version : 6.0
Release : 56.4.el8

looks like AlmaLinux offers the correct version - 56.4.el8 matching centos 8 stream


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
60 [AlmaLinux-8] almalinux-release major N/A 2021-04-07 18:16 2021-12-31 02:32
Reporter: hvdkooij Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Minimal ISO does require network repository during installation
Description: Minimal ISO does require network repository during installation from an USB thumbdrive.
I have not found a way to install a minimal system from that ISO image. It always asks for a repository.
This is not expected behaviour.
Tags: not-a-bug
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000145)
hvdkooij   
2021-04-12 18:55   
I have now also tested the full DVD ISO.
If I write it to a USB device and try to install from it the system fails to setup a repository.
So installing from USB on a clean system is not possible at this time.
(0000146)
hvdkooij   
2021-04-12 18:59   
How to reproduce:
 1. Download ISO image of AlmaLinux.
 2. Use Rufus on Windows 10 to create a boootable USB drive.
 3. Boot test machine from this USB device.
 4. Installer will fail to find a source to install from and only presents a network install option for which I don't know the URL.
(0000147)
enigma131   
2021-04-13 16:21   
It was working here via same way. Had you verifed checksum of downloaded iso ?
(0000461)
akdev   
2021-12-31 02:32   
works for me on latest 8.5 image - I was able to install from the minimal ISO with no internet


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
166 [AlmaLinux-8] almalinux-release major always 2021-12-28 18:59 2021-12-30 07:25
Reporter: regobk Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Running almalinux-deploy.sh results in Download RPM-GPG-KEY-AlmaLinux Error
Description: After running an update on a centos 8 server to ensure compatibility with AlmaLinux 8.5, the typical download of the deploy script is ran. After the download and making it executable, running ./almalinux-deploy.sh results in:

"Check root privileges OK
Download RPM-GPG-KEY-AlmaLinux ERROR
    curl: (60) SSL certificate problem: certificate has expired
    More details here: https://curl.haxx.se/docs/sslcerts.html

    curl failed to verify the legitimacy of the server and therefore could not
    establish a secure connection to it. To learn more about this situation and
    how to fix it, please visit the web page mentioned above."
Tags:
Steps To Reproduce: Unsure of steps to reproduce as this has only happened on one server.
Additional Information: Running CentOS Linux release 8.5.2111 - All updates have been ran.
Attached Files:
Notes
(0000459)
regobk   
2021-12-28 19:13   
Update: I edited the script to add the -k flag for curl to disable the strict cert check. This fixed the issue I was having.
(0000460)
alukoshko   
2021-12-30 07:25   
I see repo.almalinux.org cert was renewed exactly 2021-12-28.
Could you recheck please?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
117 [AlmaLinux-8] lynx minor have not tried 2021-08-12 16:49 2021-12-13 14:14
Reporter: moredaylight Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: CVE-2021-38165: Lynx through 2.8.9 can expose credentials via SNI
Description: https://nvd.nist.gov/vuln/detail/CVE-2021-38165
Lynx through 2.8.9 mishandles the userinfo subcomponent of a URI, which allows remote attackers to discover cleartext credentials because they may appear in SNI data.

https://www.openwall.com/lists/oss-security/2021/08/07/1
Tags:
Steps To Reproduce: If you have an HTTPS server listening on localhost, this is pretty easy to reproduce.

Use tcpdump or wireshark to watch traffic.
tcpdump -vvA -i lo port 443

Attempt to connect to localhost passing credentials in the URL.
lynx https://user:password@localhost/

You will see "user:password@localhost" in the plaintext of the tcpdump output.
Additional Information:
Attached Files:
Notes
(0000445)
akdev   
2021-12-13 03:59   
this is something to be reported and fixed upstream
(0000451)
alukoshko   
2021-12-13 14:14   
RHEL8 is not listed for some reason.
https://access.redhat.com/security/cve/cve-2021-38165


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
34 [AlmaLinux-8] acpid tweak sometimes 2021-02-26 19:23 2021-12-13 04:05
Reporter: Shii Cube Kakinden Platform: HP APU Note 15inch HD TFT  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Kit Command-based Prompt Producer Program Bug
Description: / home [AMD 3] or [AMD 4] or [AMD 5] There are many problems with Hee Cmd.com systems that do not have Cloud Native nest tiles related to $$ Mcode in the folder.
Tags: fp, incomplete
Steps To Reproduce: https://en.wikipedia.org/wiki/Cron

In the weakness less than the problem-solving program, it includes subtle problems.
Additional Information: https://en.wikipedia.org/wiki/Scheduling_(computing)
Attached Files:
Notes
(0000447)
akdev   
2021-12-13 04:05   
this may well be spam


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
106 [AlmaLinux-8] lvm2 crash always 2021-06-25 23:35 2021-12-13 04:02
Reporter: toni Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: solved
Description: i use to create lvm always.
after creating i proceed for installation, and installation report about one volym group.
vg= log /var/log
we cant give a name "log" to a volym group, since it's exist .
Tags: incomplete
Steps To Reproduce:
Additional Information: naming this vg to logg will solve the problem.
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
151 [AlmaLinux-8] almalinux-release major always 2021-11-15 23:15 2021-12-11 22:19
Reporter: cshabazian Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: rpm -K on https://repo.almalinux.org/almalinux/almalinux-release-latest-8.x86_64.rpm fails
Description: Reported as high priority in case the package has been compromised
Tags:
Steps To Reproduce: Run the conversion script, or download the rpm and run rpm -K on it
Additional Information:
Attached Files:
Notes
(0000391)
akdev   
2021-11-16 13:36   
I wasn't able to reproduce on a clean Alma Linux system, it doesn't seem like the package was compromised but your system might be missing some keys? (on my systems I have /etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux which is provided by almalinux-release)

    $ curl "https://repo.almalinux.org/almalinux/almalinux-release-latest-8.x86_64.rpm" -LOJ 2>/dev/null&& rpm -K almalinux-release-latest-8.x86_64.rpm
almalinux-release-latest-8.x86_64.rpm: digests signatures OK

seems like this would be a bug in the migration script
(0000392)
cshabazian   
2021-11-16 17:03   
That was my second guess, that it was a bug in the migration script as the AlmaLinux keys aren't on my system and the script doesn't add them first. It looks like the problem is in the install_rpm_pubkey() function. In order to get it to run, I had to comment out:
  # if get_status_of_stage "install_rpm_pubkey"; then
  # return 0
  # fi
Add define pubkey_url:
    #local -r pubkey_url="${ALMA_PUBKEY_URL:-https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux}"
    local -r pubkey_url="https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux"

Sorry, no time to dig deeper into it. After I did the above, it worked fine.
(0000441)
akdev   
2021-12-11 19:24   
coming back to this, I just realized there's very little detail on the original report

so I assume you mean this script: https://github.com/AlmaLinux/almalinux-deploy

could you elaborate on what you were migrating from?
(0000442)
akdev   
2021-12-11 19:29   
I looked at the source code and the relevant function looks fine, this is called unconditionally from the main function of the script.

the only thing is that there's a check to skip the function if it already ran but that seems correct as well.
(0000443)
cshabazian   
2021-12-11 22:19   
I was converting from CentOS to Alma using the conversion script. It seems to be working now, so I don't know if it got fixed or if I used an old script.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
65 [AlmaLinux-8] -OTHER minor always 2021-04-21 16:14 2021-12-10 12:12
Reporter: Znuff Platform:  
Assigned To: sfokin OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: virt-sysprep created images do not run the --firstboot script
Description: As per title, we usually create our own templates/images for deployment.

Normally we just install the OS minimally, then install the packages that we need, dump to an image to a file, then run `virt-sysprep -a file.img --firstboot our-script.sh`.

This works fine with CentOS 8, Ubuntu 20 and so on -- as expected, on first boot the script runs via the installed `guestfs-firstboot.service` without issues.

On AlmaLinux 8.3 the initial script doesn't run at all.

I'm not sure what prevents it from running. I've run `virt-sysprep -v` against both CentOS 8 and AlmaLinux 8.3, and the output is the same in regards to the `--firstboot` part.
Tags:
Steps To Reproduce: 1. Install AlmaLinux as a guest in a VM
2. Dump it to an image file (ie: qemu-img convert -O raw /block/device almalinux.img)
3. Run virt-sysprep on it -- virt-sysprep -a almalinux.img --firstboot our-script.sh
4. Deploy the newly created image in your environment
5. Expect our-script.sh to run via the installed guestfs-firstboot.service
6. Script doesn't run on first boot
Additional Information: https://libguestfs.org/virt-sysprep.1.html#firstboot-vs-script
Attached Files:
Notes
(0000281)
sfokin   
2021-06-24 13:34   
Could you please help me with reproducing bug. I've had a problem on step 3.
Ive tried on Centos 8.4
===================
# virt-sysprep -a /media/sf_mount/almalinux.img --firstboot our-script.sh
[ 0.0] Examining the guest ...
virt-sysprep: error: libguestfs error: could not create appliance through
libvirt.

Try running qemu directly without libvirt using this environment variable:
export LIBGUESTFS_BACKEND=direct

Original error from libvirt: internal error: qemu unexpectedly closed the
monitor: 2021-06-24T11:59:11.781802Z qemu-kvm: -blockdev
{"driver":"file","filename":"/media/sf_mount/almalinux.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}:
Could not open '/media/sf_mount/almalinux.img': Permission denied [code=1
int1=-1]

If reporting bugs, run virt-sysprep with debugging enabled and include the
complete output:

  virt-sysprep -v -x [...]
===================

i add LIBGUESTFS_BACKEND=direct and get
===================
# LIBGUESTFS_BACKEND=direct virt-sysprep -a /media/sf_mount/almalinux.img --firstboot our-script.sh
[ 0.0] Examining the guest ...
virt-sysprep: warning: mount_options: mount_options_stub:
/dev/mapper/cl-root: expecting a device name (ignored)
[ 21.2] Performing "abrt-data" ...
virt-sysprep: error: libguestfs error: glob_expand: glob_expand_stub: you
must call 'mount' first to mount the root filesystem

If reporting bugs, run virt-sysprep with debugging enabled and include the
complete output:

  virt-sysprep -v -x [...]
===================
(0000439)
Znuff   
2021-12-09 04:10   
Sorry this has been taking me so long to get back to this.

I'm not sure about your issue with virt-sysprep, mine just works without having done anything special.

It does seem that the mount that contains the disk image doesn't seem to be a local one and libvirt has issues accessing it?

---

That being said, the issue is still present. It seems to be something about systemd not liking... something. Again, the issue is **not** present on CentOS8.

There's a discussion on the systemd issue tracker at https://github.com/systemd/systemd/issues/6334 that might seem relevant.

Also, worth mentioning that this is not only happening on Alma Linux, but it's also happening on Rocky Linux 8.4.

Relevant snippets from the virt-sysprep log:


[ 9.5] Installing firstboot script: our-script.sh

commandrvf: ln -sf -- /usr/lib/systemd/system/guestfs-firstboot.service /sysroot/etc/systemd/system/multi-user.target.wants

In the output image the file is present in the proper systemd directory:


[root@test multi-user.target.wants]# cat /usr/lib/systemd/system/guestfs-firstboot.service
[Unit]
Description=libguestfs firstboot service
After=network.target
Before=prefdm.service

[Service]
Type=oneshot
ExecStart=/usr/lib/virt-sysprep/firstboot.sh start
RemainAfterExit=yes
StandardOutput=journal+console
StandardError=inherit

[Install]
WantedBy=multi-user.target
[root@test multi-user.target.wants]# systemctl status guestfs-firstboot.service
● guestfs-firstboot.service - libguestfs firstboot service
   Loaded: loaded (/usr/lib/systemd/system/guestfs-firstboot.service; bad; vendor preset: disabled)
   Active: inactive (dead)


And the symlink is present:

[root@test multi-user.target.wants]# stat $(pwd)/guestfs-firstboot.service
  File: /etc/systemd/system/multi-user.target.wants/guestfs-firstboot.service -> /usr/lib/systemd/system/guestfs-firstboot.service
  Size: 49 Blocks: 0 IO Block: 4096 symbolic link
Device: fd01h/64769d Inode: 140550 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Context: system_u:object_r:unlabeled_t:s0
Access: 2021-12-09 06:02:49.352448191 +0200
Modify: 2021-12-09 05:05:40.532000000 +0200
Change: 2021-12-09 05:05:40.532000000 +0200
 Birth: 2021-12-09 05:05:40.532000000 +0200

systemd reports the unit "bad" though, and I can't figure out why:

[root@test multi-user.target.wants]# systemctl status guestfs-firstboot.service
● guestfs-firstboot.service - libguestfs firstboot service
   Loaded: loaded (/usr/lib/systemd/system/guestfs-firstboot.service; bad; vendor preset: disabled)
   Active: inactive (dead)

The default target seems to be reached:

[root@test multi-user.target.wants]# systemctl status default.target
● multi-user.target - Multi-User System
   Loaded: loaded (/usr/lib/systemd/system/multi-user.target; bad; vendor preset: disabled)
   Active: active since Thu 2021-12-09 07:10:03 EET; 1h 0min left
     Docs: man:systemd.special(7)

Dec 09 07:10:03 test.web-host.ro systemd[1]: Reached target Multi-User System.


So I'm not sure at this point what else is preventing this from being run.
(0000440)
Znuff   
2021-12-10 12:12   
Hello again,

Going back to this, the issue was SELinux.

Running:

virt-sysprep -a almalinux.img --firstboot our-script.sh --selinux-relabel

Fixes the problem.

Seems that our reference CentOS image was an 8.1, and between 8.1 > 8.4 some SELinux stuff changed.

This can be closed now.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
162 [AlmaLinux-8] -OTHER minor N/A 2021-12-02 20:33 2021-12-02 20:33
Reporter: almalinuxjack Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: The AlmaLinux OS 8.x documentation does not incorporate WCAG 2.0 AA
Description: The AlmaLinux OS 8.x documentation does not incorporate WCAG 2.0 AA.

See: https://www.w3.org/WAI/WCAG2AA-Conformance
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
161 [AlmaLinux-8] -OTHER minor N/A 2021-12-02 20:24 2021-12-02 20:25
Reporter: almalinuxjack Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: The AlmaLinux OS 8.x documentation does not currently have an Accessibility User Guide
Description: The AlmaLinux OS 8.x documentation does not currently have an Accessibility User Guide
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000438)
almalinuxjack   
2021-12-02 20:25   
This is required for VPAT.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
147 [AlmaLinux-8] initial-setup major always 2021-11-13 22:38 2021-12-01 08:33
Reporter: sges Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: AlmaLinux 8.5 Boot installer Cannot install without formatting
Description: I tried to install on a preformatted ext4 empty partition mounting it as root. The installer would not proceed until I selected format and ext4. So there is no way to install on a partition with preexisting data, for example, a /home directory
Tags:
Steps To Reproduce: Try to mount root on a prexisting formatted partition using the boot installer without formatting
Additional Information:
Attached Files:
Notes
(0000436)
alukoshko   
2021-12-01 08:33   
Hello.
I suppose that is normal behavior for Anaconda installer.
Have you tried the same on CentOS or RHEL?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
135 [AlmaLinux-8] setup block always 2021-10-20 19:44 2021-11-24 18:47
Reporter: GeskoSmart Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Installation can not be finished
Description: When configuring the Installation I'm asked to add an Installation-Source and an Software selection.
When I click on installation-source and just leave the new screen with the finished button, I get the yellow warning sign on it, and I can't go to this menu again.
Also the installation can not be continued.
Some for the Software selection button.

Wenn ich die Installation starte komme ich in die Zusammenfassung der Installation.
Dort gibt es den Button Installationquelle und Software Auswahl.
Beide haben eine rote Warnung!
Wenn ich in Installationquelle gehe und dann sofort wieder raus über den FERTIG Button, dann habe ich nur noch das gelbe Warnsymbol. Aber die Installation kann
nicht fortgesetzt werden. Ich kann den Button Installationquelle auch nicht noch mal klicken.
Das gleich gilt für den Button Software-Auswahl.
Die Installation kann nicht fortgesetzt werden.
Tags: block, installation, setup
Steps To Reproduce: Download ISO
Start installation
Select Language GERMAN
Continue
Selete Installationsquelle
Klick FERTIG
See the installation can not be continued and also the Button Installationsquelle can not be klicked anymore.
Additional Information:
Attached Files:
Notes
(0000425)
alukoshko   
2021-11-24 16:59   
Hello. Sorry for delay.
Have you tried AlmaLinux 8.5? It detects the nearest mirror for network install automatically.
(0000426)
GeskoSmart   
2021-11-24 18:30   
Thanks for coming back. I already thought this forum is dead.

Anyway, after trying and trying for hours I then tried it on a different system and I found out it's indeed a network issue.
Even at 8.5 it doesn't automatically detect network at all.
I also don't understand why it is necessary to have ntwork connectivity while doing the install from an iso.
Why is there no option to configure the network? Why is there no option to skip network usage and configure later?
This is really very stupid and makes AlmaLinux for me unusable.
Meanwhile I switched back to Ubuntu although I hate it. But it still installs like a charme.
(0000427)
alukoshko   
2021-11-24 18:47   
You have to setup network only on boot (netinstall) ISO because it doens't contain any packages.
Minimal and DVD ISOs don't require network to install. You can just not enable network during install.
What ISO are you trying?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
155 [AlmaLinux-8] -OTHER block always 2021-11-19 06:54 2021-11-22 08:56
Reporter: nikk2000 Platform: x86_64  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Cannot boot after finished minimal installations with NIST 800-171 policy
Description: After finished installations, boot failed because modprobe is blocked.
Tags: boot
Steps To Reproduce: 1) Minimal installations
2) Use LVM partitions
3) Use NIST 800-171 security policy
Additional Information:
Attached Files: Screenshot_20211119_141112.png (32,186 bytes) 2021-11-19 06:54
https://bugs.almalinux.org/file_download.php?file_id=106&type=bug
Notes
(0000406)
nikk2000   
2021-11-19 10:21   
I have tried disable fapolicyd and SELinux (by mounting and editing config files), but still cannot boot.
(0000407)
nikk2000   
2021-11-20 09:20   
I guess boot got lockup because I don't have TPM module.

I have tested on machines with TPM module and found no issues.
(0000408)
nikk2000   
2021-11-20 20:32   
I've just found the problem, I need to remove `fips=1` from kernel option. Also I already have HMAC file in /boot/.

Perhaps, AMD Ryzen 2700 doesn't support FIPS? Because Intel Core i7-10750H boot just fine with `fips=1`.

Probably related to:
* https://almalinux.discourse.group/t/kernel-4-18-0-240-22-1-with-fips-1-will-not-boot/88
(0000409)
alukoshko   
2021-11-22 08:38   
Hello. Thanks for report and investigation.
No, it's not related to issues with 4.18.0-240.22.1, that was broken kernel version and since then all kernel versions are checked to not repeat that problem.

Usually we ask to check on CentOS or RHEL to find out if this AlmaLinux specific or upstream problem.
If it's upstream one then the best option would be check on CentOS Stream to find out if the problem is fixed already.
If not, then you can open a bug to CentOS Stream bugzilla: https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%208&version=CentOS%20Stream

Of course it's up to you. But it would be great if you could check it because working with CentOS Stream bugs helps the whole EL community.
(0000410)
nikk2000   
2021-11-22 08:56   
You're welcome. Thank you for reply.

Noted, I'll try and check on CentOS Stream.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
146 [AlmaLinux-8] -OTHER crash always 2021-11-12 14:37 2021-11-15 16:14
Reporter: Nick Platform: VMWare  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: VMWare - KDE crash on login
Description: I have installed KDE on a VM (VMWare) using:

yum groupinstall "KDE Plasma Workspaces"

The install goes well with the PowerTools repo enabled.

After reboot, upon logging in and selecting Plasma, kwin crashes (see attached).
Tags: KDE, kwin, Plasma, segfault, VMWare
Steps To Reproduce: 1. Install KDE using yum groupinstall "KDE Plasma Workspaces"
2. Reboot
3. Login selecting Plasma
Additional Information: See attached crash dump.
Attached Files: kwin_x11-20211112-161114.kcrash.txt (5,346 bytes) 2021-11-12 14:37
https://bugs.almalinux.org/file_download.php?file_id=102&type=bug
Notes
(0000378)
Nick   
2021-11-12 14:41   
Not entirely sure this crash should be reported to AlmaLinux or KDE but since the the live ISO has a KDE-beta I thought I might report it here as well.
(0000379)
alukoshko   
2021-11-12 22:49   
Hello and thanks for report!
It would be useful to recheck this on CentOS or RHEL to find out is it AlmaLinux specific bug or not. This will help in investigation.
(0000381)
Nick   
2021-11-12 23:11   
I will install a CentOS 8 in a similar VM and come back with the result.
(0000382)
alukoshko   
2021-11-12 23:18   
Also if AlmaLinux version is 8.5 please try epel-next because KDE in epel built with Qt 5.12 and RHEL/CentOS/AlmaLinux/whatever 8.5 has Qt 5.15.
(0000388)
Nick   
2021-11-14 07:59   
KDE has a successful install on Alma 8.5 having enabled/installed the following:
epel-release
epel-next-release
powertools

It works with both X server and Wayland.
(0000389)
srbala   
2021-11-15 16:14   
This is not AlmaLinux issue, current `epel` is broken, which needs update


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
149 [AlmaLinux-8] -OTHER minor have not tried 2021-11-15 04:47 2021-11-15 04:47
Reporter: gralex Platform:  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.5  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: needs-restarting from Yum-utils does not report a reboot
Description: Hello,

Running: AlmaLinux release 8.5 (Arctic Sphynx)
With yum-utils-4.0.21-3.el8.noarch : Yum-utils CLI compatibility layer


Updated kernel today:

2021-11-15T11:01:25+0700 DEBUG Installed: kernel-4.18.0-348.el8.x86_64
2021-11-15T11:01:25+0700 DEBUG Installed: kernel-core-4.18.0-348.el8.x86_64
2021-11-15T11:01:25+0700 DEBUG Installed: kernel-devel-4.18.0-348.el8.x86_64
2021-11-15T11:01:25+0700 DEBUG Installed: kernel-modules-4.18.0-348.el8.x86_64
2021-11-15T11:01:25+0700 DEBUG Installed: libbpf-0.4.0-1.el8.x86_64
2021-11-15T11:01:25+0700 DEBUG Installed: python3-cloud-what-1.28.21-3.el8.alma.x86_64

And the tool needs-restarting reports false negative results:

# needs-restarting -r
No core libraries or services have been updated since boot-up.
Reboot should not be necessary.
#

Kindly advice.

Regards,
Alex,
Tags: needs-restarting, yum-utils
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
144 [AlmaLinux-8] -OTHER major random 2021-11-09 06:58 2021-11-12 23:19
Reporter: johnnyxalma Platform: Linux  
Assigned To: OS: Alama Linux  
Priority: high OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Server Shutdown randomly when installing Alma Linux 8.4 on HP ProLiant DL560 Gen9
Description: We tried installing AlmaLinux 8.4 on HP ProLiant DL560 Gen9 server, but the server would shutdown randomly without any warning or error log. This behavior would occur during installation and even after successful installation.
Tags:
Steps To Reproduce:
Additional Information: We tried installing the same OS (Alma Linux 8.4) on another HP ProLiant DL560 gen 9 server and did not face any shutdown issue during or after installation. Both servers have the exact same hardware specifications.
We later installed Ubuntu 20 on the server without any such issues.
I am uploading a file containing the DMESG details of the server.
Attached Files: dmesg.txt (155,477 bytes) 2021-11-09 06:58
https://bugs.almalinux.org/file_download.php?file_id=101&type=bug
Notes
(0000383)
alukoshko   
2021-11-12 23:19   
Could you try recently released 8.5 ?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
136 [AlmaLinux-8] selinux-policy minor always 2021-10-22 11:30 2021-11-08 09:31
Reporter: joystick Platform:  
Assigned To: OS: AlmaLinux  
Priority: normal OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: container-selinux doesn't remove selinux modules
Description: Package container-selinux doesn't remove the selinux modules it installs. Why is this happening? Beacuse the package is trying to remove the module with the wrong priority.
Tags: selinux
Steps To Reproduce: Before installation container-selinux package:
root@alma:~ dnf list installed | grep container-selinux
root@alma:~ semodule -l | grep container

Aftef installation:
root@alma:~ dnf list installed | grep container-selinux
container-selinux.noarch 2:2.167.0-1.module_el8.4.0+2535+b6fd1bdf @AppStream
root@alma:~ semodule -l | grep container
container
pcpupstream-container

After remove package:
root@alma:~ dnf remove container-selinux
Dependencies resolved.
===========================================================================================================================================================================================================
 Package Architecture Version Repository Size
===========================================================================================================================================================================================================
Removing:
 container-selinux noarch 2:2.167.0-1.module_el8.4.0+2535+b6fd1bdf @AppStream 48 k
 
Transaction Summary
===========================================================================================================================================================================================================
Remove 1 Package
 
Freed space: 48 k
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing : 1/1
  Running scriptlet: container-selinux-2:2.167.0-1.module_el8.4.0+2535+b6fd1bdf.noarch 1/1
  Erasing : container-selinux-2:2.167.0-1.module_el8.4.0+2535+b6fd1bdf.noarch 1/1
  Running scriptlet: container-selinux-2:2.167.0-1.module_el8.4.0+2535+b6fd1bdf.noarch 1/1
  Verifying : container-selinux-2:2.167.0-1.module_el8.4.0+2535+b6fd1bdf.noarch 1/1
 
Removed:
  container-selinux-2:2.167.0-1.module_el8.4.0+2535+b6fd1bdf.noarch
 
Complete!
 
root@alma:~ dnf list installed | grep container-selinux
root@alma:~ semodule -l | grep container
container
pcpupstream-container

Package is trying to remove the module with the wrong priority:
root@alma:/var/lib/selinux/targeted/active/modules/200 ls | grep container
drwx------. 2 root root 44 Oct 21 11:28 container

root@alma:~ semodule -r container
libsemanage.semanage_direct_remove_key: Unable to remove module container at priority 400. (No such file or directory).
semodule: Failed!

root@alma:~ semodule -X 200 -r container
libsemanage.semanage_direct_remove_key: Removing last container module (no other container module exists at another priority).
Additional Information:
Attached Files:
Notes
(0000375)
alukoshko   
2021-11-08 09:04   
Hi. Could you try to reproduce this on CentOS 8 and CentOS Stream 8?
If it's upstream bug then we have to submit it to Red Hat.
(0000376)
joystick   
2021-11-08 09:31   
Hi, I managed to reproduce this problem on CentOS 8 (Linux), I haven't tested it on stream.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
143 [AlmaLinux-8] almalinux-release major have not tried 2021-11-06 00:15 2021-11-08 08:46
Reporter: Vee Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Failure to install Gnome Desktop on Raspberry Pi 4
Description: I am installing Almalinux on my Pi. I am getting this error
Error: Failed to download metadata for repo 'raspberrypi':
Cannot download repomd.xml : Cannot download repodata/repomd.xml: All mirrors were tried

Another error is
- Curl error (6): Couldn't resolve host name for https://repo.almalinux.org/almalinux/8/raspberrypi/aarch64/os/repodata/repomd.xml
[Could not resolve host: repo.almalinux.org]
Tags: aarch64, Raspberrypi, raspberrypi 4
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000373)
alukoshko   
2021-11-08 08:46   
Hi. Looks like network/DNS issue.
Please check network setup, try to ping some internet sites.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
134 [AlmaLinux-8] -OTHER major always 2021-10-20 18:17 2021-11-03 02:30
Reporter: Adrien_D Platform: VMWare Workstation  
Assigned To: alukoshko OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: ELevate : UEFI not updated
Description: I installed CentOS 7 to test the ELevate update to Alma Linux 8 : https://wiki.almalinux.org/elevate/ELevate-quickstart-guide.html
precheck : some warnings, i applied solutions : OK
Reboot : upgrading : OK
Reboot after upgrading : nothing.
The UEFI not updated (because the efi file is before in the centos folder, and after update it's in almalinux folder.
Tags:
Steps To Reproduce: 1- Install CentOS 7 on vmware workstation with UEFI
2- Update CentOS 7
3- Elevate the system as https://wiki.almalinux.org/elevate/ELevate-quickstart-guide.html
4- See the system doesn't reboot after upgrading
Additional Information:
Attached Files:
Notes
(0000362)
alukoshko   
2021-10-22 13:48   
Thanks for report.
Looks like Leapp doesn't support changing efi dirs because is developed just for Red Hat.
We have to develop a new actor for this.
BTW could you also check CentOS 7 -> CentOS Stream 8 update in your environment?
(0000365)
Adrien_D   
2021-10-24 16:38   
Yes i know leapp.
Before making a video on my youtube channel i made a snapshot of the VM in CentOS 7.
So i make the test on the SAME VM. (i didn't destroyed it)

After upgrading from CentOS 7 to CentOS 8 Stream : All is okay because efi is in centos folder in the EFI partition


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
89 [AlmaLinux-8] -OTHER feature always 2021-05-31 16:25 2021-11-01 18:35
Reporter: ppyy Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: please add plus repo
Description: we use CentOSPlus kernel from CentOS. and fail to migrate to AlmaLinux.
 
https://wiki.centos.org/AdditionalResources/Repositories/CentOSPlus
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000274)
toracat   
2021-06-12 19:05   
As the maintainer of the centosplus kernel, I am curious to know which feature(s) you are interested in that are not in the distro kernel.
(0000276)
ppyy   
2021-06-14 14:48   
CONFIG_MLX4_CORE_GEN2

please refer to:
https://elrepo.org/bugs/view.php?id=1037
(0000277)
toracat   
2021-06-14 15:42   
ELRepo has a kmod package for that:

https://elrepo.org/linux/elrepo/el8/x86_64/RPMS/kmod-mlx4-4.0-5.el8_4.elrepo.x86_64.rpm

I believe the above kmod was built with MLX4_CORE_GEN2 enabled.
(0000371)
toracat   
2021-11-01 18:35   
@ppyy

Did you have a chance to give the kmod package a try? If so, how did it go?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
140 [AlmaLinux-8] -OTHER minor always 2021-10-31 06:27 2021-11-01 12:29
Reporter: kfujinaga Platform: Virtuozzo Hybrid Server  
Assigned To: alukoshko OS: CentOS  
Priority: normal OS Version: 8.4  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: almalinux-deploy: almalinux-deploy install unnecessary kernel packages in the Virtuozzo/OpenVZ container enviroments.
Description: In the Virtuozzo/OpenVZ container enviroments, each container use host's kernel.
So kernel packages are not installed in the container.

But almalinux-deploy install kernel packages at the migration.
These packages are unnecessary and are not used.
# NOTE: The migration was successful, and AlmaLinux container works fine.

On the other hand, the migration tools of Rocky Linux and CentOS Stream doesn't install kernel packages in the Virtuozzo/OpenVZ container enviroments.

Unnecessary kernel packages cause a misunderstanding for users.
So I want you to fix this problem.
Tags:
Steps To Reproduce: Run almalinux-deploy in the Virtuozzo/OpenVZ container enviroments.

1. Check enviroment before migration

------------
[root@fujinaga-test ~]# uname -a
Linux fujinaga-test 4.18.0 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@fujinaga-test ~]# cat /etc/redhat-release
CentOS Linux release 8.4.2105
[root@fujinaga-test ~]# ls /boot/
efi grub2
[root@fujinaga-test ~]# ls /lib/modules
[root@fujinaga-test ~]# rpm -qa |grep kernel
[root@fujinaga-test ~]#
------------

No kernel package is installed.

2. Run almalinux-deploy

------------
[root@fujinaga-test ~]# bash almalinux-deploy.sh

   ...

Complete!
Run dnf distro-sync -y OK
Restoring of alternatives is done OK
Install AlmaLinux kernel OK
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.18.0-305.19.1.el8_4.x86_64
Found initrd image: /boot/initramfs-4.18.0-305.19.1.el8_4.x86_64.img
done
grep: /boot/grub2/grubenv: No such file or directory
All Secure Boot related packages which were released by not AlmaLinux are reinstalledOK

Migration to AlmaLinux is completed
------------

Migration is completed.
But following message is outputed.
  "grep: /boot/grub2/grubenv: No such file or directory"

3. Check enviroment after migration

------------
[root@fujinaga-test ~]# uname -a
Linux fujinaga-test 4.18.0 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@fujinaga-test ~]# cat /etc/redhat-release
AlmaLinux release 8.4 (Electric Cheetah)
[root@fujinaga-test ~]# ls /boot/
System.map-4.18.0-305.19.1.el8_4.x86_64
config-4.18.0-305.19.1.el8_4.x86_64
efi
grub2
initramfs-4.18.0-305.19.1.el8_4.x86_64.img
loader
vmlinuz-4.18.0-305.19.1.el8_4.x86_64
[root@fujinaga-test ~]# ls /lib/modules
4.18.0-305.19.1.el8_4.x86_64
[root@fujinaga-test ~]# rpm -qa |grep kernel
kernel-core-4.18.0-305.19.1.el8_4.x86_64
kernel-4.18.0-305.19.1.el8_4.x86_64
kernel-modules-4.18.0-305.19.1.el8_4.x86_64
[root@fujinaga-test ~]#
------------

Kernel packages are installed.

These kernel packages are unnecessary.
If the container is restarted, the container use host's kernel.
Additional Information:
Attached Files:
Notes
(0000369)
alukoshko   
2021-11-01 12:29   
Hi. Thanks for report.
Right now almalinux-deploy detects only LXC containers, we're working on detection of others too.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
139 [AlmaLinux-8] rpcbind major always 2021-10-30 11:25 2021-10-30 11:25
Reporter: commandline-be Platform: x86  
Assigned To: OS: Alma Linux  
Priority: high OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: rpcbind fatal flaw on boot/start of service
Description: During boot

[ 8.777218] traps: rpcbind[767] general protection fault ip:7f94de660bb8 sp:7ffe8e484960 error:0 in libc-2.28.so[7f94de57a000+1bc000]
[FAILED] Failed to start RPC Bind.
See 'systemctl status rpcbind.service' for details.
Tags:
Steps To Reproduce: boot the system
run rpcbind
start the rpcbind service
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
132 [AlmaLinux-8] -OTHER minor always 2021-10-13 09:55 2021-10-25 09:11
Reporter: atapy Platform:  
Assigned To: alukoshko OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: [Cloud/AWS]AMI wrongly assumes RTC as LOCALTIME
Description: Official AMI assumes syetem real-time-clock as LOCALTIME,
but it is incorrect because EC2 supplies their RTC clock as UTC.

Refer: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html
> Update the /etc/sysconfig/clock file with the new time zone.
(snip)
> Do not change the UTC=true entry to another value.
> This entry is for the hardware clock,
> and does not need to be adjusted
> when you're setting a different time zone on your instance.

It may cause inaccurate time settings, espacially time zone is set OTHER THAN UTC.
Please consider changing default RTC setting, to UTC.
Tags: aws, Bug, cloud
Steps To Reproduce: [ec2-user@ip-172-31-44-137 ~]$ timedatectl status
               Local time: Wed 2021-10-13 09:46:11 UTC
           Universal time: Wed 2021-10-13 09:46:11 UTC
                 RTC time: Wed 2021-10-13 09:46:11
                Time zone: UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: yes <------ INCORRECT FOR AWS

Warning: The system is configured to read the RTC time in the local time zone.
         This mode cannot be fully supported. It will create various problems
         with time zone changes and daylight saving time adjustments. The RTC
         time is never updated, it relies on external facilities to maintain it.
         If at all possible, use RTC in UTC by calling
         'timedatectl set-local-rtc 0'.
Additional Information: Tested at ap-northeast-1.
AlmaLinux OS 8.4 x86_64-stage2-c076b20a-2305-4771-823f-944909847a05

RHEL 8, CentOS 8 and Rocky Linux 8 do not have this bug.
This bug exists only on AlmaLinux 8.
Attached Files:
Notes
(0000353)
lkhn   
2021-10-17 15:05   
Hey atapy,

Thanks for making AlmaLinux better. You can get the updated AMIs from the Community AMI wiki page or AWS Marketplace. You'll get the product subscription e-mail when the second one is published on the AWS Marketplace by Amazon.

[1] Community AMI wiki page: https://wiki.almalinux.org/cloud/AWS.html


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
137 [AlmaLinux-8] gdm crash sometimes 2021-10-23 21:27 2021-10-23 21:48
Reporter: spatial25 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: GDM sometimes crashes on image and pdf use
Description: When I am using Libreoffice writer and recently Evince the system crashes and I am taken back to the command line login interface. I don't have graphical.target set to load automatically. I log in with my credentials and type "sudo systemctl start graphical.target" nothing happens after the crash and it requires a reboot to load start again. I think it is the gdm but I am not sure and can't sort through my log.messages accurately enough to identify why it crashed.
Its happened when moving images around in libreoffice and when clicking on a pdf to select text on evince. If anyone can guide me to what log info I need to put please let me know. I am looking through it now.
Tags:
Steps To Reproduce: attach images to libreoffice writer document and resize and position pictures in it. Have doc open for 1/2 an hour and move pictures around and crash.
view document on evince and have it up while also searching info on browser. Go back to highlight text and crash.
Additional Information:
Attached Files:
Notes
(0000364)
spatial25   
2021-10-23 21:48   
Every time it crashed I noticed the user@42.service and a starting Mark boot. Looking through these logs I found

Oct 23 16:17:25 spaced pia-client.desktop[6509]: [2021-10-23 21:17:25.294][f273][qml][qrc:/components/core/LoaderCleaner.qml:31][info] Clean up again in 6000 ms
Oct 23 16:17:26 spaced dnscrypt-proxy[2089]: System DNS configuration not usable yet, exceptionally resolving [dns2.dnscrypt.ca] using fallback resolvers over tcp
Oct 23 16:17:26 spaced dbus-daemon[5280]: [session uid=1000 pid=5280] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.74' (uid=1000 pid=7611 comm="gnome-terminal " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Oct 23 16:17:26 spaced systemd[5236]: Starting GNOME Terminal Server...
Oct 23 16:17:26 spaced gnome-terminal-server[7616]: Display does not support owner-change; copy/paste will be broken!
Oct 23 16:17:26 spaced dbus-daemon[5280]: [session uid=1000 pid=5280] Successfully activated service 'org.gnome.Terminal'
Oct 23 16:17:26 spaced systemd[5236]: Started GNOME Terminal Server.
Oct 23 16:17:26 spaced org.gnome.Terminal.desktop[7611]: # watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0)

Thanks or the help, let me know if I can send more.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
128 [AlmaLinux-8] fwupdate minor always 2021-09-23 12:13 2021-10-19 13:03
Reporter: olahaye74 Platform:  
Assigned To: alukoshko OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: fwupdate-efi installs in /boot/efi/EFI/redhat instead of /boot/efi/EFI/almalinux
Description: fwupdate-efi installs in /boot/efi/EFI/redhat instead of /boot/efi/EFI/almalinux
Tags:
Steps To Reproduce: dnf -y install fwupdate-efi ; rpm -ql fwupdate-efi|grep redhat
Additional Information:
Attached Files:
Notes
(0000356)
alukoshko   
2021-10-19 13:03   
Updated fwupdate-efi was released with correct path.
Sorry for delay.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
127 [AlmaLinux-8] -OTHER block always 2021-09-20 14:38 2021-10-19 12:09
Reporter: karelklic Platform:  
Assigned To: alukoshko OS: AlmaLinux 8  
Priority: high OS Version: 8.4  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: AlmaLinux fails to install via virt-install
Description: I can set up a CentOS virtual machine using virt-install from the command line, but the same procedure fails with AlmaLinux.
Tags:
Steps To Reproduce: 1. Use a typical workstation with fully updated AlmaLinux 8, virt-manager, libvirt, virt-install, and firewalld.

2. Try to install CentOS 8 VM:
sudo virt-install \
    --memory 3072 \
    --vcpus 2 \
    --graphics none \
    --network bridge=virbr0 \
    --os-type=linux \
    --os-variant=centos8 \
    --location http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os/ \
    --noreboot \
    --hvm \
    --wait -1 \
    --extra-args "console=ttyS0,115200"

3. See that the textual Anaconda installer starts after a few minutes time, allowing to proceed with the installation.

4. Now let's try to install AlmaLinux 8 VM with equivalent arguments:
sudo virt-install \
    --memory 3072 \
    --vcpus 2 \
    --graphics none \
    --network bridge=virbr0 \
    --os-type=linux \
    --os-variant=almalinux8 \
    --location https://repo.almalinux.org/almalinux/8/BaseOS/x86_64/os/ \
    --noreboot \
    --hvm \
    --wait -1 \
    --extra-args "console=ttyS0,115200"

5. See that the VM startup is stuck and the Anaconda installer never starts:
[ OK ] Reached target Basic System.
[ 12.114346] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 12.117493] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 12.118667] 8021q: adding VLAN 0 to HW filter on device enp1s0
[ 12.122468] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 12.125027] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 12.319085] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
[ 160.556064] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 161.187649] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 161.781877] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 162.376911] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 162.974903] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 163.568660] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 164.179282] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 164.777730] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 165.378744] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 165.996595] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 166.612907] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 167.230635] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 167.846792] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 168.446548] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 169.059694] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 169.668433] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 170.264853] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 170.887612] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 171.482921] dracut-initqueue[981]: Warning: dracut-initqueue timeout - starting timeout scripts
Additional Information: The kickstart repo (https://repo.almalinux.org/almalinux/8/BaseOS/x86_64/kickstart/) fails as well.

The older 8.3 repo (https://repo.almalinux.org/almalinux/8.3/BaseOS/x86_64/os/) fails as well.

I tried to change the --os-variant argument and it has no effect (CentOS 8 installer starts fine with --os-variant almalinux8).
Attached Files:
Notes
(0000346)
sej7278   
2021-10-14 22:47   
Looking at the process list, the only difference i can find between a working centos8 and non-working alma8 is the centos commandline includes:

inst.repo=http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os/

looks like the following is missing from the osinfo-db entry:

    <kernel-url-argument>inst.repo</kernel-url-argument>

or something like that - the above is found in rhel/fedora, i think centos bakes it into the initrd or something, lots of chat here: https://github.com/coreos/fedora-coreos-tracker/issues/221
(0000348)
sej7278   
2021-10-15 09:01   
if you turn on virt-install --debug you can see centos has inst.repo injected (by osinfo-db?):

    <cmdline>console=ttyS0,115200 inst.repo=http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os/</cmdline>

but almalinux only has what you've set:

    <cmdline>console=ttyS0,115200</cmdline>

as a workaround, inject the inst.repo yourself:

    --extra-args "console=ttyS0,115200 inst.repo=http://repo.almalinux.org/almalinux/8/BaseOS/x86_64/os/"

but this needs fixing by the osinfo-db folks, although not really sure where as the centos and almalinux xml seems to use a totally different setup:

https://gitlab.com/libosinfo/osinfo-db/-/blob/master/data/os/almalinux.org/almalinux-8.xml.in

https://gitlab.com/libosinfo/osinfo-db/-/blob/master/data/os/centos.org/centos-8.xml.in

possibly something needs changing here:

https://gitlab.com/libosinfo/osinfo-db/-/blob/master/data/install-script/redhat.com/rhel-kickstart-jeos.xml.in
(0000350)
alukoshko   
2021-10-15 12:15   
Thank you for report and for updates.
Could you please test the same with updated osinfo-sb from 8.5 beta?
https://repo.almalinux.org/almalinux/8.5-beta/AppStream/x86_64/os/Packages/osinfo-db-20210809-1.el8.noarch.rpm
(0000351)
karelklic   
2021-10-15 13:39   
sej7278, thank you for figuring out the workaround, adding inst.repo to extra-args works great!

alukoshko, the osinfo-db-20210809-1 package doesn't solve the issue for me. The workaround is still required.
(0000352)
sej7278   
2021-10-15 15:26   
yeah, its not fixed in git and i'm running a debian host anyway, so the 8.5 beta rpm isn't going to include the fix as its not been written yet.

not really sure what needs to be fixed in the osinfo-db code though otherwise i'd report it to them.
(0000355)
alukoshko   
2021-10-19 12:09   
The problem is on virt-install side.
PR to upstream: https://github.com/virt-manager/virt-manager/pull/314
Also released virt-install-2.2.1-4.el8.alma to fix this issue.
Thanks everyone.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
133 [AlmaLinux-8] -OTHER minor always 2021-10-16 15:33 2021-10-16 15:33
Reporter: andreas_reschke Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Raspberry Pi boot from SD-Card vs USB
Description: Hi there,
I’ve installed my Raspberry PI 4 with installation tips from GitHub - AlmaLinux/raspberry-pi: AlmaLinux Raspberry Pi 2.

    boot from SD-Card
    boot from USB

With boot from SD-Card WiFi works fine with nmcli --ask dev wifi connect network-ssid, but not with boot from USB. Failure: Error: Connection activation failed: (7) Secrets were required, but not provided.

All with same hardware but different boot method SDCard <> USB
Tags: AlmaLinux
Steps To Reproduce:
Update: I’ve made the same experience with CentOS, Rocky Linux and Fedora.

    boot from SD-Card: Wifi is working
    boot from USB: Wifi is not working
    All tests on Raspberry Pi 4 with 8 GB and same OS on SD-Card and USB.

[root@raspi4 ~]# nmcli device wifi connect FRITZTuxNetzwerk password password
Error: Connection activation failed: (7) Secrets were required, but not provided.
[root@raspi4 ~]#

Andreas
Additional Information: Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.1260] audit: op="connection-update" uuid="0bd11f75-aa9d-4d1f-bdd7-3ae662f24e48" name="FRITZTuxNetzwerk" args="802-11-wireless-security.psk" pid=27875 uid=0 result="success"
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.1359] device (wlan0): state change: need-auth -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.1382] device (wlan0): disconnecting for new activation request.
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.1384] audit: op="connection-activate" uuid="0bd11f75-aa9d-4d1f-bdd7-3ae662f24e48" name="FRITZTuxNetzwerk" pid=27875 uid=0 result="success"
Okt 16 17:30:38 raspi4.reschke.lan dbus-daemon[326]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=413 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Okt 16 17:30:38 raspi4.reschke.lan systemd[1]: Starting Network Manager Script Dispatcher Service...
Okt 16 17:30:38 raspi4.reschke.lan dbus-daemon[326]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <warn> [1634398238.1854] device (wlan0): Deactivation failed: GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.1858] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Okt 16 17:30:38 raspi4.reschke.lan gnome-shell[900]: An active wireless connection, in infrastructure mode, involves no access point?
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2036] device (wlan0): Activation: starting connection 'FRITZTuxNetzwerk' (0bd11f75-aa9d-4d1f-bdd7-3ae662f24e48)
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2061] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2074] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2084] device (wlan0): Activation: (wifi) access point 'FRITZTuxNetzwerk' has security, but secrets are required.
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2085] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2184] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2196] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2578] device (wlan0): Activation: (wifi) connection 'FRITZTuxNetzwerk' has security, and secrets exist. No new secrets needed.
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2579] Config: added 'ssid' value 'FRITZTuxNetzwerk'
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2580] Config: added 'scan_ssid' value '1'
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2580] Config: added 'bgscan' value 'simple:30:-70:86400'
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2581] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2581] Config: added 'auth_alg' value 'OPEN'
Okt 16 17:30:38 raspi4.reschke.lan NetworkManager[413]: <info> [1634398238.2581] Config: added 'psk' value '<hidden>'
Okt 16 17:30:38 raspi4.reschke.lan systemd[1]: Started Network Manager Script Dispatcher Service.
Okt 16 17:30:38 raspi4.reschke.lan chronyd[1796]: Source 2a01:4f8:212:2058::99 offline
Okt 16 17:30:39 raspi4.reschke.lan NetworkManager[413]: <info> [1634398239.3133] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:30:39 raspi4.reschke.lan NetworkManager[413]: <info> [1634398239.3134] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:30:40 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Trying to associate with SSID 'FRITZTuxNetzwerk'
Okt 16 17:30:40 raspi4.reschke.lan NetworkManager[413]: <info> [1634398240.2579] device (wlan0): supplicant interface state: scanning -> associating
Okt 16 17:30:40 raspi4.reschke.lan NetworkManager[413]: <info> [1634398240.2580] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Okt 16 17:30:41 raspi4.reschke.lan wpa_supplicant[461]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=04:f0:21:0a:62:c7 status_code=16
Okt 16 17:30:41 raspi4.reschke.lan wpa_supplicant[461]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="FRITZTuxNetzwerk" auth_failures=1 duration=10 reason=CONN_FAILED
Okt 16 17:30:41 raspi4.reschke.lan NetworkManager[413]: <info> [1634398241.5285] device (wlan0): supplicant interface state: associating -> disconnected
Okt 16 17:30:41 raspi4.reschke.lan NetworkManager[413]: <info> [1634398241.5286] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnected
Okt 16 17:30:48 raspi4.reschke.lan systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Okt 16 17:30:51 raspi4.reschke.lan NetworkManager[413]: <info> [1634398251.5498] device (wlan0): supplicant interface state: disconnected -> scanning
Okt 16 17:30:51 raspi4.reschke.lan NetworkManager[413]: <info> [1634398251.5499] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Okt 16 17:30:52 raspi4.reschke.lan wpa_supplicant[461]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="FRITZTuxNetzwerk"
Okt 16 17:30:52 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Trying to associate with SSID 'FRITZTuxNetzwerk'
Okt 16 17:30:52 raspi4.reschke.lan NetworkManager[413]: <info> [1634398252.5154] device (wlan0): supplicant interface state: scanning -> associating
Okt 16 17:30:52 raspi4.reschke.lan NetworkManager[413]: <info> [1634398252.5155] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Okt 16 17:30:53 raspi4.reschke.lan wpa_supplicant[461]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=04:f0:21:0a:62:c7 status_code=16
Okt 16 17:30:53 raspi4.reschke.lan wpa_supplicant[461]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="FRITZTuxNetzwerk" auth_failures=2 duration=20 reason=CONN_FAILED
Okt 16 17:30:53 raspi4.reschke.lan NetworkManager[413]: <info> [1634398253.4553] device (wlan0): supplicant interface state: associating -> disconnected
Okt 16 17:30:53 raspi4.reschke.lan NetworkManager[413]: <info> [1634398253.4554] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnected
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <warn> [1634398263.4589] device (wlan0): Activation: (wifi) association took too long
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <info> [1634398263.4590] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <warn> [1634398263.4620] device (wlan0): Activation: (wifi) asking for new secrets
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <warn> [1634398263.4628] device (wlan0): no secrets: No agents were available for this request.
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <info> [1634398263.4629] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <warn> [1634398263.4799] device (wlan0): Activation: failed for connection 'FRITZTuxNetzwerk'
Okt 16 17:31:03 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Reject scan trigger since one is already pending
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <info> [1634398263.4915] device (wlan0): supplicant interface state: disconnected -> scanning
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <info> [1634398263.4916] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Okt 16 17:31:03 raspi4.reschke.lan NetworkManager[413]: <info> [1634398263.4941] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Okt 16 17:31:04 raspi4.reschke.lan NetworkManager[413]: <info> [1634398264.4237] device (wlan0): supplicant interface state: scanning -> disconnected
Okt 16 17:31:04 raspi4.reschke.lan NetworkManager[413]: <info> [1634398264.4239] device (p2p-dev-wlan0): supplicant management interface state: scanning -> disconnected
Okt 16 17:31:06 raspi4.reschke.lan NetworkManager[413]: <info> [1634398266.4845] device (wlan0): supplicant interface state: disconnected -> scanning
Okt 16 17:31:06 raspi4.reschke.lan NetworkManager[413]: <info> [1634398266.4846] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Okt 16 17:31:07 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:07 raspi4.reschke.lan NetworkManager[413]: <info> [1634398267.4257] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:07 raspi4.reschke.lan NetworkManager[413]: <info> [1634398267.4259] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:31:09 raspi4.reschke.lan NetworkManager[413]: <info> [1634398269.4843] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:31:09 raspi4.reschke.lan NetworkManager[413]: <info> [1634398269.4844] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:31:10 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:10 raspi4.reschke.lan NetworkManager[413]: <info> [1634398270.4279] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:10 raspi4.reschke.lan NetworkManager[413]: <info> [1634398270.4280] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:31:15 raspi4.reschke.lan NetworkManager[413]: <info> [1634398275.4846] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:31:15 raspi4.reschke.lan NetworkManager[413]: <info> [1634398275.4847] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:31:16 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:16 raspi4.reschke.lan NetworkManager[413]: <info> [1634398276.4248] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:16 raspi4.reschke.lan NetworkManager[413]: <info> [1634398276.4250] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:31:16 raspi4.reschke.lan NetworkManager[413]: <info> [1634398276.4650] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:31:16 raspi4.reschke.lan NetworkManager[413]: <info> [1634398276.4652] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:31:17 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:17 raspi4.reschke.lan NetworkManager[413]: <info> [1634398277.4048] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:17 raspi4.reschke.lan NetworkManager[413]: <info> [1634398277.4050] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:31:20 raspi4.reschke.lan NetworkManager[413]: <info> [1634398280.4846] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:31:20 raspi4.reschke.lan NetworkManager[413]: <info> [1634398280.4847] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:31:21 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:21 raspi4.reschke.lan NetworkManager[413]: <info> [1634398281.4246] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:21 raspi4.reschke.lan NetworkManager[413]: <info> [1634398281.4247] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:31:25 raspi4.reschke.lan NetworkManager[413]: <info> [1634398285.4865] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:31:25 raspi4.reschke.lan NetworkManager[413]: <info> [1634398285.4866] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:31:26 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:26 raspi4.reschke.lan NetworkManager[413]: <info> [1634398286.4249] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:26 raspi4.reschke.lan NetworkManager[413]: <info> [1634398286.4250] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:31:32 raspi4.reschke.lan NetworkManager[413]: <info> [1634398292.4867] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:31:32 raspi4.reschke.lan NetworkManager[413]: <info> [1634398292.4868] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:31:33 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:33 raspi4.reschke.lan NetworkManager[413]: <info> [1634398293.4268] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:33 raspi4.reschke.lan NetworkManager[413]: <info> [1634398293.4269] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:31:42 raspi4.reschke.lan NetworkManager[413]: <info> [1634398302.4840] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:31:42 raspi4.reschke.lan NetworkManager[413]: <info> [1634398302.4841] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:31:43 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:43 raspi4.reschke.lan NetworkManager[413]: <info> [1634398303.4236] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:43 raspi4.reschke.lan NetworkManager[413]: <info> [1634398303.4237] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:31:56 raspi4.reschke.lan NetworkManager[413]: <info> [1634398316.4871] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:31:56 raspi4.reschke.lan NetworkManager[413]: <info> [1634398316.4872] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:31:57 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:31:57 raspi4.reschke.lan NetworkManager[413]: <info> [1634398317.4271] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:31:57 raspi4.reschke.lan NetworkManager[413]: <info> [1634398317.4272] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Okt 16 17:32:16 raspi4.reschke.lan NetworkManager[413]: <info> [1634398336.4971] device (wlan0): supplicant interface state: inactive -> scanning
Okt 16 17:32:16 raspi4.reschke.lan NetworkManager[413]: <info> [1634398336.4972] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Okt 16 17:32:17 raspi4.reschke.lan wpa_supplicant[461]: wlan0: Failed to initiate sched scan
Okt 16 17:32:17 raspi4.reschke.lan NetworkManager[413]: <info> [1634398337.4368] device (wlan0): supplicant interface state: scanning -> inactive
Okt 16 17:32:17 raspi4.reschke.lan NetworkManager[413]: <info> [1634398337.4369] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
121 [AlmaLinux-8] -OTHER minor always 2021-08-27 22:02 2021-10-14 14:41
Reporter: Berkey Platform: x86_64  
Assigned To: OS: alma  
Priority: normal OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Anaconda doesnt support Rufus default/recommended iso creation method
Description: It seems anaconda installer does not fully support offline usb iso based installation. Although installer boots up normally, the 9gb usb iso key isn't available for use as the install source. Installer keeps trying to force user to setup online repo.
Tags:
Steps To Reproduce: Tried multiple times, and experienced the same outcome. Once I had created the usb installer using Rufus with DD mode instead of ISO based anaconda properly detected the files from my usb key instead prompting to setup an online repo.
Additional Information: Apologies if I have formatted this report incorrectly or in the wrong place, I have never reported a bug before, but I thought this information might be helpful to others. I understand technically I was doing it wrong, but I hope there is a good reason to only support DD mode.
Attached Files:
Notes
(0000344)
alukoshko   
2021-10-14 14:41   
AFAIK it's upstream issue and latest RHEL/CentOS versions require DD too


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
105 [AlmaLinux-8] -OTHER feature N/A 2021-06-23 05:15 2021-10-14 14:40
Reporter: ziex Platform:  
Assigned To: alukoshko OS:  
Priority: normal OS Version:  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Parsable errata format
Description: Huge fan that errata is available via errata.almalinux.org.

However, we use a platform for patching servers automatically and thus we parse errata. For CentOS we have been using unofficial errata cefs[.]steve-meier[.]de. For AlmaLinux we would like errata to be published in a structured format (such as JSON or XML), so we won't have to parse HTML that will likely change some day.
Tags:
Steps To Reproduce: -
Additional Information: -
Attached Files:
Notes
(0000291)
alukoshko   
2021-06-29 15:16   
Hello.
Errata is also available in traditional updateinfo.xml format for dnf, for example:
https://repo.almalinux.org/almalinux/8/BaseOS/x86_64/os/repodata/321c965c99e4179149d63e824b6e2f168e2b6761358681cb54ea41adda030f4e-updateinfo.xml.gz
Is it an option for you?
(0000343)
alukoshko   
2021-10-14 14:40   
We now also have it in JSON: https://errata.almalinux.org/8/errata.json


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
131 [AlmaLinux-8] thunderbird minor have not tried 2021-10-05 13:33 2021-10-09 01:37
Reporter: arrfab Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: [RFE] Enable openGPG support in thunderbird
Description: Long story short : opengpg support is there by default in upstream thunderbird, but disabled by Red Hat for RHEL (see https://bugzilla.redhat.com/show_bug.cgi?id=1886958)

We (CentOS Side) decided to rebuild it with a specific patch that in fact revert the rhel patch, and so provide a thunderbird package that can be use for openpgp.
The simple patch can be seen in the centosplus branch : https://git.centos.org/rpms/thunderbird/c/fac902a8f3bb58e71da8144a54061da4dcbf1735?branch=c8-plus

This is a RFE to consider either rebuilding thunderbird with that feature, or just do like for centos : rebuild in/for another repository

Reason is simple : we saw people (including RHEL users) using that pkg as they needed gpg support in thunderbird, and as CentOS 8 will disappear end of this year (and so centosplus repository) people switching to another compatible rebuild will start searching for same level of compatibility
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
130 [AlmaLinux-8] selinux-policy block always 2021-10-04 22:25 2021-10-04 22:52
Reporter: jtremblay Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: when using CHEF to manage SELINUX the cookbook fails
Description:
 - selinux (2.1.1)
  - selinux_policy (2.4.3)

Recipe: selinux::_common
  * selinux_install[selinux os prep] action install
    
    ================================================================================
    Error executing action `install` on resource 'selinux_install[selinux os prep]'
    ================================================================================
    
    RuntimeError
    ------------
     not supported!
    
    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/selinux/resources/install.rb:29:in `block in class_from_file'
    
    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/selinux/recipes/_common.rb
    
      2: selinux_install 'selinux os prep'
    
    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/selinux/recipes/_common.rb:2:in `from_file'
    
    selinux_install("selinux os prep") do
      action [:install]
      default_guard_interpreter :default
      declared_type :selinux_install
      cookbook_name "selinux"
      recipe_name "_common"
    end
    
    System Info:
    ------------
    chef_version=13.12.14
    platform=almalinux
    platform_version=8.4
    ruby=ruby 2.4.5p335 (2018-10-18 revision 65137) [x86_64-linux]
    program_name=chef-client worker: ppid=9037;start=17:59:19;
    executable=/opt/chef/bin/chef-client
Tags:
Steps To Reproduce: install almalinux 8.4 with chef-client 13.12.14 and assign the cookbook recipe "selinux::disabled"
Additional Information: this works on an identical RHEL 8.4 box both installed and bootstrapped into CHEF with the same runlist.
Attached Files: chef-stacktrace.out (8,006 bytes) 2021-10-04 22:25
https://bugs.almalinux.org/file_download.php?file_id=98&type=bug
Notes
(0000339)
jtremblay   
2021-10-04 22:35   
it seems that when CHEF is trying to identify Alma it fails
when 'rhel', 'fedora', 'amazon'
 26 package %w(policycoreutils selinux-policy selinux-policy-targeted libselinux-utils mcstrans)
 27 else
 28 # implement support for your platform here!
 29 raise "#{node['platform_family']} not supported!"
 30 end
 31
(0000340)
jtremblay   
2021-10-04 22:39   
1 #
  2 # Cookbook:: selinux
  3 # Resource:: install
  4 #
  5 # Copyright:: 2016-2017, Chef Software, Inc.
  6 #
  7 # Licensed under the Apache License, Version 2.0 (the "License");
  8 # you may not use this file except in compliance with the License.
  9 # You may obtain a copy of the License at
 10 #
 11 # http://www.apache.org/licenses/LICENSE-2.0
 12 #
 13 # Unless required by applicable law or agreed to in writing, software
 14 # distributed under the License is distributed on an "AS IS" BASIS,
 15 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 16 # See the License for the specific language governing permissions and
 17 # limitations under the License.
 18
 19 action :install do
 20 case node['platform_family']
 21 when 'debian'
 22 package 'selinux-basics'
 23 when 'ubuntu'
 24 package %w(selinux-basics selinux-policy-default auditd)
 25 when 'rhel', 'fedora', 'amazon','centos'
 26 package %w(policycoreutils selinux-policy selinux-policy-targeted libselinux-utils mcstrans)
 27 else
 28 # implement support for your platform here!
 29 raise "#{node['platform_family']} not supported!"
 30 end
 31
 32 directory '/etc/selinux' do
 33 owner 'root'
 34 group 'root'
 35 mode '0755'
 36 action :create
 37 end
 38 end
~
(0000341)
jtremblay   
2021-10-04 22:52   
I added and removed 'centos' for testing
I also changed the os-release to
NAME="AlmaLinux"
VERSION="8.4 (Electric Cheetah)"
ID="almalinux"
ID_LIKE="fedora"
VERSION_ID="8.4"
PLATFORM_ID="platform:el8"
PRETTY_NAME="AlmaLinux 8.4 (Electric Cheetah)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:almalinux:almalinux:8.4:GA"
HOME_URL="https://almalinux.org/"
DOCUMENTATION_URL="https://wiki.almalinux.org/"
BUG_REPORT_URL="https://bugs.almalinux.org/"

ALMALINUX_MANTISBT_PROJECT="AlmaLinux-8"
ALMALINUX_MANTISBT_PROJECT_VERSION="8.4"

No change


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
119 [AlmaLinux-8] -OTHER minor always 2021-08-21 20:48 2021-09-30 23:46
Reporter: kissumisha Platform:  
Assigned To: sfokin OS: Alma  
Priority: normal OS Version: 8.4  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: NetworkManager-wifi missing
Description: The package is in the BaseOS/packages folder in the Minimal install (NetworkManager-wifi-1.30.0-7.el8.x86_64), but this package doesn't get installed. Of couse with an Ethernet connection it's as easy as "dnf install" but if Ethernet is not available it becomes a pain because of all dependencies need to be installed.
Tags:
Steps To Reproduce: Every fresh install of AlmaLinux 8.4
Additional Information:
Attached Files: 01.jpg (133,260 bytes) 2021-08-26 13:46
https://bugs.almalinux.org/file_download.php?file_id=95&type=bug
02.jpg (122,633 bytes) 2021-08-26 13:46
https://bugs.almalinux.org/file_download.php?file_id=96&type=bug
03.jpg (255,011 bytes) 2021-08-26 13:46
https://bugs.almalinux.org/file_download.php?file_id=97&type=bug
Notes
(0000326)
sfokin   
2021-08-26 13:46   
Hi. I setup alma 8.4 on virtual machine.
chose profile 'Server with GUI'.
NetworkManager-wifi was installed by anaconda.
could you check it again?
(0000338)
kissumisha   
2021-09-30 23:46   
No I haven't tried with GUI. I go with the most minimal installation, so it's CLI interface.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
129 [AlmaLinux-8] -OTHER minor have not tried 2021-09-26 03:11 2021-09-26 03:11
Reporter: netroby Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Missing packages for install kcm-fcitx
Description: Missing packages for install kcm-fcitx, But the upstream RHEL packages looks have these packages.

# dnf install kcm-fcitx
Last metadata expiration check: 0:03:30 ago on Sun 26 Sep 2021 11:07:18 AM CST.
Error:
 Problem: package kcm-fcitx-0.5.5-7.el8.x86_64 requires libFcitxQt5WidgetsAddons.so.1()(64bit), but none of the providers can be installed
  - package kcm-fcitx-0.5.5-7.el8.x86_64 requires libFcitxQt5DBusAddons.so.1()(64bit), but none of the providers can be installed
  - conflicting requests
  - nothing provides libQt5Gui.so.5(Qt_5.11.1_PRIVATE_API)(64bit) needed by fcitx-qt5-1.2.4-3.el8.x86_64
  - nothing provides qt5-qtbase(x86-64) = 5.11.1 needed by fcitx-qt5-1.2.4-3.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
124 [AlmaLinux-8] -OTHER minor N/A 2021-09-02 02:53 2021-09-02 22:45
Reporter: fdr Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Improve AWS AMI ID acquisition instructions
Description: AlmaLinux's documentation on how to find AMIs could be expanded for
the benefit of those that want to automatically acquire new base
images.

Compare
https://web.archive.org/web/20210720172500/https://wiki.almalinux.org/cloud/AWS.html
to
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/finding-an-ami.html.

Some differences:

* AlmaLinux has both Marketplace and "Community" AMIs. Is the
  Marketplace one "official?" is the "community" account number -- not
  documented anywhere -- held in as strict confidence as images that
  make it to the marketplace? Why would I use one or the other? Why
  am I given this choice?

  Whereas, Amazon Linux really has only one method: public images,
  most comparable to "community" AMIs. "System Manager" is used to
  retrieve latest AMI ID.

  An older way to do something similar is to make careful use of
  naming conventions and a well-known account number. CentOS offers
  their account number, https://wiki.centos.org/Cloud/AWS. So does
  Oracle Linux,
  https://community.oracle.com/tech/apps-infra/discussion/4417739/launch-an-oracle-linux-instance-in-aws

* A major downside of Marketplace is that it's necessary to associate
  the product subscription with each account using it. This has
  different APIs, different SDKs, different IAM policies required than
  what would be required for most programs using EC2.

* AWS provides precise API calls used to get the latest AMI,
  indicating how they anticipate you will source new image IDs, and
  will keep it working. None of the other systems do, but they
  should, and in practice, code of this kind works practically
  indefinitely:

      images(
        owners: ["764336703387"],
        filters: [
          {name: "name", values: ["AlmaLinux OS 8.* x86_64"]},
          {name: "state", values: ["available"]}
        ]
      ).max_by { |img| img.creation_date }.id


  The following such wildcarded strings can be useful for different
  levels of automatic updates:
  
  AlmaLinux OS * x86_64

  AlmaLinux OS 8.* x86_64

  AlmaLinux OS 8.4.* x86_64
Tags: aws, cloud
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000329)
fdr   
2021-09-02 02:58   
For more information about this "parameter store" that Amazon Linux uses, see https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html. I haven't used this much myself, but I seem to remember following AWS instructions to use it in the past and it was no sweat.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
118 [AlmaLinux-8] anaconda feature always 2021-08-20 06:39 2021-08-20 06:39
Reporter: lee Platform: Linux  
Assigned To: OS: EL8  
Priority: normal OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: VirtualBox Guest Additions in AlmaLinux
Description: It would be great to have guest editions in the Alma Linux installer, and the final install like Fedora does.
The above makes deploying in VMs very pleasant.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
115 [AlmaLinux-8] almalinux-logos minor N/A 2021-08-11 05:16 2021-08-12 10:53
Reporter: srbala Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Add a `PNG` format background image in `almalinux-backgrounds` package for XFCE Live use
Description: Note: This is feature request to `almalinux-backgrounds` package, Category missing for his package.

XFCE window manager expects desktop default background at `/usr/share/backgrounds/images/default.png`

Since current package only includes only `.jpg` format, XFCE Live ISO loads with empty background.
Tags:
Steps To Reproduce: Convert one of high res image and named it to `/usr/share/backgrounds/images/default.png` (Almalinux-dark?)



Additional Information: 1. Needed this for AlmaLinux XFCE Live image.
2. Prefer to have one of each type background should be added.
3. Added one image XFCE Beta use.
Attached Files: Alma-dark-2048x1536.png (642,903 bytes) 2021-08-11 05:16
https://bugs.almalinux.org/file_download.php?file_id=94&type=bug
Notes
(0000322)
srbala   
2021-08-11 11:57   
Reverse link to channel discussion https://chat.almalinux.org/almalinux/pl/yethkf1wdjbgujmihie7knqdja

Sample XFCE
 https://user-images.githubusercontent.com/1273137/129016230-1921cc3b-f949-421e-a31a-18336507a632.png
(0000323)
srbala   
2021-08-11 12:27   
Need to update/replace `/etc/xdg/kcm-about-distrorc` with following content to fix KInfo

[General]
LogoPath=/usr/share/icons/hicolor/256x256/apps/fedora-logo-icon.png
Website=https://almalinux.org/
(0000324)
srbala   
2021-08-12 10:53   
Created a repo for contents of the `extras` package and rpm post install script
https://github.com/srbala/almalinux-backgrounds-extras


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
116 [AlmaLinux-8] targetcli major always 2021-08-11 14:06 2021-08-11 14:06
Reporter: nicolae Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: db_root: cannot open: /etc/target
Description: After installing (fresh install) AlmaLinux 8.4 on three Supermicro servers at boot i have the error db_root: cannot open: /etc/target . All servers have Avago 3108 Raid card.
Also at boot, after showing the available kernel, it stays with blinking cursor more than a minute.
If i install targetcli that error disappears, but it still stays too long with blinking cursor. The servers are set to boot in legacy mode.
[root@localhost ~]# systemd-analyze blame
          6.204s NetworkManager-wait-online.service
          1.295s systemd-udev-settle.service
           592ms dracut-initqueue.service
           439ms tuned.service
           277ms initrd-switch-root.service
           223ms vdo.service
           222ms rdma-load-modules@rdma.service
           176ms sssd.service
           162ms lvm2-monitor.service
Tags:
Steps To Reproduce: Fresh install on Supermicro server.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
114 [AlmaLinux-8] libva block always 2021-08-01 22:21 2021-08-10 07:50
Reporter: puya Platform:  
Assigned To: OS: AlmaLinux  
Priority: high OS Version: 8.4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: vainfo: vaInitialize failed with error code -1 (unknown libva error)
Description: Background
-----------------
I've been trying to build gstreamer-vaapi (needed by Qt) as it is missing from EPEL. The build/installation seems to go fine but when I run:
> gst-inspect-1.0 vaapi

All I get is "0 features". (e.g. missing vaapisink needed by Qt's runtime).

Not sure if this matters but running with `GST_DEBUG=7` I get:
```
extension is not recognized as module file, ignoring file /usr/lib64/gstreamer-1.0/include/gst/gl/gstglconfig.h
extension is not recognized as module file, ignoring file /usr/lib64/gstreamer-1.0/libgstvaapi.la
```

In any case, in order to debug the above I tried installing `libva-utils` and running vainfo, this returns:
```
vaInitialize failed with error code -1 (unknown libva error)
```

The Issue
--------
Any ideas why I would get "0 Features" for my gstreamer-vaapi installation?
How do I fix my va-api installation so that vainfo does not fail to initialize the deriver?
Tags: AlmaLinux, Bug
Steps To Reproduce: ```
$ dnf install libva-devel libva-utils libva-intel-driver
...
$ vainfo
libva info: VA-API version 1.5.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_4
libva error: /usr/lib64/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
```
Additional Information: Please let me know what other information would be useful.

I am out of my depth here since my original issue was the Qt runtime failing. So any help / hint / ideas or info you may have that might nudge me in the right direction are greatly appreciated!
Attached Files:
Notes
(0000321)
enigma131   
2021-08-10 07:50   
Without information coming from your hardware (GPU part) , difficult to answer


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
110 [AlmaLinux-8] almalinux-release block always 2021-06-29 11:58 2021-07-27 12:05
Reporter: Wumbeer Platform: Dell PowerEdge T340  
Assigned To: alukoshko OS: AlmaLinux  
Priority: normal OS Version: 8.4  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
abrt_hash:
URL:
Summary: Fresh install - do all updates - reboot - BIOS does not find OS - no grub
Description: Fresh install of AlmaLinux will not boot after updates - BIOS message about no bootable device or operating system.

You do not even get to grub menu showing kernels. Been running AlamaLinux for few months on this server and was just doing updates and killed it. I reinstalled again and did a yum update and it broke again, exact same way, so it is reproducible.

Not sure what is killing it, I assume a grub problem. I found https://www.reddit.com/r/CentOS/comments/i0ozrs/cant_boot_in_after_latest_kernel_update_for/ 3 which seems similar, but 11 months ago, so we tried it - and I get same problem user Joeg1484 got. Gave up and just not going to install updates.
Tags:
Steps To Reproduce: 1. Install AlmaLinux
2. Update all packages (coming from CentOS so I been using yum)
3. Reboot

Additional Information:
Attached Files:
Notes
(0000290)
alukoshko   
2021-06-29 13:15   
Hello.
Are you in BIOS or UEFI mode? Is Secure Boot enabled?
What version I should install to reproduce update bug 8.3 or 8.4?
(0000296)
Wumbeer   
2021-06-30 19:28   
UEFI mode. Secure boot is not enabled. 8.4 was the version.
(0000297)
Wumbeer   
2021-06-30 19:35   
I verified just to make sure I was not incorrect about the above:

[root@virtual1 ~]# mokutil --sb-state
SecureBoot disabled

[root@virtual1 ~]# ls -l /sys/firmware/efi<