Bug #20878: rocky8 libpam-arvados-go package fails tests - Arvados

Custom queries

All assigned issues
All issues assigned for grooming
My issues for grooming
My issues for grooming (no story pts)
Prioritized open issues

Actions

Copy link

Bug #20878

closed

rocky8 libpam-arvados-go package fails tests

Added by Brett Smith over 1 year ago. Updated over 1 year ago.

Status:

Resolved

Priority:

Normal

Assigned To:

Brett Smith

Category:

Deployment

Target version:

Development 2023-08-30

Story points:

0.5

Release:

Arvados 2.7.0

Release relationship:

Auto

Description

START: libpam-arvados-go test on arvados/package-test:rocky8
…
Installing:                                                          
 libpam-arvados-go-2.7.0~dev20230816133232-1.x86_64 localrepo  6.8 MB
…
Complete.

ldd: warning: you do not have execution permission for `./usr/lib/pam_arvados.so'
    libpam.so.0 => not found
^^^ Missing while scanning ./usr/lib/pam_arvados.so ^^^
ERROR: libpam-arvados-go test on arvados/package-test:rocky8 failed with exit status 1

Subtasks 1 (0 open — 1 closed)

Task #20881: Review 20878-rh-package-download

Resolved

Lucas Di Pentima

08/17/2023

Actions

Related issues 2 (0 open — 2 closed)

	Related to Arvados - Feature #20797: Build Rocky Linux / RHEL compatible packages	Resolved	Brett Smith	08/01/2023			Actions
	Related to Arvados - Idea #20822: Add build-packages-rocky8 to build-packages Jenkins multijob	Resolved	Brett Smith				Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Brett Smith over 1 year ago

Subject changed from rocky8 package build/test failures related to PAM to rocky8 libpam-arvados-go package fails tests

Actions

Copy link

Updated by Brett Smith over 1 year ago

421d6f9ea1 added an explicit dependency on pam to lib/pam/fpm-info.sh. And rocky8's pam package is the one that provides libpam.so.0 (under /usr/lib64 if that matters). And this passed before during review. Soooooo this is weird.

Actions

Copy link

Updated by Brett Smith over 1 year ago

Description updated (diff)

Actions

Copy link

Updated by Brett Smith over 1 year ago

It does succeed sometimes, seemingly at random. Since I added it to build-packages-multijob:

#23 failed at Aug 16, 2023 11:21 PM
#22 failed at Aug 16, 2023 10:01 PM
#21 failed at Aug 16, 2023 9:01 PM
#20 failed at Aug 16, 2023 8:25 PM
#19 succeeded at Aug 16, 2023 1:57 PM
#18 failed at Aug 16, 2023 2:09 AM
#17 failed at Aug 16, 2023 1:07 AM
#16 failed at Aug 15, 2023 11:42 PM
#15 failed at Aug 15, 2023 10:54 PM
#14 failed at Aug 15, 2023 10:15 PM
#13 failed at Aug 15, 2023 9:29 PM
#12 failed at Aug 15, 2023 8:48 PM
#11 failed at Aug 15, 2023 7:35 PM
#10 succeeded at Aug 15, 2023 6:48 PM

Actions

Copy link

Updated by Brett Smith over 1 year ago

A successful build (#10) during the build process:

libpam-arvados-go-2.7.0~dev20230815174158-1.x86_64.rpm not found, building

And then later during the test:

START: libpam-arvados-go test on arvados/package-test:rocky8
…
Package                                             Repository     Size
Installing:                                                            
 cracklib-2.9.6-15.el8.x86_64                       baseos      94.2 kB
 cracklib-dicts-2.9.6-15.el8.x86_64                 baseos       4.1 MB
 libpam-arvados-go-2.7.0~dev20230815174158-1.x86_64 localrepo    6.8 MB
 libpwquality-1.4.4-6.el8.x86_64                    baseos     108.6 kB
 pam-1.3.1-25.el8.x86_64                            baseos     762.8 kB

A failed build (#11) during the build process:

Package libpam-arvados-go-2.7.0~dev20230814202948-1.x86_64.rpm exists upstream, not rebuilding, downloading instead!

And then during tests it only installs libpam-arvados-go, without any dependencies. So there's some difference between these two different build cases that causes the distinction between pass and fail.

Actions

Copy link

Updated by Brett Smith over 1 year ago

The download logic always checks the CentOS 7 repository. So if build-packages-centos7 runs first, those packages upload and then reused for build-packages-rocky8. If it goes the other way, the rocky8 packages build and pass.

The download logic needs to be adapted for the addition of rocky8.

Actions

Copy link