Skip to content

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

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

Description

@ioggstream
ioggstream
opened on Jul 11, 2017

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

Activity

  1. ioggstream
    added a commit that references this issue on Jul 11, 2017

    fix redhat-openstack#370: run deployment_bastion_node_cleanup only on…

    825021d
  2. ioggstream
    added a commit that references this issue on Aug 11, 2017

    fix redhat-openstack#370: run deployment_bastion_node_cleanup only on…

    88d0dbf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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