Failed to add static route.

[olegivanovicholegivanovich-ux]

Hello,

We are using CloudStack version 4.22 with Router version 4.22.0 and have encountered an issue when creating static routes within a VPC.

When selecting a specific Private Gateway, we are able to specify a static route with only one parameter — the Destination Network CIDR. However, when attempting to create the route, we receive an error.

Could you please assist us in troubleshooting this issue?

Thank you in advance for your support.

Managemen-server.log

[weizhouapache]

@olegivanovicholegivanovich-ux
can you share the content of /etc/cloudstack/staticroutes.json ?

[weizhouapache]

"172.16.20.0/24": {
"gateway": "192.168.128.100",
"network": "172.16.20.0/24",
"revoke": false
},

@olegivanovicholegivanovich-ux
I think the issue is caused by this which misses "ip_address" ?
can you share more information of this static route ?

[weizhouapache]

I see, it is a static route with next hop
strange, the ip address is missing in the json file
I am able to reproduce the issue

[weizhouapache]

@olegivanovicholegivanovich-ux
it has been fixed by #11967
can you apply the changes in the VPC VR ?

[olegivanovicholegivanovich-ux]

We updated CloudStack to version 4.22 from the repository using "dnf update cloudstack-management" on December 5th. However, the bugfix was applied on December 16th and was not released as a separate branch.

As a result, both our version and yours are labeled 4.22.0, but they are effectively different. Because of this, the package manager does not recognize any available updates.

Could you please advise on how we should proceed in this situation?

[olegivanovicholegivanovich-ux]

We were able to resolve the issue by editing the staticroutes.json file and removing entries that were missing the ip_address field.

This allowed us to manage Static Routes within the Private Gateway. However, inside the VPC, when multiple Private Gateways are present, this functionality does not work — it requires a next hop, but fails when one is provided.

[weizhouapache]

@olegivanovicholegivanovich-ux
#11967 is not included in 4.22.0.0, it will be included in 4.22.1.0
as a workaround, you can refer to #11967 (comment)

[olegivanovicholegivanovich-ux]

Please clarify when we can expect the 4.22.1 release?
We would like to update the entire system at once.

[weizhouapache]

ease clarify when we can expect the 4.22.1 release?
We would like to update the entire system at once.

@olegivanovicholegivanovich-ux
you can find the update at : https://lists.apache.org/thread/d0dnd6rb1hvd633hfncb60tj6h4vk0f6

[olegivanovicholegivanovich-ux]

Got it, thank you!