-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
None
-
False
-
-
-
Hypershift Sprint 258, Hypershift Sprint 261
-
None
Description of problem:
Currently ROSA CAPA is identifying itself as ROSA CLI "PATCH /api/clusters_mgmt/v1/clusters/2ceqm6pbi84revftqus09g8eou8ubt03/node_pools/c59xlkafka-2 HTTP/1.1" 200 - 672 1007 10993 10993 "54.148.10.105,10.128.7.106" "ROSACLI/1.2.36 OCM-SDK/0.1.414" "1de23f66-70e8-4af9-a8af-1c9f3efb722a" "api.openshift.com" "/sockets/api.socket" This should be fixed
Version-Release number of selected component (if applicable):
latest?
How reproducible:
Always
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
User agent is ROSACAPA/Version
Additional info:
This impacts identifying client usage and also bug fixes in newer versions
- is blocked by
-
HOSTEDCP-1967 Migrate CAPA provider to AWS Go SDK v2
- To Do
- relates to
-
HOSTEDCP-1551 [Upstream MVP-3] ROSA implementation for Cluster API
- Closed