Skip to content

listRouter provides "FAULT" redundantstate for VPC with no instance running #10677

@sbrueseke

Description

@sbrueseke

problem

When all instances are stopped in a VPC with redundant routers the redundantstate will change to FAULT. This is a misleading state, because the routers are still running and working correctly. If you start an instance the routers will change to PRIMARY and BACKUP redundantstate.

versions

The versions of ACS: 4.19.2.0

The steps to reproduce the bug

  1. create a vpc
  2. create networks and instances in this vpc
  3. stop all instances in vpc
  4. use api call listRouters or take aloook at the UI in Infrastructure -> Virtual routers
    ...

What to do about it?

I would not expect FAULT as Redundant state when all instnaces are stopped in a vpc, because this indicates that something is wrong with the it. But this is not the case, after starting at least 1 instance the Redundant state gets back to PRIMARY and BACKUP.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions