Bug 1857004 - Scale down of unreachable nodes unsuccessful
Summary: Scale down of unreachable nodes unsuccessful
Keywords:
Status: CLOSED DUPLICATE of bug 1857365
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-14 22:36 UTC by Sai Sindhur Malleni
Modified: 2020-07-17 14:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-17 14:00:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sai Sindhur Malleni 2020-07-14 22:36:57 UTC
Description of problem:
When we are trying to delete nodes that are unreachable using openstack overcloud delete command, it is failing. This is even after incorporating the patches mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1843721 (https://review.opendev.org/#/c/723382/) as well as https://github.com/openstack/tripleo-heat-templates/commit/5843a7667c93ded7c7ed3e59d408ddd5ca4876fd#diff-fdfa9108b5c67b2c4ce1dae2a05ec0c2R1175.

The problem is the resulting scale_playbook.yaml generated has scale_ignore_unreachable argument as a parameter for the play

- hosts: overcloud
  name: Scaling
  # NOTE(cloudnull): This is set to true explicitly so that we have up-to-date facts
  #                  on all overcloud when performing a scaling operation.
  #                  Without up-to-date facts, we're creating a potential failure
  #                  scenario.
  gather_facts: true
  scale_ignore_unreachable: true
  become: false



Version-Release number of selected component (if applicable):
16.1

How reproducible:
100%

Steps to Reproduce:
1. Delete an unreachable node using openstack overcloud node delete
2.
3.

Actual results:
Scale down fails

Expected results:
Scale down should succeed

Additional info:

Comment 1 Alex Schultz 2020-07-17 14:00:16 UTC
This was caused by an invalid patch. We are tracking fixing the unreachable nodes via Bug 1857365 for inclusion into 16.1.1

*** This bug has been marked as a duplicate of bug 1857365 ***


Note You need to log in before you can comment on or make changes to this bug.