Whitelist feature can fail after pools are whitelisted post CCCL creation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the whitelist-after-CCCL-creation scenario: create a Route, whitelist a pool, add /Common/http as a health monitor, then delete the Route. Start with the IcrPool restoration path and the logged invalid session value, and confirm that deleting the Route restores the pool without the reported 400 error.
Written by the indexing model from the issue text.
Description
JIRA won’t let me post comments, so I’ll just send it to you directly.
Based on feedback from ad-hoc testing:
I create a Route and let the controller create all the resources. I then whitelist a pool. If I try to add a pre-existing health monitor to the pool (/Common/http for example), the controller deletes the monitor off of the pool. I then delete the Route, the controller attempts to “restore” the pool back to its original state, and I get this error:
2018/04/09 17:23:39 [ERROR] [2018-04-09 17:23:39,307 f5_cccl.resource.resource ERROR] HTTP error(400): CCCL resource(IcrPool) /test/openshift_default_svc-1.
2018/04/09 17:23:39 [ERROR] [2018-04-09 17:23:39,307 f5_cccl.service.manager ERROR] F5CcclResourceRequestError - 400 Unexpected Error: Bad Request for uri: https://172.16.2.8:443/mgmt/tm/ltm/pool/~test~openshift_default_svc-1/
2018/04/09 17:23:39 [INFO] Text: u'{"code":400,"message":"invalid property value \\"session\\":\\"monitor-enabled\\"","errorStack":[],"apiError":26214401}'```
- Dominant language
- Python
- Stars
- 13
- Forks
- 48
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from f5devcentral/f5-cccl
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
f5devcentral/f5-cccl#250 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
f5devcentral/f5-cccl#248 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
f5devcentral/f5-cccl#247 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
f5devcentral/f5-cccl#246 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
f5devcentral/f5-cccl#245 ·
All issues in f5devcentral/f5-cccl
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
MIT-LCP/wfdb-python#590 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
pollen-robotics/reachy_mini#1517 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
NRLMMD-GEOIPS/pluginify#41 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
scverse/spatialdata#1293 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
UKGovernmentBEIS/inspect_evals#2788 ·
Maintainers usually reply within 1 day