<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1254">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">Hi all,</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">I found a workaround and like to share my solution but I don't know if it is working for all having the same issue:<br>
<br>
Start by "skuba node join --v 9 --role worker --target $HOSTNAME $HOSTNAME"<br>
<br>
Updating the whole cluster (still in beta status) did not work for me.<br>
<br>
There is a hint in the kubeadm forums that the join token for kubeadm get's invalid after 24h<br>
In this rare case you can just hop to you first kubernetes master and type:<br>
kubeadm token create --print-join-command<br>
</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Copy that string and run it on the destination worker node to join the cluster.<br>
After that "kubectl get nodes" will may show that node as "Not Ready" but as member of the cluster.<br>
Follow the Suse upgrade node documentation for CaaS and the node will be shown as "Ready".</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Regards<br>
<br>
Roy<br>
<br>
<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Von:</b> Carsten Duch <carsten.duch@suse.com><br>
<b>Gesendet:</b> Freitag, 19. Juli 2019 12:06:22<br>
<b>An:</b> caasp-beta@lists.suse.com <caasp-beta@lists.suse.com><br>
<b>Betreff:</b> Problem adding additional node to cluster after 24h</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
span.x_E-MailFormatvorlage17
{font-family:"Calibri",sans-serif;
color:windowtext}
p.x_xxxmsonormal, li.x_xxxmsonormal, div.x_xxxmsonormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
.x_MsoChpDefault
{font-family:"Calibri",sans-serif}
@page WordSection1
{margin:70.85pt 70.85pt 2.0cm 70.85pt}
div.x_WordSection1
{}
-->
</style>
<div lang="DE" link="#0563C1" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">Hi all,</p>
<p class="x_MsoNormal">I recently installed CaaSP 4 with a customer.</p>
<p class="x_MsoNormal">We tried to add another worker node after >24h to the cluster.</p>
<p class="x_MsoNormal">But skuba failed to deploy the node.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">After we found out how to set debug level in skuba, we found out that this might be related to an existing issue on github:</p>
<p class="x_MsoNormal"><span style="font-size:12.0pt; color:black"><a href="https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkubernetes%2Fkubeadm%2Fissues%2F1310&data=02%7C01%7C%7Cf35ab2ace10849095da408d70c30cab0%7Cf481d56fc63d4d748406d64e74f44395%7C0%7C0%7C636991276021929597&sdata=VWFwk0CVI%2B%2BcmLFiCanCFjUCYDa%2BcztprTLg1hVemsU%3D&reserved=0" originalsrc="https://github.com/kubernetes/kubeadm/issues/1310" shash="l3E8uK4Ow6VXcCqLVj0ELgxSmQ1L8PrNS0tfwxSwBRIkxqtcICAeUDCP1JvlIMokv7/IrI9vnd3LuokYXemjkAhJrZFY9VoJrLhFQqjd8qBIPiH5PQiryILR/LXGjzhy781Zdy2p1KU0ZqODCVcMgq5bPkSMUPzpaGcGOuQo/FQ=">https://github.com/kubernetes/kubeadm/issues/1310</a></span></p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">This is the debug output we got:</p>
<p class="x_xxxmsonormal"><span lang="EN-US" style="color:black">I0718 19:19:52.762272 12629 ssh.go:190] stdout | [preflight] Running pre-flight checks</span><span style="color:black"></span></p>
<p class="x_xxxmsonormal"><span lang="EN-US" style="color:black">I0718 19:19:52.889960 12629 ssh.go:190] stdout | [preflight] Reading configuration from the cluster...</span><span style="color:black"></span></p>
<p class="x_xxxmsonormal"><span lang="EN-US" style="color:black">I0718 19:19:52.890010 12629 ssh.go:190] stdout | [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'</span><span style="color:black"></span></p>
<p class="x_xxxmsonormal"><span lang="EN-US" style="color:black">I0718 19:19:53.043975 12629 ssh.go:190] stdout | [kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.15" ConfigMap in the kube-system namespace</span><span style="color:black"></span></p>
<p class="x_xxxmsonormal"><span lang="EN-US" style="color:black">I0718 19:19:53.372300 12629 ssh.go:190] stderr | error execution phase kubelet-start: configmaps "kubelet-config-1.15" is forbidden: User "system:bootstrap:pwupeo" cannot get resource "configmaps"
in API group "" in the namespace "kube-system"</span><span style="color:black"></span></p>
<p class="x_xxxmsonormal"><span lang="EN-US" style="color:black">I0718 19:19:53.373248 12629 ssh.go:167] running command: "rm /tmp/kubeadm-init.conf"</span><span style="color:black"></span></p>
<p class="x_xxxmsonormal"><span lang="EN-US" style="color:black">[join] failed to apply join to node failed to apply state kubeadm.join: Process exited with status 1</span><span style="color:black"></span></p>
<p class="x_xxxmsonormal"><span lang="EN-US" style="color:black">F0718 19:19:53.402383 12629 join.go:49] error joining node s030v0302: failed to apply state kubeadm.join: Process exited with status 1</span><span style="color:black"></span></p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Is this a bug in skuba? Looks like it’s required to reissue a token for kubeadm after 24h, I am unsure if skuba does this automatically or not.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span style="">Mit freundlichem Gruß / Best regards</span></p>
<p class="x_MsoNormal"><span style=""> </span></p>
<p class="x_MsoNormal">Carsten Duch</p>
<p class="x_MsoNormal">Sales Engineer</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">SUSE Software Solutions Germany GmbH</p>
<p class="x_MsoNormal">Maxfeldstr. 5</p>
<p class="x_MsoNormal">90409 Nürnberg</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">(P)+49 173 5876 707</p>
<p class="x_MsoNormal"><a href="mailto:carsten.duch@suse.com"><span style="color:#0563C1">carsten.duch@suse.com</span></a></p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">--</p>
<p class="x_MsoNormal">SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)</p>
<p class="x_MsoNormal"> </p>
</div>
</div>
---------------------------------------------------------------- <br>
innogy SE<br>
Vorsitzender des Aufsichtsrates: Dr. Erhard Schipporeit<br>
Vorstand: Uwe Tigges (Vorsitzender), Dr. Hans Buenting,<br>
Dr. Bernhard Guenther, Arno Hahn, Martin Herrmann, Hildegard Mueller<br>
Sitz der Gesellschaft: Essen, Eingetragen beim Amtsgericht Essen, <br>
Handelsregister-Nr. HRB 27091, USt-IdNr. DE304171711
</body>
</html>