Re: first_virtual_router_id not allowed in ingress manifest

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Adam, 
thanks, you saved me from more time spent looking in the dark.
I’ll plan an update. 


R
-- 
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

On 21 Feb 2024, at 16:02, Adam King <adking@xxxxxxxxxx> wrote:

It seems the quincy backport for that feature (https://github.com/ceph/ceph/pull/53098) was merged Oct 1st 2023. According to the quincy part of https://docs.ceph.com/en/latest/releases/#release-timeline it looks like that would mean it would only be present in 17.2.7, but not 17.2.6.

On Wed, Feb 21, 2024 at 8:52 AM Ramon Orrù <ramon.orru@xxxxxxxxxxx> wrote:
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


_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux