Bug 1558236

Summary: [Deployment][TLS] TLS ODL container deployments fail due to no odl user/group on host
Product: Red Hat OpenStack Reporter: Tim Rozet <trozet>
Component: puppet-tripleoAssignee: Tim Rozet <trozet>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: high Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: aadam, jjoyce, jschluet, mkolesni, slinaber, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: odl_deployment, odl_tls
Fixed In Version: puppet-tripleo-8.3.1-0.20180304033909 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:47:45 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:
Bug Depends On:    
Bug Blocks: 1488826    

Description Tim Rozet 2018-03-19 21:05:04 UTC
Description of problem:
In TLS deployments a key and certificate are created for ODL on the host (as owner/group odl/odl).  These artifacts are then used to configure TLS for ODL.  In containerized deployments these files are still created on the host, and then mounted into the ODL container.  However, now that we containerize ODL, it means the RPM is no longer installed on the host, and the 'odl' linux group/user are not created.  Thus when deploying with TLS and ODL, there is a puppet error saying:

            "Error: /Stage[main]/Tripleo::Certmonger::Opendaylight/File[/etc/pki/tls/certs/odl.crt]/group: change from root to odl failed: Could not find group odl",                            
            "Error: /Stage[main]/Tripleo::Certmonger::Opendaylight/File[/etc/pki/tls/private/odl.key]/owner: change from root to odl failed: Could not find user odl",                           
            "Error: /Stage[main]/Tripleo::Certmonger::Opendaylight/File[/etc/pki/tls/private/odl.key]/group: change from root to odl failed: Could not find group odl"    

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

How reproducible:

Steps to Reproduce:
1.  Deploy ODL with internal TLS enabled and containers

Actual results:

Expected results:

Additional info:
A workaround to this issue is to virt-customize the overcloud image and install ODL on it to get the user/group created.

Comment 7 Itzik Brown 2018-04-26 09:35:57 UTC
Checked with:

Comment 9 errata-xmlrpc 2018-06-27 13:47:45 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.