Private SSH key for deployment has wrong permissions
Bug #1859244 reported by
Luke Short
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Luke Short |
Bug Description
Description
===========
Sometimes a deployment will fail being unable to use a private SSH key created by TripleO for the Overcloud due to insecure permissions.
Related BZ: https:/
Steps to reproduce
==================
This issue seems random but happens on new deployments.
Expected result
===============
The private SSH key should have 0600 permissions.
Actual result
=============
The private SSH key has 0670 permissions.
Environment
===========
Train
Logs & Configs
==============
https:/
Changed in tripleo: | |
milestone: | none → ussuri-1 |
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/702147
Review: https:/