I would think you just need to remove the two instances of "{{ v4v6_flag }}" from https://github.com/ceph/ceph/blob/main/src/pybind/mgr/cephadm/templates/serv... and then tell it to use that modified version of the template. As a general thing, it might be safer to start with the template from the release you're on (e.g. https://github.com/ceph/ceph/blob/v18.2.4/src/pybind/mgr/cephadm/templates/s... if you were on 18.2.4) and modify it from there. That should make it much less likely that it references some variable cephadm isn't passing into the template. Alternatively, you could go find out what cephadm is passing the template and just make sure only those things are referenced in the the one you set with the config command. Using 18.2.4 as an example again, you'd want the template to only reference variables being passed in https://github.com/ceph/ceph/blob/v18.2.4/src/pybind/mgr/cephadm/services/in... . On Wed, May 7, 2025 at 2:35 PM Steven Vacaroaia <stef97@gmail.com> wrote:
Hi Adam
Thanks for offering to help
yes, I did a ceph config set using below template as some people reported that it will help solve NFS HA issue ( e.g. haproxy,cfg deployed missing "check")
Now neither NFS nor RGW works :-(
How do I fix this ?
thanks Steven
https://github.com/ceph/ceph/blob/main/src/pybind/mgr/cephadm/templates/serv...
On Wed, 7 May 2025 at 13:50, Adam King <adking@redhat.com> wrote:
That flag got added to cephadm's haproxy template as part of https://github.com/ceph/ceph/pull/61833. I'm very confused as to how you're seeing it affect reef though, as we never backported it. It doesn't seem to exist at all in the reef branch when I checked
adking@fedora:~/orch-ceph/ceph/src$ git checkout main Already on 'main' Your branch is up to date with 'upstream/main'. adking@fedora:~/orch-ceph/ceph/src$ adking@fedora:~/orch-ceph/ceph/src$ (cd pybind/mgr/cephadm/; ack "v4v6") services/ingress.py 207: v4v6_flag = "v4v6" if ip == "[::]" else "" 227: 'v4v6_flag': v4v6_flag,
templates/services/ingress/haproxy.cfg.j2 61: bind {{ ip }}:{{ frontend_port }} ssl crt /var/lib/haproxy/haproxy.pem {{ v4v6_flag }} 63: bind {{ ip }}:{{ frontend_port }} {{ v4v6_flag }}
tests/test_services.py 2940: 'bind [::]:8089 v4v6\n ' adking@fedora:~/orch-ceph/ceph/src$ adking@fedora:~/orch-ceph/ceph/src$ adking@fedora:~/orch-ceph/ceph/src$ git checkout reef M ceph-object-corpus M src/fmt M src/googletest M src/libkmip M src/s3select M src/seastar M src/spawn M src/spdk M src/xxHash Switched to branch 'reef' Your branch is up to date with 'upstream/reef'. adking@fedora:~/orch-ceph/ceph/src$ adking@fedora:~/orch-ceph/ceph/src$ adking@fedora:~/orch-ceph/ceph/src$ (cd pybind/mgr/cephadm/; ack "v4v6") adking@fedora:~/orch-ceph/ceph/src$ adking@fedora:~/orch-ceph/ceph/src$
Are you using some customized reef build or template file for haproxy?
On Wed, May 7, 2025 at 1:33 PM Steven Vacaroaia <stef97@gmail.com> wrote:
Hi,
I am unable to deploy ingress service because "v4v6_flag" is undefined
I couldn't find any information about this flag
The ingress.yaml file used is similar with this one
Any help would be greatly appreciated
Steven
service_type: ingress service_id: rgw placement: hosts: - ceph-node-06.cephlab.com - ceph-node-07.cephlab.com spec: backend_service: rgw.client virtual_ip: 192.168.122.152/24 frontend_port: 80 monitor_port: 1967 use_tcp_mode_over_rgw: True _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io