Skip to content

VR healthchecks fail on VPC with ConfigDrive (rather than VirtualRouter) #12265

@bhouse-nexthop

Description

@bhouse-nexthop

problem

When viewing the healthchecks on a VPC that is using ConfigDrive for address assignment rather than the VirtualRouter, it shows these healthcheck failures:

Image Image

All other health checks are successful.

ConfigDrive has to be used due to RHEL 10 / AlmaLinux 10 / RockyLinux 10 not properly supporting cloud-init via dhcp with CloudStack (think this is due to the use of systemd's built-in dhcp client in these recent releases).

versions

4.22.0

The steps to reproduce the bug

  1. Create VPC using ConfigDrive instead of Virtual Router for address assignment
  2. Create Network Tier
  3. Create VM instance in Network Tier
  4. Observe healthcheck failures in the Virtual Router

What to do about it?

Ignore it?

Metadata

Metadata

Assignees

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions