[caasp-beta] Q: Any skuba bootstrap error with kubeadmn known?
Roger Klorese
roger.klorese at suse.com
Fri Jul 12 02:37:00 MDT 2019
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 <caasp-beta-bounces at lists.suse.com> on behalf of egov-devops <egov-devops at akdb.de>
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 <LB IP/FQDN> 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/FQDN> <NODE NAME> -> 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<mailto:egov-devops at adkb.de>
__________________________________________________________
AKDB · Anstalt des öffentlichen Rechts · Hauptverwaltung
Hansastraße 12-16 · 80686 München · www.akdb.de<http://www.akdb.de/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20190712/44d2aebe/attachment.html>
More information about the caasp-beta
mailing list