Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 2.14.0 GA
Affects Version/s: 2.12.0 GA
Component/s: 3scale Operator
Labels:

Blocked:
False
Blocked Reason:
None
Ready:
False
3Scale PT Tested upstream:
Not Started
3scale PT Docs:
Not Started
3scale PT Product Specs:
Not Started
3scale PT Product Update Ready:
Not Started
3scale PT Released In Saas:
Not Started
3scale PT Verified Product:
Not Started
Target Release:

2.14.0 GA
Workaround Description:
- Use the 3scale API to define methods and mapping rules instead of using the Operator Capabilities
Git Pull Request:
https://github.com/3scale/3scale-porta-go-client/pull/54, https://github.com/3scale/3scale-operator/pull/809
Steps to Reproduce:
Hide

Use the attached `backend-foobar-sample.yaml` to generate a backend via Operator Capabilities

After the methods have been created, the creation of the mapping rules will fail. This will take a few minutes to reproduce because the methods creation needs to complete before the failure occurs.
Show
Use the attached `backend-foobar-sample.yaml` to generate a backend via Operator Capabilities After the methods have been created, the creation of the mapping rules will fail. This will take a few minutes to reproduce because the methods creation needs to complete before the failure occurs.

SFDC Cases Counter:
SFDC Cases Links:

Description

The 3scale Backend Operator Capability does not allow creating more than 500 methods.

This is normally possible via 3scale API or UI but when attempted via the Operator Capabilities, then the creation of Mapping Rules is compromised: only some (or none) of the Mapping Rules specified in the backend are actually generated.

In the attachments, find the backend specification used to replicate the behaviour and the Operator logs.