Hello, I deployed RGW and NFSGW services over a ceph (version 17.2.6) cluster. Both services are being accessed using 2 (separated) ingresses, actually working as expected when contacted by clients. Besides, I’m experiencing some problem while letting the ingresses work on the same cluster.
keepalived logs are full of "(VI_0) received an invalid passwd!” lines,
because both ingresses are using the same virtualrouter id, so I’m trying to
introduce some additional parameter in service definition manifests to
workaround the problem (first_virtual_router_id, default value is 50), below
are the manifest content:
service_type: ingress
service_id: ingress.rgw
service_name: ingress.rgw
placement:
hosts:
- c00.domain.org
- c01.domain.org
- c02.domain.org
spec:
backend_service: rgw.rgw
frontend_port: 8080
monitor_port: 1967
virtual_ips_list:
- X.X.X.200/24
first_virtual_router_id: 60
service_type: ingress
service_id: nfs.nfsgw
service_name: ingress.nfs.nfsgw
placement:
count: 2
spec:
backend_service: nfs.nfsgw
frontend_port: 2049
monitor_port: 9049
virtual_ip: X.X.X.222/24
first_virtual_router_id: 70
When I apply the manifests I’m getting the error, for both ingress definitions:
Error EINVAL: ServiceSpec: __init__() got an unexpected keyword argument
‘first_virtual_router_id'
even the documentation for quincy version describes the option and includes
some similar example at: https://docs.ceph.com/en/quincy/cephadm/services/rgw
Both manifests are working smoothly if I remove the first_virtual_router_id
line.
Any ideas on how I can troubleshoot the issue?
Thanks in advance
Ramon
--
Ramon Orrù
Servizio di Calcolo
Laboratori Nazionali di Frascati
Istituto Nazionale di Fisica Nucleare
Via E. Fermi, 54 - 00044 Frascati (RM) Italy
Tel. +39 06 9403 2345
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
