From egov-devops at akdb.de Mon Jul 1 23:23:19 2019 From: egov-devops at akdb.de (egov-devops) Date: Tue, 2 Jul 2019 05:23:19 +0000 Subject: [caasp-beta] Problem: Manifest Error with registry.suse.com/caasp/v4/kured:v1.2.0 Message-ID: Hi everyone, anybody noticed this problem, too? -registry.suse.com/caasp/v4/kured:v1.2.0 FATA[0000] Error determining manifest MIME type for docker://registry.suse.com/caasp/v4/kured:v1.2.0: Error reading manifest v1.2.0 in registry.suse.com/caasp/v4/kured: manifest unknown: manifest unknown I'm trying to download the images for a CAASP 4 Beta install, as described in the Handbook: CaaSP-CAP-POC-Setup-Guide.pdf Mit freundlichen Gr??en Alexander Schie?l DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 Alexander.Schiessl at akdb.de egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmeister at suse.de Tue Jul 2 05:52:35 2019 From: mmeister at suse.de (Maximilian Meister) Date: Tue, 2 Jul 2019 13:52:35 +0200 Subject: [caasp-beta] Problem: Manifest Error with registry.suse.com/caasp/v4/kured:v1.2.0 In-Reply-To: References: Message-ID: <91b12a68-c03e-b127-2ced-53fec4be012e@suse.de> Hi Alexander, the kured image is tagged without the "v" in registry.suse.com ``` $ reg ls registry.suse.com | grep kured INFO[0000] domain: registry.suse.com INFO[0000] server address: registry.suse.com caasp/v4/kured?????????????????????????? 1.2.0, 1.2.0-rev1, 1.2.0-rev1-build1.9, 1.2.0-rev1-build2.2.4, 1.2.0-rev1-build2.2.7, 1.2.0-rev1-build2.2.8, beta ``` So I think the reference is wrong here, can you double check? Thanks Max On 7/2/19 7:23 AM, egov-devops wrote: > > Hi everyone, > > anybody noticed this problem, too? > > -registry.suse.com/caasp/v4/kured:v1.2.0 > > FATA[0000] Error determining manifest MIME type for > docker://registry.suse.com/caasp/v4/kured:v1.2.0: Error reading > manifest v1.2.0 in registry.suse.com/caasp/v4/kured: manifest unknown: > manifest unknown > > I?m trying to download the images for a CAASP 4 Beta install, as > described in the Handbook: CaaSP-CAP-POC-Setup-Guide.pdf > > Mit freundlichen Gr??en > > Alexander Schie?l > > DevOps > > Gesch?ftsfeld eGovernment > > Telefon +49 800 2553222-65 > > Alexander.Schiessl at akdb.de > > egov-devops at adkb.de > > __________________________________________________________ > > AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung > > Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta -- Maximilian Meister ----------------------------------------------------------------------- Software Engineer (Container Technologies) SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: mmeister at suse.de ----------------------------------------------------------------------- GF: Felix Imend?rffer, Mary Higgins, Sri Rasiah HRB 21284 (AG N?rnberg) -------------- next part -------------- An HTML attachment was scrubbed... URL: From egov-devops at akdb.de Tue Jul 2 23:22:48 2019 From: egov-devops at akdb.de (egov-devops) Date: Wed, 3 Jul 2019 05:22:48 +0000 Subject: [caasp-beta] Problem: Manifest Error with registry.suse.com/caasp/v4/kured:v1.2.0 Message-ID: <9f16078a50b9480a995d6eaeb0362ac8@akdb.de> Hi everyone, anybody noticed this problem, too? -registry.suse.com/caasp/v4/kured:v1.2.0 FATA[0000] Error determining manifest MIME type for docker://registry.suse.com/caasp/v4/kured:v1.2.0: Error reading manifest v1.2.0 in registry.suse.com/caasp/v4/kured: manifest unknown: manifest unknown I'm trying to download the images for a CAASP 4 Beta install, as described in the Handbook: CaaSP-CAP-POC-Setup-Guide.pdf Mit freundlichen Gr??en Alexander Schie?l DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 Alexander.Schiessl at akdb.de egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From jean-marc.lambert at suse.com Wed Jul 3 00:52:11 2019 From: jean-marc.lambert at suse.com (Jean Marc Lambert) Date: Wed, 3 Jul 2019 06:52:11 +0000 Subject: [caasp-beta] Problem: Manifest Error with registry.suse.com/caasp/v4/kured:v1.2.0 In-Reply-To: <9f16078a50b9480a995d6eaeb0362ac8@akdb.de> References: <9f16078a50b9480a995d6eaeb0362ac8@akdb.de> Message-ID: <21754305-98f4-42fb-b425-83ed2d81efe2@email.android.com> I see that the doc is for CAP ? If that is the case I expect it not ready yet for caasp4. As crio is not yet supported. Jmarc Le 3 juil. 2019 07:12, egov-devops a ?crit : Hi everyone, anybody noticed this problem, too? -registry.suse.com/caasp/v4/kured:v1.2.0 FATA[0000] Error determining manifest MIME type for docker://registry.suse.com/caasp/v4/kured:v1.2.0: Error reading manifest v1.2.0 in registry.suse.com/caasp/v4/kured: manifest unknown: manifest unknown I?m trying to download the images for a CAASP 4 Beta install, as described in the Handbook: CaaSP-CAP-POC-Setup-Guide.pdf Mit freundlichen Gr??en Alexander Schie?l DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 Alexander.Schiessl at akdb.de egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGonin at suse.com Wed Jul 3 04:08:04 2019 From: PGonin at suse.com (Paul Gonin) Date: Wed, 3 Jul 2019 10:08:04 +0000 Subject: [caasp-beta] Problem: Manifest Error with registry.suse.com/caasp/v4/kured:v1.2.0 In-Reply-To: <9f16078a50b9480a995d6eaeb0362ac8@akdb.de> References: <9f16078a50b9480a995d6eaeb0362ac8@akdb.de> Message-ID: <48a7cf12541b1494ec82c1d0179da1eea54a00a6.camel@suse.com> Hi Alexander, Le mercredi 03 juillet 2019 ? 05:22 +0000, egov-devops a ?crit : Hi everyone, anybody noticed this problem, too? -registry.suse.com/caasp/v4/kured:v1.2.0 FATA[0000] Error determining manifest MIME type for docker://registry.suse.com/caasp/v4/kured:v1.2.0: Error reading manifest v1.2.0 in registry.suse.com/caasp/v4/kured: manifest unknown: manifest unknown We have not looked into image mirroring much with CaaSP4. We will give a try and reproduce to check what is happening. I?m trying to download the images for a CAASP 4 Beta install, as described in the Handbook: CaaSP-CAP-POC-Setup-Guide.pdf Mit freundlichen Gr??en rgds Paul Alexander Schie?l DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 Alexander.Schiessl at akdb.de egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Sun Jul 7 14:54:42 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Sun, 7 Jul 2019 20:54:42 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <86CAF87B-E67D-4FDE-966B-FD3E0FBF0C53@suse.com> References: <8596D447-C4E6-4BF7-B57D-BB38299854DC@sap.com> <93EB0ACC-1D0C-4718-9C1C-F9D707836C1E@sap.com> <86CAF87B-E67D-4FDE-966B-FD3E0FBF0C53@suse.com> Message-ID: <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Sun Jul 7 15:10:17 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Sun, 7 Jul 2019 21:10:17 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> References: <8596D447-C4E6-4BF7-B57D-BB38299854DC@sap.com> <93EB0ACC-1D0C-4718-9C1C-F9D707836C1E@sap.com> <86CAF87B-E67D-4FDE-966B-FD3E0FBF0C53@suse.com> <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> Message-ID: <4694144B-47A4-4627-92B2-D037BD24E7F0@sap.com> Sorry I sent a wrong log. Here is the error about skuba-update-start. ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 14:07:55.095343 9349 ssh.go:306] The authenticity of host '10.48.164.146:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 14:07:55.095454 9349 ssh.go:307] accepting SSH key for "lvsusekub6:22" I0707 14:07:55.095473 9349 ssh.go:308] adding fingerprint for "lvsusekub6:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 14:09:29.024025 9349 bootstrap.go:48] error bootstraping node: failed to apply state skuba-update.start: Process exited with status BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Rushi NS Date: Sunday, July 7, 2019 at 1:54 PM To: Jeff Price Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Sun Jul 7 15:55:58 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Sun, 7 Jul 2019 21:55:58 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <12DF6EDC-2312-4FF6-AD5E-91C238FAE3F7@suse.com> References: <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> <12DF6EDC-2312-4FF6-AD5E-91C238FAE3F7@suse.com> Message-ID: <91093A64-177C-4551-8996-8FCE373DF1C5@sap.com> I see this after trying with ?v5? . I have HA (NGINX as load balancer during the cluster init) I0707 14:55:10.527098 5173 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" I0707 14:55:10.527232 5173 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents I0707 14:55:10.741276 5173 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" I0707 14:55:10.866573 5173 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 I0707 14:55:10.866632 5173 ssh.go:190] stdout | [preflight] Running pre-flight checks I0707 14:55:11.136692 5173 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: I0707 14:55:11.136727 5173 ssh.go:190] stderr | [ERROR Port-6443]: Port 6443 is in use I0707 14:55:11.136737 5173 ssh.go:190] stderr | [ERROR Port-10251]: Port 10251 is in use I0707 14:55:11.136795 5173 ssh.go:190] stderr | [ERROR Port-10252]: Port 10252 is in use I0707 14:55:11.136825 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists I0707 14:55:11.136839 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists I0707 14:55:11.136848 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists I0707 14:55:11.136863 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists I0707 14:55:11.136872 5173 ssh.go:190] stderr | [ERROR Port-10250]: Port 10250 is in use I0707 14:55:11.136879 5173 ssh.go:190] stderr | [ERROR Port-2379]: Port 2379 is in use I0707 14:55:11.136886 5173 ssh.go:190] stderr | [ERROR Port-2380]: Port 2380 is in use I0707 14:55:11.136894 5173 ssh.go:190] stderr | [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty I0707 14:55:11.136910 5173 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` I0707 14:55:11.138914 5173 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" F0707 14:55:11.237429 5173 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Roger Klorese Date: Sunday, July 7, 2019 at 2:27 PM To: Rushi NS Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Run skuba with ?-v5? - you will probably see a clear error message in the verbose messages. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Sun Jul 7 16:12:44 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Sun, 7 Jul 2019 22:12:44 +0000 Subject: [caasp-beta] [CAUTION] Re: CAASP v4 beta 3 Message-ID: Looks like some files exist from (not sure ? ) so I did clean up /etc/Kubernetes and /var/lib ran again and got this error with skuba-update.timer ? I0707 15:10:49.618715 5276 states.go:35] === applying state kured.deploy === I0707 15:10:49.618820 5276 deployments.go:50] uploading local file "addons/kured/kured.yaml" to remote file "/tmp/kured.d/kured.yaml" I0707 15:10:49.618911 5276 files.go:29] uploading to remote file "/tmp/kured.d/kured.yaml" with contents I0707 15:10:49.817280 5276 ssh.go:167] running command: "sudo sh -c 'kubectl --kubeconfig=/etc/kubernetes/admin.conf apply -f /tmp/kured.d'" I0707 15:10:50.165124 5276 ssh.go:190] stdout | clusterrole.rbac.authorization.k8s.io/kured created I0707 15:10:50.185205 5276 ssh.go:190] stdout | clusterrolebinding.rbac.authorization.k8s.io/kured created I0707 15:10:50.205116 5276 ssh.go:190] stdout | role.rbac.authorization.k8s.io/kured created I0707 15:10:50.230699 5276 ssh.go:190] stdout | rolebinding.rbac.authorization.k8s.io/kured created I0707 15:10:50.254912 5276 ssh.go:190] stdout | serviceaccount/kured created I0707 15:10:50.295535 5276 ssh.go:190] stdout | daemonset.apps/kured created I0707 15:10:50.299889 5276 ssh.go:167] running command: "sudo sh -c 'rm -rf /tmp/kured.d'" I0707 15:10:50.395094 5276 states.go:40] === state kured.deploy applied successfully === I0707 15:10:50.395120 5276 states.go:35] === applying state skuba-update.start === I0707 15:10:50.396165 5276 ssh.go:167] running command: "sudo sh -c 'systemctl enable --now skuba-update.timer'" I0707 15:10:50.519774 5276 ssh.go:190] stderr | Failed to enable unit: Unit file skuba-update.timer does not exist. F0707 15:10:50.521997 5276 bootstrap.go:48] error bootstraping node: failed to apply state skuba-update.start: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: caasp-beta on behalf of Rushi NS Date: Sunday, July 7, 2019 at 2:58 PM To: Roger Klorese Cc: "caasp-beta at lists.suse.com" Subject: [CAUTION] Re: [caasp-beta] CAASP v4 beta 3 I see this after trying with ?v5? . I have HA (NGINX as load balancer during the cluster init) I0707 14:55:10.527098 5173 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" I0707 14:55:10.527232 5173 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents I0707 14:55:10.741276 5173 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" I0707 14:55:10.866573 5173 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 I0707 14:55:10.866632 5173 ssh.go:190] stdout | [preflight] Running pre-flight checks I0707 14:55:11.136692 5173 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: I0707 14:55:11.136727 5173 ssh.go:190] stderr | [ERROR Port-6443]: Port 6443 is in use I0707 14:55:11.136737 5173 ssh.go:190] stderr | [ERROR Port-10251]: Port 10251 is in use I0707 14:55:11.136795 5173 ssh.go:190] stderr | [ERROR Port-10252]: Port 10252 is in use I0707 14:55:11.136825 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists I0707 14:55:11.136839 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists I0707 14:55:11.136848 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists I0707 14:55:11.136863 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists I0707 14:55:11.136872 5173 ssh.go:190] stderr | [ERROR Port-10250]: Port 10250 is in use I0707 14:55:11.136879 5173 ssh.go:190] stderr | [ERROR Port-2379]: Port 2379 is in use I0707 14:55:11.136886 5173 ssh.go:190] stderr | [ERROR Port-2380]: Port 2380 is in use I0707 14:55:11.136894 5173 ssh.go:190] stderr | [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty I0707 14:55:11.136910 5173 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` I0707 14:55:11.138914 5173 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" F0707 14:55:11.237429 5173 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Roger Klorese Date: Sunday, July 7, 2019 at 2:27 PM To: Rushi NS Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Run skuba with ?-v5? - you will probably see a clear error message in the verbose messages. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Sun Jul 7 16:33:43 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Sun, 7 Jul 2019 22:33:43 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <91093A64-177C-4551-8996-8FCE373DF1C5@sap.com> References: <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> <12DF6EDC-2312-4FF6-AD5E-91C238FAE3F7@suse.com> <91093A64-177C-4551-8996-8FCE373DF1C5@sap.com> Message-ID: Looks like its bug as I have tried several nodes but the error is always same. I0707 15:32:37.970409 5379 ssh.go:167] running command: "sudo sh -c 'rm -rf /tmp/kured.d'" I0707 15:32:38.155906 5379 states.go:40] === state kured.deploy applied successfully === I0707 15:32:38.155934 5379 states.go:35] === applying state skuba-update.start === I0707 15:32:38.156319 5379 ssh.go:167] running command: "sudo sh -c 'systemctl enable --now skuba-update.timer'" I0707 15:32:38.278443 5379 ssh.go:190] stderr | Failed to enable unit: Unit file skuba-update.timer does not exist. F0707 15:32:38.281186 5379 bootstrap.go:48] error bootstraping node: failed to apply state skuba-update.start: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Rushi NS Date: Sunday, July 7, 2019 at 2:55 PM To: Roger Klorese Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 I see this after trying with ?v5? . I have HA (NGINX as load balancer during the cluster init) I0707 14:55:10.527098 5173 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" I0707 14:55:10.527232 5173 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents I0707 14:55:10.741276 5173 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" I0707 14:55:10.866573 5173 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 I0707 14:55:10.866632 5173 ssh.go:190] stdout | [preflight] Running pre-flight checks I0707 14:55:11.136692 5173 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: I0707 14:55:11.136727 5173 ssh.go:190] stderr | [ERROR Port-6443]: Port 6443 is in use I0707 14:55:11.136737 5173 ssh.go:190] stderr | [ERROR Port-10251]: Port 10251 is in use I0707 14:55:11.136795 5173 ssh.go:190] stderr | [ERROR Port-10252]: Port 10252 is in use I0707 14:55:11.136825 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists I0707 14:55:11.136839 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists I0707 14:55:11.136848 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists I0707 14:55:11.136863 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists I0707 14:55:11.136872 5173 ssh.go:190] stderr | [ERROR Port-10250]: Port 10250 is in use I0707 14:55:11.136879 5173 ssh.go:190] stderr | [ERROR Port-2379]: Port 2379 is in use I0707 14:55:11.136886 5173 ssh.go:190] stderr | [ERROR Port-2380]: Port 2380 is in use I0707 14:55:11.136894 5173 ssh.go:190] stderr | [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty I0707 14:55:11.136910 5173 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` I0707 14:55:11.138914 5173 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" F0707 14:55:11.237429 5173 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Roger Klorese Date: Sunday, July 7, 2019 at 2:27 PM To: Rushi NS Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Run skuba with ?-v5? - you will probably see a clear error message in the verbose messages. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Sun Jul 7 19:19:37 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Mon, 8 Jul 2019 01:19:37 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <547C0B00-5548-4CFC-9135-37A9CDA72B54@suse.com> References: <547C0B00-5548-4CFC-9135-37A9CDA72B54@suse.com> Message-ID: <6E867CA2-4E6F-4A89-801B-66BE3B234C06@sap.com> I am sure it may be a bug as standard KUBEADM cluster init and kubeadm cluster join all working but skuba is not . BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Roger Klorese Date: Sunday, July 7, 2019 at 3:37 PM To: Rushi NS Cc: "caasp-beta at lists.suse.com" , Jeff Price Subject: Re: [caasp-beta] CAASP v4 beta 3 I haven?t seen it - I?m sure someone in engineering will look at the post on Europe Monday... Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 3:35 PM, Ns, Rushi wrote: Looks like its bug as I have tried several nodes but the error is always same. I0707 15:32:37.970409 5379 ssh.go:167] running command: "sudo sh -c 'rm -rf /tmp/kured.d'" I0707 15:32:38.155906 5379 states.go:40] === state kured.deploy applied successfully === I0707 15:32:38.155934 5379 states.go:35] === applying state skuba-update.start === I0707 15:32:38.156319 5379 ssh.go:167] running command: "sudo sh -c 'systemctl enable --now skuba-update.timer'" I0707 15:32:38.278443 5379 ssh.go:190] stderr | Failed to enable unit: Unit file skuba-update.timer does not exist. F0707 15:32:38.281186 5379 bootstrap.go:48] error bootstraping node: failed to apply state skuba-update.start: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Rushi NS Date: Sunday, July 7, 2019 at 2:55 PM To: Roger Klorese Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 I see this after trying with ?v5? . I have HA (NGINX as load balancer during the cluster init) I0707 14:55:10.527098 5173 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" I0707 14:55:10.527232 5173 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents I0707 14:55:10.741276 5173 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" I0707 14:55:10.866573 5173 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 I0707 14:55:10.866632 5173 ssh.go:190] stdout | [preflight] Running pre-flight checks I0707 14:55:11.136692 5173 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: I0707 14:55:11.136727 5173 ssh.go:190] stderr | [ERROR Port-6443]: Port 6443 is in use I0707 14:55:11.136737 5173 ssh.go:190] stderr | [ERROR Port-10251]: Port 10251 is in use I0707 14:55:11.136795 5173 ssh.go:190] stderr | [ERROR Port-10252]: Port 10252 is in use I0707 14:55:11.136825 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists I0707 14:55:11.136839 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists I0707 14:55:11.136848 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists I0707 14:55:11.136863 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists I0707 14:55:11.136872 5173 ssh.go:190] stderr | [ERROR Port-10250]: Port 10250 is in use I0707 14:55:11.136879 5173 ssh.go:190] stderr | [ERROR Port-2379]: Port 2379 is in use I0707 14:55:11.136886 5173 ssh.go:190] stderr | [ERROR Port-2380]: Port 2380 is in use I0707 14:55:11.136894 5173 ssh.go:190] stderr | [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty I0707 14:55:11.136910 5173 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` I0707 14:55:11.138914 5173 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" F0707 14:55:11.237429 5173 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Roger Klorese Date: Sunday, July 7, 2019 at 2:27 PM To: Rushi NS Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Run skuba with ?-v5? - you will probably see a clear error message in the verbose messages. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmassaguerpla at suse.de Mon Jul 8 04:42:04 2019 From: jmassaguerpla at suse.de (Jordi Massaguer Pla) Date: Mon, 8 Jul 2019 12:42:04 +0200 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: References: <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> <12DF6EDC-2312-4FF6-AD5E-91C238FAE3F7@suse.com> <91093A64-177C-4551-8996-8FCE373DF1C5@sap.com> Message-ID: <625626ae-a1e4-f239-93d5-b337bdfcb746@suse.de> Hi, could you open a bug in bugzilla about it? The skuba-update.timer? is used for updating the nodes. Thus the cluster should be working fine but it is not upgradable. https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SUSE%20CaaS%20Platform%204 thanks On 07/08/2019 12:33 AM, Ns, Rushi wrote: > > Looks like its bug as I have tried several nodes but the error is > always same. > > I0707 15:32:37.970409??? 5379 ssh.go:167] running command: "sudo sh -c > 'rm -rf /tmp/kured.d'" > > I0707 15:32:38.155906??? 5379 states.go:40] === state kured.deploy > applied successfully === > > I0707 15:32:38.155934??? 5379 states.go:35] === applying state > skuba-update.start === > > I0707 15:32:38.156319??? 5379 ssh.go:167] running command: "sudo sh -c > 'systemctl enable --now skuba-update.timer'" > > I0707 15:32:38.278443??? 5379 ssh.go:190] stderr | Failed to enable > unit: Unit file skuba-update.timer does not exist. > > F0707 15:32:38.281186??? 5379 bootstrap.go:48] error bootstraping > node: failed to apply state skuba-update.start: Process exited with > status 1 > > BR, > > Rushi. > > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE > > *From: *Rushi NS > *Date: *Sunday, July 7, 2019 at 2:55 PM > *To: *Roger Klorese > *Cc: *Jeff Price , "caasp-beta at lists.suse.com" > > *Subject: *Re: [caasp-beta] CAASP v4 beta 3 > > I see this after trying with ?v5? > > . I have HA (NGINX as load balancer during the cluster init) > > I0707 14:55:10.527098??? 5173 deployments.go:50] uploading local file > "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" > > I0707 14:55:10.527232??? 5173 files.go:29] uploading to remote file > "/tmp/kubeadm-init.conf" with contents > > I0707 14:55:10.741276??? 5173 ssh.go:167] running command: "sudo sh -c > 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" > > I0707 14:55:10.866573??? 5173 ssh.go:190] stdout | [init] Using > Kubernetes version: v1.14.1 > > I0707 14:55:10.866632??? 5173 ssh.go:190] stdout | [preflight] Running > pre-flight checks > > I0707 14:55:11.136692??? 5173 ssh.go:190] stderr | error execution > phase preflight: [preflight] Some fatal errors occurred: > > I0707 14:55:11.136727??? 5173 ssh.go:190] stderr |???? ????? [ERROR > Port-6443]: Port 6443 is in use > > I0707 14:55:11.136737??? 5173 ssh.go:190] stderr |???? ????? [ERROR > Port-10251]: Port 10251 is in use > > I0707 14:55:11.136795??? 5173 ssh.go:190] stderr |???? ????? [ERROR > Port-10252]: Port 10252 is in use > > I0707 14:55:11.136825??? 5173 ssh.go:190] stderr |???? ????? [ERROR > FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: > /etc/kubernetes/manifests/kube-apiserver.yaml already exists > > I0707 14:55:11.136839??? 5173 ssh.go:190] stderr |???? ????? [ERROR > FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: > /etc/kubernetes/manifests/kube-controller-manager.yaml already exists > > I0707 14:55:11.136848??? 5173 ssh.go:190] stderr |???? ????? [ERROR > FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: > /etc/kubernetes/manifests/kube-scheduler.yaml already exists > > I0707 14:55:11.136863??? 5173 ssh.go:190] stderr |???? ????? [ERROR > FileAvailable--etc-kubernetes-manifests-etcd.yaml]: > /etc/kubernetes/manifests/etcd.yaml already exists > > I0707 14:55:11.136872??? 5173 ssh.go:190] stderr |???? ????? [ERROR > Port-10250]: Port 10250 is in use > > I0707 14:55:11.136879??? 5173 ssh.go:190] stderr |???? ????? [ERROR > Port-2379]: Port 2379 is in use > > I0707 14:55:11.136886??? 5173 ssh.go:190] stderr |???? ????? [ERROR > Port-2380]: Port 2380 is in use > > I0707 14:55:11.136894??? 5173 ssh.go:190] stderr |???? ????? [ERROR > DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty > > I0707 14:55:11.136910??? 5173 ssh.go:190] stderr | [preflight] If you > know what you are doing, you can make a check non-fatal with > `--ignore-preflight-errors=...` > > I0707 14:55:11.138914??? 5173 ssh.go:167] running command: "sudo sh -c > 'rm /tmp/kubeadm-init.conf'" > > F0707 14:55:11.237429??? 5173 bootstrap.go:48] error bootstraping > node: failed to apply state kubeadm.init: Process exited with status 1 > > BR, > > Rushi. > > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE > > *From: *Roger Klorese > *Date: *Sunday, July 7, 2019 at 2:27 PM > *To: *Rushi NS > *Cc: *Jeff Price , "caasp-beta at lists.suse.com" > > *Subject: *Re: [caasp-beta] CAASP v4 beta 3 > > Run skuba with ?-v5? - you will probably see a clear error message in > the verbose messages. > > > > > Roger B.A. Klorese > > Senior Product Manager > SUSE > 705 5th Ave S , Suite 1000 > > Seattle WA 98104 > (P)+1 206.217.7432 > (M)+1 425.444.5493 > roger.klorese at suse.com > Schedule a meeting: https://doodle.com/RogerKlorese > GPG Key: D567 F186 A6AE D244 067E? 95E4 E67D 019F 0670 D9CC > > > > > On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: > > Hi jeff, > > Sorry to bother , I see that new CAASP introduced SKUBA (replace > of CAASPCTL ) and I started deploying a new cluster with SKUBA and > ran into the same issue as before with SSH-agent . > > I did the ssh-agent and did the copy of ssh-copy-id to all all the > nodes and I can ssh without password but after all doing the skube > boot strap is failing > > Setup ssh-agent > > eval "$(ssh-agent -s)" > > add the keys to agent > > ssh-add > > skuba node bootstrap --user root --target lv1host lmaster1 > > ------- > > ** This is a BETA release and NOT intended for production usage. ** > > [bootstrap] updating init configuration with target information > > W0707 13:52:59.141264 ???8016 ssh.go:306] > > The authenticity of host '10.48.164.174:22' can't be established. > > ECDSA key fingerprint is > 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. > > I0707 13:52:59.141375??? 8016 ssh.go:307] accepting SSH key for > "lv1host:22" > > I0707 13:52:59.141412??? 8016 ssh.go:308] adding fingerprint for > "lv1host:22" to "known_hosts" > > [bootstrap] writing init configuration for node > > [bootstrap] applying init configuration to node > > F0707 13:53:01.718642??? 8016 bootstrap.go:48] error bootstraping > node: failed to apply state kubeadm.init: Process exited with status 1 > > Do you know what the root cause of the issue now? > > BR, > > Rushi. > > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A > DIFFERENCE > > *From: *Jeff Price > *Date: *Thursday, May 30, 2019 at 7:05 PM > *To: *Rushi NS > *Cc: *"Le Bihan St?phane (AMUNDI-ITS)" > , Jean Marc Lambert > , "caasp-beta at lists.suse.com" > > *Subject: *Re: [caasp-beta] CAASP v4 beta 3 > > Setup ssh-agent > > |eval "$(ssh-agent -s)"| > > add the keys to agent > > ssh-add > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta > > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta -- Jordi Massaguer Pla Release Manager for SUSE CaaS Platform SUSE Linux https://www.suse.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Mon Jul 8 10:47:54 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Mon, 8 Jul 2019 16:47:54 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <625626ae-a1e4-f239-93d5-b337bdfcb746@suse.de> References: <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> <12DF6EDC-2312-4FF6-AD5E-91C238FAE3F7@suse.com> <91093A64-177C-4551-8996-8FCE373DF1C5@sap.com> <625626ae-a1e4-f239-93d5-b337bdfcb746@suse.de> Message-ID: <692B6C28-E91D-403C-82FC-2C18DC401300@sap.com> Hi, Just submitted the bug . here you go. Bug 1140757 - skuba node bootstrap BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jordi Massaguer Pla Date: Monday, July 8, 2019 at 3:42 AM To: Rushi NS , Roger Klorese Cc: "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Hi, could you open a bug in bugzilla about it? The skuba-update.timer is used for updating the nodes. Thus the cluster should be working fine but it is not upgradable. https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SUSE%20CaaS%20Platform%204 thanks On 07/08/2019 12:33 AM, Ns, Rushi wrote: Looks like its bug as I have tried several nodes but the error is always same. I0707 15:32:37.970409 5379 ssh.go:167] running command: "sudo sh -c 'rm -rf /tmp/kured.d'" I0707 15:32:38.155906 5379 states.go:40] === state kured.deploy applied successfully === I0707 15:32:38.155934 5379 states.go:35] === applying state skuba-update.start === I0707 15:32:38.156319 5379 ssh.go:167] running command: "sudo sh -c 'systemctl enable --now skuba-update.timer'" I0707 15:32:38.278443 5379 ssh.go:190] stderr | Failed to enable unit: Unit file skuba-update.timer does not exist. F0707 15:32:38.281186 5379 bootstrap.go:48] error bootstraping node: failed to apply state skuba-update.start: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Rushi NS Date: Sunday, July 7, 2019 at 2:55 PM To: Roger Klorese Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 I see this after trying with ?v5? . I have HA (NGINX as load balancer during the cluster init) I0707 14:55:10.527098 5173 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" I0707 14:55:10.527232 5173 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents I0707 14:55:10.741276 5173 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" I0707 14:55:10.866573 5173 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 I0707 14:55:10.866632 5173 ssh.go:190] stdout | [preflight] Running pre-flight checks I0707 14:55:11.136692 5173 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: I0707 14:55:11.136727 5173 ssh.go:190] stderr | [ERROR Port-6443]: Port 6443 is in use I0707 14:55:11.136737 5173 ssh.go:190] stderr | [ERROR Port-10251]: Port 10251 is in use I0707 14:55:11.136795 5173 ssh.go:190] stderr | [ERROR Port-10252]: Port 10252 is in use I0707 14:55:11.136825 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists I0707 14:55:11.136839 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists I0707 14:55:11.136848 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists I0707 14:55:11.136863 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists I0707 14:55:11.136872 5173 ssh.go:190] stderr | [ERROR Port-10250]: Port 10250 is in use I0707 14:55:11.136879 5173 ssh.go:190] stderr | [ERROR Port-2379]: Port 2379 is in use I0707 14:55:11.136886 5173 ssh.go:190] stderr | [ERROR Port-2380]: Port 2380 is in use I0707 14:55:11.136894 5173 ssh.go:190] stderr | [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty I0707 14:55:11.136910 5173 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` I0707 14:55:11.138914 5173 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" F0707 14:55:11.237429 5173 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Roger Klorese Date: Sunday, July 7, 2019 at 2:27 PM To: Rushi NS Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Run skuba with ?-v5? - you will probably see a clear error message in the verbose messages. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -- Jordi Massaguer Pla Release Manager for SUSE CaaS Platform SUSE Linux https://www.suse.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From roger.klorese at suse.com Sun Jul 7 15:26:50 2019 From: roger.klorese at suse.com (Roger Klorese) Date: Sun, 7 Jul 2019 21:26:50 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> References: <5AA3D83D-8D18-4254-AD3B-BA97AC7E84E2@sap.com> Message-ID: <12DF6EDC-2312-4FF6-AD5E-91C238FAE3F7@suse.com> Run skuba with ?-v5? - you will probably see a clear error message in the verbose messages. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: ? Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From roger.klorese at suse.com Sun Jul 7 16:36:58 2019 From: roger.klorese at suse.com (Roger Klorese) Date: Sun, 7 Jul 2019 22:36:58 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: References: Message-ID: <547C0B00-5548-4CFC-9135-37A9CDA72B54@suse.com> I haven?t seen it - I?m sure someone in engineering will look at the post on Europe Monday... Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 3:35 PM, Ns, Rushi wrote: ? Looks like its bug as I have tried several nodes but the error is always same. I0707 15:32:37.970409 5379 ssh.go:167] running command: "sudo sh -c 'rm -rf /tmp/kured.d'" I0707 15:32:38.155906 5379 states.go:40] === state kured.deploy applied successfully === I0707 15:32:38.155934 5379 states.go:35] === applying state skuba-update.start === I0707 15:32:38.156319 5379 ssh.go:167] running command: "sudo sh -c 'systemctl enable --now skuba-update.timer'" I0707 15:32:38.278443 5379 ssh.go:190] stderr | Failed to enable unit: Unit file skuba-update.timer does not exist. F0707 15:32:38.281186 5379 bootstrap.go:48] error bootstraping node: failed to apply state skuba-update.start: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Rushi NS Date: Sunday, July 7, 2019 at 2:55 PM To: Roger Klorese Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 I see this after trying with ?v5? . I have HA (NGINX as load balancer during the cluster init) I0707 14:55:10.527098 5173 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" I0707 14:55:10.527232 5173 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents I0707 14:55:10.741276 5173 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" I0707 14:55:10.866573 5173 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 I0707 14:55:10.866632 5173 ssh.go:190] stdout | [preflight] Running pre-flight checks I0707 14:55:11.136692 5173 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: I0707 14:55:11.136727 5173 ssh.go:190] stderr | [ERROR Port-6443]: Port 6443 is in use I0707 14:55:11.136737 5173 ssh.go:190] stderr | [ERROR Port-10251]: Port 10251 is in use I0707 14:55:11.136795 5173 ssh.go:190] stderr | [ERROR Port-10252]: Port 10252 is in use I0707 14:55:11.136825 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists I0707 14:55:11.136839 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists I0707 14:55:11.136848 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists I0707 14:55:11.136863 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists I0707 14:55:11.136872 5173 ssh.go:190] stderr | [ERROR Port-10250]: Port 10250 is in use I0707 14:55:11.136879 5173 ssh.go:190] stderr | [ERROR Port-2379]: Port 2379 is in use I0707 14:55:11.136886 5173 ssh.go:190] stderr | [ERROR Port-2380]: Port 2380 is in use I0707 14:55:11.136894 5173 ssh.go:190] stderr | [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty I0707 14:55:11.136910 5173 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` I0707 14:55:11.138914 5173 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" F0707 14:55:11.237429 5173 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Roger Klorese Date: Sunday, July 7, 2019 at 2:27 PM To: Rushi NS Cc: Jeff Price , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Run skuba with ?-v5? - you will probably see a clear error message in the verbose messages. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: Hi jeff, Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add skuba node bootstrap --user root --target lv1host lmaster1 ------- ** This is a BETA release and NOT intended for production usage. ** [bootstrap] updating init configuration with target information W0707 13:52:59.141264 8016 ssh.go:306] The authenticity of host '10.48.164.174:22' can't be established. ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" [bootstrap] writing init configuration for node [bootstrap] applying init configuration to node F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Do you know what the root cause of the issue now? BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Jeff Price Date: Thursday, May 30, 2019 at 7:05 PM To: Rushi NS Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Setup ssh-agent eval "$(ssh-agent -s)" add the keys to agent ssh-add _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From LancelotT at supermicro.com.tw Sun Jul 7 21:59:07 2019 From: LancelotT at supermicro.com.tw (Lancelot Tsai) Date: Mon, 8 Jul 2019 03:59:07 +0000 Subject: [caasp-beta] SUSE CaaS Platform 4 Beta Access Message-ID: Dear CaaS Platform Staff, I?m Lancelot from Supermicro. I?m developing a bundle with our server and SUSE CaaSP 4. It seems we need CaaS Platform access code. May I retrieve the access code? Or, who should I contact for this code? Thanks! Best Regards, Lancelot Tsai PM of Enterprise/Cloud Solutions Super Micro Computer, Inc. Taiwan 23511?????????150?3? 3F., No.150, Jian 1st Rd., Zhonghe Dist., New Taipei City 23511, Taiwan (R.O.C.) Tel: +886-2-8226-3990 Ext.3059 Mobile:+886-966751059 [2015-12-23_090153] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 9415 bytes Desc: image001.png URL: From smf34 at cam.ac.uk Tue Jul 9 03:39:40 2019 From: smf34 at cam.ac.uk (Simon Flood) Date: Tue, 9 Jul 2019 09:39:40 +0000 Subject: [caasp-beta] SUSE CaaS Platform 4 Beta Access In-Reply-To: References: Message-ID: <9fa54648-b5ce-d7c2-44e6-059b87e040b8@cam.ac.uk> Hi Lancelot, On 08/07/2019 04:59, Lancelot Tsai wrote: > Dear CaaS Platform Staff, > > I?m Lancelot from Supermicro. I?m developing a bundle with our server and SUSE CaaSP 4. It seems we need CaaS Platform access code. May I retrieve the access code? Or, who should I contact for this code? > > Thanks! > > Best Regards, > Lancelot Tsai > PM of Enterprise/Cloud Solutions > Super Micro Computer, Inc. Taiwan > 23511?????????150?3? > 3F., No.150, Jian 1st Rd., Zhonghe Dist., New Taipei City 23511, Taiwan (R.O.C.) > Tel: +886-2-8226-3990 Ext.3059 > Mobile:+886-966751059 > [2015-12-23_090153] From the SUSE CaaS Platform 4.0 Beta 3 announcement email: "Beta Registration codes You should not use a SLES 15 SP1 environment with the SLE Beta Registration Code anymore. Because the SLE Beta Registration Code is expired now but you can either use your regular SLE Registration Code or use a Trial. Registration is not working with your regular key, special Beta Registration Code is required. You need to request one for SUSE CaaS Platform 4.0 Beta Program by contacting us at beta-programs at lists.suse.com[6]." where [6]:mailto:beta-programs at lists.suse.com?subject=Requesting%20SUSE%20CaaSP%204.0%20Beta%20Registration%20Codes&body=Requesting%20SUSE%20CaaSP%204.0 See also the FAQ for the beta @ https://www.suse.com/betaprogram/caasp-beta/#faq-reg HTH, Simon -- Simon Flood Linux System Administrator MRC Biostatistics Unit, University of Cambridge United Kingdom SUSE Knowledge Partner From vmoutoussamy at suse.com Tue Jul 9 04:01:40 2019 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 9 Jul 2019 10:01:40 +0000 Subject: [caasp-beta] Roadmap for SUSE CaaSP 4 GA release In-Reply-To: <4cfeb691c5b3c438c3489dcc5e88867366fd3798.camel@adfinis-sygroup.ch> References: <4cfeb691c5b3c438c3489dcc5e88867366fd3798.camel@adfinis-sygroup.ch> Message-ID: <17902114-738C-42B4-B05A-373AA5EE1D31@suse.com> Hi, We didn?t forget your question, it is just that we are still discussing which milestones/dates will be public or internal only. We should have an official answer by tomorrow, sorry for the inconvenience but stay tuned! Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager > On 26 Jun 2019, at 10:25, Lukas Grossar wrote: > > Hi everyone > > Can you provide any information about a roadmap and possible dates for > the final GA (or a least RC) release of SUSE CaaSP 4? > > We currently working successfully with the Beta 2 and planning an > upgrade to Beta 3, but performing the production deploy with a RC or GA > release would be preferable. > > Regards > Lukas > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta From AnDavis at suse.com Tue Jul 9 08:18:37 2019 From: AnDavis at suse.com (Ann Davis) Date: Tue, 9 Jul 2019 14:18:37 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <547C0B00-5548-4CFC-9135-37A9CDA72B54@suse.com> References: <547C0B00-5548-4CFC-9135-37A9CDA72B54@suse.com> Message-ID: <7B3B7ADD-36B4-409A-A7B5-F4982278463D@suse.com> Hi, We have another (separate) report of this same error. Apparently it did not happen with beta 2... Thanks, Ann > On Jul 7, 2019, at 4:36 PM, Roger Klorese wrote: > > I haven?t seen it - I?m sure someone in engineering will look at the post on Europe Monday... > > Roger B.A. Klorese > Senior Product Manager > SUSE > 705 5th Ave S, Suite 1000 > Seattle WA 98104 > (P)+1 206.217.7432 > (M)+1 425.444.5493 > roger.klorese at suse.com > Schedule a meeting: https://doodle.com/RogerKlorese > GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC > >> On Jul 7, 2019, at 3:35 PM, Ns, Rushi wrote: >> >> ? >> Looks like its bug as I have tried several nodes but the error is always same. >> >> I0707 15:32:37.970409 5379 ssh.go:167] running command: "sudo sh -c 'rm -rf /tmp/kured.d'" >> I0707 15:32:38.155906 5379 states.go:40] === state kured.deploy applied successfully === >> I0707 15:32:38.155934 5379 states.go:35] === applying state skuba-update.start === >> I0707 15:32:38.156319 5379 ssh.go:167] running command: "sudo sh -c 'systemctl enable --now skuba-update.timer'" >> I0707 15:32:38.278443 5379 ssh.go:190] stderr | Failed to enable unit: Unit file skuba-update.timer does not exist. >> F0707 15:32:38.281186 5379 bootstrap.go:48] error bootstraping node: failed to apply state skuba-update.start: Process exited with status 1 >> >> >> BR, >> >> Rushi. >> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE >> >> >> From: Rushi NS >> Date: Sunday, July 7, 2019 at 2:55 PM >> To: Roger Klorese >> Cc: Jeff Price , "caasp-beta at lists.suse.com" >> Subject: Re: [caasp-beta] CAASP v4 beta 3 >> >> I see this after trying with ?v5? >> . I have HA (NGINX as load balancer during the cluster init) >> >> >> I0707 14:55:10.527098 5173 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" >> I0707 14:55:10.527232 5173 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents >> I0707 14:55:10.741276 5173 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" >> I0707 14:55:10.866573 5173 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 >> I0707 14:55:10.866632 5173 ssh.go:190] stdout | [preflight] Running pre-flight checks >> I0707 14:55:11.136692 5173 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: >> I0707 14:55:11.136727 5173 ssh.go:190] stderr | [ERROR Port-6443]: Port 6443 is in use >> I0707 14:55:11.136737 5173 ssh.go:190] stderr | [ERROR Port-10251]: Port 10251 is in use >> I0707 14:55:11.136795 5173 ssh.go:190] stderr | [ERROR Port-10252]: Port 10252 is in use >> I0707 14:55:11.136825 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists >> I0707 14:55:11.136839 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists >> I0707 14:55:11.136848 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists >> I0707 14:55:11.136863 5173 ssh.go:190] stderr | [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists >> I0707 14:55:11.136872 5173 ssh.go:190] stderr | [ERROR Port-10250]: Port 10250 is in use >> I0707 14:55:11.136879 5173 ssh.go:190] stderr | [ERROR Port-2379]: Port 2379 is in use >> I0707 14:55:11.136886 5173 ssh.go:190] stderr | [ERROR Port-2380]: Port 2380 is in use >> I0707 14:55:11.136894 5173 ssh.go:190] stderr | [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty >> I0707 14:55:11.136910 5173 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` >> I0707 14:55:11.138914 5173 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" >> F0707 14:55:11.237429 5173 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 >> >> BR, >> >> Rushi. >> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE >> >> >> From: Roger Klorese >> Date: Sunday, July 7, 2019 at 2:27 PM >> To: Rushi NS >> Cc: Jeff Price , "caasp-beta at lists.suse.com" >> Subject: Re: [caasp-beta] CAASP v4 beta 3 >> >> Run skuba with ?-v5? - you will probably see a clear error message in the verbose messages. >> >> >> >> Roger B.A. Klorese >> Senior Product Manager >> SUSE >> 705 5th Ave S, Suite 1000 >> Seattle WA 98104 >> (P)+1 206.217.7432 >> (M)+1 425.444.5493 >> roger.klorese at suse.com >> Schedule a meeting: https://doodle.com/RogerKlorese >> GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC >> >> >> >> On Jul 7, 2019, at 1:55 PM, Ns, Rushi wrote: >> >> Hi jeff, >> >> Sorry to bother , I see that new CAASP introduced SKUBA (replace of CAASPCTL ) and I started deploying a new cluster with SKUBA and ran into the same issue as before with SSH-agent . >> >> I did the ssh-agent and did the copy of ssh-copy-id to all all the nodes and I can ssh without password but after all doing the skube boot strap is failing >> >> Setup ssh-agent >> >> eval "$(ssh-agent -s)" >> >> add the keys to agent >> >> ssh-add >> >> >> >> skuba node bootstrap --user root --target lv1host lmaster1 >> ------- >> >> ** This is a BETA release and NOT intended for production usage. ** >> [bootstrap] updating init configuration with target information >> W0707 13:52:59.141264 8016 ssh.go:306] >> The authenticity of host '10.48.164.174:22' can't be established. >> ECDSA key fingerprint is 39:99:33:64:be:7d:a9:db:90:f6:93:67:3b:b9:3e:73. >> I0707 13:52:59.141375 8016 ssh.go:307] accepting SSH key for "lv1host:22" >> I0707 13:52:59.141412 8016 ssh.go:308] adding fingerprint for "lv1host:22" to "known_hosts" >> [bootstrap] writing init configuration for node >> [bootstrap] applying init configuration to node >> F0707 13:53:01.718642 8016 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 >> >> >> >> >> Do you know what the root cause of the issue now? >> >> BR, >> >> Rushi. >> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE >> >> >> From: Jeff Price >> Date: Thursday, May 30, 2019 at 7:05 PM >> To: Rushi NS >> Cc: "Le Bihan St?phane (AMUNDI-ITS)" , Jean Marc Lambert , "caasp-beta at lists.suse.com" >> Subject: Re: [caasp-beta] CAASP v4 beta 3 >> >> Setup ssh-agent >> >> eval "$(ssh-agent -s)" >> >> add the keys to agent >> >> ssh-add >> _______________________________________________ >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/caasp-beta > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta From lukas.grossar at adfinis-sygroup.ch Tue Jul 9 08:26:56 2019 From: lukas.grossar at adfinis-sygroup.ch (Lukas Grossar) Date: Tue, 09 Jul 2019 16:26:56 +0200 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <7B3B7ADD-36B4-409A-A7B5-F4982278463D@suse.com> References: <547C0B00-5548-4CFC-9135-37A9CDA72B54@suse.com> <7B3B7ADD-36B4-409A-A7B5-F4982278463D@suse.com> Message-ID: <824f0c5ba87db07afee494ac6be043976af7ab46.camel@adfinis-sygroup.ch> On Tue, 2019-07-09 at 14:18 +0000, Ann Davis wrote: > [...] > We have another (separate) report of this same error. Apparently it > did not happen with beta 2... I can confirm that I'm currently facing the same issues during a skuba bootstrap. Regards Lukas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From rushi.ns at sap.com Tue Jul 9 08:31:18 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Tue, 9 Jul 2019 14:31:18 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <824f0c5ba87db07afee494ac6be043976af7ab46.camel@adfinis-sygroup.ch> References: <547C0B00-5548-4CFC-9135-37A9CDA72B54@suse.com> <7B3B7ADD-36B4-409A-A7B5-F4982278463D@suse.com> <824f0c5ba87db07afee494ac6be043976af7ab46.camel@adfinis-sygroup.ch> Message-ID: <829C70AF-2484-4D51-987C-40EA1975627B@sap.com> Ok good to see that I am not the one having this issue. As I said before standard KUBEADM init and KUBEADM join to make cluster working on the same SUSE 15 SP1 without using SKUBA . seems somewhere skuba is not working with CNI- network as I found through some debug it shows CNI- errors. Look the below. 13518 kubelet.go:2170] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: Missing CNI default network BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE ?On 7/9/19, 7:28 AM, "Lukas Grossar" wrote: On Tue, 2019-07-09 at 14:18 +0000, Ann Davis wrote: > [...] > We have another (separate) report of this same error. Apparently it > did not happen with beta 2... I can confirm that I'm currently facing the same issues during a skuba bootstrap. Regards Lukas From vmoutoussamy at suse.com Wed Jul 10 07:05:32 2019 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 10 Jul 2019 13:05:32 +0000 Subject: [caasp-beta] Roadmap for SUSE CaaSP 4 GA release In-Reply-To: <17902114-738C-42B4-B05A-373AA5EE1D31@suse.com> References: <4cfeb691c5b3c438c3489dcc5e88867366fd3798.camel@adfinis-sygroup.ch> <17902114-738C-42B4-B05A-373AA5EE1D31@suse.com> Message-ID: <25273F61-A995-4918-B5CD-677456562AC5@suse.com> Hi, We have updated the release schedule for SUSE CaaS Platform 4 at: https://www.suse.com/betaprogram/caasp-beta/#releases With the following dates: * Beta 4 ? 15th July 2019 * Beta 5 ? 29th July 2019 * RC1 ? 12th August 2019 * GMC ? 09th September 2019 * FCS? Mid-September 2019 Please keep in mind that we are working hard to stick with the schedule, however, like any beta program this could be subject to change. Thank you for your patience and hopefully have fun beta testing! Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager On 9 Jul 2019, at 12:01, Vincent Moutoussamy > wrote: Hi, We didn?t forget your question, it is just that we are still discussing which milestones/dates will be public or internal only. We should have an official answer by tomorrow, sorry for the inconvenience but stay tuned! Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager On 26 Jun 2019, at 10:25, Lukas Grossar > wrote: Hi everyone Can you provide any information about a roadmap and possible dates for the final GA (or a least RC) release of SUSE CaaSP 4? We currently working successfully with the Beta 2 and planning an upgrade to Beta 3, but performing the production deploy with a RC or GA release would be preferable. Regards Lukas _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From egov-devops at akdb.de Fri Jul 12 02:16:39 2019 From: egov-devops at akdb.de (egov-devops) Date: Fri, 12 Jul 2019 08:16:39 +0000 Subject: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? Message-ID: <357d4fe2903b4568968e4fcbc2475d52@akdb.de> Howdy, I'm trying to bootstrap a caasp 4 beta 3 cluster (https://susedoc.github.io/doc-caasp/beta/caasp-deployment/single-html/#bootstrap). But I get an error: "F0712 09:46:39.270173 13949 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1" So far I have done: 1. ssh-keygen; ssh-add; ssh-copy-id; ssh via sles from "admin" sles server to master{1-3} and node{1-3} via user sles is working 2. Own RMT Server with images as described in CaaSP-CAP-POC-Setup-Guide.pdf setup and working 3. skuba cluster init --control-plane my-cluster -> LB IP we use; 4. Skipped kured (4.1.2.1) and prometheus (4.1.3) changes 5. cd my-cluster 6. skuba node bootstrap --user sles --sudo --target -> IP of master1; NAME master1 ? skuba node bootstrap --user sles --sudo --target 10.255.1.3 master1 ? ** This is a BETA release and NOT intended for production usage. ** ? [bootstrap] updating init configuration with target information ? [bootstrap] writing init configuration for node ? [bootstrap] applying init configuration to node ? F0712 09:46:39.270173 13949 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Master1 setup: - OS SLES 15 SP1 - SUSEConnect stuff as described here (https://susedoc.github.io/doc-caasp/beta/caasp-deployment/single-html/#_preparation_of_the_vm_as_a_template) - SUSEConnect --list-extensions AVAILABLE EXTENSIONS AND MODULES Basesystem Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64 Containers Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p /15.1/x86_64 SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 Server Applications Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-server-applications/15.1/x86_64 Public Cloud Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-public-cloud/15.1/x86_64 - sudo zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins Refreshing service 'SMT-http_smt_akdb_net'. Retrieving repository 'SLE-Module-Basesystem15-SP1-Updates' metadata .......................................[done] Building repository 'SLE-Module-Basesystem15-SP1-Updates' cache ............................................[done] Retrieving repository 'SLE-Module-Containers15-SP1-Updates' metadata .......................................[done] Building repository 'SLE-Module-Containers15-SP1-Updates' cache ............................................[done] Retrieving repository 'SLE-Module-Server-Applications15-SP1-Updates' metadata ..............................[done] Building repository 'SLE-Module-Server-Applications15-SP1-Updates' cache ...................................[done] Loading repository data... Reading installed packages... 'cni-plugins' is already installed. No update candidate for 'cni-plugins-0.7.4-1.11.x86_64'. The highest available version is already installed. 'kubernetes-kubelet' is already installed. No update candidate for 'kubernetes-kubelet-1.14.1-1.8.x86_64'. The highest available version is already installed. 'cri-o' is already installed. No update candidate for 'cri-o-1.14.1-1.2.x86_64'. The highest available version is already installed. 'kubernetes-kubeadm' is already installed. No update candidate for 'kubernetes-kubeadm-1.14.1-1.8.x86_64'. The highest available version is already installed. 'kubernetes-client' is already installed. No update candidate for 'kubernetes-client-1.14.1-1.8.x86_64'. The highest available version is already installed. Resolving package dependencies... Nothing to do. Any idea, what I did wrong? What can I check? What can I fix to make it work? Mit freundlichen Gr??en Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From roger.klorese at suse.com Fri Jul 12 02:37:00 2019 From: roger.klorese at suse.com (Roger Klorese) Date: Fri, 12 Jul 2019 08:37:00 +0000 Subject: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? In-Reply-To: <357d4fe2903b4568968e4fcbc2475d52@akdb.de> References: <357d4fe2903b4568968e4fcbc2475d52@akdb.de> Message-ID: Often, the default terseness of skuba hides what can be very simple errors to handle from the underlying tools. Try running skuba vith "-v 5" and see if you get a more useful message. Once, I got this message because I missed a step; another time, it was because I had a typo in an option... Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC ________________________________ From: caasp-beta on behalf of egov-devops Sent: Friday, July 12, 2019 1:16 AM To: caasp-beta at lists.suse.com Cc: Gergo Kovacs Subject: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? Howdy, I?m trying to bootstrap a caasp 4 beta 3 cluster (https://susedoc.github.io/doc-caasp/beta/caasp-deployment/single-html/#bootstrap). But I get an error: ?F0712 09:46:39.270173 13949 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1? So far I have done: 1. ssh-keygen; ssh-add; ssh-copy-id; ssh via sles from ?admin? sles server to master{1-3} and node{1-3} via user sles is working 2. Own RMT Server with images as described in CaaSP-CAP-POC-Setup-Guide.pdf setup and working 3. skuba cluster init --control-plane my-cluster -> LB IP we use; 4. Skipped kured (4.1.2.1) and prometheus (4.1.3) changes 5. cd my-cluster 6. skuba node bootstrap --user sles --sudo --target -> IP of master1; NAME master1 ? skuba node bootstrap --user sles --sudo --target 10.255.1.3 master1 ? ** This is a BETA release and NOT intended for production usage. ** ? [bootstrap] updating init configuration with target information ? [bootstrap] writing init configuration for node ? [bootstrap] applying init configuration to node ? F0712 09:46:39.270173 13949 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Master1 setup: - OS SLES 15 SP1 - SUSEConnect stuff as described here (https://susedoc.github.io/doc-caasp/beta/caasp-deployment/single-html/#_preparation_of_the_vm_as_a_template) - SUSEConnect --list-extensions AVAILABLE EXTENSIONS AND MODULES Basesystem Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64 Containers Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p /15.1/x86_64 SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 Server Applications Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-server-applications/15.1/x86_64 Public Cloud Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-public-cloud/15.1/x86_64 - sudo zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins Refreshing service 'SMT-http_smt_akdb_net'. Retrieving repository 'SLE-Module-Basesystem15-SP1-Updates' metadata .......................................[done] Building repository 'SLE-Module-Basesystem15-SP1-Updates' cache ............................................[done] Retrieving repository 'SLE-Module-Containers15-SP1-Updates' metadata .......................................[done] Building repository 'SLE-Module-Containers15-SP1-Updates' cache ............................................[done] Retrieving repository 'SLE-Module-Server-Applications15-SP1-Updates' metadata ..............................[done] Building repository 'SLE-Module-Server-Applications15-SP1-Updates' cache ...................................[done] Loading repository data... Reading installed packages... 'cni-plugins' is already installed. No update candidate for 'cni-plugins-0.7.4-1.11.x86_64'. The highest available version is already installed. 'kubernetes-kubelet' is already installed. No update candidate for 'kubernetes-kubelet-1.14.1-1.8.x86_64'. The highest available version is already installed. 'cri-o' is already installed. No update candidate for 'cri-o-1.14.1-1.2.x86_64'. The highest available version is already installed. 'kubernetes-kubeadm' is already installed. No update candidate for 'kubernetes-kubeadm-1.14.1-1.8.x86_64'. The highest available version is already installed. 'kubernetes-client' is already installed. No update candidate for 'kubernetes-client-1.14.1-1.8.x86_64'. The highest available version is already installed. Resolving package dependencies... Nothing to do. Any idea, what I did wrong? What can I check? What can I fix to make it work? Mit freundlichen Gr??en Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From lcavajani at suse.com Fri Jul 12 04:41:32 2019 From: lcavajani at suse.com (Ludovic Cavajani) Date: Fri, 12 Jul 2019 12:41:32 +0200 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <829C70AF-2484-4D51-987C-40EA1975627B@sap.com> References: <547C0B00-5548-4CFC-9135-37A9CDA72B54@suse.com> <7B3B7ADD-36B4-409A-A7B5-F4982278463D@suse.com> <824f0c5ba87db07afee494ac6be043976af7ab46.camel@adfinis-sygroup.ch> <829C70AF-2484-4D51-987C-40EA1975627B@sap.com> Message-ID: <2dff18da-4813-39ae-4a32-5f8c373e2e8e@suse.com> Hi, There is a change in beta3 when installing a node, it is now required to install `patterns-caasp-Node` which will then install all the correct packages. Please try again installing this pattern, run `kubeadm reset` and bootstrap again. On 7/9/19 4:31 PM, Ns, Rushi wrote: > Ok good to see that I am not the one having this issue. As I said before standard KUBEADM init and KUBEADM join to make cluster working on the same SUSE 15 SP1 without using SKUBA . seems somewhere skuba is not working with CNI- network as I found through some debug it shows CNI- errors. Look the below. > > > 13518 kubelet.go:2170] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: Missing CNI default network > > BR, > > Rushi. > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE > > > ?On 7/9/19, 7:28 AM, "Lukas Grossar" wrote: > > On Tue, 2019-07-09 at 14:18 +0000, Ann Davis wrote: > > > [...] > > We have another (separate) report of this same error. Apparently it > > did not happen with beta 2... > > I can confirm that I'm currently facing the same issues during a skuba > bootstrap. > > Regards > Lukas > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From roger.klorese at suse.com Mon Jul 15 02:12:10 2019 From: roger.klorese at suse.com (Roger Klorese) Date: Mon, 15 Jul 2019 08:12:10 +0000 Subject: [caasp-beta] SUSE CaaS Platform 4 Beta Access In-Reply-To: References: Message-ID: The instructions are a little convoluted - the beta page points to the FAQ, but the FAQ has instructions for SLE instead of CaaS Platform - but the instructions are actually the same: You might request one via beta-programs at lists.suse.com, Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC ________________________________ From: caasp-beta on behalf of Lancelot Tsai Sent: Sunday, July 7, 2019 8:59 PM To: caasp-beta at lists.suse.com Subject: [caasp-beta] SUSE CaaS Platform 4 Beta Access Dear CaaS Platform Staff, I?m Lancelot from Supermicro. I?m developing a bundle with our server and SUSE CaaSP 4. It seems we need CaaS Platform access code. May I retrieve the access code? Or, who should I contact for this code? Thanks! Best Regards, Lancelot Tsai PM of Enterprise/Cloud Solutions Super Micro Computer, Inc. Taiwan 23511?????????150?3? 3F., No.150, Jian 1st Rd., Zhonghe Dist., New Taipei City 23511, Taiwan (R.O.C.) Tel: +886-2-8226-3990 Ext.3059 Mobile:+886-966751059 [2015-12-23_090153] ________________________________ ?This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 9415 bytes Desc: image001.png URL: From egov-devops at akdb.de Mon Jul 15 05:50:56 2019 From: egov-devops at akdb.de (egov-devops) Date: Mon, 15 Jul 2019 11:50:56 +0000 Subject: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? In-Reply-To: References: <357d4fe2903b4568968e4fcbc2475d52@akdb.de> Message-ID: Howdy list members, Howdy Roger. Many thanks to Roger for his obvious tip, I couldn't see it, cause I'm so so so frustrated with my progress of my caasp 4 beta installation. ;-/ Roger's tip worked as advertised. Now I know my problem, but I couldn't find a solution, yet. It seems that my changed kubeadm-init.conf is reset before it is copied to the caasp-master1. Hence my own image repository (10.255.1.2:5000), which I changed (as mentioned in CaaSP-CAP-POC-Setup-Guide.pdf) beforehand, is reverted to registry.suse.com. Which in our airgap sitiuation is not available. Hence, the bootstrap fails. Output of skuba with -v 5: ... I0715 13:15:55.634379 26691 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" I0715 13:15:55.634476 26691 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents I0715 13:15:55.779811 26691 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" I0715 13:15:55.874646 26691 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 I0715 13:15:55.874743 26691 ssh.go:190] stdout | [preflight] Running pre-flight checks I0715 13:15:55.940883 26691 ssh.go:190] stderr | [WARNING Hostname]: hostname "master1" could not be reached I0715 13:15:55.940915 26691 ssh.go:190] stderr | [WARNING Hostname]: hostname "master1": lookup master1 on 10.255.1.253:53: no such host I0715 13:15:56.090490 26691 ssh.go:190] stdout | [preflight] Pulling images required for setting up a Kubernetes cluster I0715 13:15:56.090516 26691 ssh.go:190] stdout | [preflight] This might take a minute or two, depending on the speed of your internet connection I0715 13:15:56.090522 26691 ssh.go:190] stdout | [preflight] You can also perform this action in beforehand using 'kubeadm config images pull' I0715 13:15:56.236126 26691 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: I0715 13:15:56.236152 26691 ssh.go:190] stderr | [ERROR ImagePull]: failed to pull image registry.suse.com/caasp/v4/hyperkube:v1.14.1: output: time="2019-07-15T13:16:03+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.suse.com/v2/: dial tcp: lookup registry.suse.com on 10.255.1.253:53: no such host" I0715 13:15:56.236162 26691 ssh.go:190] stderr | , error: exit status 1 I0715 13:15:56.236172 26691 ssh.go:190] stderr | [ERROR ImagePull]: failed to pull image registry.suse.com/caasp/v4/pause:3.1: output: time="2019-07-15T13:16:03+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.suse.com/v2/: dial tcp: lookup registry.suse.com on 10.255.1.253:53: no such host" I0715 13:15:56.236177 26691 ssh.go:190] stderr | , error: exit status 1 I0715 13:15:56.236183 26691 ssh.go:190] stderr | [ERROR ImagePull]: failed to pull image registry.suse.com/caasp/v4/etcd:3.3.11: output: time="2019-07-15T13:16:03+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.suse.com/v2/: dial tcp: lookup registry.suse.com on 10.255.1.253:53: no such host" I0715 13:15:56.236189 26691 ssh.go:190] stderr | , error: exit status 1 I0715 13:15:56.236198 26691 ssh.go:190] stderr | [ERROR ImagePull]: failed to pull image registry.suse.com/caasp/v4/coredns:1.2.6: output: time="2019-07-15T13:16:03+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.suse.com/v2/: dial tcp: lookup registry.suse.com on 10.255.1.253:53: no such host" I0715 13:15:56.236204 26691 ssh.go:190] stderr | , error: exit status 1 I0715 13:15:56.236210 26691 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` I0715 13:15:56.238552 26691 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" F0715 13:15:56.321598 26691 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 The registry is available and working: caasp-master1:/tmp # curl --insecure https://10.255.1.2:5000/v2/_catalog { "repositories": [ "cap/cf-usb-sidecar-mysql", "cap/cf-usb-sidecar-mysql-setup", "cap/cf-usb-sidecar-postgres", "cap/cf-usb-sidecar-postgres-setup", "cap/scf-adapter", "cap/scf-api-group", "cap/scf-autoscaler-api", "cap/scf-autoscaler-eventgenerator", "cap/scf-autoscaler-metrics", "cap/scf-autoscaler-operator", "cap/scf-autoscaler-postgres", "cap/scf-autoscaler-scalingengine", "cap/scf-autoscaler-scheduler", "cap/scf-autoscaler-servicebroker", "cap/scf-bits", "cap/scf-blobstore", "cap/scf-cc-clock", "cap/scf-cc-uploader", "cap/scf-cc-worker", "cap/scf-cf-usb-group", "cap/scf-credhub-user", "cap/scf-diego-api", "cap/scf-diego-brain", "cap/scf-diego-cell", "cap/scf-diego-ssh", "cap/scf-doppler", "cap/scf-eirini", "cap/scf-locket", "cap/scf-log-api", "cap/scf-log-cache-scheduler", "cap/scf-loggregator-agent", "cap/scf-mysql", "cap/scf-nats", "cap/scf-nfs-broker", "cap/scf-post-deployment-setup", "cap/scf-router", "cap/scf-routing-api", "cap/scf-secret-generation", "cap/scf-syslog-scheduler", "cap/scf-tcp-router", "cap/stratos-console", "cap/stratos-jetstream", "cap/stratos-mariadb", "cap/stratos-metrics-configmap-reload", "cap/stratos-metrics-firehose-exporter", "cap/stratos-metrics-firehose-init", "cap/stratos-metrics-init-chown-data", "cap/stratos-metrics-nginx", "cap/stratos-metrics-prometheus", "cap/stratos-postflight-job", "cap/uaa-mysql", "cap/uaa-secret-generation", "cap/uaa-uaa", "gcr.io/google-containers/busybox", "gcr.io/kubernetes-helm/tiller", "k8s.gcr.io/kubernetes-dashboard-amd64", "mysql", "quay.io/external_storage/nfs-client-provisioner", "registry.suse.com/caasp/v4/caaspctl-tooling", "registry.suse.com/caasp/v4/cilium", "registry.suse.com/caasp/v4/cilium-etcd-operator", "registry.suse.com/caasp/v4/cilium-init", "registry.suse.com/caasp/v4/cilium-operator", "registry.suse.com/caasp/v4/coredns", "registry.suse.com/caasp/v4/default-http-backend", "registry.suse.com/caasp/v4/dnsmasq-nanny", "registry.suse.com/caasp/v4/etcd", "registry.suse.com/caasp/v4/flannel", "registry.suse.com/caasp/v4/haproxy", "registry.suse.com/caasp/v4/hyperkube", "registry.suse.com/caasp/v4/kubedns", "registry.suse.com/caasp/v4/kured", "registry.suse.com/caasp/v4/mariadb", "registry.suse.com/caasp/v4/nginx-ingress-controller", "registry.suse.com/caasp/v4/openldap", "registry.suse.com/caasp/v4/pause", "registry.suse.com/caasp/v4/registry", "registry.suse.com/caasp/v4/salt-api", "registry.suse.com/caasp/v4/salt-master", "registry.suse.com/caasp/v4/salt-minion", "registry.suse.com/caasp/v4/sidecar", "registry.suse.com/caasp/v4/tiller", "splatform/minibroker" ] } Does anyone have an idea how to keep the changed kubeadm-init.conf, hence my replaced 10.255.1.2:5000 registry entries, intact? Best regards, Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de Von: Roger Klorese Gesendet: Freitag, 12. Juli 2019 10:37 An: egov-devops ; caasp-beta at lists.suse.com Cc: Gergo Kovacs Betreff: Re: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? Often, the default terseness of skuba hides what can be very simple errors to handle from the underlying tools. Try running skuba vith "-v 5" and see if you get a more useful message. Once, I got this message because I missed a step; another time, it was because I had a typo in an option... Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC ________________________________ From: caasp-beta > on behalf of egov-devops > Sent: Friday, July 12, 2019 1:16 AM To: caasp-beta at lists.suse.com Cc: Gergo Kovacs Subject: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? Howdy, I'm trying to bootstrap a caasp 4 beta 3 cluster (https://susedoc.github.io/doc-caasp/beta/caasp-deployment/single-html/#bootstrap). But I get an error: "F0712 09:46:39.270173 13949 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1" So far I have done: 1. ssh-keygen; ssh-add; ssh-copy-id; ssh via sles from "admin" sles server to master{1-3} and node{1-3} via user sles is working 2. Own RMT Server with images as described in CaaSP-CAP-POC-Setup-Guide.pdf setup and working 3. skuba cluster init --control-plane my-cluster -> LB IP we use; 4. Skipped kured (4.1.2.1) and prometheus (4.1.3) changes 5. cd my-cluster 6. skuba node bootstrap --user sles --sudo --target -> IP of master1; NAME master1 ==> skuba node bootstrap --user sles --sudo --target 10.255.1.3 master1 ==> ** This is a BETA release and NOT intended for production usage. ** ==> [bootstrap] updating init configuration with target information ==> [bootstrap] writing init configuration for node ==> [bootstrap] applying init configuration to node ==> F0712 09:46:39.270173 13949 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Master1 setup: - OS SLES 15 SP1 - SUSEConnect stuff as described here (https://susedoc.github.io/doc-caasp/beta/caasp-deployment/single-html/#_preparation_of_the_vm_as_a_template) - SUSEConnect --list-extensions AVAILABLE EXTENSIONS AND MODULES Basesystem Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64 Containers Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p /15.1/x86_64 SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 Server Applications Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-server-applications/15.1/x86_64 Public Cloud Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-public-cloud/15.1/x86_64 - sudo zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins Refreshing service 'SMT-http_smt_akdb_net'. Retrieving repository 'SLE-Module-Basesystem15-SP1-Updates' metadata .......................................[done] Building repository 'SLE-Module-Basesystem15-SP1-Updates' cache ............................................[done] Retrieving repository 'SLE-Module-Containers15-SP1-Updates' metadata .......................................[done] Building repository 'SLE-Module-Containers15-SP1-Updates' cache ............................................[done] Retrieving repository 'SLE-Module-Server-Applications15-SP1-Updates' metadata ..............................[done] Building repository 'SLE-Module-Server-Applications15-SP1-Updates' cache ...................................[done] Loading repository data... Reading installed packages... 'cni-plugins' is already installed. No update candidate for 'cni-plugins-0.7.4-1.11.x86_64'. The highest available version is already installed. 'kubernetes-kubelet' is already installed. No update candidate for 'kubernetes-kubelet-1.14.1-1.8.x86_64'. The highest available version is already installed. 'cri-o' is already installed. No update candidate for 'cri-o-1.14.1-1.2.x86_64'. The highest available version is already installed. 'kubernetes-kubeadm' is already installed. No update candidate for 'kubernetes-kubeadm-1.14.1-1.8.x86_64'. The highest available version is already installed. 'kubernetes-client' is already installed. No update candidate for 'kubernetes-client-1.14.1-1.8.x86_64'. The highest available version is already installed. Resolving package dependencies... Nothing to do. Any idea, what I did wrong? What can I check? What can I fix to make it work? Mit freundlichen Gr??en Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From roger.klorese at suse.com Mon Jul 15 05:57:54 2019 From: roger.klorese at suse.com (Roger Klorese) Date: Mon, 15 Jul 2019 11:57:54 +0000 Subject: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? In-Reply-To: References: <357d4fe2903b4568968e4fcbc2475d52@akdb.de> , Message-ID: Looks to me from the message that the DNS server, not the registry, was unreachable... Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC ________________________________ From: egov-devops Sent: Monday, July 15, 2019 4:50 AM To: caasp-beta at lists.suse.com Cc: Roger Klorese Subject: AW: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? Howdy list members, Howdy Roger. Many thanks to Roger for his obvious tip, I couldn?t see it, cause I?m so so so frustrated with my progress of my caasp 4 beta installation. ;-/ Roger?s tip worked as advertised. Now I know my problem, but I couldn?t find a solution, yet. It seems that my changed kubeadm-init.conf is reset before it is copied to the caasp-master1. Hence my own image repository (10.255.1.2:5000), which I changed (as mentioned in CaaSP-CAP-POC-Setup-Guide.pdf) beforehand, is reverted to registry.suse.com. Which in our airgap sitiuation is not available. Hence, the bootstrap fails. Output of skuba with ?v 5: ? I0715 13:15:55.634379 26691 deployments.go:50] uploading local file "kubeadm-init.conf" to remote file "/tmp/kubeadm-init.conf" I0715 13:15:55.634476 26691 files.go:29] uploading to remote file "/tmp/kubeadm-init.conf" with contents I0715 13:15:55.779811 26691 ssh.go:167] running command: "sudo sh -c 'kubeadm init --config /tmp/kubeadm-init.conf --skip-token-print '" I0715 13:15:55.874646 26691 ssh.go:190] stdout | [init] Using Kubernetes version: v1.14.1 I0715 13:15:55.874743 26691 ssh.go:190] stdout | [preflight] Running pre-flight checks I0715 13:15:55.940883 26691 ssh.go:190] stderr | [WARNING Hostname]: hostname "master1" could not be reached I0715 13:15:55.940915 26691 ssh.go:190] stderr | [WARNING Hostname]: hostname "master1": lookup master1 on 10.255.1.253:53: no such host I0715 13:15:56.090490 26691 ssh.go:190] stdout | [preflight] Pulling images required for setting up a Kubernetes cluster I0715 13:15:56.090516 26691 ssh.go:190] stdout | [preflight] This might take a minute or two, depending on the speed of your internet connection I0715 13:15:56.090522 26691 ssh.go:190] stdout | [preflight] You can also perform this action in beforehand using 'kubeadm config images pull' I0715 13:15:56.236126 26691 ssh.go:190] stderr | error execution phase preflight: [preflight] Some fatal errors occurred: I0715 13:15:56.236152 26691 ssh.go:190] stderr | [ERROR ImagePull]: failed to pull image registry.suse.com/caasp/v4/hyperkube:v1.14.1: output: time="2019-07-15T13:16:03+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.suse.com/v2/: dial tcp: lookup registry.suse.com on 10.255.1.253:53: no such host" I0715 13:15:56.236162 26691 ssh.go:190] stderr | , error: exit status 1 I0715 13:15:56.236172 26691 ssh.go:190] stderr | [ERROR ImagePull]: failed to pull image registry.suse.com/caasp/v4/pause:3.1: output: time="2019-07-15T13:16:03+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.suse.com/v2/: dial tcp: lookup registry.suse.com on 10.255.1.253:53: no such host" I0715 13:15:56.236177 26691 ssh.go:190] stderr | , error: exit status 1 I0715 13:15:56.236183 26691 ssh.go:190] stderr | [ERROR ImagePull]: failed to pull image registry.suse.com/caasp/v4/etcd:3.3.11: output: time="2019-07-15T13:16:03+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.suse.com/v2/: dial tcp: lookup registry.suse.com on 10.255.1.253:53: no such host" I0715 13:15:56.236189 26691 ssh.go:190] stderr | , error: exit status 1 I0715 13:15:56.236198 26691 ssh.go:190] stderr | [ERROR ImagePull]: failed to pull image registry.suse.com/caasp/v4/coredns:1.2.6: output: time="2019-07-15T13:16:03+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.suse.com/v2/: dial tcp: lookup registry.suse.com on 10.255.1.253:53: no such host" I0715 13:15:56.236204 26691 ssh.go:190] stderr | , error: exit status 1 I0715 13:15:56.236210 26691 ssh.go:190] stderr | [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` I0715 13:15:56.238552 26691 ssh.go:167] running command: "sudo sh -c 'rm /tmp/kubeadm-init.conf'" F0715 13:15:56.321598 26691 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 The registry is available and working: caasp-master1:/tmp # curl --insecure https://10.255.1.2:5000/v2/_catalog { "repositories": [ "cap/cf-usb-sidecar-mysql", "cap/cf-usb-sidecar-mysql-setup", "cap/cf-usb-sidecar-postgres", "cap/cf-usb-sidecar-postgres-setup", "cap/scf-adapter", "cap/scf-api-group", "cap/scf-autoscaler-api", "cap/scf-autoscaler-eventgenerator", "cap/scf-autoscaler-metrics", "cap/scf-autoscaler-operator", "cap/scf-autoscaler-postgres", "cap/scf-autoscaler-scalingengine", "cap/scf-autoscaler-scheduler", "cap/scf-autoscaler-servicebroker", "cap/scf-bits", "cap/scf-blobstore", "cap/scf-cc-clock", "cap/scf-cc-uploader", "cap/scf-cc-worker", "cap/scf-cf-usb-group", "cap/scf-credhub-user", "cap/scf-diego-api", "cap/scf-diego-brain", "cap/scf-diego-cell", "cap/scf-diego-ssh", "cap/scf-doppler", "cap/scf-eirini", "cap/scf-locket", "cap/scf-log-api", "cap/scf-log-cache-scheduler", "cap/scf-loggregator-agent", "cap/scf-mysql", "cap/scf-nats", "cap/scf-nfs-broker", "cap/scf-post-deployment-setup", "cap/scf-router", "cap/scf-routing-api", "cap/scf-secret-generation", "cap/scf-syslog-scheduler", "cap/scf-tcp-router", "cap/stratos-console", "cap/stratos-jetstream", "cap/stratos-mariadb", "cap/stratos-metrics-configmap-reload", "cap/stratos-metrics-firehose-exporter", "cap/stratos-metrics-firehose-init", "cap/stratos-metrics-init-chown-data", "cap/stratos-metrics-nginx", "cap/stratos-metrics-prometheus", "cap/stratos-postflight-job", "cap/uaa-mysql", "cap/uaa-secret-generation", "cap/uaa-uaa", "gcr.io/google-containers/busybox", "gcr.io/kubernetes-helm/tiller", "k8s.gcr.io/kubernetes-dashboard-amd64", "mysql", "quay.io/external_storage/nfs-client-provisioner", "registry.suse.com/caasp/v4/caaspctl-tooling", "registry.suse.com/caasp/v4/cilium", "registry.suse.com/caasp/v4/cilium-etcd-operator", "registry.suse.com/caasp/v4/cilium-init", "registry.suse.com/caasp/v4/cilium-operator", "registry.suse.com/caasp/v4/coredns", "registry.suse.com/caasp/v4/default-http-backend", "registry.suse.com/caasp/v4/dnsmasq-nanny", "registry.suse.com/caasp/v4/etcd", "registry.suse.com/caasp/v4/flannel", "registry.suse.com/caasp/v4/haproxy", "registry.suse.com/caasp/v4/hyperkube", "registry.suse.com/caasp/v4/kubedns", "registry.suse.com/caasp/v4/kured", "registry.suse.com/caasp/v4/mariadb", "registry.suse.com/caasp/v4/nginx-ingress-controller", "registry.suse.com/caasp/v4/openldap", "registry.suse.com/caasp/v4/pause", "registry.suse.com/caasp/v4/registry", "registry.suse.com/caasp/v4/salt-api", "registry.suse.com/caasp/v4/salt-master", "registry.suse.com/caasp/v4/salt-minion", "registry.suse.com/caasp/v4/sidecar", "registry.suse.com/caasp/v4/tiller", "splatform/minibroker" ] } Does anyone have an idea how to keep the changed kubeadm-init.conf, hence my replaced 10.255.1.2:5000 registry entries, intact? Best regards, Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de Von: Roger Klorese Gesendet: Freitag, 12. Juli 2019 10:37 An: egov-devops ; caasp-beta at lists.suse.com Cc: Gergo Kovacs Betreff: Re: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? Often, the default terseness of skuba hides what can be very simple errors to handle from the underlying tools. Try running skuba vith "-v 5" and see if you get a more useful message. Once, I got this message because I missed a step; another time, it was because I had a typo in an option... Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC ________________________________ From: caasp-beta > on behalf of egov-devops > Sent: Friday, July 12, 2019 1:16 AM To: caasp-beta at lists.suse.com Cc: Gergo Kovacs Subject: [caasp-beta] Q: Any skuba bootstrap error with kubeadmn known? Howdy, I?m trying to bootstrap a caasp 4 beta 3 cluster (https://susedoc.github.io/doc-caasp/beta/caasp-deployment/single-html/#bootstrap). But I get an error: ?F0712 09:46:39.270173 13949 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1? So far I have done: 1. ssh-keygen; ssh-add; ssh-copy-id; ssh via sles from ?admin? sles server to master{1-3} and node{1-3} via user sles is working 2. Own RMT Server with images as described in CaaSP-CAP-POC-Setup-Guide.pdf setup and working 3. skuba cluster init --control-plane my-cluster -> LB IP we use; 4. Skipped kured (4.1.2.1) and prometheus (4.1.3) changes 5. cd my-cluster 6. skuba node bootstrap --user sles --sudo --target -> IP of master1; NAME master1 ==> skuba node bootstrap --user sles --sudo --target 10.255.1.3 master1 ==> ** This is a BETA release and NOT intended for production usage. ** ==> [bootstrap] updating init configuration with target information ==> [bootstrap] writing init configuration for node ==> [bootstrap] applying init configuration to node ==> F0712 09:46:39.270173 13949 bootstrap.go:48] error bootstraping node: failed to apply state kubeadm.init: Process exited with status 1 Master1 setup: - OS SLES 15 SP1 - SUSEConnect stuff as described here (https://susedoc.github.io/doc-caasp/beta/caasp-deployment/single-html/#_preparation_of_the_vm_as_a_template) - SUSEConnect --list-extensions AVAILABLE EXTENSIONS AND MODULES Basesystem Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64 Containers Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p /15.1/x86_64 SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 Server Applications Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-server-applications/15.1/x86_64 Public Cloud Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-public-cloud/15.1/x86_64 - sudo zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins Refreshing service 'SMT-http_smt_akdb_net'. Retrieving repository 'SLE-Module-Basesystem15-SP1-Updates' metadata .......................................[done] Building repository 'SLE-Module-Basesystem15-SP1-Updates' cache ............................................[done] Retrieving repository 'SLE-Module-Containers15-SP1-Updates' metadata .......................................[done] Building repository 'SLE-Module-Containers15-SP1-Updates' cache ............................................[done] Retrieving repository 'SLE-Module-Server-Applications15-SP1-Updates' metadata ..............................[done] Building repository 'SLE-Module-Server-Applications15-SP1-Updates' cache ...................................[done] Loading repository data... Reading installed packages... 'cni-plugins' is already installed. No update candidate for 'cni-plugins-0.7.4-1.11.x86_64'. The highest available version is already installed. 'kubernetes-kubelet' is already installed. No update candidate for 'kubernetes-kubelet-1.14.1-1.8.x86_64'. The highest available version is already installed. 'cri-o' is already installed. No update candidate for 'cri-o-1.14.1-1.2.x86_64'. The highest available version is already installed. 'kubernetes-kubeadm' is already installed. No update candidate for 'kubernetes-kubeadm-1.14.1-1.8.x86_64'. The highest available version is already installed. 'kubernetes-client' is already installed. No update candidate for 'kubernetes-client-1.14.1-1.8.x86_64'. The highest available version is already installed. Resolving package dependencies... Nothing to do. Any idea, what I did wrong? What can I check? What can I fix to make it work? Mit freundlichen Gr??en Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB ? Anstalt des ?ffentlichen Rechts ? Hauptverwaltung Hansastra?e 12-16 ? 80686 M?nchen ? www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Donaldson at NGIC.COM Mon Jul 15 09:18:59 2019 From: Ian.Donaldson at NGIC.COM (Donaldson, Ian) Date: Mon, 15 Jul 2019 15:18:59 +0000 Subject: [caasp-beta] CaaSP v4 Beta Dashboard Message-ID: <2C9513E8FF804D8AEBFCB8723D7DB94AD7F5272B@unknown> Hello, I have setup a basic v4 Beta cluster. How do I access a dashboard for this? Thanks, Ian ---------------------------------------------------------------------- Note: Please be aware that unencrypted electronic mail is not secure. For this reason, please do not send any sensitive personal information such as your address, driver license, policy number, Social Security Number, or claims information by unencrypted electronic mail. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From CSeader at suse.com Mon Jul 15 11:46:49 2019 From: CSeader at suse.com (Cameron Seader) Date: Mon, 15 Jul 2019 17:46:49 +0000 Subject: [caasp-beta] CaaSP v4 Beta Dashboard In-Reply-To: <2C9513E8FF804D8AEBFCB8723D7DB94AD7F5272B@unknown> References: <2C9513E8FF804D8AEBFCB8723D7DB94AD7F5272B@unknown> Message-ID: What kind of dashboard are you looking for? Kubernetes Dashboard? If your looking for Velum like you saw in CaaSP v3 then you won't find it because its been deprecated in v4. -- Cameron Seader Technology Strategist SUSE cs at suse.com (M)208-420-2167 www.susecon.com ________________________________ From: caasp-beta on behalf of Donaldson, Ian Sent: Monday, July 15, 2019 9:18 AM To: caasp-beta at lists.suse.com Subject: [caasp-beta] CaaSP v4 Beta Dashboard Hello, I have setup a basic v4 Beta cluster. How do I access a dashboard for this? Thanks, Ian ________________________________ Note: Please be aware that unencrypted electronic mail is not secure. For this reason, please do not send any sensitive personal information such as your address, driver license, policy number, Social Security Number, or claims information by unencrypted electronic mail. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Mon Jul 15 12:07:55 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Mon, 15 Jul 2019 18:07:55 +0000 Subject: [caasp-beta] CaaSP v4 Beta Dashboard Message-ID: <981AD125-A5D8-440E-B211-E86E30D311BE@sap.com> If I am not wrong, he is asking about ?kubernetes dashoard ?(not CAASP VELUM) ,. As per CAASP 4 documentation and roadmap somewhere it was stated CAASP 4 ?velum? is deprecated . You can use simple Kubernetes commands to install dashboard and access with either editing the service of Kubernetes dashboard in ?kube-system? to open with NodePort but there is token process that you need follow. Do this step to install dashboard pod. The Dashboard UI is not deployed by default. To deploy it, run the following command: kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta1/aio/deploy/recommended.yaml open service and edit to make with node port Run ?kubectl edit service kubernetes-dashboard -n kube-system? After you can access any nodes port [cid:image001.png at 01D53AFD.8C47F2C0] Accessing the Dashboard UI To protect your cluster data, Dashboard deploys with a minimal RBAC configuration by default. Currently, Dashboard only supports logging in with a Bearer Token. To create a token for this demo, Follow this step to user and create token to access dashboard after install https://github.com/kubernetes/dashboard/wiki/Creating-sample-user BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: caasp-beta on behalf of Cameron Seader Date: Monday, July 15, 2019 at 10:47 AM To: "Donaldson, Ian" , "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CaaSP v4 Beta Dashboard What kind of dashboard are you looking for? Kubernetes Dashboard? If your looking for Velum like you saw in CaaSP v3 then you won't find it because its been deprecated in v4. -- Cameron Seader Technology Strategist SUSE cs at suse.com (M)208-420-2167 www.susecon.com ________________________________ From: caasp-beta on behalf of Donaldson, Ian Sent: Monday, July 15, 2019 9:18 AM To: caasp-beta at lists.suse.com Subject: [caasp-beta] CaaSP v4 Beta Dashboard Hello, I have setup a basic v4 Beta cluster. How do I access a dashboard for this? Thanks, Ian ________________________________ Note: Please be aware that unencrypted electronic mail is not secure. For this reason, please do not send any sensitive personal information such as your address, driver license, policy number, Social Security Number, or claims information by unencrypted electronic mail. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19875 bytes Desc: image001.png URL: From JPrice at suse.com Mon Jul 15 12:11:18 2019 From: JPrice at suse.com (Jeff Price) Date: Mon, 15 Jul 2019 18:11:18 +0000 Subject: [caasp-beta] CaaSP v4 Beta Dashboard In-Reply-To: References: <2C9513E8FF804D8AEBFCB8723D7DB94AD7F5272B@unknown>, Message-ID: Hello, I am attaching a sample module from SUSE Consulting's Delivery Matrix for the Kubernetes Dashboard. It has certain assumptions of Helm/Tiller being available in order to deploy it. This should hopefully help you with the installation, and show you an example/value of SUSE Consulting Services for a roll-out/deployment. Please contact us if your organization is interested in discussing our services. Cheers! -jeff -------------------------------------- Jeff Price Chief Architect SUSE Services jeff at suse.com (m) 612.799.3293 [cid:a513b82e-a5a5-4471-bdc9-b9a2e5e8d015] ________________________________ From: caasp-beta on behalf of Cameron Seader Sent: Monday, July 15, 2019 12:46:49 PM To: Donaldson, Ian; caasp-beta at lists.suse.com Subject: Re: [caasp-beta] CaaSP v4 Beta Dashboard What kind of dashboard are you looking for? Kubernetes Dashboard? If your looking for Velum like you saw in CaaSP v3 then you won't find it because its been deprecated in v4. -- Cameron Seader Technology Strategist SUSE cs at suse.com (M)208-420-2167 www.susecon.com ________________________________ From: caasp-beta on behalf of Donaldson, Ian Sent: Monday, July 15, 2019 9:18 AM To: caasp-beta at lists.suse.com Subject: [caasp-beta] CaaSP v4 Beta Dashboard Hello, I have setup a basic v4 Beta cluster. How do I access a dashboard for this? Thanks, Ian ________________________________ Note: Please be aware that unencrypted electronic mail is not secure. For this reason, please do not send any sensitive personal information such as your address, driver license, policy number, Social Security Number, or claims information by unencrypted electronic mail. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-x4nydk1d.png Type: image/png Size: 3489 bytes Desc: Outlook-x4nydk1d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: suse-consulting-deployment-module-SCDM-CaasPv4-K8s-Dashboard-k8sD (1).pdf Type: application/pdf Size: 863676 bytes Desc: suse-consulting-deployment-module-SCDM-CaasPv4-K8s-Dashboard-k8sD (1).pdf URL: From JPrice at suse.com Mon Jul 15 12:17:46 2019 From: JPrice at suse.com (Jeff Price) Date: Mon, 15 Jul 2019 18:17:46 +0000 Subject: [caasp-beta] CaaSP v4 Beta Dashboard In-Reply-To: References: <2C9513E8FF804D8AEBFCB8723D7DB94AD7F5272B@unknown>, , Message-ID: I should mention... Be very careful if you expect to copy/paste any yaml file examples out of a PDF. I noticed that some of the example yaml content spans pages in the PDF I sent earlier. Copy/paste tends to include page separators and other text and will invalidate the yaml formatting if you aren't cautious. -jeff -------------------------------------- Jeff Price Chief Architect SUSE Services jeff at suse.com (m) 612.799.3293 [cid:fb50011b-5b4f-482c-bf29-925a90754266] ________________________________ From: caasp-beta on behalf of Jeff Price Sent: Monday, July 15, 2019 1:11:18 PM To: Cameron Seader; Donaldson, Ian; caasp-beta at lists.suse.com Subject: Re: [caasp-beta] CaaSP v4 Beta Dashboard Hello, I am attaching a sample module from SUSE Consulting's Delivery Matrix for the Kubernetes Dashboard. It has certain assumptions of Helm/Tiller being available in order to deploy it. This should hopefully help you with the installation, and show you an example/value of SUSE Consulting Services for a roll-out/deployment. Please contact us if your organization is interested in discussing our services. Cheers! -jeff -------------------------------------- Jeff Price Chief Architect SUSE Services jeff at suse.com (m) 612.799.3293 [cid:a513b82e-a5a5-4471-bdc9-b9a2e5e8d015] ________________________________ From: caasp-beta on behalf of Cameron Seader Sent: Monday, July 15, 2019 12:46:49 PM To: Donaldson, Ian; caasp-beta at lists.suse.com Subject: Re: [caasp-beta] CaaSP v4 Beta Dashboard What kind of dashboard are you looking for? Kubernetes Dashboard? If your looking for Velum like you saw in CaaSP v3 then you won't find it because its been deprecated in v4. -- Cameron Seader Technology Strategist SUSE cs at suse.com (M)208-420-2167 www.susecon.com ________________________________ From: caasp-beta on behalf of Donaldson, Ian Sent: Monday, July 15, 2019 9:18 AM To: caasp-beta at lists.suse.com Subject: [caasp-beta] CaaSP v4 Beta Dashboard Hello, I have setup a basic v4 Beta cluster. How do I access a dashboard for this? Thanks, Ian ________________________________ Note: Please be aware that unencrypted electronic mail is not secure. For this reason, please do not send any sensitive personal information such as your address, driver license, policy number, Social Security Number, or claims information by unencrypted electronic mail. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-x4nydk1d.png Type: image/png Size: 3489 bytes Desc: Outlook-x4nydk1d.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-4gmvsdhr.png Type: image/png Size: 3489 bytes Desc: Outlook-4gmvsdhr.png URL: From rob.knight at suse.com Mon Jul 15 09:53:03 2019 From: rob.knight at suse.com (Rob Knight) Date: Mon, 15 Jul 2019 15:53:03 +0000 Subject: [caasp-beta] CaaSP v4 Beta Dashboard In-Reply-To: <2C9513E8FF804D8AEBFCB8723D7DB94AD7F5272B@unknown> References: <2C9513E8FF804D8AEBFCB8723D7DB94AD7F5272B@unknown> Message-ID: Hi Ian. There isn't currently a dashboard for version 4. This is on our roadmap though for future integration in a future release. Adding/removing nodes can be done with the Skuba tooling. Updates can also be applied using the Skuba tool (for Kubernetes updates. OS updates can use any existing SLES-compatible tool). You are free however to deploy the upstream Kubernetes dashboard (via helm or kubectl) or other k8s compatible dashboards such as Kubernetic. Rob ----- Rob de Canha-Knight EMEA Platform and Management Technical Strategist SUSE rob.decanha-knight at suse.com (P) +44 (0) 1635 937689 (M) +44 (0) 7869 113493 (TW) rssfed23 I work in GMT/BST time zone ---- From: caasp-beta On Behalf Of Donaldson, Ian Sent: 15 July 2019 16:19 To: caasp-beta at lists.suse.com Subject: [caasp-beta] CaaSP v4 Beta Dashboard Hello, I have setup a basic v4 Beta cluster. How do I access a dashboard for this? Thanks, Ian ________________________________ Note: Please be aware that unencrypted electronic mail is not secure. For this reason, please do not send any sensitive personal information such as your address, driver license, policy number, Social Security Number, or claims information by unencrypted electronic mail. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Donaldson at NGIC.COM Mon Jul 15 12:33:14 2019 From: Ian.Donaldson at NGIC.COM (Donaldson, Ian) Date: Mon, 15 Jul 2019 18:33:14 +0000 Subject: [caasp-beta] CaaSP v4 Beta Dashboard In-Reply-To: References: <2C9513E8FF804D8AEBFCB8723D7DB94AD7F5272B@unknown>, Message-ID: <389c1584fd354682865053b5745a41dc@WSWPPME001.NGIC.COM> This looks promising, thanks Jeff! Ian From: Jeff Price Sent: Monday, July 15, 2019 2:11 PM To: Cameron Seader ; Donaldson, Ian ; caasp-beta at lists.suse.com Subject: Re: CaaSP v4 Beta Dashboard WARNING: This Message came from an external source. Please exercise caution when opening any attachments or clicking on links. ________________________________ Hello, I am attaching a sample module from SUSE Consulting's Delivery Matrix for the Kubernetes Dashboard. It has certain assumptions of Helm/Tiller being available in order to deploy it. This should hopefully help you with the installation, and show you an example/value of SUSE Consulting Services for a roll-out/deployment. Please contact us if your organization is interested in discussing our services. Cheers! -jeff -------------------------------------- Jeff Price Chief Architect SUSE Services jeff at suse.com (m) 612.799.3293 [cid:image001.png at 01D53B1A.3BD7BB00] ________________________________ From: caasp-beta > on behalf of Cameron Seader Sent: Monday, July 15, 2019 12:46:49 PM To: Donaldson, Ian; caasp-beta at lists.suse.com Subject: Re: [caasp-beta] CaaSP v4 Beta Dashboard What kind of dashboard are you looking for? Kubernetes Dashboard? If your looking for Velum like you saw in CaaSP v3 then you won't find it because its been deprecated in v4. -- Cameron Seader Technology Strategist SUSE cs at suse.com (M)208-420-2167 www.susecon.com ________________________________ From: caasp-beta > on behalf of Donaldson, Ian > Sent: Monday, July 15, 2019 9:18 AM To: caasp-beta at lists.suse.com Subject: [caasp-beta] CaaSP v4 Beta Dashboard Hello, I have setup a basic v4 Beta cluster. How do I access a dashboard for this? Thanks, Ian ________________________________ Note: Please be aware that unencrypted electronic mail is not secure. For this reason, please do not send any sensitive personal information such as your address, driver license, policy number, Social Security Number, or claims information by unencrypted electronic mail. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3489 bytes Desc: image001.png URL: From Ian.Donaldson at NGIC.COM Mon Jul 15 12:34:24 2019 From: Ian.Donaldson at NGIC.COM (Donaldson, Ian) Date: Mon, 15 Jul 2019 18:34:24 +0000 Subject: [caasp-beta] CaaSP v4 Beta Dashboard In-Reply-To: <981AD125-A5D8-440E-B211-E86E30D311BE@sap.com> References: <981AD125-A5D8-440E-B211-E86E30D311BE@sap.com> Message-ID: Rushi, This looks helpful, thanks! Ian From: Ns, Rushi Sent: Monday, July 15, 2019 2:08 PM To: Cameron Seader ; Donaldson, Ian ; caasp-beta at lists.suse.com Subject: Re: [caasp-beta] CaaSP v4 Beta Dashboard WARNING: This Message came from an external source. Please exercise caution when opening any attachments or clicking on links. ________________________________ If I am not wrong, he is asking about ?kubernetes dashoard ?(not CAASP VELUM) ,. As per CAASP 4 documentation and roadmap somewhere it was stated CAASP 4 ?velum? is deprecated . You can use simple Kubernetes commands to install dashboard and access with either editing the service of Kubernetes dashboard in ?kube-system? to open with NodePort but there is token process that you need follow. Do this step to install dashboard pod. The Dashboard UI is not deployed by default. To deploy it, run the following command: kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta1/aio/deploy/recommended.yaml open service and edit to make with node port Run ?kubectl edit service kubernetes-dashboard -n kube-system? After you can access any nodes port [cid:image001.png at 01D53B1A.650C21A0] Accessing the Dashboard UI To protect your cluster data, Dashboard deploys with a minimal RBAC configuration by default. Currently, Dashboard only supports logging in with a Bearer Token. To create a token for this demo, Follow this step to user and create token to access dashboard after install https://github.com/kubernetes/dashboard/wiki/Creating-sample-user BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: caasp-beta > on behalf of Cameron Seader > Date: Monday, July 15, 2019 at 10:47 AM To: "Donaldson, Ian" >, "caasp-beta at lists.suse.com" > Subject: Re: [caasp-beta] CaaSP v4 Beta Dashboard What kind of dashboard are you looking for? Kubernetes Dashboard? If your looking for Velum like you saw in CaaSP v3 then you won't find it because its been deprecated in v4. -- Cameron Seader Technology Strategist SUSE cs at suse.com (M)208-420-2167 www.susecon.com ________________________________ From: caasp-beta > on behalf of Donaldson, Ian > Sent: Monday, July 15, 2019 9:18 AM To: caasp-beta at lists.suse.com Subject: [caasp-beta] CaaSP v4 Beta Dashboard Hello, I have setup a basic v4 Beta cluster. How do I access a dashboard for this? Thanks, Ian ________________________________ Note: Please be aware that unencrypted electronic mail is not secure. For this reason, please do not send any sensitive personal information such as your address, driver license, policy number, Social Security Number, or claims information by unencrypted electronic mail. The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 19875 bytes Desc: image001.png URL: From roger.klorese at suse.com Wed Jul 17 04:40:05 2019 From: roger.klorese at suse.com (Roger Klorese) Date: Wed, 17 Jul 2019 10:40:05 +0000 Subject: [caasp-beta] Beta 4 timing Message-ID: We had intended, as some of you are aware, to release SUSE CaaS Platform 4 Beta 4 by now. It is technically complete and tested. This beta release has the ability to be applied as an update to clusters running Beta 3. In order to do so, we need to set up Update channels. That process is going on now. When that is complete, a notification will be sent out. Thanks for your patience. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at lists.suse.com Wed Jul 17 09:41:14 2019 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Wed, 17 Jul 2019 17:41:14 +0200 Subject: [caasp-beta] [ANNOUNCE] SUSE CaaS Platform 4.0 Beta 4 is out! Message-ID: <5d2f419a63b3_41db5b6684498eb@zourite.lab.gb.mail> We are happy to announce the Beta 4 of SUSE CaaS Platform 4.0. Notable changes in Beta 4 - This beta is being published as an update on top of Beta 3. New packages versions have been provided in Update repository as a proof of concept for the whole maintenance process. Please check out our documentation for upgrading from Beta 3 to Beta 4[1], - Beta 4 also makes platform upgrades possible in addition to the non-interactive base OS. Skuba is now capable with still few manual steps to upgrade Kubernetes and related core tools and images[2], - Beta 4 introduces Role Based Access Control provided by Dex[3] and Gangway[4] tools. Check out our documentation to know more about the Authentication Flow and RBAC Operations[5], - Kubernetes was updated from v1.14.1 (Beta3) to v1.15.0 (Beta4), - SUSE CaaS Platform clusters are passing Sonobuoy conformance tests[6]. For more details, see the Release Notes[7]. Architecture and working features: The architecture of SUSE CaaS Platform 4.0 is described here[8]. This build has been tested on SUSE OpenStack Cloud 8, VMware ESXi 6.7.0 and bare metal. We have validated the following features: - Bootstrapping a cluster - Deploying with Terraform in SUSE OpenStack Cloud and VMware - Deploying with autoyast for Bare Metal - Adding and removing nodes - Deploying, scaling, and exposing nginx:alpine image - PodSecurityPolicy deployment and conformance - Applying Base OS updates - Centralized Logging - Cluster upgrade from Kubernetes 1.14.1 to Kubernetes 1.15.0 (beta 3 to beta 4) Please check our Release Notes[9] for most recent changes and Known Issues[10]. Note that the product is not feature complete yet, we will continue to improve it. Beta Registration codes You should not use a SLES 15 SP1 environment with the SLE Beta Registration Code anymore. Because the SLE Beta Registration Code is expired now but you can either use your regular SLE Registration Code or use a Trial. Registration is not working with your regular key, special Beta Registration Code is required. You need to request one for SUSE CaaS Platform 4.0 Beta Program by contacting us at beta-programs at lists.suse.com[11]. Installation Use the terraform package to install SUSE CaaS Platform. Refer to the Deployment Guide[12]. Beta Page ?[13] Documentation ?[14] Have fun beta testing! Your SUSE CaaS Platform Team Please refer to our dedicated SUSE CaaSP Beta Program[15] webpage for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Click here to unsubscribe.[16] [1]:https://susedoc.github.io/doc-caasp/beta/caasp-admin/sing le-html/#_applying_updates [2]:https://susedoc.github.io/doc-caasp/beta/caasp-admin/sing le-html/#_cluster_updates [3]:https://github.com/dexidp/dex [4]:https://github.com/heptiolabs/gangway [5]:https://susedoc.github.io/doc-caasp/beta/caasp-admin/sing le-html/#_role_based_access_control_rbac [6]:https://sonobuoy.io/ [7]:https://susedoc.github.io/caasp-release-notes/beta/releas e-notes/single-html/ [8]:https://susedoc.github.io/doc-caasp/master/caasp-architec ture/single-html/ [9]:https://www.suse.com/betaprogram/caasp-beta/#releasenotes [10]:https://www.suse.com/betaprogram/caasp-beta/#knownissues [11]:mailto:beta-programs at lists.suse.com?subject=Requesting%2 0SUSE%20CaaSP%204.0%20Beta%20Registration%20Codes&body=Reques ting%20SUSE%20CaaSP%204.0 [12]:https://susedoc.github.io/doc-caasp/master/caasp-deploym ent/single-html/ [13]:https://www.suse.com/betaprogram/caasp-beta [14]:https://www.suse.com/betaprogram/caasp-beta/#documentati on [15]:https://www.suse.com/betaprogram/caasp-beta/ [16]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe% 20from%20SUSE%20CaaSP%20Beta&body=Unsubscribe%20from%20SUSE%2 0CaaSP%20Beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From egov-devops at akdb.de Thu Jul 18 00:40:03 2019 From: egov-devops at akdb.de (egov-devops) Date: Thu, 18 Jul 2019 06:40:03 +0000 Subject: [caasp-beta] Q: CAASP4B4 new cluster / join problem Message-ID: <0c45d9233b59447c96426ef20ac563ae@akdb.de> Howdy, yesterday, finally I got our Airgap install of CAASP4B3 working (only 1 master so far) - Needed to solve internal (AKDB) and external (SUSE) problems to make it work. Today I learned that CASSP4B4 is out, so I tried to set up CAASP4B4 fresh. What have I done so far: 1) made a "kubeadm reset" on master1. To reset the master I set up with CAASP4B3, yesterday 2) updated our "fake" registry.suse.com with new images (see attachment) 3) made a "skuba cluster init --control-plane 10.255.1.2 caasp4b4" 4) made a "skuba node bootstrap -v 5 --user sles --sudo --target 10.255.1.3 caasp-master1" --> [bootstrap] successfully bootstrapped node "10.255.1.3" with Kubernetes: "1.15.0" 5) made a "skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2" --> I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 --> F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join. upload-secrets: Process exited with status 1 Some Background: - ssh from "caasp-admin" via pubkey as sles or root works fine. - Each planned master and node is installed/updated with "zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins sudo" - SUSECOnnect activated: caasp-master1:~ # SUSEConnect --list-extensions AVAILABLE EXTENSIONS AND MODULES Basesystem Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64 Containers Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p /15.1/x86_64 SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 Server Applications Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-server-applications/15.1/x86_64 Public Cloud Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-public-cloud/15.1/x86_64 Any idea what I made wrong? Where can I check? What can I fix? :-/ Many Thanks... Mit freundlichen Gr??en Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB * Anstalt des ?ffentlichen Rechts * Hauptverwaltung M?nchen Hansastr. 12 - 16 * 80686 M?nchen * www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: registry.txt URL: From jean-marc.lambert at suse.com Thu Jul 18 02:43:00 2019 From: jean-marc.lambert at suse.com (Jean Marc Lambert) Date: Thu, 18 Jul 2019 08:43:00 +0000 Subject: [caasp-beta] Q: CAASP4B4 new cluster / join problem In-Reply-To: <0c45d9233b59447c96426ef20ac563ae@akdb.de> References: <0c45d9233b59447c96426ef20ac563ae@akdb.de> Message-ID: One element, is also, (I think it is not yet documented, as I discovered it yesterday) that you need to update the skuba itself on your 'CLI' node. New features in it. Like upgrade plans etc There is a skuba node reset that you may use to reinit the node. JMarc De : caasp-beta De la part de egov-devops Envoy? : jeudi 18 juillet 2019 08:40 ? : caasp-beta at lists.suse.com Cc : Gergo Kovacs Objet : [caasp-beta] Q: CAASP4B4 new cluster / join problem Howdy, yesterday, finally I got our Airgap install of CAASP4B3 working (only 1 master so far) - Needed to solve internal (AKDB) and external (SUSE) problems to make it work. Today I learned that CASSP4B4 is out, so I tried to set up CAASP4B4 fresh. What have I done so far: 1) made a "kubeadm reset" on master1. To reset the master I set up with CAASP4B3, yesterday 2) updated our "fake" registry.suse.com with new images (see attachment) 3) made a "skuba cluster init --control-plane 10.255.1.2 caasp4b4" 4) made a "skuba node bootstrap -v 5 --user sles --sudo --target 10.255.1.3 caasp-master1" --> [bootstrap] successfully bootstrapped node "10.255.1.3" with Kubernetes: "1.15.0" 5) made a "skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2" --> I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 --> F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join. upload-secrets: Process exited with status 1 Some Background: * ssh from "caasp-admin" via pubkey as sles or root works fine. - Each planned master and node is installed/updated with "zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins sudo" * SUSECOnnect activated: caasp-master1:~ # SUSEConnect --list-extensions AVAILABLE EXTENSIONS AND MODULES Basesystem Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64 Containers Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p /15.1/x86_64 SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 Server Applications Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-server-applications/15.1/x86_64 Public Cloud Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-public-cloud/15.1/x86_64 Any idea what I made wrong? Where can I check? What can I fix? :-/ Many Thanks... Mit freundlichen Gr??en Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB * Anstalt des ?ffentlichen Rechts * Hauptverwaltung M?nchen Hansastr. 12 - 16 * 80686 M?nchen * www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From lcavajani at suse.com Thu Jul 18 03:08:34 2019 From: lcavajani at suse.com (Ludovic Cavajani) Date: Thu, 18 Jul 2019 11:08:34 +0200 Subject: [caasp-beta] Q: CAASP4B4 new cluster / join problem In-Reply-To: References: <0c45d9233b59447c96426ef20ac563ae@akdb.de> Message-ID: <883e768b-9e8b-80bf-9a19-c5e7a0f7d803@suse.com> Hi, Updating from `beta3` to `beta4` is possible so there is no need to reset everything. The documentation can be found here: https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_cluster_updates @egov-devops I see you used `-v5` flag, could you share the entire logs if there are no sensitive information from your side ? Is `10.255.1.2` correctly configured as an LB with the 3 masters nodes ? Could you share the configuration if possible ? Thanks, On 7/18/19 10:43 AM, Jean Marc Lambert wrote: > One element, is also, (I think it is not yet documented, as I discovered it yesterday) that you need to update the skuba itself on your 'CLI' node. New features in it. Like upgrade plans etc > There is a skuba node reset that you may use to reinit the node. > JMarc > > De : caasp-beta De la part de egov-devops > Envoy? : jeudi 18 juillet 2019 08:40 > ? : caasp-beta at lists.suse.com > Cc : Gergo Kovacs > Objet : [caasp-beta] Q: CAASP4B4 new cluster / join problem > > Howdy, > > yesterday, finally I got our Airgap install of CAASP4B3 working (only 1 master so far) - Needed to solve internal (AKDB) and external (SUSE) problems to make it work. > > Today I learned that CASSP4B4 is out, so I tried to set up CAASP4B4 fresh. > > What have I done so far: > 1) made a "kubeadm reset" on master1. To reset the master I set up with CAASP4B3, yesterday > 2) updated our "fake" registry.suse.com with new images (see attachment) > 3) made a "skuba cluster init --control-plane 10.255.1.2 caasp4b4" > 4) made a "skuba node bootstrap -v 5 --user sles --sudo --target 10.255.1.3 caasp-master1" > --> [bootstrap] successfully bootstrapped node "10.255.1.3" with Kubernetes: "1.15.0" > 5) made a "skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2" > --> I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 > --> F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join. upload-secrets: Process exited with status 1 > > Some Background: > > * ssh from "caasp-admin" via pubkey as sles or root works fine. > > - Each planned master and node is installed/updated with "zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins sudo" > > * SUSECOnnect activated: > > caasp-master1:~ # SUSEConnect --list-extensions > > AVAILABLE EXTENSIONS AND MODULES > > > > Basesystem Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64 > > > > Containers Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p /15.1/x86_64 > > > > SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) > > Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 > > > > Server Applications Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p sle-module-server-applications/15.1/x86_64 > > > > Public Cloud Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p sle-module-public-cloud/15.1/x86_64 > > > Any idea what I made wrong? Where can I check? What can I fix? :-/ > > Many Thanks... > > Mit freundlichen Gr??en > > Alexander Schie?l > Team DevOps > Gesch?ftsfeld eGovernment > > Telefon +49 800 2553222-65 > egov-devops at adkb.de > __________________________________________________________ > > AKDB * Anstalt des ?ffentlichen Rechts * Hauptverwaltung M?nchen > Hansastr. 12 - 16 * 80686 M?nchen * www.akdb.de > > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From egov-devops at akdb.de Thu Jul 18 03:13:25 2019 From: egov-devops at akdb.de (egov-devops) Date: Thu, 18 Jul 2019 09:13:25 +0000 Subject: [caasp-beta] Q: CAASP4B4 new cluster / join problem In-Reply-To: References: <0c45d9233b59447c96426ef20ac563ae@akdb.de> Message-ID: <1d0362384c1c4fff8c7c3e294eebf8d7@akdb.de> Skuba was updated before, just forgot to mention: caasp-admin:~/caasp4b4 # zypper in skuba Refreshing service 'SMT-http_smt_akdb_net'. Loading repository data... Reading installed packages... 'skuba' is already installed. No update candidate for 'skuba-0.7.1-2.4.1.x86_64'. The highest available version is already installed. Resolving package dependencies... Nothing to do. /AS Von: Jean Marc Lambert Gesendet: Donnerstag, 18. Juli 2019 10:43 An: egov-devops ; caasp-beta at lists.suse.com Cc: Gergo Kovacs Betreff: RE: Q: CAASP4B4 new cluster / join problem One element, is also, (I think it is not yet documented, as I discovered it yesterday) that you need to update the skuba itself on your 'CLI' node. New features in it. Like upgrade plans etc There is a skuba node reset that you may use to reinit the node. JMarc De : caasp-beta > De la part de egov-devops Envoy? : jeudi 18 juillet 2019 08:40 ? : caasp-beta at lists.suse.com Cc : Gergo Kovacs > Objet : [caasp-beta] Q: CAASP4B4 new cluster / join problem Howdy, yesterday, finally I got our Airgap install of CAASP4B3 working (only 1 master so far) - Needed to solve internal (AKDB) and external (SUSE) problems to make it work. Today I learned that CASSP4B4 is out, so I tried to set up CAASP4B4 fresh. What have I done so far: 1) made a "kubeadm reset" on master1. To reset the master I set up with CAASP4B3, yesterday 2) updated our "fake" registry.suse.com with new images (see attachment) 3) made a "skuba cluster init --control-plane 10.255.1.2 caasp4b4" 4) made a "skuba node bootstrap -v 5 --user sles --sudo --target 10.255.1.3 caasp-master1" --> [bootstrap] successfully bootstrapped node "10.255.1.3" with Kubernetes: "1.15.0" 5) made a "skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2" --> I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 --> F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join. upload-secrets: Process exited with status 1 Some Background: - ssh from "caasp-admin" via pubkey as sles or root works fine. - Each planned master and node is installed/updated with "zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins sudo" - SUSECOnnect activated: caasp-master1:~ # SUSEConnect --list-extensions AVAILABLE EXTENSIONS AND MODULES Basesystem Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-basesystem/15.1/x86_64 Containers Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p /15.1/x86_64 SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 Server Applications Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-server-applications/15.1/x86_64 Public Cloud Module 15 SP1 x86_64 (Activated) Deactivate with: SUSEConnect -d -p sle-module-public-cloud/15.1/x86_64 Any idea what I made wrong? Where can I check? What can I fix? :-/ Many Thanks... Mit freundlichen Gr??en Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB * Anstalt des ?ffentlichen Rechts * Hauptverwaltung M?nchen Hansastr. 12 - 16 * 80686 M?nchen * www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From egov-devops at akdb.de Thu Jul 18 03:20:01 2019 From: egov-devops at akdb.de (egov-devops) Date: Thu, 18 Jul 2019 09:20:01 +0000 Subject: [caasp-beta] Q: CAASP4B4 new cluster / join problem In-Reply-To: <883e768b-9e8b-80bf-9a19-c5e7a0f7d803@suse.com> References: <0c45d9233b59447c96426ef20ac563ae@akdb.de> <883e768b-9e8b-80bf-9a19-c5e7a0f7d803@suse.com> Message-ID: <28090f2830504d209d700ed6dba56200@akdb.de> Full output: -----------8<---------- caasp-admin:~/caasp4b4 # skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2 ** This is a BETA release and NOT intended for production usage. ** I0718 08:05:16.208668 20242 loader.go:359] Config loaded from file: admin.conf I0718 08:05:16.209494 20242 round_trippers.go:416] GET https://10.255.1.2:6443/api/v1/nodes/caasp-master2 I0718 08:05:16.209504 20242 round_trippers.go:423] Request Headers: I0718 08:05:16.209510 20242 round_trippers.go:426] Accept: application/json, */* I0718 08:05:16.209517 20242 round_trippers.go:426] User-Agent: skuba/v0.0.0 (linux/amd64) kubernetes/fd919f4I0718 08:05:16.221502 20242 round_trippers.go:441] Response Status: 404 Not Found in 11 milliseconds [join] applying states to new node I0718 08:05:16.221927 20242 states.go:35] === applying state kubernetes.join.upload-secrets === I0718 08:05:16.221937 20242 deployments.go:50] uploading local file "pki/ca.crt" to remote file "/etc/kubernetes/pki/ca.crt" I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 -----------8<---------- LB Config: -----------8<---------- user nginx; worker_processes auto; # load_module lib64/nginx/modules/ngx_http_fancyindex_module.so; # load_module lib64/nginx/modules/ngx_http_geoip_module.so; # load_module lib64/nginx/modules/ngx_http_headers_more_filter_module.so; # load_module lib64/nginx/modules/ngx_http_image_filter_module.so; # load_module lib64/nginx/modules/ngx_http_perl_module.so; # load_module lib64/nginx/modules/ngx_http_xslt_filter_module.so; # load_module lib64/nginx/modules/ngx_mail_module.so; # load_module lib64/nginx/modules/ngx_rtmp_module.so; # load_module lib64/nginx/modules/ngx_stream_geoip_module.so; load_module lib64/nginx/modules/ngx_stream_module.so; #error_log /var/log/nginx/error.log; #error_log /var/log/nginx/error.log notice; #error_log /var/log/nginx/error.log info; #pid /run/nginx.pid; events { worker_connections 1024; use epoll; } stream { log_format proxy '$remote_addr [$time_local] ' '$protocol $status $bytes_sent $bytes_received ' '$session_time "$upstream_addr"'; error_log /var/log/nginx/k8s-masters-lb-error.log; access_log /var/log/nginx/k8s-masters-lb-access.log proxy; upstream k8s-masters { #hash $remote_addr consistent; server caasp-master1:6443 weight=1 max_fails=1; server caasp-master2:6443 weight=1 max_fails=1; server caasp-master3:6443 weight=1 max_fails=1; } server { listen 6443; proxy_connect_timeout 1s; proxy_timeout 3s; proxy_pass k8s-masters; } } -----------8<---------- caasp-admin:~/caasp4b4 # systemctl status nginx.service ? nginx.service - The nginx HTTP and reverse proxy server Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2019-07-02 17:29:59 CEST; 2 weeks 1 days ago Main PID: 1248 (nginx) Tasks: 5 (limit: 4915) Memory: 22.5M CPU: 2min 31.546s CGroup: /system.slice/nginx.service ??1248 nginx: master process /usr/sbin/nginx -g daemon off; ??1249 nginx: worker process ??1250 nginx: worker process ??1251 nginx: worker process ??1252 nginx: worker process Jul 02 17:29:59 caasp-admin systemd[1]: Starting The nginx HTTP and reverse proxy server... Jul 02 17:29:59 caasp-admin nginx[1239]: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok Jul 02 17:29:59 caasp-admin nginx[1239]: nginx: configuration file /etc/nginx/nginx.conf test is successful Jul 02 17:29:59 caasp-admin systemd[1]: Started The nginx HTTP and reverse proxy server. -----------8<---------- /etc/hosts ... 10.255.1.2 admin 10.255.1.3 master1 caasp-master1 10.255.1.4 master2 caasp-master2 10.255.1.5 master3 caasp-master3 10.255.2.14 node1 caasp-node1 10.255.2.15 node2 caasp-node2 10.255.2.16 node3 caasp-node3 -----------8<---------- /AS -----Urspr?ngliche Nachricht----- Von: caasp-beta Im Auftrag von Ludovic Cavajani Gesendet: Donnerstag, 18. Juli 2019 11:09 An: caasp-beta at lists.suse.com Betreff: Re: [caasp-beta] Q: CAASP4B4 new cluster / join problem Hi, Updating from `beta3` to `beta4` is possible so there is no need to reset everything. The documentation can be found here: https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_cluster_updates @egov-devops I see you used `-v5` flag, could you share the entire logs if there are no sensitive information from your side ? Is `10.255.1.2` correctly configured as an LB with the 3 masters nodes ? Could you share the configuration if possible ? Thanks, On 7/18/19 10:43 AM, Jean Marc Lambert wrote: > One element, is also, (I think it is not yet documented, as I > discovered it yesterday) that you need to update the skuba itself on your 'CLI' node. New features in it. Like upgrade plans etc There is a skuba node reset that you may use to reinit the node. > JMarc > > De : caasp-beta De la part de > egov-devops Envoy? : jeudi 18 juillet 2019 08:40 ? : > caasp-beta at lists.suse.com Cc : Gergo Kovacs > Objet : [caasp-beta] Q: CAASP4B4 new cluster / join problem > > Howdy, > > yesterday, finally I got our Airgap install of CAASP4B3 working (only 1 master so far) - Needed to solve internal (AKDB) and external (SUSE) problems to make it work. > > Today I learned that CASSP4B4 is out, so I tried to set up CAASP4B4 fresh. > > What have I done so far: > 1) made a "kubeadm reset" on master1. To reset the master I set up > with CAASP4B3, yesterday > 2) updated our "fake" registry.suse.com with new images (see > attachment) > 3) made a "skuba cluster init --control-plane 10.255.1.2 caasp4b4" > 4) made a "skuba node bootstrap -v 5 --user sles --sudo --target 10.255.1.3 caasp-master1" > --> [bootstrap] successfully bootstrapped node "10.255.1.3" with Kubernetes: "1.15.0" > 5) made a "skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2" > --> I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 > --> F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join. upload-secrets: Process exited with status 1 > > Some Background: > > * ssh from "caasp-admin" via pubkey as sles or root works fine. > > - Each planned master and node is installed/updated with "zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins sudo" > > * SUSECOnnect activated: > > caasp-master1:~ # SUSEConnect --list-extensions > > AVAILABLE EXTENSIONS AND MODULES > > > > Basesystem Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p > sle-module-basesystem/15.1/x86_64 > > > > Containers Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p /15.1/x86_64 > > > > SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) > > Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 > > > > Server Applications Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p > sle-module-server-applications/15.1/x86_64 > > > > Public Cloud Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p > sle-module-public-cloud/15.1/x86_64 > > > Any idea what I made wrong? Where can I check? What can I fix? :-/ > > Many Thanks... > > Mit freundlichen Gr??en > > Alexander Schie?l > Team DevOps > Gesch?ftsfeld eGovernment > > Telefon +49 800 2553222-65 > egov-devops at adkb.de > __________________________________________________________ > > AKDB * Anstalt des ?ffentlichen Rechts * Hauptverwaltung M?nchen > Hansastr. 12 - 16 * 80686 M?nchen * www.akdb.de > > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > Check the mailing list archives or Unsubscribe at > http://lists.suse.com/mailman/listinfo/caasp-beta From jean-marc.lambert at suse.com Thu Jul 18 03:28:13 2019 From: jean-marc.lambert at suse.com (Jean Marc Lambert) Date: Thu, 18 Jul 2019 09:28:13 +0000 Subject: [caasp-beta] Q: CAASP4B4 new cluster / join problem In-Reply-To: <28090f2830504d209d700ed6dba56200@akdb.de> References: <0c45d9233b59447c96426ef20ac563ae@akdb.de> <883e768b-9e8b-80bf-9a19-c5e7a0f7d803@suse.com> <28090f2830504d209d700ed6dba56200@akdb.de> Message-ID: Have you tried to create a new fresh vm to populate your cluster, as while doing that yesterday, I recreated vms rather than reset/join stuff... Maybe some reset are not done properly yet (beta) JMarc -----Message d'origine----- De?: caasp-beta De la part de egov-devops Envoy??: jeudi 18 juillet 2019 11:20 ??: Ludovic Cavajani ; caasp-beta at lists.suse.com Objet?: Re: [caasp-beta] Q: CAASP4B4 new cluster / join problem Full output: -----------8<---------- caasp-admin:~/caasp4b4 # skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2 ** This is a BETA release and NOT intended for production usage. ** I0718 08:05:16.208668 20242 loader.go:359] Config loaded from file: admin.conf I0718 08:05:16.209494 20242 round_trippers.go:416] GET https://10.255.1.2:6443/api/v1/nodes/caasp-master2 I0718 08:05:16.209504 20242 round_trippers.go:423] Request Headers: I0718 08:05:16.209510 20242 round_trippers.go:426] Accept: application/json, */* I0718 08:05:16.209517 20242 round_trippers.go:426] User-Agent: skuba/v0.0.0 (linux/amd64) kubernetes/fd919f4I0718 08:05:16.221502 20242 round_trippers.go:441] Response Status: 404 Not Found in 11 milliseconds [join] applying states to new node I0718 08:05:16.221927 20242 states.go:35] === applying state kubernetes.join.upload-secrets === I0718 08:05:16.221937 20242 deployments.go:50] uploading local file "pki/ca.crt" to remote file "/etc/kubernetes/pki/ca.crt" I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 -----------8<---------- LB Config: -----------8<---------- user nginx; worker_processes auto; # load_module lib64/nginx/modules/ngx_http_fancyindex_module.so; # load_module lib64/nginx/modules/ngx_http_geoip_module.so; # load_module lib64/nginx/modules/ngx_http_headers_more_filter_module.so; # load_module lib64/nginx/modules/ngx_http_image_filter_module.so; # load_module lib64/nginx/modules/ngx_http_perl_module.so; # load_module lib64/nginx/modules/ngx_http_xslt_filter_module.so; # load_module lib64/nginx/modules/ngx_mail_module.so; # load_module lib64/nginx/modules/ngx_rtmp_module.so; # load_module lib64/nginx/modules/ngx_stream_geoip_module.so; load_module lib64/nginx/modules/ngx_stream_module.so; #error_log /var/log/nginx/error.log; #error_log /var/log/nginx/error.log notice; #error_log /var/log/nginx/error.log info; #pid /run/nginx.pid; events { worker_connections 1024; use epoll; } stream { log_format proxy '$remote_addr [$time_local] ' '$protocol $status $bytes_sent $bytes_received ' '$session_time "$upstream_addr"'; error_log /var/log/nginx/k8s-masters-lb-error.log; access_log /var/log/nginx/k8s-masters-lb-access.log proxy; upstream k8s-masters { #hash $remote_addr consistent; server caasp-master1:6443 weight=1 max_fails=1; server caasp-master2:6443 weight=1 max_fails=1; server caasp-master3:6443 weight=1 max_fails=1; } server { listen 6443; proxy_connect_timeout 1s; proxy_timeout 3s; proxy_pass k8s-masters; } } -----------8<---------- caasp-admin:~/caasp4b4 # systemctl status nginx.service ? nginx.service - The nginx HTTP and reverse proxy server Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2019-07-02 17:29:59 CEST; 2 weeks 1 days ago Main PID: 1248 (nginx) Tasks: 5 (limit: 4915) Memory: 22.5M CPU: 2min 31.546s CGroup: /system.slice/nginx.service ??1248 nginx: master process /usr/sbin/nginx -g daemon off; ??1249 nginx: worker process ??1250 nginx: worker process ??1251 nginx: worker process ??1252 nginx: worker process Jul 02 17:29:59 caasp-admin systemd[1]: Starting The nginx HTTP and reverse proxy server... Jul 02 17:29:59 caasp-admin nginx[1239]: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok Jul 02 17:29:59 caasp-admin nginx[1239]: nginx: configuration file /etc/nginx/nginx.conf test is successful Jul 02 17:29:59 caasp-admin systemd[1]: Started The nginx HTTP and reverse proxy server. -----------8<---------- /etc/hosts ... 10.255.1.2 admin 10.255.1.3 master1 caasp-master1 10.255.1.4 master2 caasp-master2 10.255.1.5 master3 caasp-master3 10.255.2.14 node1 caasp-node1 10.255.2.15 node2 caasp-node2 10.255.2.16 node3 caasp-node3 -----------8<---------- /AS -----Urspr?ngliche Nachricht----- Von: caasp-beta Im Auftrag von Ludovic Cavajani Gesendet: Donnerstag, 18. Juli 2019 11:09 An: caasp-beta at lists.suse.com Betreff: Re: [caasp-beta] Q: CAASP4B4 new cluster / join problem Hi, Updating from `beta3` to `beta4` is possible so there is no need to reset everything. The documentation can be found here: https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_cluster_updates @egov-devops I see you used `-v5` flag, could you share the entire logs if there are no sensitive information from your side ? Is `10.255.1.2` correctly configured as an LB with the 3 masters nodes ? Could you share the configuration if possible ? Thanks, On 7/18/19 10:43 AM, Jean Marc Lambert wrote: > One element, is also, (I think it is not yet documented, as I > discovered it yesterday) that you need to update the skuba itself on your 'CLI' node. New features in it. Like upgrade plans etc There is a skuba node reset that you may use to reinit the node. > JMarc > > De : caasp-beta De la part de > egov-devops Envoy? : jeudi 18 juillet 2019 08:40 ? : > caasp-beta at lists.suse.com Cc : Gergo Kovacs > Objet : [caasp-beta] Q: CAASP4B4 new cluster / join problem > > Howdy, > > yesterday, finally I got our Airgap install of CAASP4B3 working (only 1 master so far) - Needed to solve internal (AKDB) and external (SUSE) problems to make it work. > > Today I learned that CASSP4B4 is out, so I tried to set up CAASP4B4 fresh. > > What have I done so far: > 1) made a "kubeadm reset" on master1. To reset the master I set up > with CAASP4B3, yesterday > 2) updated our "fake" registry.suse.com with new images (see > attachment) > 3) made a "skuba cluster init --control-plane 10.255.1.2 caasp4b4" > 4) made a "skuba node bootstrap -v 5 --user sles --sudo --target 10.255.1.3 caasp-master1" > --> [bootstrap] successfully bootstrapped node "10.255.1.3" with Kubernetes: "1.15.0" > 5) made a "skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2" > --> I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 > --> F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join. upload-secrets: Process exited with status 1 > > Some Background: > > * ssh from "caasp-admin" via pubkey as sles or root works fine. > > - Each planned master and node is installed/updated with "zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins sudo" > > * SUSECOnnect activated: > > caasp-master1:~ # SUSEConnect --list-extensions > > AVAILABLE EXTENSIONS AND MODULES > > > > Basesystem Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p > sle-module-basesystem/15.1/x86_64 > > > > Containers Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p /15.1/x86_64 > > > > SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) > > Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 > > > > Server Applications Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p > sle-module-server-applications/15.1/x86_64 > > > > Public Cloud Module 15 SP1 x86_64 (Activated) > > Deactivate with: SUSEConnect -d -p > sle-module-public-cloud/15.1/x86_64 > > > Any idea what I made wrong? Where can I check? What can I fix? :-/ > > Many Thanks... > > Mit freundlichen Gr??en > > Alexander Schie?l > Team DevOps > Gesch?ftsfeld eGovernment > > Telefon +49 800 2553222-65 > egov-devops at adkb.de > __________________________________________________________ > > AKDB * Anstalt des ?ffentlichen Rechts * Hauptverwaltung M?nchen > Hansastr. 12 - 16 * 80686 M?nchen * www.akdb.de > > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > Check the mailing list archives or Unsubscribe at > http://lists.suse.com/mailman/listinfo/caasp-beta _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/caasp-beta From lcavajani at suse.com Thu Jul 18 03:31:51 2019 From: lcavajani at suse.com (Ludovic Cavajani) Date: Thu, 18 Jul 2019 11:31:51 +0200 Subject: [caasp-beta] Q: CAASP4B4 new cluster / join problem In-Reply-To: References: <0c45d9233b59447c96426ef20ac563ae@akdb.de> <883e768b-9e8b-80bf-9a19-c5e7a0f7d803@suse.com> <28090f2830504d209d700ed6dba56200@akdb.de> Message-ID: It is possible that the LB is sending a request to a master which is not ready. Can you try to remove the other masters from the nginx configuration: From: upstream k8s-masters { #hash $remote_addr consistent; server caasp-master1:6443 weight=1 max_fails=1; server caasp-master2:6443 weight=1 max_fails=1; server caasp-master3:6443 weight=1 max_fails=1; } To upstream k8s-masters { #hash $remote_addr consistent; server caasp-master1:6443 weight=1 max_fails=1; } And once all the masters are deployed, readding them. On 7/18/19 11:28 AM, Jean Marc Lambert wrote: > Have you tried to create a new fresh vm to populate your cluster, as while doing that yesterday, I recreated vms rather than reset/join stuff... > Maybe some reset are not done properly yet (beta) > JMarc > > -----Message d'origine----- > De?: caasp-beta De la part de egov-devops > Envoy??: jeudi 18 juillet 2019 11:20 > ??: Ludovic Cavajani ; caasp-beta at lists.suse.com > Objet?: Re: [caasp-beta] Q: CAASP4B4 new cluster / join problem > > Full output: > -----------8<---------- > caasp-admin:~/caasp4b4 # skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2 > ** This is a BETA release and NOT intended for production usage. ** > I0718 08:05:16.208668 20242 loader.go:359] Config loaded from file: admin.conf > I0718 08:05:16.209494 20242 round_trippers.go:416] GET https://10.255.1.2:6443/api/v1/nodes/caasp-master2 > I0718 08:05:16.209504 20242 round_trippers.go:423] Request Headers: > I0718 08:05:16.209510 20242 round_trippers.go:426] Accept: application/json, */* > I0718 08:05:16.209517 20242 round_trippers.go:426] User-Agent: skuba/v0.0.0 (linux/amd64) kubernetes/fd919f4I0718 08:05:16.221502 20242 round_trippers.go:441] Response Status: 404 Not Found in 11 milliseconds > [join] applying states to new node > I0718 08:05:16.221927 20242 states.go:35] === applying state kubernetes.join.upload-secrets === > I0718 08:05:16.221937 20242 deployments.go:50] uploading local file "pki/ca.crt" to remote file "/etc/kubernetes/pki/ca.crt" > I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents > [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 > F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 > -----------8<---------- > > LB Config: > -----------8<---------- > user nginx; > worker_processes auto; > > # load_module lib64/nginx/modules/ngx_http_fancyindex_module.so; > # load_module lib64/nginx/modules/ngx_http_geoip_module.so; > # load_module lib64/nginx/modules/ngx_http_headers_more_filter_module.so; > # load_module lib64/nginx/modules/ngx_http_image_filter_module.so; > # load_module lib64/nginx/modules/ngx_http_perl_module.so; > # load_module lib64/nginx/modules/ngx_http_xslt_filter_module.so; > # load_module lib64/nginx/modules/ngx_mail_module.so; > # load_module lib64/nginx/modules/ngx_rtmp_module.so; > # load_module lib64/nginx/modules/ngx_stream_geoip_module.so; > load_module lib64/nginx/modules/ngx_stream_module.so; > > #error_log /var/log/nginx/error.log; > #error_log /var/log/nginx/error.log notice; #error_log /var/log/nginx/error.log info; > > #pid /run/nginx.pid; > > > events { > worker_connections 1024; > use epoll; > } > > stream { > log_format proxy '$remote_addr [$time_local] ' > '$protocol $status $bytes_sent $bytes_received ' > '$session_time "$upstream_addr"'; > > error_log /var/log/nginx/k8s-masters-lb-error.log; > access_log /var/log/nginx/k8s-masters-lb-access.log proxy; > > upstream k8s-masters { > #hash $remote_addr consistent; > server caasp-master1:6443 weight=1 max_fails=1; > server caasp-master2:6443 weight=1 max_fails=1; > server caasp-master3:6443 weight=1 max_fails=1; > } > > server { > listen 6443; > proxy_connect_timeout 1s; > proxy_timeout 3s; > proxy_pass k8s-masters; > } > } > -----------8<---------- > caasp-admin:~/caasp4b4 # systemctl status nginx.service ? nginx.service - The nginx HTTP and reverse proxy server > Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled) > Active: active (running) since Tue 2019-07-02 17:29:59 CEST; 2 weeks 1 days ago Main PID: 1248 (nginx) > Tasks: 5 (limit: 4915) > Memory: 22.5M > CPU: 2min 31.546s > CGroup: /system.slice/nginx.service > ??1248 nginx: master process /usr/sbin/nginx -g daemon off; > ??1249 nginx: worker process > ??1250 nginx: worker process > ??1251 nginx: worker process > ??1252 nginx: worker process > > Jul 02 17:29:59 caasp-admin systemd[1]: Starting The nginx HTTP and reverse proxy server... > Jul 02 17:29:59 caasp-admin nginx[1239]: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok Jul 02 17:29:59 caasp-admin nginx[1239]: nginx: configuration file /etc/nginx/nginx.conf test is successful Jul 02 17:29:59 caasp-admin systemd[1]: Started The nginx HTTP and reverse proxy server. > -----------8<---------- > /etc/hosts > ... > 10.255.1.2 admin > 10.255.1.3 master1 caasp-master1 > 10.255.1.4 master2 caasp-master2 > 10.255.1.5 master3 caasp-master3 > 10.255.2.14 node1 caasp-node1 > 10.255.2.15 node2 caasp-node2 > 10.255.2.16 node3 caasp-node3 > -----------8<---------- > > /AS > > -----Urspr?ngliche Nachricht----- > Von: caasp-beta Im Auftrag von Ludovic Cavajani > Gesendet: Donnerstag, 18. Juli 2019 11:09 > An: caasp-beta at lists.suse.com > Betreff: Re: [caasp-beta] Q: CAASP4B4 new cluster / join problem > > Hi, > > Updating from `beta3` to `beta4` is possible so there is no need to reset everything. The documentation can be found here: > https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_cluster_updates > > @egov-devops I see you used `-v5` flag, could you share the entire logs if there are no sensitive information from your side ? Is `10.255.1.2` correctly configured as an LB with the 3 masters nodes ? Could you share the configuration if possible ? > > Thanks, > > > On 7/18/19 10:43 AM, Jean Marc Lambert wrote: >> One element, is also, (I think it is not yet documented, as I >> discovered it yesterday) that you need to update the skuba itself on your 'CLI' node. New features in it. Like upgrade plans etc There is a skuba node reset that you may use to reinit the node. >> JMarc >> >> De : caasp-beta De la part de >> egov-devops Envoy? : jeudi 18 juillet 2019 08:40 ? : >> caasp-beta at lists.suse.com Cc : Gergo Kovacs >> Objet : [caasp-beta] Q: CAASP4B4 new cluster / join problem >> >> Howdy, >> >> yesterday, finally I got our Airgap install of CAASP4B3 working (only 1 master so far) - Needed to solve internal (AKDB) and external (SUSE) problems to make it work. >> >> Today I learned that CASSP4B4 is out, so I tried to set up CAASP4B4 fresh. >> >> What have I done so far: >> 1) made a "kubeadm reset" on master1. To reset the master I set up >> with CAASP4B3, yesterday >> 2) updated our "fake" registry.suse.com with new images (see >> attachment) >> 3) made a "skuba cluster init --control-plane 10.255.1.2 caasp4b4" >> 4) made a "skuba node bootstrap -v 5 --user sles --sudo --target 10.255.1.3 caasp-master1" >> --> [bootstrap] successfully bootstrapped node "10.255.1.3" with Kubernetes: "1.15.0" >> 5) made a "skuba node join -v 5 --role master --user sles --sudo --target 10.255.1.4 caasp-master2" >> --> I0718 08:05:16.221988 20242 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 >> --> F0718 08:05:16.503251 20242 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join. upload-secrets: Process exited with status 1 >> >> Some Background: >> >> * ssh from "caasp-admin" via pubkey as sles or root works fine. >> >> - Each planned master and node is installed/updated with "zypper in kubernetes-kubeadm kubernetes-kubelet kubernetes-client cri-o cni-plugins sudo" >> >> * SUSECOnnect activated: >> >> caasp-master1:~ # SUSEConnect --list-extensions >> >> AVAILABLE EXTENSIONS AND MODULES >> >> >> >> Basesystem Module 15 SP1 x86_64 (Activated) >> >> Deactivate with: SUSEConnect -d -p >> sle-module-basesystem/15.1/x86_64 >> >> >> >> Containers Module 15 SP1 x86_64 (Activated) >> >> Deactivate with: SUSEConnect -d -p /15.1/x86_64 >> >> >> >> SUSE CaaS Platform 4.0 x86_64 (BETA) (Activated) >> >> Deactivate with: SUSEConnect -d -p caasp/4.0/x86_64 >> >> >> >> Server Applications Module 15 SP1 x86_64 (Activated) >> >> Deactivate with: SUSEConnect -d -p >> sle-module-server-applications/15.1/x86_64 >> >> >> >> Public Cloud Module 15 SP1 x86_64 (Activated) >> >> Deactivate with: SUSEConnect -d -p >> sle-module-public-cloud/15.1/x86_64 >> >> >> Any idea what I made wrong? Where can I check? What can I fix? :-/ >> >> Many Thanks... >> >> Mit freundlichen Gr??en >> >> Alexander Schie?l >> Team DevOps >> Gesch?ftsfeld eGovernment >> >> Telefon +49 800 2553222-65 >> egov-devops at adkb.de >> __________________________________________________________ >> >> AKDB * Anstalt des ?ffentlichen Rechts * Hauptverwaltung M?nchen >> Hansastr. 12 - 16 * 80686 M?nchen * www.akdb.de >> >> >> >> _______________________________________________ >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> Check the mailing list archives or Unsubscribe at >> http://lists.suse.com/mailman/listinfo/caasp-beta > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From carsten.duch at suse.com Fri Jul 19 04:06:22 2019 From: carsten.duch at suse.com (Carsten Duch) Date: Fri, 19 Jul 2019 10:06:22 +0000 Subject: [caasp-beta] Problem adding additional node to cluster after 24h Message-ID: Hi all, I recently installed CaaSP 4 with a customer. We tried to add another worker node after >24h to the cluster. But skuba failed to deploy the node. 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: https://github.com/kubernetes/kubeadm/issues/1310 This is the debug output we got: I0718 19:19:52.762272 12629 ssh.go:190] stdout | [preflight] Running pre-flight checks I0718 19:19:52.889960 12629 ssh.go:190] stdout | [preflight] Reading configuration from the cluster... 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' 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 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" I0718 19:19:53.373248 12629 ssh.go:167] running command: "rm /tmp/kubeadm-init.conf" [join] failed to apply join to node failed to apply state kubeadm.join: Process exited with status 1 F0718 19:19:53.402383 12629 join.go:49] error joining node s030v0302: failed to apply state kubeadm.join: Process exited with status 1 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. Mit freundlichem Gru? / Best regards Carsten Duch Sales Engineer SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 N?rnberg (P)+49 173 5876 707 carsten.duch at suse.com -- SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmassaguerpla at suse.de Fri Jul 19 04:56:58 2019 From: jmassaguerpla at suse.de (Jordi Massaguer Pla) Date: Fri, 19 Jul 2019 12:56:58 +0200 Subject: [caasp-beta] Problem adding additional node to cluster after 24h In-Reply-To: References: Message-ID: Hi Carsten, this looks indeed like a bug. Could you open a bug in bugzilla about it? https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SUSE%20CaaS%20Platform%204 thanks for your feedback! On 07/19/2019 12:06 PM, Carsten Duch wrote: > > Hi all, > > I recently installed CaaSP 4 with a customer. > > We tried to add another worker node after >24h to the cluster. > > But skuba failed to deploy the node. > > 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: > > https://github.com/kubernetes/kubeadm/issues/1310 > > This is the debug output we got: > > I0718 19:19:52.762272?? 12629 ssh.go:190] stdout | [preflight] Running > pre-flight checks > > I0718 19:19:52.889960?? 12629 ssh.go:190] stdout | [preflight] Reading > configuration from the cluster... > > 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' > > 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 > > 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" > > I0718 19:19:53.373248?? 12629 ssh.go:167] running command: "rm > /tmp/kubeadm-init.conf" > > [join] failed to apply join to node failed to apply state > kubeadm.join: Process exited with status 1 > > F0718 19:19:53.402383?? 12629 join.go:49] error joining node > s030v0302: failed to apply state kubeadm.join: Process exited with > status 1 > > 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. > > Mit freundlichem Gru? / Best regards > > Carsten Duch > > Sales Engineer > > SUSE Software Solutions Germany GmbH > > Maxfeldstr. 5 > > 90409 N?rnberg > > (P)+49 173 5876 707 > > carsten.duch at suse.com > > -- > > SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, > HRB 21284 (AG N?rnberg) > > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/caasp-beta -- Jordi Massaguer Pla Release Manager for SUSE CaaS Platform SUSE Linux https://www.suse.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From roy.siek at innogy.com Fri Jul 19 05:36:54 2019 From: roy.siek at innogy.com (roy.siek at innogy.com) Date: Fri, 19 Jul 2019 11:36:54 +0000 Subject: [caasp-beta] Problem adding additional node to cluster after 24h In-Reply-To: References: Message-ID: Hi all, 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: Start by "skuba node join --v 9 --role worker --target $HOSTNAME $HOSTNAME" Updating the whole cluster (still in beta status) did not work for me. There is a hint in the kubeadm forums that the join token for kubeadm get's invalid after 24h In this rare case you can just hop to you first kubernetes master and type: kubeadm token create --print-join-command Copy that string and run it on the destination worker node to join the cluster. After that "kubectl get nodes" will may show that node as "Not Ready" but as member of the cluster. Follow the Suse upgrade node documentation for CaaS and the node will be shown as "Ready". Regards Roy ________________________________ Von: Carsten Duch Gesendet: Freitag, 19. Juli 2019 12:06:22 An: caasp-beta at lists.suse.com Betreff: Problem adding additional node to cluster after 24h Hi all, I recently installed CaaSP 4 with a customer. We tried to add another worker node after >24h to the cluster. But skuba failed to deploy the node. 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: https://github.com/kubernetes/kubeadm/issues/1310 This is the debug output we got: I0718 19:19:52.762272 12629 ssh.go:190] stdout | [preflight] Running pre-flight checks I0718 19:19:52.889960 12629 ssh.go:190] stdout | [preflight] Reading configuration from the cluster... 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' 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 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" I0718 19:19:53.373248 12629 ssh.go:167] running command: "rm /tmp/kubeadm-init.conf" [join] failed to apply join to node failed to apply state kubeadm.join: Process exited with status 1 F0718 19:19:53.402383 12629 join.go:49] error joining node s030v0302: failed to apply state kubeadm.join: Process exited with status 1 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. Mit freundlichem Gru? / Best regards Carsten Duch Sales Engineer SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 N?rnberg (P)+49 173 5876 707 carsten.duch at suse.com -- SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) ---------------------------------------------------------------- innogy SE Vorsitzender des Aufsichtsrates: Dr. Erhard Schipporeit Vorstand: Uwe Tigges (Vorsitzender), Dr. Hans Buenting, Dr. Bernhard Guenther, Arno Hahn, Martin Herrmann, Hildegard Mueller Sitz der Gesellschaft: Essen, Eingetragen beim Amtsgericht Essen, Handelsregister-Nr. HRB 27091, USt-IdNr. DE304171711 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kukuk at suse.de Fri Jul 19 05:44:37 2019 From: kukuk at suse.de (Thorsten Kukuk) Date: Fri, 19 Jul 2019 13:44:37 +0200 Subject: [caasp-beta] Problem adding additional node to cluster after 24h In-Reply-To: References: Message-ID: <20190719114437.GA2645@suse.de> On Fri, Jul 19, roy.siek at innogy.com wrote: > There is a hint in the kubeadm forums that the join token for kubeadm get's > invalid after 24h Correct, that's well documented in the kubeadm documentation and you can list the current TTL of existing tokens with: # kubeadm token list Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) From roger.klorese at suse.com Fri Jul 19 05:47:09 2019 From: roger.klorese at suse.com (Roger Klorese) Date: Fri, 19 Jul 2019 11:47:09 +0000 Subject: [caasp-beta] Problem adding additional node to cluster after 24h In-Reply-To: <20190719114437.GA2645@suse.de> References: , <20190719114437.GA2645@suse.de> Message-ID: Since we're wrapping kubeadm in CaaSP for most stuff, however, we should document it in CaaSP. Roger B.A. Klorese Senior Product Manager SUSE 705 5th Ave S, Suite 1000 Seattle WA 98104 (P)+1 206.217.7432 (M)+1 425.444.5493 roger.klorese at suse.com Schedule a meeting: https://doodle.com/RogerKlorese GPG Key: D567 F186 A6AE D244 067E 95E4 E67D 019F 0670 D9CC ________________________________ From: caasp-beta on behalf of Thorsten Kukuk Sent: Friday, July 19, 2019 4:44 AM To: caasp-beta at lists.suse.com Subject: Re: [caasp-beta] Problem adding additional node to cluster after 24h On Fri, Jul 19, roy.siek at innogy.com wrote: > There is a hint in the kubeadm forums that the join token for kubeadm get's > invalid after 24h Correct, that's well documented in the kubeadm documentation and you can list the current TTL of existing tokens with: # kubeadm token list Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From rfernandezlopez at suse.com Fri Jul 19 06:06:52 2019 From: rfernandezlopez at suse.com (Rafael Fernandez Lopez) Date: Fri, 19 Jul 2019 12:06:52 +0000 Subject: [caasp-beta] Problem adding additional node to cluster after 24h In-Reply-To: References: Message-ID: Hello, On Fri, 2019-07-19 at 11:36 +0000, roy.siek at innogy.com wrote: > Hi all, > > > 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: > > Start by "skuba node join --v 9 --role worker --target $HOSTNAME > $HOSTNAME" > > Updating the whole cluster (still in beta status) did not work for > me. > > There is a hint in the kubeadm forums that the join token for kubeadm > get's invalid after 24h > In this rare case you can just hop to you first kubernetes master and > type: > kubeadm token create --print-join-command When joining a new node from the cluster definition folder, `skuba` will create this token automatically for you (using the `admin.conf` kubeconfig file in the cluster definition folder) and insert it on the configuration of the new node that is joining, so there should be no need to worry about the join token. Thank you, Rafa. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: This is a digitally signed message part URL: From roy.siek at innogy.com Fri Jul 19 06:33:14 2019 From: roy.siek at innogy.com (roy.siek at innogy.com) Date: Fri, 19 Jul 2019 12:33:14 +0000 Subject: [caasp-beta] Problem adding additional node to cluster after 24h In-Reply-To: References: , Message-ID: Hi Rafa, I did that together with Carsten and it did not work ... in any case (please refere to carsten.duch at suse.com). This was the only way to get it running after all tries (and multiple tries reinstalling the worker node). Cheers Roy ________________________________ Von: Rafael Fernandez Lopez Gesendet: Freitag, 19. Juli 2019 14:06:52 An: Carsten Duch ; caasp-beta at lists.suse.com ; Siek, Roy Betreff: Re: [caasp-beta] Problem adding additional node to cluster after 24h Hello, On Fri, 2019-07-19 at 11:36 +0000, roy.siek at innogy.com wrote: > Hi all, > > > 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: > > Start by "skuba node join --v 9 --role worker --target $HOSTNAME > $HOSTNAME" > > Updating the whole cluster (still in beta status) did not work for > me. > > There is a hint in the kubeadm forums that the join token for kubeadm > get's invalid after 24h > In this rare case you can just hop to you first kubernetes master and > type: > kubeadm token create --print-join-command When joining a new node from the cluster definition folder, `skuba` will create this token automatically for you (using the `admin.conf` kubeconfig file in the cluster definition folder) and insert it on the configuration of the new node that is joining, so there should be no need to worry about the join token. Thank you, Rafa. ---------------------------------------------------------------- innogy SE Vorsitzender des Aufsichtsrates: Dr. Erhard Schipporeit Vorstand: Uwe Tigges (Vorsitzender), Dr. Hans Buenting, Dr. Bernhard Guenther, Arno Hahn, Martin Herrmann, Hildegard Mueller Sitz der Gesellschaft: Essen, Eingetragen beim Amtsgericht Essen, Handelsregister-Nr. HRB 27091, USt-IdNr. DE304171711 -------------- next part -------------- An HTML attachment was scrubbed... URL: From egov-devops at akdb.de Mon Jul 22 07:10:58 2019 From: egov-devops at akdb.de (egov-devops) Date: Mon, 22 Jul 2019 13:10:58 +0000 Subject: [caasp-beta] Q: How to get more output from skuba? Message-ID: <2e2f3a50f9954ee0a2662d56c813d5e8@akdb.de> Howdy, I'm still stuck at joining my second master "master2", after initially bootstrapping master1, successfully and an supposedly running cluster. caasp-admin:~/caasp4b4 # skuba cluster status ** This is a BETA release and NOT intended for production usage. ** NAME OS-IMAGE KERNEL-VERSION KUBELET-VERSION CONTAINER-RUNTIME HAS-UPDATES HAS-DISRUPTIVE-UPDATES caasp-master1 SUSE Linux Enterprise Server 15 SP1 4.12.14-197.10-default v1.15.0 cri-o://1.15.0 no no Is there a way to get more debug output from skuba? Yes, I've already set -v 9, see my command bleow... I still get the error: caasp-admin:~/caasp4b4 # skuba node join -v 9 --role master --user sles --sudo --target 10.255.1.4 caasp-master2 2 >&1 | tee out.m2.txt ** This is a BETA release and NOT intended for production usage. ** I0722 15:03:19.034550 8926 loader.go:359] Config loaded from file: admin.conf I0722 15:03:19.035579 8926 round_trippers.go:419] curl -k -v -XGET -H "Accept: application/json, */*" -H "User -Agent: skuba/v0.0.0 (linux/amd64) kubernetes/fd919f4" 'https://10.255.1.2:6443/api/v1/nodes/caasp-master2' I0722 15:03:19.047282 8926 round_trippers.go:438] GET https://10.255.1.2:6443/api/v1/nodes/caasp-master2 404 No t Found in 11 milliseconds I0722 15:03:19.047359 8926 round_trippers.go:444] Response Headers: I0722 15:03:19.047388 8926 round_trippers.go:447] Content-Type: application/json I0722 15:03:19.047415 8926 round_trippers.go:447] Content-Length: 196 I0722 15:03:19.047444 8926 round_trippers.go:447] Date: Mon, 22 Jul 2019 13:03:30 GMT I0722 15:03:19.047510 8926 request.go:947] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"sta tus":"Failure","message":"nodes \"caasp-master2\" not found","reason":"NotFound","details":{"name":"caasp-master2" ,"kind":"nodes"},"code":404} [join] applying states to new node I0722 15:03:19.047945 8926 states.go:35] === applying state kubernetes.join.upload-secrets === I0722 15:03:19.047981 8926 deployments.go:50] uploading local file "pki/ca.crt" to remote file "/etc/kubernetes /pki/ca.crt" I0722 15:03:19.048080 8926 files.go:29] uploading to remote file "/etc/kubernetes/pki/ca.crt" with contents [join] failed to apply join to node failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 F0722 15:03:19.318024 8926 join.go:50] error joining node caasp-master2: failed to apply state kubernetes.join.upload-secrets: Process exited with status 1 So how to debug, what the problem is? Mit freundlichen Gr??en Alexander Schie?l Team DevOps Gesch?ftsfeld eGovernment Telefon +49 800 2553222-65 egov-devops at adkb.de __________________________________________________________ AKDB * Anstalt des ?ffentlichen Rechts * Hauptverwaltung M?nchen Hansastr. 12 - 16 * 80686 M?nchen * www.akdb.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.lebihan at amundi.com Thu Jul 25 10:31:42 2019 From: stephane.lebihan at amundi.com (=?iso-8859-1?Q?Le_Bihan_St=E9phane_=28AMUNDI-ITS=29?=) Date: Thu, 25 Jul 2019 16:31:42 +0000 Subject: [caasp-beta] How make skuba search image in local registry Message-ID: <78852a427f0f40a5b5ab13e4f4bcb406@amundi.com> Hi all, By default skuba search image on registry.suse.com. For security reason, caasp nodes are not authorized to pull image from external server. We use a registry mirror for pull and control image. I don't find if skuba can bootstrap cluster with local registry instead registry suse. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From jean-marc.lambert at suse.com Thu Jul 25 11:05:44 2019 From: jean-marc.lambert at suse.com (Jean Marc Lambert) Date: Thu, 25 Jul 2019 17:05:44 +0000 Subject: [caasp-beta] How make skuba search image in local registry In-Reply-To: <78852a427f0f40a5b5ab13e4f4bcb406@amundi.com> References: <78852a427f0f40a5b5ab13e4f4bcb406@amundi.com> Message-ID: Stephane, I may just share some elements on registries setup. Each node must be setup and the doc is available there : https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_configuring_container_registries_for_cri_o Skuba is just a cli and performs the bootstrapping of the Kubernetes, the setup of VMs is for the moment done before(sles15sp1 with some patterns) and if you need such change, you have to play in the CRIO world and change the params as indicated. Hope that helps BRs Jean Marc Lambert SUSE Professional Services EMEA Solutions Architect & PaaS/CaaS Consultant Linux Foundation CKA & CKAD Certified Tel : 33682827992 De : caasp-beta De la part de Le Bihan St?phane (AMUNDI-ITS) Envoy? : jeudi 25 juillet 2019 18:32 ? : caasp-beta at lists.suse.com Objet : [caasp-beta] How make skuba search image in local registry Hi all, By default skuba search image on registry.suse.com. For security reason, caasp nodes are not authorized to pull image from external server. We use a registry mirror for pull and control image. I don't find if skuba can bootstrap cluster with local registry instead registry suse. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.lebihan at amundi.com Thu Jul 25 11:17:07 2019 From: stephane.lebihan at amundi.com (=?iso-8859-1?Q?Le_Bihan_St=E9phane_=28AMUNDI-ITS=29?=) Date: Thu, 25 Jul 2019 17:17:07 +0000 Subject: [caasp-beta] How make skuba search image in local registry In-Reply-To: References: <78852a427f0f40a5b5ab13e4f4bcb406@amundi.com> Message-ID: For CRIO I work on that . I have just difficulty to set credentials for pull images. But for skuba, after "skuba cluster init --control-plane", I modify : kubeadm-init.conf ./addons/cni/cilium.yaml ./addons/kured/kured.yaml ./addons/dex/dex.yaml ./addons/gangway/gangway.yaml For not use registry.suse.com, but internal registry. And change default podSubnet, serviceSubnet. But when I launch : skuba node bootstrap ... My kubeadm-init.conf is erased, and /tmp/kubeadm-init.conf deploy on server has bad option for registry and Subnet. Regards, From: Jean Marc Lambert Sent: jeudi 25 juillet 2019 19:06 To: Le Bihan St?phane (AMUNDI-ITS) ; caasp-beta at lists.suse.com Subject: RE: How make skuba search image in local registry Stephane, I may just share some elements on registries setup. Each node must be setup and the doc is available there : https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_configuring_container_registries_for_cri_o Skuba is just a cli and performs the bootstrapping of the Kubernetes, the setup of VMs is for the moment done before(sles15sp1 with some patterns) and if you need such change, you have to play in the CRIO world and change the params as indicated. Hope that helps BRs Jean Marc Lambert SUSE Professional Services EMEA Solutions Architect & PaaS/CaaS Consultant Linux Foundation CKA & CKAD Certified Tel : 33682827992 De : caasp-beta > De la part de Le Bihan St?phane (AMUNDI-ITS) Envoy? : jeudi 25 juillet 2019 18:32 ? : caasp-beta at lists.suse.com Objet : [caasp-beta] How make skuba search image in local registry Hi all, By default skuba search image on registry.suse.com. For security reason, caasp nodes are not authorized to pull image from external server. We use a registry mirror for pull and control image. I don't find if skuba can bootstrap cluster with local registry instead registry suse. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.lebihan at amundi.com Fri Jul 26 01:10:41 2019 From: stephane.lebihan at amundi.com (=?iso-8859-1?Q?Le_Bihan_St=E9phane_=28AMUNDI-ITS=29?=) Date: Fri, 26 Jul 2019 07:10:41 +0000 Subject: [caasp-beta] How make skuba search image in local registry In-Reply-To: References: <78852a427f0f40a5b5ab13e4f4bcb406@amundi.com> Message-ID: <4a2bdf5826af450db01093e4708b037b@amundi.com> Ok, I re read documentation, so for registry we must configure Cri-O. I test that. Thanks Any idea for subnet, because default conflicts with internal vlan Regards, From: Jean Marc Lambert Sent: jeudi 25 juillet 2019 19:06 To: Le Bihan St?phane (AMUNDI-ITS) ; caasp-beta at lists.suse.com Subject: RE: How make skuba search image in local registry Stephane, I may just share some elements on registries setup. Each node must be setup and the doc is available there : https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_configuring_container_registries_for_cri_o Skuba is just a cli and performs the bootstrapping of the Kubernetes, the setup of VMs is for the moment done before(sles15sp1 with some patterns) and if you need such change, you have to play in the CRIO world and change the params as indicated. Hope that helps BRs Jean Marc Lambert SUSE Professional Services EMEA Solutions Architect & PaaS/CaaS Consultant Linux Foundation CKA & CKAD Certified Tel : 33682827992 De : caasp-beta > De la part de Le Bihan St?phane (AMUNDI-ITS) Envoy? : jeudi 25 juillet 2019 18:32 ? : caasp-beta at lists.suse.com Objet : [caasp-beta] How make skuba search image in local registry Hi all, By default skuba search image on registry.suse.com. For security reason, caasp nodes are not authorized to pull image from external server. We use a registry mirror for pull and control image. I don't find if skuba can bootstrap cluster with local registry instead registry suse. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From lcavajani at suse.com Fri Jul 26 01:57:50 2019 From: lcavajani at suse.com (Ludovic Cavajani) Date: Fri, 26 Jul 2019 09:57:50 +0200 Subject: [caasp-beta] How make skuba search image in local registry In-Reply-To: <4a2bdf5826af450db01093e4708b037b@amundi.com> References: <78852a427f0f40a5b5ab13e4f4bcb406@amundi.com> <4a2bdf5826af450db01093e4708b037b@amundi.com> Message-ID: <1d8158b8-dafc-d5fc-97c6-4f8c9526dfbc@suse.com> Hi St?phane, There is no preference for the subnet, you can use any private subnet which is large enough for **all** the pods in the cluster. This means you not only take into consideration the running pods, but all the pods which can exist on the cluster at different stages. For example if you drain a node with 50 pods, there will be 50 pods in `Terminating` with an IP and 50 pods in `ContainerCreating` on other nodes which will get IPs as well, so that's 100 IPs taken for 50 desired pods. In general, using a /16 is a good practice. On 7/26/19 9:10 AM, Le Bihan St?phane (AMUNDI-ITS) wrote: > Ok, I re read documentation, so for registry we must configure Cri-O. > > I test that. Thanks > > Any idea for subnet, because default conflicts with internal vlan > > Regards, > > From: Jean Marc Lambert > Sent: jeudi 25 juillet 2019 19:06 > To: Le Bihan St?phane (AMUNDI-ITS) ; caasp-beta at lists.suse.com > Subject: RE: How make skuba search image in local registry > > Stephane, > I may just share some elements on registries setup. > Each node must be setup and the doc is available there : > https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_configuring_container_registries_for_cri_o > Skuba is just a cli and performs the bootstrapping of the Kubernetes, the setup of VMs is for the moment done before(sles15sp1 with some patterns) and if you need such change, you have to play in the CRIO world and change the params as indicated. > Hope that helps > BRs > > Jean Marc Lambert > SUSE Professional Services > EMEA Solutions Architect & PaaS/CaaS Consultant > Linux Foundation CKA & CKAD Certified > Tel : 33682827992 > > > > > De : caasp-beta > De la part de Le Bihan St?phane (AMUNDI-ITS) > Envoy? : jeudi 25 juillet 2019 18:32 > ? : caasp-beta at lists.suse.com > Objet : [caasp-beta] How make skuba search image in local registry > > Hi all, > > By default skuba search image on registry.suse.com. > For security reason, caasp nodes are not authorized to pull image from external server. > > We use a registry mirror for pull and control image. > > I don't find if skuba can bootstrap cluster with local registry instead registry suse. > > Regards, > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From jean-marc.lambert at suse.com Fri Jul 26 02:47:27 2019 From: jean-marc.lambert at suse.com (Jean Marc Lambert) Date: Fri, 26 Jul 2019 08:47:27 +0000 Subject: [caasp-beta] How make skuba search image in local registry In-Reply-To: <4a2bdf5826af450db01093e4708b037b@amundi.com> References: <78852a427f0f40a5b5ab13e4f4bcb406@amundi.com> <4a2bdf5826af450db01093e4708b037b@amundi.com> Message-ID: Skuba init is generating the files of conf in the subdir you choose In that subdir, you have a kubeadm-init.conf Inside, you may change the networking setting prior to bootstrap & join the other nodes. [cid:image001.png at 01D5439F.826054F0] Hope that helps JMarc De : Le Bihan St?phane (AMUNDI-ITS) Envoy? : vendredi 26 juillet 2019 09:11 ? : caasp-beta at lists.suse.com; Jean Marc Lambert Objet : RE: How make skuba search image in local registry Ok, I re read documentation, so for registry we must configure Cri-O. I test that. Thanks Any idea for subnet, because default conflicts with internal vlan Regards, From: Jean Marc Lambert > Sent: jeudi 25 juillet 2019 19:06 To: Le Bihan St?phane (AMUNDI-ITS) >; caasp-beta at lists.suse.com Subject: RE: How make skuba search image in local registry Stephane, I may just share some elements on registries setup. Each node must be setup and the doc is available there : https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_configuring_container_registries_for_cri_o Skuba is just a cli and performs the bootstrapping of the Kubernetes, the setup of VMs is for the moment done before(sles15sp1 with some patterns) and if you need such change, you have to play in the CRIO world and change the params as indicated. Hope that helps BRs Jean Marc Lambert SUSE Professional Services EMEA Solutions Architect & PaaS/CaaS Consultant Linux Foundation CKA & CKAD Certified Tel : 33682827992- De : caasp-beta > De la part de Le Bihan St?phane (AMUNDI-ITS) Envoy? : jeudi 25 juillet 2019 18:32 ? : caasp-beta at lists.suse.com Objet : [caasp-beta] How make skuba search image in local registry Hi all, By default skuba search image on registry.suse.com. For security reason, caasp nodes are not authorized to pull image from external server. We use a registry mirror for pull and control image. I don't find if skuba can bootstrap cluster with local registry instead registry suse. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3387 bytes Desc: image001.png URL: From stephane.lebihan at amundi.com Fri Jul 26 03:05:16 2019 From: stephane.lebihan at amundi.com (=?iso-8859-1?Q?Le_Bihan_St=E9phane_=28AMUNDI-ITS=29?=) Date: Fri, 26 Jul 2019 09:05:16 +0000 Subject: [caasp-beta] How make skuba search image in local registry In-Reply-To: References: <78852a427f0f40a5b5ab13e4f4bcb406@amundi.com> <4a2bdf5826af450db01093e4708b037b@amundi.com> Message-ID: Yes. It's work with good CRI-o configuration. Or because first I create scuba sub-dir in home of user use for deploy may be. But it's seems ok now, I have just problem with loadbalancing F5 Thanks From: Jean Marc Lambert Sent: vendredi 26 juillet 2019 10:47 To: Le Bihan St?phane (AMUNDI-ITS) ; caasp-beta at lists.suse.com Subject: RE: How make skuba search image in local registry Skuba init is generating the files of conf in the subdir you choose In that subdir, you have a kubeadm-init.conf Inside, you may change the networking setting prior to bootstrap & join the other nodes. [cid:image001.png at 01D543A2.0055E5D0] Hope that helps JMarc De : Le Bihan St?phane (AMUNDI-ITS) > Envoy? : vendredi 26 juillet 2019 09:11 ? : caasp-beta at lists.suse.com; Jean Marc Lambert > Objet : RE: How make skuba search image in local registry Ok, I re read documentation, so for registry we must configure Cri-O. I test that. Thanks Any idea for subnet, because default conflicts with internal vlan Regards, From: Jean Marc Lambert > Sent: jeudi 25 juillet 2019 19:06 To: Le Bihan St?phane (AMUNDI-ITS) >; caasp-beta at lists.suse.com Subject: RE: How make skuba search image in local registry Stephane, I may just share some elements on registries setup. Each node must be setup and the doc is available there : https://susedoc.github.io/doc-caasp/beta/caasp-admin/single-html/#_configuring_container_registries_for_cri_o Skuba is just a cli and performs the bootstrapping of the Kubernetes, the setup of VMs is for the moment done before(sles15sp1 with some patterns) and if you need such change, you have to play in the CRIO world and change the params as indicated. Hope that helps BRs Jean Marc Lambert SUSE Professional Services EMEA Solutions Architect & PaaS/CaaS Consultant Linux Foundation CKA & CKAD Certified Tel : 33682827992- De : caasp-beta > De la part de Le Bihan St?phane (AMUNDI-ITS) Envoy? : jeudi 25 juillet 2019 18:32 ? : caasp-beta at lists.suse.com Objet : [caasp-beta] How make skuba search image in local registry Hi all, By default skuba search image on registry.suse.com. For security reason, caasp nodes are not authorized to pull image from external server. We use a registry mirror for pull and control image. I don't find if skuba can bootstrap cluster with local registry instead registry suse. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3387 bytes Desc: image001.png URL: From beta-programs at lists.suse.com Wed Jul 31 07:23:16 2019 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Wed, 31 Jul 2019 15:23:16 +0200 Subject: [caasp-beta] [ANNOUNCE] SUSE CaaS Platform 4.0 Beta 5 is out! Message-ID: <5d41964475637_41210ac6889342@zourite.lab.gb.mail> We are happy to announce the Beta 5 of SUSE CaaS Platform 4.0. Notable changes in Beta 5 - This beta is being published as an update on top of Beta 4. New packages versions have been provided in the Update repository as a proof of concept for the whole maintenance process. Please note that updating requires a manual step[1] that you need to perform. Please also check out our documentation for updating to Beta 5 from previous versions[2] - The most notable feature we are releasing in this sprint is the Cloud Provider Interface for OpenStack, which supports the use of OpenStack services from the underlying cloud. See our documentation[3] for deployment instructions - Beta 4 introduced Role Based Access Control provided by Dex[4] and Gangway[5] tools. In Beta5, we are introducing a Directory Server Container based on 389-ds (https://directory.fedoraproject.org/), an LDAP implementation that replaces OpenLDAP, for those who don't have their own server. Also, we are including instructions on how to set it up alternatively with Active Directory. See the Administration guide[6] for more information - Also relevant is the fact that we tested with a cluster of 250 nodes and our results were successful. We have not reached the limit with this, so further testing will be done by adding more nodes. - SUSE CaaS Platform clusters are passing Sonobuoy conformance tests[7]. For more details, see the Release Notes[8]. Reporting issues: If you find issues, kindly report them to the SUSE Bugzilla[9]. Feedback is very welcome. Architecture and working features: The architecture of SUSE CaaS Platform 4.0 is described here[10]. This build has been tested on SUSE OpenStack Cloud 8, VMware ESXi 6.7.0 and bare metal. We have validated the following features: - Bootstrapping a cluster - Deploying with Terraform in SUSE OpenStack Cloud and VMware - Deploying with autoyast for Bare Metal - Adding, removing nodes and resetting nodes - Deploying, scaling, and exposing nginx image - PodSecurityPolicy deployment and conformance - Applying Base OS updates - Centralized Logging - Authentication and Role Base Access Control - Cluster upgrade from Kubernetes 1.14.1 to Kubernetes 1.15.0 (Beta 3 to Beta 5) - http/https proxy for crio - AppArmor installed and enabled on nodes - helm/tiller deployment - Cilium L3/L4 policies - SCC and RMT registration - Cloud Provider Integration for OpenStack - 389 Directory Service and Active Directory integration for Role Base Access Control - Kubernetes conformance tests - Custom registry for containers - Bootstrap a cluster for 250 nodes See our Release Notes[11] for most recent changes and Known Issues[12]. Note that the product is not feature complete yet, we will continue to improve it. Beta Registration codes You should not use a SLES 15 SP1 environment with the SLE Beta Registration Code anymore. Because the SLE Beta Registration Code is expired now but you can either use your regular SLE Registration Code or use a Trial. Registration is not working with your regular key, special Beta Registration Code is required. You need to request one for SUSE CaaS Platform 4.0 Beta Program by contacting us at beta-programs at lists.suse.com[13]. Installation Use the terraform package to install SUSE CaaS Platform on SUSE OpenStack Cloud or VMware. Use autoyast for installing on Bare Metal. Refer to the Deployment Guide[14] for further information. Beta Page ?[15] Documentation ?[16] Have fun beta testing! Your SUSE CaaS Platform Team Please refer to our dedicated SUSE CaaSP Beta Program[17] webpage for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Click here to unsubscribe.[18] [1]:https://susedoc.github.io/caasp-release-notes/beta/releas e-notes/single-html/#_updating_from_beta_4_to_beta_5 [2]:%20https://susedoc.github.io/doc-caasp/beta/caasp-admin/s ingle-html/#_applying_updates [3]:https://susedoc.github.io/doc-caasp/beta/caasp-deployment /single-html/#_enabling_cloud_provider_integration [4]:https://github.com/dexidp/dex [5]:https://github.com/heptiolabs/gangway [6]:https://susedoc.github.io/doc-caasp/beta/caasp-admin/sing le-html/#_external_ldap [7]:https://sonobuoy.io/ [8]:https://susedoc.github.io/caasp-release-notes/beta/releas e-notes/single-html/ [9]:https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SU SE%20CaaS%20Platform%204 [10]:https://susedoc.github.io/doc-caasp/master/caasp-archite cture/single-html/ [11]:https://www.suse.com/betaprogram/caasp-beta/#releasenote s [12]:https://www.suse.com/betaprogram/caasp-beta/#knownissues [13]:mailto:beta-programs at lists.suse.com?subject=Requesting%2 0SUSE%20CaaSP%204.0%20Beta%20Registration%20Codes&body=Reques ting%20SUSE%20CaaSP%204.0 [14]:https://susedoc.github.io/doc-caasp/master/caasp-deploym ent/single-html/ [15]:https://www.suse.com/betaprogram/caasp-beta [16]:https://www.suse.com/betaprogram/caasp-beta/#documentati on [17]:https://www.suse.com/betaprogram/caasp-beta/ [18]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe% 20from%20SUSE%20CaaSP%20Beta&body=Unsubscribe%20from%20SUSE%2 0CaaSP%20Beta -------------- next part -------------- An HTML attachment was scrubbed... URL: