Route-map does not exist during bgp restart

VyOS 1.3-rolling-202212102131 on bare metal

The BGP neighbor has v4 & v6 import and export route maps

When I do a “run restart bgp” I get the error:
The route-map ‘Cogent-Ingress’ does not exist.
The route-map ‘Cogent-Egress’ does not exist.
The route-map ‘Cogent-Ingress’ does not exist.
The route-map ‘Cogent-Egress’ does not exist.

If I do a “run restart all” everything restarts fine. Not sure if its a race condition when running a larger route-map that takes longer than expected to load?

vyos@edge-rtr-2# show policy route-map Cogent-Ingress
rule 10 {
action deny
match {
ip {
address {
prefix-list v4-Bogons
}
}
ipv6 {
address {
prefix-list v6-Bogons
}
}
}
}
rule 12 {
action deny
match {
ip {
address {
prefix-list v4_Default_Route
}
}
ipv6 {
address {
prefix-list v6_Default_Route
}
}
}
}
rule 20 {
action deny
match {
ip {
address {
prefix-list v4_Prefixes
}
}
ipv6 {
address {
prefix-list v6_Prefixes
}
}
}
}
rule 100 {
action permit
set {
community none
large-community 174:4000:1000
local-preference 100
metric 5000
}
}

vyos@edge-rtr-2# show policy route-map Cogent-Egress
rule 10 {
action deny
description “Deny Bogons”
match {
ip {
address {
prefix-list v4-Bogons
}
}
ipv6 {
address {
prefix-list v6-Bogons
}
}
}
}
rule 12 {
action deny
description “Deny Default Routes”
match {
ip {
address {
prefix-list v4_Default_Route
}
}
ipv6 {
address {
prefix-list v6_Default_Route
}
}
}
}
rule 20 {
action deny
match {
large-community {
large-community-list Transit-IXP-Routes
}
}
}
rule 100 {
action permit
match {
large-community {
large-community-list Cogent-Prepend-0
}
}
}
rule 101 {
action permit
match {
large-community {
large-community-list Cogent-Prepend-1
}
}
set {
as-path-prepend 12345
}
}
rule 102 {
action permit
match {
large-community {
large-community-list Cogent-Prepend-2
}
}
set {
as-path-prepend “12345 12345”
}
}
rule 103 {
action permit
match {
large-community {
large-community-list Cogent-Prepend-3
}
}
set {
as-path-prepend “12345 12345 12345”
}
}

Any thoughts as to why this is happening or remedies?

Thanks

provide please info from show version

I’ve had this same problem on:

Version:          VyOS 1.3.2
Release train:    equuleus

Built by:         Sentrium S.L.
Built on:         Mon 05 Sep 2022 09:23 UTC
Build UUID:       1ceaab3a-4f4e-4692-b551-7c05e1da0a77
Build commit ID:  7ce86511888635

Architecture:     x86_64
Boot via:         installed image
System type:      KVM guest

Hardware vendor:  Red Hat
Hardware model:   KVM
Hardware S/N:
Hardware UUID:    842ecad3-387e-4143-a1e3-6b5ecad15316

Copyright:        VyOS maintainers and contributors