OpenShift nodes are always detected as new
Bug #1802323 reported by
Martin André
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Martin André |
Bug Description
During a scale out operation, adding new nodes to a tripleo deployed openshift, the previously provisioned nodes are marked as new while they should not.
Changed in tripleo: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/613637 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=346929d9662 e7168435cc524c8 b9b4d8a68cf988
Committed: https:/
Submitter: Zuul
Branch: master
commit 346929d9662e716 8435cc524c8b9b4 d8a68cf988
Author: Martin André <email address hidden>
Date: Fri Oct 26 18:28:30 2018 +0200
Fix new node detection
For the openshift-node service, the new_node detection was checking for
stdout instead of rc causing it to always tag nodes as new. This commit
fixes it.
Change-Id: I518f386395b515 f59e98877274f4a 0fce52ec4d5
Closes-Bug: #1802323