Find out why /var/run/shibboleth is not in the knightly image

After the knightly build deploy, the OOD interface is not accessible. After @cmcclung inspected the log file on the node, it's because the socket file path doesn't exist for shibboleth while the path should be provided by the rpm package.

added Backlog label

changed the description

changed milestone to %ood nightly builds

assigned to @louistw

added Sprint 22-20 label and removed Backlog label

Checking in this job: https://gitlab.rc.uab.edu/louistw/packer-openstack-hpc-image/-/jobs/29986#L1029

This line indicates that /var/run/shibboleth exists while building the image.

https://shibboleth.atlassian.net/browse/SSPCPP-411?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

Seems like this issue has been addressed in Shibboleth 2.5.0, and should not be an issue for us since we are running Shibboleth 3.3.0-1.

Logged in and checked again on shibd.service status, it's running as expected. Also checked the stat on /var/run/shibboleth. Seems like the fix mentioned above is doing its job. I guess we just need to wait for the shibd.service to retry and it will create the folder.

● shibd.service - Shibboleth Service Provider Daemon
   Loaded: loaded (/usr/lib/systemd/system/shibd.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2022-10-20 01:19:35 CDT; 10h ago
     Docs: https://wiki.shibboleth.net/confluence/display/SP3/Home
 Main PID: 1157 (shibd)
    Tasks: 6
   Memory: 35.1M
   CGroup: /system.slice/shibd.service
           └─1157 /usr/sbin/shibd -f -F

  File: ‘/var/run/shibboleth’
  Size: 60        	Blocks: 0          IO Block: 4096   directory
Device: 14h/20d	Inode: 17366       Links: 2
Access: (0755/drwxr-xr-x)  Uid: (  446/   shibd)   Gid: (  448/   shibd)
Access: 2022-10-20 12:14:54.802285042 -0500
Modify: 2022-10-20 01:19:35.873885590 -0500
Change: 2022-10-20 01:19:35.873885590 -0500
 Birth: -

If I do a ls /var/run/shibboleth during the image building process, the folder will somehow be preserved and the shibd will run just fine.

EDIT: And now it's not working...

changed title from Find out why /var/run/shibboleth is not in the ood image to Find out why /var/run/shibboleth is not in the knightly image

marked this issue as related to #23

From @jpr on Slack:

systemd management on centos 7 wrt /var/run dir https://steve-parker.org/linux/var_run/

And it's verified on the knightly instance:

$ cat /usr/lib/tmpfiles.d/shibboleth.conf
d /run/shibboleth 755 shibd shibd -

added Sprint 22-21 label and removed Sprint 22-20 label

closed