Bug 1841869 - Reading a password has failed in volume_key tests
Summary: Reading a password has failed in volume_key tests
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: volume_key
Version: 39
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Kucera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1841901
TreeView+ depends on / blocked
 
Reported: 2020-05-29 16:52 UTC by Jiri Kucera
Modified: 2023-08-16 07:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1841901 (view as bug list)
Environment:
Last Closed: 2021-11-30 16:16:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Log from CI (128.34 KB, text/plain)
2020-05-29 16:52 UTC, Jiri Kucera
no flags Details

Description Jiri Kucera 2020-05-29 16:52:11 UTC
Created attachment 1693469 [details]
Log from CI

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 Ben Cotton 2020-08-11 13:34:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 2 Ben Cotton 2021-11-04 17:38:23 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2021-11-30 16:16:59 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Ben Cotton 2022-02-08 21:22:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 5 Ben Cotton 2023-04-25 16:40:18 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Fedora Release Engineering 2023-08-16 07:04:34 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


Note You need to log in before you can comment on or make changes to this bug.