* Added a check to striker-initialize-host the see if anvil-X RPM is already installed. If so, it will not install the Alteeve repo, even if it's not found.
Signed-off-by: Digimer <digimer@alteeve.ca>
<keyname="job_0106">Cluster hasn't started, calling local start.</key>
<keyname="job_0106">Cluster hasn't started, calling local start.</key>
<keyname="job_0107">Corosync is not yet configured, waiting. It will be created when node 1 initializes the cluster.</key>
<keyname="job_0107">Corosync is not yet configured, waiting. It will be created when node 1 initializes the cluster.</key>
<keyname="job_0108">Corosync is configured. Will wait for the cluster to start. If it hasn't started in two minutes, we'll try to join it.</key>
<keyname="job_0108">Corosync is configured. Will wait for the cluster to start. If it hasn't started in two minutes, we'll try to join it.</key>
@ -730,6 +730,7 @@ It should be provisioned in the next minute or two.</key>
<keyname="job_0269">One or more machines are not yet accessible on the first BCN. Will check again in a moment.</key>
<keyname="job_0269">One or more machines are not yet accessible on the first BCN. Will check again in a moment.</key>
<keyname="job_0270">All machines are now available on the first BCN!</key>
<keyname="job_0270">All machines are now available on the first BCN!</key>
<keyname="job_0271">One of the Striker dashboards has not yet updated network information in the database. We need this to know which IP to tell the peer to use to connect to us. We'll wait a moment and check again.</key>
<keyname="job_0271">One of the Striker dashboards has not yet updated network information in the database. We need this to know which IP to tell the peer to use to connect to us. We'll wait a moment and check again.</key>
<keyname="job_0272">The cluster still hasn't started. Calling startup again (will try once per minute).</key>
<keyname="warning_0075">[ Warning ] - We were asked to insert or update a host with the name: [#!variable!host_name!#]. Another host: [#!variable!host_uuid!#] has the same name, which could be a failed node that is being replaced. We're going to set it's 'host_key' to 'DELETED'. If this warning is logged only once, and after a machine is replaced, it's safe to ignore. If this warning is repeatedly being logged, then there are two active machines with the same host name, and that needs to be fixed.</key>
<keyname="warning_0075">[ Warning ] - We were asked to insert or update a host with the name: [#!variable!host_name!#]. Another host: [#!variable!host_uuid!#] has the same name, which could be a failed node that is being replaced. We're going to set it's 'host_key' to 'DELETED'. If this warning is logged only once, and after a machine is replaced, it's safe to ignore. If this warning is repeatedly being logged, then there are two active machines with the same host name, and that needs to be fixed.</key>
<keyname="warning_0076">[ Warning ] - It looks like the postfix daemon is not running. Enabling and starting it now.</key>
<keyname="warning_0076">[ Warning ] - It looks like the postfix daemon is not running. Enabling and starting it now.</key>
<keyname="warning_0077">[ Warning ] - Checking the mail queue after attempting to start postgres appears to have still failed. Output received was: [#!variable!output!#].</key>
<keyname="warning_0077">[ Warning ] - Checking the mail queue after attempting to start postgres appears to have still failed. Output received was: [#!variable!output!#].</key>
<keyname="warning_0078">[ Warning ] - Not installing the Alteeve repo! The package: [#!variable!anvil_role_rpm!#] is already installed. This is OK, but be aware that updates from Alteeve will not be available. To change this, please install: [#!variable!alteeve_repo!#].</key>
<!-- The entries below here are not sequential, but use a key to find the entry. -->
<!-- The entries below here are not sequential, but use a key to find the entry. -->
<!-- Run 'striker-parse-os-list to find new entries. -->
<!-- Run 'striker-parse-os-list to find new entries. -->