Bug 1370035 - repository section shoudn't be in the same level as middleware
Summary: repository section shoudn't be in the same level as middleware
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.2.1
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 06:36 UTC by Gan Huang
Modified: 2016-10-18 17:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-18 17:48:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Gan Huang 2016-08-25 06:36:09 UTC
Description of problem:
When enable s3 backend storage in 3.2 installation, it's not correct that repository section was in the same level as middleware.

Version-Release number of selected component (if applicable):
openshift-ansible-3.2.24-1.git.0.337259b.el7.noarch.rpm

How reproducible:
always

Steps to Reproduce:
1.Trigger a 3.2 installation which enables s3 backend storage as docker-reigstry
2.
3.

Actual results:
sh-4.2$ cat /etc/registryconfig/config.yml
<--snip-->
auth:
  openshift:
    realm: openshift
middleware:
repository:
  - name: openshift
    options:
      pullthrough: True


Expected results:
sh-4.2$ cat /etc/registryconfig/config.yml
<--snip-->
auth:
  openshift:
    realm: openshift
middleware:
  repository:
  - name: openshift
    options:
      pullthrough: True


Additional info:
Waiting for PR merged to 3.2: 
https://github.com/openshift/openshift-ansible/pull/2314

Comment 1 Brenton Leanhardt 2016-08-25 12:57:15 UTC
Would this just be a simple backport to 3.2 or would something need to change?

Comment 2 Scott Dodson 2016-08-25 14:27:31 UTC
Yeah, should be easy to backport. I've added the backport/enterprise-3.2 label to that PR.

Comment 3 Scott Dodson 2016-10-18 17:48:32 UTC
This was fixed already in openshift-ansible-3.2.33-1


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