Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: Operator-0.0.3
Affects Version/s: None
Component/s: MTR Operator
Labels:
None

Blocked:
False
Ready:
False
Epic Link:
Provide an Operator for MTA
Release Note Text:
Undefined
Git Pull Request:
https://github.com/windup/windup-operator/pull/24
Steps to Reproduce:
Hide

in an OCP instance:

create project `mta-1`

install MTA operatora in `mta-1` project

create `Windup` application and wait for it to be ready

create project `mta-2`

install MTA operatora in `mta-2` project

create `Windup` application

check the "mta-*" route created (e.g. "mta-7wm64") in`mta-2` project: the status is "Rejected" with the message "a route in another namespace holds <url> and is older than mta-7wm64"
Show
in an OCP instance: create project `mta-1` install MTA operatora in `mta-1` project create `Windup` application and wait for it to be ready create project `mta-2` install MTA operatora in `mta-2` project create `Windup` application check the "mta-*" route created (e.g. "mta-7wm64") in`mta-2` project: the status is "Rejected" with the message " a route in another namespace holds <url> and is older than mta-7wm64 "
[QE] How to address?:
---
[QE] Why QE missed?:
---
Market:

Sprint:
Sprint 197 AMM, Sprint 198 AMM

Regression:
None

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

I've tried to deploy MTA using the operator twice in 2 different projects in the same OCP instance using the default values and the second instance had the same route's location as the first one.
More details in the "Steps to Reproduce" section.

As a suggestion, worth adding the project name to the location like it happens with the templates to get some unique.