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.

Bug 1841901

Summary: Reading a password has failed in volume_key tests
Product: Red Hat Enterprise Linux 8 Reporter: Jiri Kucera <jkucera>
Component: volume_keyAssignee: Jiri Kucera <jkucera>
Status: CLOSED WONTFIX QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.2CC: extras-qa, huzaifas, jkucera
Target Milestone: rcKeywords: Reopened
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1841869 Environment:
Last Closed: 2022-12-06 07:27:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1841869    
Bug Blocks:    

Description Jiri Kucera 2020-05-29 18:45:04 UTC
+++ This bug was initially created as a clone of Bug #1841869 +++

Description of problem:
When tests are running in CI and volume_key is trying to read a password given to
it by expect, it fails with

  volume_key: Error opening `image.img': Error getting LUKS data encryption key: Invalid argument

error message.

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

How reproducible:
often

Steps to Reproduce:
1. fedpkg scratch-build
2. wait until scratch build is done
3. go to https://jenkins-continuous-infra.apps.ci.centos.org
4. find the volume_key job/pipeline
5. see the logs

Actual results:
See https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-build-pipeline/detail/fedora-rawhide-build-pipeline/13175/pipeline
volume_key is terminated with "volume_key: Error opening `image.img': Error getting LUKS data encryption key: Invalid argument" error message.

Expected results:
volume_key should read the password correctly, tests should pass

Additional info:
"Invalid argument" argument is issued when fread in password reading function return NULL. fread return NULL when read return -1. Investigating the password reading function, there is no (errno == EINTR || errno == EAGAIN) handling, so reading a password is probably interrupted by system during CI testing.

Comment 1 Jiri Kucera 2020-05-29 18:49:38 UTC
This issue happens also when running tests on beaker or on BaseOS CI. The steps to reproduce are similar.

Comment 2 Jiri Kucera 2020-05-29 18:54:28 UTC
The affected version of volume_key on RHEL 8 is volume_key-0.3.11-5.

Comment 5 RHEL Program Management 2021-11-29 07:27:04 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 8 RHEL Program Management 2022-12-06 07:27:49 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.