Created attachment 1357598 [details] Screenshot of the journal messages Description of problem: Overcloud deployment fails due to the galera cluster problems. Main message: Galera unable to detect last known write sequence number ~ crmd: Result of start operation of galera on ${node} (unknown error) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Delete Stack and redeploy. 2. Error occurs after 1.5h 3. Actual results: Deployment fails as non of the openstack services can be installed properly. Expected results: Deployment succeeds Additional info:
Please provide full sosreports.
Created attachment 1357643 [details] SOSREPORT MYSQL,PACEMAKER,COROSYNC
Created attachment 1357648 [details] output mysqd_save --wsrep-recover
Created attachment 1357662 [details] oc2
Created attachment 1357665 [details] oc0
Created attachment 1357666 [details] oc1
Created attachment 1357678 [details] hosts
we would need the sosreports to be complete via the customer portal (including ps commands, all installed rpms, etc) so that we can pull them into collab-shell and additionally we need to see the full overcloud deploy command as well as all configurations and heat templates used to create the stack. Additionally if we can get a directory listing of all /var/lib/mysql.
Created attachment 1358142 [details] oc2
Created attachment 1358143 [details] oc1
Created attachment 1358144 [details] oc0
Created attachment 1358145 [details] templates in use
Created attachment 1358148 [details] Verification Undercloud Domain Settings domain relevant settings verified on undercloud
Francisco, the last sosreports that you have uploaded lack important files for investigation, they only include galera/gaproxy/cluster logs we need _all_ logs that sosreports can provide, e.g. processes running, network settings etc. Could you get those uploaded?
Hi, please see connected for full sosreports. These only contain, rpm,yum,corosync, pacemaker and system.
Most likely the issue is that the CloudDomain does not match what is configured for the dhcp_domain in nova.conf of the undercloud.
Closing this particular bz as per commant #18 it appears deployment error was due to a misconfiguration.