Bug 1562327 - [ASB]update provision plan will make secret reference changed
Summary: [ASB]update provision plan will make secret reference changed
Keywords:
Status: CLOSED DUPLICATE of bug 1564979
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.10.0
Assignee: Jesus M. Rodriguez
QA Contact: shahan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-30 08:00 UTC by shahan
Modified: 2018-04-25 13:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-25 13:07:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description shahan 2018-03-30 08:00:30 UTC
Description of problem:
 update provision plan will make secret reference changed

Version-Release number of selected component (if applicable):
  OpenShift Master:v3.9.14 
  ASB version: 1.1.16

How reproducible:
Always

Steps to Reproduce:
1. Install OCP cluster enable asb
2. provision apb serviceclass with multiple plan, like MySQL (APB).
3. check serviceinstance yaml file 
4. change current plan for serviceinstance
5. check serviceinstance yaml file

Actual results:
3. will find parameter secret under secretKeyRef. like this:
  parametersFrom:
    - secretKeyRef:
        key: parameters
        name: rh-mysql-apb-parametersi4ghu
      
5. will find parameter secret under secretKeyRef. like this:
    parametersFrom:
    - secretKeyRef:
        key: parameters
        name: rh-mysql-apbyn9i2
        
This new secret just contains version info and no other parameters like name, password,user etc.

Expected results:
Should contain all useful info for user.

Additional info:

Comment 1 John Matthews 2018-04-02 20:12:19 UTC
I'm aligning this to 3.10.0 target release instead of 3.9.z.  Please ping me so we can discuss if you feel strongly this should be addressed in 3.9.z

Initial thoughts are we may need to reassign this to a different component once we've investigated.

Comment 2 Jesus M. Rodriguez 2018-04-25 13:07:19 UTC

*** This bug has been marked as a duplicate of bug 1564979 ***


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