Bug #53522
closed
cephadm: Changing grafana port: `orch ps` is still shows old port
Added by Sebastian Wagner over 2 years ago.
Updated about 2 years ago.
Category:
cephadm/scheduler
Description
Changed grafana port to 1493 with orch apply. ‘orch ls’ shows the new port, but ps doesn’t. ran a reconfig of the grafana service and still the port change is not present in ps or the daemon. regressed the change to 3000 for now.
Related issues
1 (1 open — 0 closed)
- Related to Bug #52041: `orch ps` shows wrong ports for MGR added
- Assignee set to Redouane Kachach Elhichou
I tried to reproduce the issue but couldn't. On a cluster running ceph version 17.0.0-10469-g29e1fc17 (29e1fc1722aa5915b44828a5ad02ec45ce760aa3)
Used the following spec to change grafana port:
service_type: grafana
service_name: grafana
placement:
count: 1
networks:
- 192.168.100.0/24
spec:
port: 4200
> ceph orch apply -i new_grafana_spec.yaml
Results:
[root@ceph-node-0 ~]# cephadm shell ceph orch ls | grep grafana
Inferring fsid f718baf6-c643-11ec-bcba-525400dac7ca
Inferring config /var/lib/ceph/f718baf6-c643-11ec-bcba-525400dac7ca/mon.ceph-node-0/config
Using ceph image with id '7c19d72820af' and tag 'custom-v0.6' created on 2022-04-26 10:36:30 +0000 UTC
registry.hub.docker.com/rkachach/ceph@sha256:ce909f2900b93d4808bf0524e3a985cd284afad8b08b4e2b3bf84b32960138f9
grafana ?:4200 1/1 3m ago 15h count:1
And when running orch ps:
[root@ceph-node-0 ~]# cephadm shell ceph orch ps | grep grafana
Inferring fsid f718baf6-c643-11ec-bcba-525400dac7ca
Inferring config /var/lib/ceph/f718baf6-c643-11ec-bcba-525400dac7ca/mon.ceph-node-0/config
Using ceph image with id '7c19d72820af' and tag 'custom-v0.6' created on 2022-04-26 10:36:30 +0000 UTC
registry.hub.docker.com/rkachach/ceph@sha256:ce909f2900b93d4808bf0524e3a985cd284afad8b08b4e2b3bf84b32960138f9
grafana.ceph-node-0 ceph-node-0 192.168.100.100:4200 running (15h) 4m ago 15h 52.4M - 8.3.5 dad864ee21e9 6a899b535b30
Please, feel free to reopen if you can reproduce the issue using another setup. In that case it would be great if you can put the steps to reproduce the BUG.
- Status changed from New to Closed
Also available in: Atom
PDF