Bug 1462809 - Error message when installing certbot
Error message when installing certbot
Status: NEW
Product: Fedora
Classification: Fedora
Component: certbot (Show other bugs)
All Linux
unspecified Severity medium
: ---
: ---
Assigned To: James Hogarth
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-06-19 11:16 EDT by Quentin Armitage
Modified: 2018-05-03 04:42 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Quentin Armitage 2017-06-19 11:16:47 EDT
Description of problem:
The following error messages are produced when installing certbot:
ValueError: File context for /etc/(letsencrypt|certbot)/(live|archive)(/.*)? already defined
restorecon: lstat(/etc/letsencrypt) failed: No such file or directory

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

How reproducible:

Steps to Reproduce:
1. dnf install certbot

Actual results:
Error messages listed above

Expected results:
No error messages

Additional info:
Is this two separate errors? The first one seems to suggest that the base selinux policies are handling the certbot directories, and the second one seems to suggest that the /etc/letsencrypt directory isn't being created by the installation of certbot.
Comment 1 Fedora End Of Life 2018-05-03 04:42:53 EDT
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

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