Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1488572

Summary:	ssh:server::options: should be ssh::server::options: in puppet/compute-puppet.yaml
Product:	Red Hat OpenStack	Reporter:	Alex Schultz <aschultz>
Component:	openstack-tripleo-heat-templates	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Gurenko Alex <agurenko>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	agurenko, aschultz, awaugama, dmacpher, emacchi, lyarwood, mburns, mflusche, rhel-osp-director-maint
Target Milestone:	zstream	Keywords:	Triaged, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:	1487869	Environment:
Last Closed:	2017-10-19 18:12:53 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:
Bug Depends On:	1487869
Bug Blocks:	1488570

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