<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Testo normale Carattere";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.TestonormaleCarattere
{mso-style-name:"Testo normale Carattere";
mso-style-priority:99;
mso-style-link:"Testo normale";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="IT" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">Hi,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span lang="EN-US">How to go ahead?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Looking at minion messages I have seen following lines describing the root cause (probably):<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.093353+00:00 susecaas3 etcd[2782]: recognized and used environment variable ETCD_PEER_KEY_FILE=/etc/pki/minion.key<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.093610+00:00 susecaas3 etcd[2782]: recognized and used environment variable ETCD_PEER_TRUSTED_CA_FILE=/etc/pki/trust/anchors/SUSE_CaaSP_CA.crt<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.093866+00:00 susecaas3 etcd[2782]: recognized and used environment variable ETCD_TRUSTED_CA_FILE=/etc/pki/trust/anchors/SUSE_CaaSP_CA.crt<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.094156+00:00 susecaas3 etcd[2782]: recognized environment variable ETCD_NAME, but unused: shadowed by corresponding flag
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.094418+00:00 susecaas3 etcd[2782]: recognized environment variable ETCD_DATA_DIR, but unused: shadowed by corresponding flag
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.094673+00:00 susecaas3 etcd[2782]: recognized environment variable ETCD_LISTEN_CLIENT_URLS, but unused: shadowed by corresponding flag
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.095895+00:00 susecaas3 etcd[2782]: setting maximum number of CPUs to 2, total number of available CPUs is 2<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.096552+00:00 susecaas3 etcd[2782]: the server is already initialized as member before, starting as etcd member...<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.096823+00:00 susecaas3 etcd[2782]: peerTLS: cert = /etc/pki/minion.crt, key = /etc/pki/minion.key, ca = /etc/pki/trust/anchors/SUSE_CaaSP_CA.crt, trusted-ca = /etc/pki/trust/anchors/SUSE_CaaSP_CA.crt,
client-cert-auth = false<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.097083+00:00 susecaas3 etcd[2782]: listening for peers on https://0.0.0.0:2380<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.097390+00:00 susecaas3 etcd[2782]: The scheme of client url http://0.0.0.0:2379 is HTTP while peer key/cert files are presented. Ignored key/cert files.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.097654+00:00 susecaas3 etcd[2782]: listening for client requests on 0.0.0.0:2379<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.098440+00:00 susecaas3 etcd[2782]: resolving susecaas3.localdomain:2380 to 26.2.254.197:2380<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:red">2017-06-08T11:44:34.098868+00:00 susecaas3 etcd[2782]: resolving susecaas3.localdomain:2380 to 26.2.254.197:2380<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:red">2017-06-08T11:44:34.106481+00:00 susecaas3 etcd[2782]: failed to join discovery cluster (discovery: cluster is full)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:red">2017-06-08T11:44:34.106803+00:00 susecaas3 etcd[2782]: discovery token http://26.2.254.195:2379/v2/keys/_etcd/registry/k8s was used, but failed to bootstrap the cluster.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:red">2017-06-08T11:44:34.107112+00:00 susecaas3 etcd[2782]: please generate a new discovery token and try to bootstrap again.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.108189+00:00 susecaas3 systemd[1]: etcd.service: Main process exited, code=exited, status=1/FAILURE<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.109481+00:00 susecaas3 systemd[1]: Failed to start Etcd Server.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.109840+00:00 susecaas3 systemd[1]: etcd.service: Unit entered failed state.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.110114+00:00 susecaas3 systemd[1]: etcd.service: Failed with result 'exit-code'.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.297786+00:00 susecaas3 systemd[1]: etcd.service: Service hold-off time over, scheduling restart.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.298953+00:00 susecaas3 systemd[1]: Stopped Etcd Server.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.299257+00:00 susecaas3 systemd[1]: etcd.service: Start request repeated too quickly.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.299566+00:00 susecaas3 systemd[1]: Failed to start Etcd Server.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.299824+00:00 susecaas3 systemd[1]: etcd.service: Unit entered failed state.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2017-06-08T11:44:34.300173+00:00 susecaas3 systemd[1]: etcd.service: Failed with result 'start-limit'.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">So etcd wan’t to run on the third node. How can I solve issue?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">I must wait latest release or there is something I can do to run Caas ?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Regards<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText">Rosario Pagano<o:p></o:p></p>
<p class="MsoPlainText">Infrastrutture Tecnologiche e Innovazione <o:p></o:p></p>
<p class="MsoPlainText">SISTEMI OPEN<o:p></o:p></p>
<p class="MsoPlainText">ITI.SOP <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Sogei spa <o:p></o:p></p>
<p class="MsoPlainText">Via Mario Carucci, 99 00143 – Roma<o:p></o:p></p>
<p class="MsoPlainText">Tel. +39 0650253400<o:p></o:p></p>
<p class="MsoPlainText">Cell +39 3387970127<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">www.sogei.it <o:p></o:p></p>
<p class="MsoPlainText"> Rispetta l'ambiente. Non stampare questa mail se non è necessario<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><span style="mso-fareast-language:IT">-----Messaggio originale-----<br>
Da: Flavio Castelli [mailto:fcastelli@suse.com] <br>
Inviato: giovedì 8 giugno 2017 13:45<br>
A: PAGANO ROSARIO; caasp-beta@lists.suse.com<br>
Oggetto: Re: [caasp-beta] R: Problem with Caas Platform installation</span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On 06/08/2017 11:18 AM, PAGANO ROSARIO wrote:<o:p></o:p></p>
<p class="MsoPlainText">> for this issue I checked messages and I see lot of lines like following:<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> 017-06-08T09:08:14.486063+00:00 susecaas1 hyperkube[2051]: E0608<o:p></o:p></p>
<p class="MsoPlainText">> 09:08:14.485989 2051 reflector.go:188]<o:p></o:p></p>
<p class="MsoPlainText">> pkg/kubelet/config/apiserver.go:44: Failed to list *api.Pod: Get<o:p></o:p></p>
<p class="MsoPlainText">> <a href="http://127.0.0.1:8080/api/v1/pods?fieldSelector=spec.nodeName%3D127.0.0.1&resourceVersion=0">
<span style="color:windowtext;text-decoration:none">http://127.0.0.1:8080/api/v1/pods?fieldSelector=spec.nodeName%3D127.0.0.1&resourceVersion=0</span></a>:<o:p></o:p></p>
<p class="MsoPlainText">> dial tcp 127.0.0.1:8080: getsockopt: connection refused<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This is a know issue that has been fixed inside of the current development branch of SUSE CaaSP.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The issues you have been describing are probably solved with the next release of the CaaSP platform.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Cheers<o:p></o:p></p>
<p class="MsoPlainText">Flavio<o:p></o:p></p>
</div>
<title></title>
<hr>
<p style="text-align: justify;"><span style="font-size:12px;"><span style="color:#666666;"><span style="font-family:arial,helvetica,sans-serif;"><em>Le informazioni contenute in questo messaggio di posta elettronica sono da considerarsi riservate e confidenziali.
Il loro utilizzo è consentito esclusivamente al destinatario in indirizzo e ne è vietata la diffusione in qualunque modo eseguita, salvo che ne sia data espressa autorizzazione dal mittente. Nel caso in cui il messaggio Le fosse pervenuto per errore, La invitiamo
gentilmente ad eliminarlo in modo permanente dopo averne dato tempestiva comunicazione al mittente e a non utilizzare in alcun caso il suo contenuto. Qualsivoglia utilizzo non autorizzato di questo messaggio e dei suoi eventuali allegati espone il responsabile
alle relative conseguenze civili e penali.</em></span></span></span></p>
<p style="text-align: justify;"><span style="color:#666666;"><span style="font-size:12px;"><span style="font-family:arial,helvetica,sans-serif;"><em>This communication is confidential and the use of the contained information is allowed solely for the intended
recipient. Its disclosure, distribution or copying is prohibited, unless expressly authorized by the sender. If you receive this communication by mistake please notify us and delete the message and its attachments. Anyone responsible for the unauthorized use
of this message and its attachments is liable to face legal consequences.</em></span></span></span></p>
</body>
</html>