Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem: Builds are failing with below error :

error: build error: devmapper: Error mounting '/dev/mapper/docker-253:7-786433-66102a8b70b2778aac36aa9ef99d6cbb7d9b9f46188ff870807c017496162a7c' on '/var/lib/docker/devicemapper/mnt/66102a8b70b2778aac36aa9ef99d6cbb7d9b9f46188ff870807c017496162a7c': invalid argument


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
 
Actual results: Fails each time with the error


Expected results: It should suceed


Additional info :

Seems similar to  https://github.com/openshift/origin/issues/17330

This impacts our user community, can you please priortize this

Any updates on this issue 

Thanks,
Cynthia

I can't find error message in the log. Where did you get this error message. I will need all the surrounding messages around that and see if something is odd.

Also please provide me a system where problem is reproducible.

I believe this would only happen if the container was created on a docker enabled selinux system which was later disabled, on the host.

I actually think the system has SELinux disabled.

This label also looks strange since it only uses one category.  Not sure if OpenShift allows users to specify the MCS Label?  Using one category is not a great idea,  Since all containers with s0:c12,c* can write to this label.

Antonio do we have these patches merged?

*** Bug 1535694 has been marked as a duplicate of this bug. ***

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0202