bumping the post if folks missed it. On Wed, Mar 5, 2025 at 9:25 PM Satish Patel <satish.txt@gmail.com> wrote:
Folks,
I am dealing with a very strange DHCP issue because of the priority of ha_chassis. I have the following ha_chassis group and I want os-chn-gen-comp-001 and os-chn-gen-comp-002 to always service DHCP for sriov interface.
I have used following command to give them high priority
$ ovn-nbctl --no-leader-only set ha_chassis 97077f76-46ae-4e15-9502-24fdb4ad0214 priority=32767 $ ovn-nbctl --no-leader-only set ha_chassis 97077f76-46ae-4e15-9502-24fdb4ad0214 priority=32767
But suddenly today something happened and all priority got reset causing small outage and cause all sriov VM started looking IP address. Solution was I have again set high priority again by hand to fix it.. How do I make priority permanently so it will never reset again.
$ (ovn-nb-db)[root@os-chn-ctrl01 /]# ovn-nbctl --no-leader-only list HA_Chassis 784ec6e9-9af8-45c6-86e0-75ae7ccf9278 7fa04343-4471-4707-b5e9-23bd7f29ca6e 97077f76-46ae-4e15-9502-24fdb4ad0214 c75de7ab-b346-4aa5-886b-31b0fd12401e dd6ce2d4-9746-4429-862a-e78750bb4909 _uuid : 784ec6e9-9af8-45c6-86e0-75ae7ccf9278 chassis_name : os-chn-ctrl03 external_ids : {} priority : 32764
_uuid : 7fa04343-4471-4707-b5e9-23bd7f29ca6e chassis_name : os-chn-gen-comp-001 external_ids : {} priority : 32766
_uuid : 97077f76-46ae-4e15-9502-24fdb4ad0214 chassis_name : os-chn-gen-comp-002 external_ids : {} priority : 32767
_uuid : c75de7ab-b346-4aa5-886b-31b0fd12401e chassis_name : os-chn-ctrl01 external_ids : {} priority : 32765
_uuid : dd6ce2d4-9746-4429-862a-e78750bb4909 chassis_name : os-chn-ctrl02 external_ids : {} priority : 32763