@jjung seems like the nodes have been messed up between master and worker roles: lab2_worker_worker2 lab2_worker_master3 lab2_master_worker1 lab2_master_master2 lab2_bootstrap_master1 Maybe it's worth setting the roles manually and reinstalling
@jjung in any case you're right that we should consider the node names when automatically assigning roles right now we only do it based on resource considerations
@odepaz regardless of the roles, do we need to update to a different version?
@lgamliel ?
I can redo an installation specifying the roles / server, but the allocation error is not a major issue, as the worker1 (acting as master) and master 3 (acting as worker) that were swapped have exactly the same hardware. So it is not failing because one of the masters is below minimum hardware specs (e.g. worker 2 is only 2 CPUs and 8GB RAM). Also the default allocation on the same hardware with Assisted Install toward 4.6.8 does pick up the right nodes with the right names (but maybe it was just luck?). I'll wait for instructions to keep debugging this install, or to wipe it and redo an install. Let me know.
Hey, sorry I missed your message Can you do 'oc adm must-gather' against the created cluster? If not, it will help having the console operator logs
Hi, Created must-gather.tar.gz Attachement is 139MB: https://1drv.ms/u/s!AoJ0Ren1qyzsgr9lAaMlhK1d57o4hw?e=YygaGL Let me know if you require further information. Regards, JP Jung
we opened this issue : https://bugzilla.redhat.com/show_bug.cgi?id=1926345
*** This bug has been marked as a duplicate of bug 1926345 ***