MySQL Bugs: #89629: After a complete crash of innoDB cluster, I can reboot the cluster

Bug #89629	After a complete crash of innoDB cluster, I can reboot the cluster
Submitted:	12 Feb 2018 15:28	Modified:	19 Mar 2018 9:10
Reporter:	Sibel Kamer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.7	OS:	Red Hat
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
Hi,

Last weekend, we upgraded our DB server to 5.7 and created a 3 node cluster. As we had to hand over the DB back, the 2 nodes were not successfully added to the cluster. Today, we had serious issues about some variable issues and had to restart the mysqld. That obviously caused the cluster crash and now I cant bring it online. 

mysql-js>  shell.connect('cladm@dbcl1:3306');
Please provide the password for 'cladm@dbcl1:3306':
Creating a Session to 'cladm@dbcl1:3306'
Your MySQL connection id is 131710
No default schema selected; type \use <schema> to set one.
mysql-js> var cluster = dba.getCluster('mycl');
Dba.getCluster: This function is not available through a session to a standalone instance (RuntimeError)
mysql-js> cluster.status();
TypeError: Cannot read property 'status' of undefined
mysql-js>  var cluster = dba.rebootClusterFromCompleteOutage('mycl');
Reconfiguring the cluster 'mycl' from complete outage...
Dba.rebootClusterFromCompleteOutage: The cluster's instance 'dbcl3:3306' belongs to an unmanaged GR group.  (RuntimeError)

How to repeat:
Run the commands above

the commands provided run on host dbcl1, and the error comes from dbcl3 which wasnt even added properly-gad errors-

Hi,
From what version you upgraded?
Can you show us your config files on all three servers?
Were you running mysql_upgrade after the upgrade

all best
Bogdan

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".