Bug 1488572 - ssh:server::options: should be ssh::server::options: in puppet/compute-puppet.yaml
Summary: ssh:server::options: should be ssh::server::options: in puppet/compute-puppet...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: zstream
: 7.0 (Kilo)
Assignee: Alex Schultz
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On: 1487869
Blocks: 1488570
TreeView+ depends on / blocked
 
Reported: 2017-09-05 17:58 UTC by Alex Schultz
Modified: 2017-10-19 18:12 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-0.8.6-137.el7ost
Doc Type: Bug Fix
Doc Text:
A missing colon prevented SSH server options from being used during overcloud deployment. This fix adds the extra colon and ensures successful overcloud deployment.
Clone Of: 1487869
Environment:
Last Closed: 2017-10-19 18:12:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2995 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OSP 7 director Bug Fix Advisory 2017-10-19 22:12:39 UTC

Description Alex Schultz 2017-09-05 17:58:33 UTC 
OSP7

+++ This bug was initially created as a clone of Bug #1487869 +++

Description of problem:
missing colon prevents the ssh server options from being used during deployment.  Only default sshd parameter are applied by the ::ssh::server puppet class.

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-0.8.14-30.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. deploy OSP 8 w/ THT openstack-tripleo-heat-templates-0.8.14-30.el7ost.noarch
2. verify /etc/ssh/sshd_config does not include sshd config from puppet/compute.yaml


Additional info:
Likely an issue with other OSP versions.
Comment 5 errata-xmlrpc 2017-10-19 18:12:53 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:2995
Note You need to log in before you can comment on or make changes to this bug.