Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container Health - no Route matched with those values #13

Open
abbdulwahab86 opened this issue Dec 16, 2024 · 1 comment
Open

Container Health - no Route matched with those values #13

abbdulwahab86 opened this issue Dec 16, 2024 · 1 comment

Comments

@abbdulwahab86
Copy link

Why i am getting message "no Route matched with those values" upon checking Container Health

gspector@gspector-virtual-machine:~/Desktop$ sudo helm list -A
[sudo] password for gspector:
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
kpimon-go ricxapp 1 2024-12-16 13:10:25.848376251 +0500 PKT deployed kpimon-go-2.0.2-alpha 1.0
r4-a1mediator ricplt 1 2024-12-16 09:43:37.932220348 +0500 PKT deployed a1mediator-3.0.0 1.0
r4-alarmmanager ricplt 1 2024-12-16 09:44:11.332107383 +0500 PKT deployed alarmmanager-5.0.0 1.0
r4-appmgr ricplt 1 2024-12-16 09:43:04.059287067 +0500 PKT deployed appmgr-3.0.0 1.0
r4-dbaas ricplt 1 2024-12-16 09:42:55.727908377 +0500 PKT deployed dbaas-2.0.0 1.0
r4-e2mgr ricplt 1 2024-12-16 09:43:20.957666977 +0500 PKT deployed e2mgr-3.0.0 1.0
r4-e2term ricplt 1 2024-12-16 09:43:29.419425958 +0500 PKT deployed e2term-3.0.0 1.0
r4-infrastructure ricplt 1 2024-12-16 09:42:44.848879254 +0500 PKT deployed infrastructure-3.0.0 1.0
r4-o1mediator ricplt 1 2024-12-16 09:44:02.938417568 +0500 PKT deployed o1mediator-3.0.0 1.0
r4-rtmgr ricplt 1 2024-12-16 09:43:12.590182623 +0500 PKT deployed rtmgr-3.0.0 1.0
r4-submgr ricplt 1 2024-12-16 09:43:46.290572902 +0500 PKT deployed submgr-3.0.0 1.0
r4-vespamgr ricplt 1 2024-12-16 09:43:54.630339066 +0500 PKT deployed vespamgr-3.0.0 1.0
gspector@gspector-virtual-machine:~/Desktop$ sudo kubectl get pods -n ricplt
NAME READY STATUS RESTARTS AGE
deployment-ricplt-a1mediator-64fd4bf64-k8mvs 1/1 Running 2 (2m5s ago) 3h35m
deployment-ricplt-alarmmanager-7d47d8f4d4-x8ft4 1/1 Running 1 (3m30s ago) 3h34m
deployment-ricplt-appmgr-79848f94c-7zhfw 1/1 Running 1 (3m30s ago) 3h36m
deployment-ricplt-e2mgr-856f655b4-47drj 1/1 Running 5 (92s ago) 3h35m
deployment-ricplt-e2term-alpha-d5fd5d9c6-wvfnz 1/1 Running 2 (3m30s ago) 3h35m
deployment-ricplt-o1mediator-76c4646878-rs8n8 1/1 Running 1 (3m30s ago) 3h35m
deployment-ricplt-rtmgr-6556c5bc7b-jcml8 1/1 Running 2 (3m30s ago) 3h35m
deployment-ricplt-submgr-66485ccc6c-bm9r9 1/1 Running 2 (2m18s ago) 3h35m
deployment-ricplt-vespamgr-786666549b-f9rjv 1/1 Running 1 (3m30s ago) 3h35m
r4-infrastructure-kong-5986fc7965-fjjtx 2/2 Running 2 (3m30s ago) 3h36m
r4-infrastructure-prometheus-alertmanager-64f9876d6d-tgjxd 2/2 Running 2 (3m30s ago) 3h36m
r4-infrastructure-prometheus-server-bcc8cc897-wshnr 1/1 Running 1 (3m30s ago) 3h36m
statefulset-ricplt-dbaas-server-0 1/1 Running 1 (3m30s ago) 3h36m
gspector@gspector-virtual-machine:~/Desktop$ sudo kubectl get pods -n ricinfra
NAME READY STATUS RESTARTS AGE
deployment-tiller-ricxapp-676dfd8664-jz942 1/1 Running 1 (3m39s ago) 3h36m
tiller-secret-generator-p6mcn 0/1 Completed 0 3h36m
gspector@gspector-virtual-machine:~/Desktop$ curl -v http://localhost:32080/appmgr/ric/v1/health/ready

  • Trying 127.0.0.1:32080...
  • TCP_NODELAY set
  • Connected to localhost (127.0.0.1) port 32080 (#0)

GET /appmgr/ric/v1/health/ready HTTP/1.1
Host: localhost:32080
User-Agent: curl/7.68.0
Accept: /

  • Mark bundle as not supporting multiuse
    < HTTP/1.1 404 Not Found
    < Date: Mon, 16 Dec 2024 08:19:49 GMT
    < Content-Type: application/json; charset=utf-8
    < Connection: keep-alive
    < Content-Length: 103
    < X-Kong-Response-Latency: 0
    < Server: kong/3.6.1
    < X-Kong-Request-Id: 75c3ba660af50a1085f60d3c09651530
    <
    {
    "message":"no Route matched with those values",
    "request_id":"75c3ba660af50a1085f60d3c09651530"
  • Connection #0 to host localhost left intact
    }
    gspector@gspector-virtual-machine:~/Desktop$ curl -v http://192.168.44.129:32080/appmgr/ric/v1/health/ready
  • Trying 192.168.44.129:32080...
  • TCP_NODELAY set
  • Connected to 192.168.44.129 (192.168.44.129) port 32080 (#0)

GET /appmgr/ric/v1/health/ready HTTP/1.1
Host: 192.168.44.129:32080
User-Agent: curl/7.68.0
Accept: /

  • Mark bundle as not supporting multiuse
    < HTTP/1.1 404 Not Found
    < Date: Mon, 16 Dec 2024 08:19:58 GMT
    < Content-Type: application/json; charset=utf-8
    < Connection: keep-alive
    < Content-Length: 103
    < X-Kong-Response-Latency: 0
    < Server: kong/3.6.1
    < X-Kong-Request-Id: 3057e0646b351559ac7be15c07156d14
    <
    {
    "message":"no Route matched with those values",
    "request_id":"3057e0646b351559ac7be15c07156d14"
  • Connection #0 to host 192.168.44.129 left intact
@onehouwong
Copy link
Contributor

Please check similar issues from O-RAN SC or submit a report to them: https://lf-o-ran-sc.atlassian.net/jira/projects?page=1&sortKey=name&sortOrder=ASC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants