Can't create IPV6 addresses for virtual server destination
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- backend, networking
Research direction
Start by tracing how the virtualServers destination and mask are translated into the BIG-IP virtual-server request, then reproduce the configuration shown in the issue with an IPv6 destination. Done means an IPv6 destination can be created successfully while existing IPv4 virtual-server configurations continue to work.
Written by the indexing model from the issue text.
Description
The following error is reported if a IPV6 address is used for the destination field of the virtual server:
[2017-12-01 15:13:58,008 f5_cccl.resource.resource ERROR] HTTP error(400): CCCL resource(ApiVirtualServer) /Part-2/default_test-svc-43-map.
[2017-12-01 15:13:58,008 f5_cccl.service.manager ERROR] F5CcclResourceRequestError - 400 Unexpected Error: Bad Request for uri: https://10.190.24.209:443/mgmt/tm/ltm/virtual/~Part-2~default_test-svc-43-map/
Text: u'{"code":400,"message":"0107028f:3: The destination (1::%2) address and mask (255.255.255.255) for virtual server (/Part-2/default_test-svc-43-map) must be be the same type (IPv4 or IPv6).","errorStack":[],"apiError":3}'
[2017-12-01 15:13:58,008 f5_cccl.service.manager ERROR] Resource /Part-2/default_test-svc-43-map update error, requeuing task...
The configuration that was used (for the k8s-bigip-ctlr) was the following:
{
...
"resources": {
"Part-2": {
"virtualServers": [
{
"name": "default_test-svc-43-map",
"destination": "/Part-2/1::.80",
"source": "::/0",
"enabled": true,
"ipProtocol": "tcp"
}
]
}
}
}
- Dominant language
- Python
- Stars
- 13
- Forks
- 48
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
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 1-3 hours Newbie friendliness 66/100
AlexsLemonade/scpca-docs#518 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 95/100
rocketride-org/rocketride-server#2705 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#786 ·
Maintainers usually reply within 1 day
-
prototype(verifier_token): map disallowed warning to contraindicated before composite precedence checkPossibly taken @drk-ram claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentrust-io/trace-spec#582 ·
Maintainers usually reply within 1 day
-
area:cli priority:low refactor size:small
Difficulty 1/5 Under an hour Newbie friendliness 88/100
RonaldHensbergen/composable-data-stack#906 ·
Maintainers usually reply within 1 day