Bug 1391865

Summary: Trouble creating service signer certificate while running upgrade in containerized environment
Product: OpenShift Container Platform Reporter: Jaspreet Kaur <jkaur>
Component: Cluster Version OperatorAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: high    
Version: 3.3.0CC: aos-bugs, bpaulsru, jokerman, mmccomas
Target Milestone: ---   
Target Release: 3.3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-ansible-3.3.46-1.git.0.2558730.el7 Doc Type: Bug Fix
Doc Text:
Previously containerized upgrades from OCP 3.2 to 3.3 would fail to properly create the service signing certificate due to an invalid path being used in containerized environments. We have corrected that error and now containerized upgrades create service signer certificates.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-15 19:11:06 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:

Description Jaspreet Kaur 2016-11-04 09:28:29 UTC
Description of problem: While upgrading to v3.2.1.15 to v3.3 (containerized) using atomic-openshift-utils-3.3.41-1.git.0.a1a327b.el7.noarch.rpm 

The command we ran was:
ansible-playbook -i inventory.ini /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_3/upgrade.yml -vvv


This error seems to be related to this github issue: https://github.com/openshift/openshift-ansible/pull/2638


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 errata-xmlrpc 2016-11-15 19:11:06 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/RHSA-2016:2778