RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1341088 - Installation in container fails because of /var/lock/opencryptoki
Summary: Installation in container fails because of /var/lock/opencryptoki
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: opencryptoki
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1341079
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-31 09:02 UTC by Jan Pazdziora
Modified: 2019-03-06 02:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1341079
Environment:
Last Closed: 2016-06-28 07:59:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Pazdziora 2016-05-31 09:02:48 UTC 
+++ This bug was initially created as a clone of Bug #1341079 +++

Description of problem:

Installing opencryptoki into container image fails because the rpm contains /var/lock/opencryptoki but Fedora base image does not contain /run/lock.

Version-Release number of selected component (if applicable):

opencryptoki-3.4.1-1.fc23.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. docker run --rm -ti fedora:23 dnf install -y opencryptoki

Actual results:

$ docker run --rm -ti fedora:23 dnf install -y opencryptoki
Fedora 23 - x86_64 - Updates                     51 MB/s |  22 MB     00:00    
Fedora 23 - x86_64                               58 MB/s |  43 MB     00:00    
Last metadata expiration check performed 0:00:26 ago on Tue May 31 08:32:12 2016.
Dependencies resolved.
================================================================================
 Package                    Arch         Version            Repository     Size
================================================================================
Installing:
 opencryptoki               x86_64       3.4.1-1.fc23       updates       101 k
 opencryptoki-icsftok       x86_64       3.4.1-1.fc23       updates       228 k
 opencryptoki-libs          x86_64       3.4.1-1.fc23       updates        45 k

Transaction Summary
================================================================================
Install  3 Packages

Total download size: 373 k
Installed size: 1.0 M
Downloading Packages:
(1/3): opencryptoki-3.4.1-1.fc23.x86_64.rpm     693 kB/s | 101 kB     00:00    
(2/3): opencryptoki-libs-3.4.1-1.fc23.x86_64.rp 202 kB/s |  45 kB     00:00    
(3/3): opencryptoki-icsftok-3.4.1-1.fc23.x86_64 1.0 MB/s | 228 kB     00:00    
--------------------------------------------------------------------------------
Total                                           276 kB/s | 373 kB     00:01     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Installing  : opencryptoki-libs-3.4.1-1.fc23.x86_64                       1/3 
  Installing  : opencryptoki-icsftok-3.4.1-1.fc23.x86_64                    2/3 
  Installing  : opencryptoki-3.4.1-1.fc23.x86_64                            3/3 
Error unpacking rpm package opencryptoki-3.4.1-1.fc23.x86_64
Error unpacking rpm package opencryptoki-3.4.1-1.fc23.x86_64
error: unpacking of archive failed on file /var/lock/opencryptoki: cpio: mkdir
opencryptoki-3.4.1-1.fc23.x86_64 was supposed to be installed but is not!
  Verifying   : opencryptoki-3.4.1-1.fc23.x86_64                            1/3 
  Verifying   : opencryptoki-libs-3.4.1-1.fc23.x86_64                       2/3 
  Verifying   : opencryptoki-icsftok-3.4.1-1.fc23.x86_64                    3/3 

Installed:
  opencryptoki-icsftok.x86_64 3.4.1-1.fc23                                      
  opencryptoki-libs.x86_64 3.4.1-1.fc23                                         

Failed:
  opencryptoki.x86_64 3.4.1-1.fc23                                              

Complete!

Expected results:

No error.

Additional info:

The /var/lock is symlink to /run/lock:

$ docker run --rm -ti fedora:23 ls -la /var/run /run/lock
ls: cannot access /run/lock: No such file or directory
lrwxrwxrwx. 1 root root 6 Mar  4 05:17 /var/run -> ../run

The /run gets mounted as tmpfs so opencryptoki should be putting in anything there anyway. If it needs the directory in runtime, it likely should use tmpfiles.

There is the same problem with centos:centos7 and opencryptoki-3.2-5.el7_2.x86_64.

On RHEL, the /run has /run/lock in the image but I believe the fix should go to RHEL as well.
Comment 1 Jakub Jelen 2016-06-28 07:59:56 UTC 
From the Fedora bug, I understand that the problem is related to the Fedora Packaging Guidelines and/or to the fedora docker image. This is not applicable for RHEL7 (the initial guess was wrong). Am I right?

If so, I believe we can close this bug as unrelated and continue the work in Fedora. Moving files and paths around in RHEL7 is probably not a good idea.
Feel free to reopen, if it will show up that we need to fix something here.
Note You need to log in before you can comment on or make changes to this bug.