Bug 1817954 - [ovirt] Workers nodes are not numbered sequentially
Summary: [ovirt] Workers nodes are not numbered sequentially
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.8.0
Assignee: Gal Zaidman
QA Contact: michal
URL:
Whiteboard:
: 1877926 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-27 10:10 UTC by Jan Zmeskal
Modified: 2021-07-27 22:32 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 22:32:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 4723 0 None closed [ovirt]: Removed '0' from machineset name 2021-03-16 11:01:23 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:32:36 UTC

Description Jan Zmeskal 2020-03-27 10:10:52 UTC
Description of problem:
When OCP installer creates master nodes, they are numbered from 0 onwards. Example (six is name of my OCP cluster):
six-rz59f-master-0
six-rz59f-master-1
six-rz59f-master-2

However, worker nodes created by the installer have all number 0 suffixed:
six-rz59f-worker-0-4tvgb
six-rz59f-worker-0-mcjx7

I understand this is because of the Machine Set whose name is "six-rz59f-worker-0" and the individual worker nodes are just variations of this Machine Set's name. However, it would be better if we could achieve the same sequential numbering that we have with masters. And if not, then I suggest to remove number 0 from the default worker Machine Set altogether, because that number does not give any valuable information and is only confusing since it *looks like* the nodes are supposed to be ordered, but actually they aren't.


Version-Release number of the following components:
openshift-install-linux-4.4.0-0.nightly-2020-03-26-041820

How reproducible:
100 %

Steps to Reproduce:
1. Run openshift-install

Actual results:
./oc get no
NAME                       STATUS   ROLES    AGE   VERSION
six-rz59f-master-0         Ready    master   20h   v1.17.1
six-rz59f-master-1         Ready    master   20h   v1.17.1
six-rz59f-master-2         Ready    master   20h   v1.17.1
six-rz59f-worker-0-4tvgb   Ready    worker   20h   v1.17.1
six-rz59f-worker-0-mcjx7   Ready    worker   20h   v1.17.1

Expected results:
Worker nodes should either be numbered sequentially or the number should be removed from Machine Set name

Comment 2 Gal Zaidman 2020-06-17 16:23:11 UTC
due to capacity constraints we will be revisiting this bug in the upcoming sprint

Comment 3 Douglas Schilling Landgraf 2020-07-09 12:16:28 UTC
due to capacity constraints we will be revisiting this bug in the upcoming sprint

Comment 4 Sandro Bonazzola 2020-09-14 09:40:45 UTC
same as comment #3 and comment #2

Comment 5 Sandro Bonazzola 2020-09-14 09:41:55 UTC
*** Bug 1877926 has been marked as a duplicate of this bug. ***

Comment 6 Sandro Bonazzola 2020-10-22 11:30:26 UTC
due to capacity constraints we will be revisiting this bug in the upcoming sprint

Comment 7 Sandro Bonazzola 2020-12-03 12:24:14 UTC
nice to have, low priority. Workers doesn't really need to be numbered.

Comment 8 Gal Zaidman 2021-01-27 09:20:18 UTC
due to capacity constraints we will be revisiting this bug in the upcoming sprint

Comment 9 Janos Bonic 2021-03-09 12:10:57 UTC
Fixed: https://github.com/openshift/installer/pull/4723

Comment 10 michal 2021-03-24 16:59:58 UTC
rhv: 4.4.5.10

ocp: 4.8.0-0.nightly-2021-03-22-104536


look on Workers name and they are without 0 at the end

Comment 13 errata-xmlrpc 2021-07-27 22:32:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2438


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