Bug 1844801

Summary: dbxtool.service: Failed with result 'exit-code'.
Product: [Fedora] Fedora Reporter: Forlorn <forlorn>
Component: dbxtoolAssignee: Peter Jones <pjones>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: fmartine, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 16:24:57 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:
Attachments:
Description Flags
strace
none
Requested efivarfs none

Description Forlorn 2020-06-07 09:57:29 UTC
Created attachment 1695786 [details]
strace

Description of problem:

Service starts and runs successfully, but still creates an error on exit.

Jun 07 11:52:30 xxx.localdomain systemd[1]: Started Secure Boot DBX (blacklist) updater.
Jun 07 11:52:30 xxx.localdomain dbxtool[22807]: dbxtool: Success
Jun 07 11:52:30 xxx.localdomain systemd[1]: dbxtool.service: Main process exited, code=exited, status=1/FAILURE
Jun 07 11:52:30 xxx.localdomain systemd[1]: dbxtool.service: Failed with result 'exit-code'.

Manually starting:

/usr/bin/dbxtool -a /usr/share/dbxtool 
dbxtool: Success

How reproducible:

Every time I restart the service this happens.

Additional info:

Started with the latest update.

Comment 1 Javier Martinez Canillas 2020-06-09 16:32:54 UTC
I'm not able to reproduce the issue. Is this with dbxtool-8-11.fc32.x86_64 ?

Comment 2 Forlorn 2020-06-09 20:00:01 UTC
(In reply to Javier Martinez Canillas from comment #1)
> I'm not able to reproduce the issue. Is this with dbxtool-8-11.fc32.x86_64 ?

Yes. I don't have the issue on three other PCs that I upgraded from F31 as well.

Comment 3 Peter Jones 2020-06-30 19:33:53 UTC
I suspect this means you've got Secure Boot on but the KEK variable doesn't list the right keys?  Can you attach the result of:

tar cjf efivarfs.tar.bz2 /sys/firmware/efi/efivars/

Comment 4 Forlorn 2020-07-01 08:18:32 UTC
Created attachment 1699441 [details]
Requested efivarfs

Uploaded as requested.

Comment 5 Fedora Program Management 2021-04-29 16:29:54 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 6 Ben Cotton 2021-05-25 16:24:57 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.