Skip to content

replacing a failed infra causes the new one to be unregistered #370

@ioggstream

Description

@ioggstream

Reproduce

  • I have 2 infra nodes
infra-0
infra-1
  • infra-1 fails, I mark it unhealty and update the stack
o stack resource mark unhealthy  shift...infra... 1
o stack update shift --existing
  • a new infra-1 is created
  • the old infra-1 is removed

I expect

  • deployment-bastion-node-cleanup to be run against the old node, if present

Instead

  • deployment-bastion-node-cleanup references infra-1 by hostname, so it will unregister the new node

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions