Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1569907 - openshift_cert_expiry is not compatible with deprecated registry configuration
Summary: openshift_cert_expiry is not compatible with deprecated registry configuration
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: All
OS: All
low
medium
Target Milestone: ---
: 3.9.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-20 08:50 UTC by Juan Luis de Sousa-Valadas
Modified: 2018-11-19 21:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 21:20:30 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Juan Luis de Sousa-Valadas 2018-04-20 08:50:15 UTC
Description of problem:
The internal registry can be configured with the following environment variables
OPENSHIFT_CA_DATA
OPENSHIFT_CERT_DATA
OPENSHIFT_KEY_DATA

Which contain a x509 PEM file used to authenticate against OpenShift, the module does not read them.

Version-Release number of selected component (if applicable):
Not implemented at all in the master branch

How reproducible:
N/A

Steps to Reproduce:
N/A

Actual results:
The playbook ignores those variables

Expected results:
Get the data and analyse it

Additional info:


Description of problem:

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Russell Teague 2018-11-19 21:20:30 UTC
There appear to be no active cases related to this bug. As such we're closing this bug in order to focus on bugs that are still tied to active customer cases. Please re-open this bug if you feel it was closed in error or a new active case is attached.


Note You need to log in before you can comment on or make changes to this bug.