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 1162502 - targetd should refuse to start if SSL credentials are missing
Summary: targetd should refuse to start if SSL credentials are missing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: targetd
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Tony Asleson
QA Contact: Martin Hoyer
URL:
Whiteboard:
Depends On: 1162278
Blocks: 1385242
TreeView+ depends on / blocked
 
Reported: 2014-11-11 08:03 UTC by Bruno Goncalves
Modified: 2023-03-08 07:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1162278
Environment:
Last Closed: 2017-08-01 20:43:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1982 0 normal SHIPPED_LIVE targetd bug fix and enhancement update 2017-08-01 18:31:11 UTC

Description Bruno Goncalves 2014-11-11 08:03:04 UTC 
+++ This bug was initially created as a clone of Bug #1162278 +++

from bgoncalv:

I configured targetd to support ssl on yaml file and the service started without problem.

As I didn't create targetd_key.pem nor targetd_cert.pem shouldn't the service fail to start? As it happens if VG or Password are not set.
Comment 1 Bruno Goncalves 2014-11-11 08:03:29 UTC 
Just to track the port of the patch to RHEL-7
Comment 5 Tony Asleson 2017-02-06 21:30:09 UTC 
What happens is the missing certificate files are not noticed until a client actually tries to use the service.  It would be better to check that the required files are present at start up to ensure that the clients can hopefully connect cleanly.

Traceback (most recent call last):
  File "/usr/lib64/python2.7/SocketServer.py", line 290, in _handle_request_noblock
    self.process_request(request, client_address)
  File "/usr/lib64/python2.7/SocketServer.py", line 318, in process_request
    self.finish_request(request, client_address)
  File "/home/tasleson/projects/targetd/targetd/main.py", line 160, in finish_request
    suppress_ragged_eofs=True)
  File "/usr/lib64/python2.7/ssl.py", line 943, in wrap_socket
    ciphers=ciphers)
  File "/usr/lib64/python2.7/ssl.py", line 554, in __init__
    self._context.load_cert_chain(certfile, keyfile)
IOError: [Errno 2] No such file or directory
Comment 7 Martin Hoyer 2017-04-28 12:26:16 UTC 
Tested with targetd-0.8.5-1.el7, works well.
No regression found.
Comment 8 errata-xmlrpc 2017-08-01 20:43:39 UTC 
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-2017:1982
Note You need to log in before you can comment on or make changes to this bug.