Skip to content

Instantly share code, notes, and snippets.

@jbw976

jbw976/fedora output

Last active January 15, 2019 23:51
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jbw976/eebc38beb1ef81b08b07252ef4047ea3 to your computer and use it in GitHub Desktop.
Save jbw976/eebc38beb1ef81b08b07252ef4047ea3 to your computer and use it in GitHub Desktop.
Download ZIP
output for k8s-vagrant-multi-node multi_os support
Raw
fedora output
jared@Jareds-MacBook-Pro ~/dev/k8s-vagrant-multi-node ((HEAD detached at upstream/multi_os))
> make up -j 2
vagrant up
NODE=1 vagrant up
Bringing machine 'node1' up with 'virtualbox' provider...
Bringing machine 'master' up with 'virtualbox' provider...
==> master: Box 'generic/fedora29' could not be found. Attempting to find and install...
master: Box Provider: virtualbox
==> node1: Box 'generic/fedora29' could not be found. Attempting to find and install...
master: Box Version: >= 0
node1: Box Provider: virtualbox
node1: Box Version: >= 0
==> master: Loading metadata for box 'generic/fedora29'
master: URL: https://vagrantcloud.com/generic/fedora29
==> node1: Loading metadata for box 'generic/fedora29'
node1: URL: https://vagrantcloud.com/generic/fedora29
==> master: Adding box 'generic/fedora29' (v1.8.54) for provider: virtualbox
master: Downloading: https://vagrantcloud.com/generic/boxes/fedora29/versions/1.8.54/providers/virtualbox.box
==> node1: Adding box 'generic/fedora29' (v1.8.54) for provider: virtualbox
node1: Downloading: https://vagrantcloud.com/generic/boxes/fedora29/versions/1.8.54/providers/virtualbox.box
master: Progress: 79% (Rate: 9384k/s, Estimated time remaining: 0:00:36)==> node1: Successfully added box 'generic/fedora29' (v1.8.54) for 'virtualbox'!
==> node1: Importing base box 'generic/fedora29'...
==> node1: Matching MAC address for NAT networking...
==> node1: Checking if box 'generic/fedora29' is up to date...
==> node1: Setting the name of the VM: k8s-vagrant-multi-node_node1_1547589765148_99060
==> master: Importing base box 'generic/fedora29'...
==> node1: Clearing any previously set network interfaces...
==> node1: Preparing network interfaces based on configuration...
node1: Adapter 1: nat
node1: Adapter 2: hostonly
==> node1: Forwarding ports...
node1: 22 (guest) => 2222 (host) (adapter 1)
==> node1: Running 'pre-boot' VM customizations...
Progress: 20%A customization command failed:
["storageattach", :id, "--storagectl", "k8svmnSATAController", "--port", 0, "--device", 0, "--type", "hdd", "--medium", ".vagrant/node1-disk-1.vdi"]
The following error was experienced:
#<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["storageattach", "42c7f91a-2c1b-49b2-a73d-6d921f7b67a4", "--storagectl", "k8svmnSATAController", "--port", "0", "--device", "0", "--type", "hdd", "--medium", ".vagrant/node1-disk-1.vdi"]
Stderr: VBoxManage: error: Could not find file for the medium '/Users/jared/dev/k8s-vagrant-multi-node/.vagrant/node1-disk-1.vdi' (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename ".vagrant/node1-disk-1.vdi"
>
Please fix this customization and try again.
make[2]: *** [start-node-1] Error 1
make[2]: *** Waiting for unfinished jobs....
==> master: Matching MAC address for NAT networking...
==> master: Checking if box 'generic/fedora29' is up to date...
==> master: Setting the name of the VM: k8s-vagrant-multi-node_master_1547589777838_33268
==> master: Clearing any previously set network interfaces...
==> master: Preparing network interfaces based on configuration...
master: Adapter 1: nat
master: Adapter 2: hostonly
==> master: Forwarding ports...
master: 8443 (guest) => 8443 (host) (adapter 1)
master: 22 (guest) => 2222 (host) (adapter 1)
==> master: Running 'pre-boot' VM customizations...
==> master: Booting VM...
==> master: Waiting for machine to boot. This may take a few minutes...
master: SSH address: 127.0.0.1:2222
master: SSH username: vagrant
master: SSH auth method: private key
master:
master: Vagrant insecure key detected. Vagrant will automatically replace
master: this with a newly generated keypair for better security.
master:
master: Inserting generated public key within guest...
master: Removing insecure key from the guest if it's present...
master: Key inserted! Disconnecting and reconnecting using new SSH key...
==> master: Machine booted and ready!
==> master: Checking for guest additions in VM...
==> master: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
# Update sysconfig
sed -i 's/\(HOSTNAME=\).*/\1master/' /etc/sysconfig/network
# Update DNS
sed -i 's/\(DHCP_HOSTNAME=\).*/\1"master"/' /etc/sysconfig/network-scripts/ifcfg-*
# Set the hostname - use hostnamectl if available
echo 'master' > /etc/hostname
if command -v hostnamectl; then
hostnamectl set-hostname --static 'master'
hostnamectl set-hostname --transient 'master'
else
hostname -F /etc/hostname
fi
# Prepend ourselves to /etc/hosts
grep -w 'master' /etc/hosts || {
sed -i'' '1i 127.0.0.1\tmaster\tmaster' /etc/hosts
}
# Restart network
service network restart
Stdout from the command:
/usr/bin/hostnamectl
Stderr from the command:
Redirecting to /bin/systemctl restart network.service
Failed to restart network.service: Unit network.service not found.
make[2]: *** [start-master] Error 1
make[1]: *** [start] Error 2
make: *** [up] Error 2
Raw
ubuntu output
> BOX_OS=ubuntu make up -j 3
vagrant up
NODE=1 vagrant up
NODE=2 vagrant up
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'node1' up with 'virtualbox' provider...
Bringing machine 'node2' up with 'virtualbox' provider...
==> node1: Box 'generic/ubuntu1804' could not be found. Attempting to find and install...
node1: Box Provider: virtualbox
node1: Box Version: >= 0
==> node2: Box 'generic/ubuntu1804' could not be found. Attempting to find and install...
node2: Box Provider: virtualbox
node2: Box Version: >= 0
==> master: Box 'generic/ubuntu1804' could not be found. Attempting to find and install...
master: Box Provider: virtualbox
master: Box Version: >= 0
==> node2: Loading metadata for box 'generic/ubuntu1804'
node2: URL: https://vagrantcloud.com/generic/ubuntu1804
==> node1: Loading metadata for box 'generic/ubuntu1804'
node1: URL: https://vagrantcloud.com/generic/ubuntu1804
==> master: Loading metadata for box 'generic/ubuntu1804'
master: URL: https://vagrantcloud.com/generic/ubuntu1804
/opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/box_add.rb:198:in `initialize': No such file or directory @ rb_sysopen - /Users/jared/.vagrant.d/tmp/boxa1bbb8ae4b0ea40a63b5fd1f1c71a4c1a6697e46 (Errno::ENOENT)
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/box_add.rb:198:in `open'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/box_add.rb:198:in `add_from_metadata'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/box_add.rb:118:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/handle_box.rb:82:in `handle_box'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/handle_box.rb:42:in `block in call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/handle_box.rb:36:in `synchronize'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/handle_box.rb:36:in `call'
==> node2: Adding box 'generic/ubuntu1804' (v1.8.54) for provider: virtualbox
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builtin/call.rb:53:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/warden.rb:34:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/builder.rb:116:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `block in run'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/util/busy.rb:19:in `busy'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:66:in `run'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine.rb:239:in `action_raw'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine.rb:208:in `block in action'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:614:in `lock'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine.rb:194:in `call'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine.rb:194:in `action'
from /opt/vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
node2: Downloading: https://vagrantcloud.com/generic/boxes/ubuntu1804/versions/1.8.54/providers/virtualbox.box
make[2]: *** [start-node-1] Error 1
make[2]: *** Waiting for unfinished jobs....
==> master: Adding box 'generic/ubuntu1804' (v1.8.54) for provider: virtualbox
master: Downloading: https://vagrantcloud.com/generic/boxes/ubuntu1804/versions/1.8.54/providers/virtualbox.box
node2: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
master: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
node2: Progress: 96% (Rate: 9.8M/s, Estimated time remaining: 0:00:06)==> master: Successfully added box 'generic/ubuntu1804' (v1.8.54) for 'virtualbox'!
==> master: Importing base box 'generic/ubuntu1804'...
Progress: 10%==> node2: Importing base box 'generic/ubuntu1804'...
==> node2: Matching MAC address for NAT networking...
==> node2: Checking if box 'generic/ubuntu1804' version '1.8.54' is up to date...
Progress: 90%==> node2: Setting the name of the VM: k8s-vagrant-multi-node_node2_1547595674906_70849
==> node2: Vagrant has detected a configuration issue which exposes a
==> node2: vulnerability with the installed version of VirtualBox. The
==> node2: current guest is configured to use an E1000 NIC type for a
==> node2: network adapter which is vulnerable in this version of VirtualBox.
==> node2: Ensure the guest is trusted to use this configuration or update
==> node2: the NIC type using one of the methods below:
==> node2:
==> node2: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> node2: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
==> node2: Clearing any previously set network interfaces...
==> node2: Preparing network interfaces based on configuration...
node2: Adapter 1: nat
node2: Adapter 2: hostonly
==> node2: Forwarding ports...
node2: 22 (guest) => 2222 (host) (adapter 1)
==> node2: Running 'pre-boot' VM customizations...
==> node2: Booting VM...
==> node2: Waiting for machine to boot. This may take a few minutes...
==> master: Matching MAC address for NAT networking...
==> master: Checking if box 'generic/ubuntu1804' version '1.8.54' is up to date...
node2: SSH address: 127.0.0.1:2222
node2: SSH username: vagrant
node2: SSH auth method: private key
==> master: Setting the name of the VM: k8s-vagrant-multi-node_master_1547595677701_17262
==> master: Fixed port collision for 22 => 2222. Now on port 2200.
==> master: Vagrant has detected a configuration issue which exposes a
==> master: vulnerability with the installed version of VirtualBox. The
==> master: current guest is configured to use an E1000 NIC type for a
==> master: network adapter which is vulnerable in this version of VirtualBox.
==> master: Ensure the guest is trusted to use this configuration or update
==> master: the NIC type using one of the methods below:
==> master:
==> master: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
==> master: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
==> master: Clearing any previously set network interfaces...
==> master: Preparing network interfaces based on configuration...
master: Adapter 1: nat
master: Adapter 2: hostonly
==> master: Forwarding ports...
master: 8443 (guest) => 8443 (host) (adapter 1)
master: 22 (guest) => 2200 (host) (adapter 1)
==> master: Running 'pre-boot' VM customizations...
==> master: Booting VM...
==> master: Waiting for machine to boot. This may take a few minutes...
master: SSH address: 127.0.0.1:2200
master: SSH username: vagrant
master: SSH auth method: private key
node2:
node2: Vagrant insecure key detected. Vagrant will automatically replace
node2: this with a newly generated keypair for better security.
node2:
node2: Inserting generated public key within guest...
node2: Removing insecure key from the guest if it's present...
node2: Key inserted! Disconnecting and reconnecting using new SSH key...
==> node2: Machine booted and ready!
==> node2: Checking for guest additions in VM...
==> node2: Setting hostname...
==> node2: Configuring and enabling network interfaces...
master:
master: Vagrant insecure key detected. Vagrant will automatically replace
master: this with a newly generated keypair for better security.
master:
master: Inserting generated public key within guest...
master: Removing insecure key from the guest if it's present...
master: Key inserted! Disconnecting and reconnecting using new SSH key...
==> master: Machine booted and ready!
==> master: Checking for guest additions in VM...
==> master: Setting hostname...
==> node2: Rsyncing folder: /Users/jared/dev/k8s-vagrant-multi-node/data/ubuntu-node2/ => /data
==> master: Configuring and enabling network interfaces...
==> node2: Running provisioner: shell...
node2: Running: inline script
==> node2: Running provisioner: shell...
node2: Running: inline script
node2: ++ apt-get update
==> master: Rsyncing folder: /Users/jared/dev/k8s-vagrant-multi-node/data/ubuntu-master/ => /data
==> master: Running provisioner: shell...
master: Running: inline script
==> master: Running provisioner: shell...
master: Running: inline script
master: ++ apt-get update
master: Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
master: Hit:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease
master: Get:3 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
node2: Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
node2: Get:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
master: Get:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
master: Get:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [242 kB]
node2: Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
master: Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [422 kB]
node2: Get:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
node2: Get:5 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [487 kB]
master: Get:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [487 kB]
master: Get:8 http://us.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [182 kB]
master: Get:9 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [701 kB]
master: Get:10 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages [185 kB]
node2: Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [422 kB]
master: Get:11 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [91.3 kB]
master: Get:12 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [710 kB]
master: Get:13 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [175 kB]
node2: Get:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [182 kB]
master: Get:14 http://us.archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages [6,524 B]
master: Get:15 http://us.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [6,376 B]
node2: Get:8 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [701 kB]
master: Get:16 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [112 kB]
master: Get:17 http://security.ubuntu.com/ubuntu bionic-security/universe i386 Packages [109 kB]
node2: Get:9 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages [185 kB]
node2: Get:10 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [710 kB]
master: Get:18 http://security.ubuntu.com/ubuntu bionic-security/universe Translation-en [63.7 kB]
master: Get:19 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [1,444 B]
master: Get:20 http://security.ubuntu.com/ubuntu bionic-security/multiverse i386 Packages [1,608 B]
node2: Get:11 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [175 kB]
node2: Get:12 http://us.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [6,376 B]
node2: Get:13 http://us.archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages [6,524 B]
node2: Get:14 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [242 kB]
node2: Get:15 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [91.3 kB]
node2: Get:16 http://security.ubuntu.com/ubuntu bionic-security/universe i386 Packages [109 kB]
node2: Get:17 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [112 kB]
node2: Get:18 http://security.ubuntu.com/ubuntu bionic-security/universe Translation-en [63.7 kB]
node2: Get:19 http://security.ubuntu.com/ubuntu bionic-security/multiverse i386 Packages [1,608 B]
node2: Get:20 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [1,444 B]
master: Fetched 3,742 kB in 3s (1,079 kB/s)
master: Reading package lists...
node2: Fetched 3,742 kB in 5s (704 kB/s)
node2: Reading package lists...
master: ++ apt-get install -y apt-transport-https curl software-properties-common ca-certificates
master: Reading package lists...
master: Building dependency tree...
master:
master: Reading state information...
master: ca-certificates is already the newest version (20180409).
master: curl is already the newest version (7.58.0-2ubuntu3.5).
master: The following additional packages will be installed:
master: python3-software-properties
master: The following NEW packages will be installed:
master: apt-transport-https
master: The following packages will be upgraded:
master: python3-software-properties software-properties-common
node2: ++ apt-get install -y apt-transport-https curl software-properties-common ca-certificates
master: 2 upgraded, 1 newly installed, 0 to remove and 35 not upgraded.
master: Need to get 33.6 kB of archives.
master: After this operation, 152 kB of additional disk space will be used.
master: Get:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 apt-transport-https all 1.6.6 [1,692 B]
node2: Reading package lists...
node2: Building dependency tree...
master: Get:2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 software-properties-common all 0.96.24.32.7 [9,908 B]
master: Get:3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-software-properties all 0.96.24.32.7 [22.0 kB]
node2: Reading state information...
master: dpkg-preconfigure: unable to re-open stdin: No such file or directory
master: Fetched 33.6 kB in 0s (80.9 kB/s)
master: Selecting previously unselected package apt-transport-https.
master: (Reading database ...
(Reading database ... 55%base ... 5%
master: (Reading database ... 60%
master: (Reading database ... 65%
node2: ca-certificates is already the newest version (20180409).
node2: curl is already the newest version (7.58.0-2ubuntu3.5).
node2: The following additional packages will be installed:
node2: python3-software-properties
node2: The following NEW packages will be installed:
node2: apt-transport-https
master: (Reading database ... 70%
node2: The following packages will be upgraded:
node2: python3-software-properties software-properties-common
master: (Reading database ... 75%
master: (Reading database ... 80%
master: (Reading database ... 85%
master: (Reading database ... 90%
master: (Reading database ... 95%
(Reading database ... 105274 files and directories currently installed.)
master: Preparing to unpack .../apt-transport-https_1.6.6_all.deb ...
master: Unpacking apt-transport-https (1.6.6) ...
master: Preparing to unpack .../software-properties-common_0.96.24.32.7_all.deb ...
master: Unpacking software-properties-common (0.96.24.32.7) over (0.96.24.32.6) ...
master: Preparing to unpack .../python3-software-properties_0.96.24.32.7_all.deb ...
master: Unpacking python3-software-properties (0.96.24.32.7) over (0.96.24.32.6) ...
master: Setting up apt-transport-https (1.6.6) ...
master: Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
master: Setting up python3-software-properties (0.96.24.32.7) ...
master: Processing triggers for dbus (1.12.2-1ubuntu1) ...
master: Setting up software-properties-common (0.96.24.32.7) ...
node2: 2 upgraded, 1 newly installed, 0 to remove and 35 not upgraded.
node2: Need to get 33.6 kB of archives.
node2: After this operation, 152 kB of additional disk space will be used.
node2: Get:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 apt-transport-https all 1.6.6 [1,692 B]
node2: Get:2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 software-properties-common all 0.96.24.32.7 [9,908 B]
node2: Get:3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-software-properties all 0.96.24.32.7 [22.0 kB]
node2: dpkg-preconfigure: unable to re-open stdin: No such file or directory
node2: Fetched 33.6 kB in 3s (12.4 kB/s)
node2: Selecting previously unselected package apt-transport-https.
node2: (Reading database ...
node2: (Reading database ... 5%
node2: (Reading database ... 10%
node2: (Reading database ... 15%
node2: (Reading database ... 20%
node2: (Reading database ... 25%
node2: (Reading database ... 30%
node2: (Reading database ... 35%
node2: (Reading database ... 40%
node2: (Reading database ... 45%
node2: (Reading database ... 50%
node2: (Reading database ... 55%
node2: (Reading database ... 60%
node2: (Reading database ... 65%
node2: (Reading database ... 70%
node2: (Reading database ... 75%
node2: (Reading database ... 80%
node2: (Reading database ... 85%
node2: (Reading database ... 90%
node2: (Reading database ... 95%
node2: (Reading database ... 100%
node2: (Reading database ...
node2: 105274 files and directories currently installed.)
node2: Preparing to unpack .../apt-transport-https_1.6.6_all.deb ...
node2: Unpacking apt-transport-https (1.6.6) ...
master: ++ sudo apt-key add -
master: ++ curl -fsSL https://download.docker.com/linux/ubuntu/gpg
node2: Preparing to unpack .../software-properties-common_0.96.24.32.7_all.deb ...
master: Warning: apt-key output should not be parsed (stdout is not a terminal)
node2: Unpacking software-properties-common (0.96.24.32.7) over (0.96.24.32.6) ...
node2: Preparing to unpack .../python3-software-properties_0.96.24.32.7_all.deb ...
node2: Unpacking python3-software-properties (0.96.24.32.7) over (0.96.24.32.6) ...
node2: Setting up apt-transport-https (1.6.6) ...
node2: Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
master: OK
master: +++ lsb_release -cs
master: ++ add-apt-repository 'deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable'
master: Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
master: Hit:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
master: Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease
master: Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
node2: Setting up python3-software-properties (0.96.24.32.7) ...
node2: Processing triggers for dbus (1.12.2-1ubuntu1) ...
node2: Setting up software-properties-common (0.96.24.32.7) ...
node2: ++ sudo apt-key add -
node2: ++ curl -fsSL https://download.docker.com/linux/ubuntu/gpg
node2: Warning: apt-key output should not be parsed (stdout is not a terminal)
master: Get:5 https://download.docker.com/linux/ubuntu bionic InRelease [64.4 kB]
master: Get:6 https://download.docker.com/linux/ubuntu bionic/stable amd64 Packages [3,695 B]
node2: OK
node2: +++ lsb_release -cs
node2: ++ add-apt-repository 'deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable'
node2: Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
node2: Hit:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
node2: Hit:3 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
node2: Get:4 https://download.docker.com/linux/ubuntu bionic InRelease [64.4 kB]
node2: Get:5 https://download.docker.com/linux/ubuntu bionic/stable amd64 Packages [3,695 B]
node2: Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease
master: Fetched 68.1 kB in 3s (24.7 kB/s)
master: Reading package lists...
master: ++ curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg
master: ++ apt-key add -
master: Warning: apt-key output should not be parsed (stdout is not a terminal)
master: OK
master: ++ cat
master: ++ '[' -n '' ']'
master: ++ KUBERNETES_PACKAGES='kubelet kubeadm kubectl'
master: ++ apt-get update
master: Hit:1 https://download.docker.com/linux/ubuntu bionic InRelease
node2: Fetched 68.1 kB in 2s (32.3 kB/s)
node2: Reading package lists...
master: Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
master: Hit:3 http://us.archive.ubuntu.com/ubuntu bionic InRelease
master: Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
master: Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
node2: ++ apt-key add -
node2: ++ curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg
node2: Warning: apt-key output should not be parsed (stdout is not a terminal)
node2: OK
node2: ++ cat
node2: ++ '[' -n '' ']'
node2: ++ KUBERNETES_PACKAGES='kubelet kubeadm kubectl'
node2: ++ apt-get update
master: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,993 B]
master: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages [22.7 kB]
node2: Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
node2: Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
node2: Hit:3 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
node2: Hit:4 https://download.docker.com/linux/ubuntu bionic InRelease
node2: Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
master: Fetched 31.7 kB in 3s (10.0 kB/s)
master: Reading package lists...
master: ++ apt-get install -y screen telnet docker-ce kubelet kubeadm kubectl
master: Reading package lists...
master: Building dependency tree...
master:
master: Reading state information...
master: telnet is already the newest version (0.17-41).
master: screen is already the newest version (4.6.2-1ubuntu1).
master: The following additional packages will be installed:
master: aufs-tools cgroupfs-mount containerd.io cri-tools docker-ce-cli
master: kubernetes-cni libltdl7 pigz socat
master: The following NEW packages will be installed:
master: aufs-tools cgroupfs-mount containerd.io cri-tools docker-ce docker-ce-cli
master: kubeadm kubectl kubelet kubernetes-cni libltdl7 pigz socat
master: 0 upgraded, 13 newly installed, 0 to remove and 35 not upgraded.
master: Need to get 96.5 MB of archives.
master: After this operation, 507 MB of additional disk space will be used.
master: Get:1 https://download.docker.com/linux/ubuntu bionic/stable amd64 containerd.io amd64 1.2.2-1 [19.9 MB]
master: Get:2 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 pigz amd64 2.4-1 [57.4 kB]
master: Get:8 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 aufs-tools amd64 1:4.9+20170918-1ubuntu1 [104 kB]
master: Get:9 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 cgroupfs-mount all 1.4 [6,320 B]
master: Get:10 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 libltdl7 amd64 2.4.6-2 [38.8 kB]
master: Get:11 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 socat amd64 1.7.3.2-2ubuntu2 [342 kB]
master: Get:12 https://download.docker.com/linux/ubuntu bionic/stable amd64 docker-ce-cli amd64 5:18.09.1~3-0~ubuntu-bionic [13.1 MB]
node2: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,993 B]
node2: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages [22.7 kB]
master: Get:13 https://download.docker.com/linux/ubuntu bionic/stable amd64 docker-ce amd64 5:18.09.1~3-0~ubuntu-bionic [17.4 MB]
master: Get:3 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 cri-tools amd64 1.12.0-00 [5,343 kB]
node2: Fetched 31.7 kB in 8s (3,934 B/s)
node2: Reading package lists...
master: Get:4 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubernetes-cni amd64 0.6.0-00 [5,910 kB]
master: Get:5 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubelet amd64 1.13.2-00 [19.0 MB]
node2: ++ apt-get install -y screen telnet docker-ce kubelet kubeadm kubectl
node2: Reading package lists...
node2: Building dependency tree...
node2: Reading state information...
node2: telnet is already the newest version (0.17-41).
node2: screen is already the newest version (4.6.2-1ubuntu1).
node2: The following additional packages will be installed:
node2: aufs-tools cgroupfs-mount containerd.io cri-tools docker-ce-cli
node2: kubernetes-cni libltdl7 pigz socat
node2: The following NEW packages will be installed:
node2: aufs-tools cgroupfs-mount containerd.io cri-tools docker-ce docker-ce-cli
node2: kubeadm kubectl kubelet kubernetes-cni libltdl7 pigz socat
master: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubectl amd64 1.13.2-00 [7,847 kB]
master: Get:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubeadm amd64 1.13.2-00 [7,362 kB]
node2: 0 upgraded, 13 newly installed, 0 to remove and 35 not upgraded.
node2: Need to get 96.5 MB of archives.
node2: After this operation, 507 MB of additional disk space will be used.
node2: Get:2 https://download.docker.com/linux/ubuntu bionic/stable amd64 containerd.io amd64 1.2.2-1 [19.9 MB]
node2: Get:7 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 pigz amd64 2.4-1 [57.4 kB]
master: dpkg-preconfigure: unable to re-open stdin: No such file or directory
master: Fetched 96.5 MB in 10s (9,250 kB/s)
master: Selecting previously unselected package pigz.
master: (Reading database ...
master: (Reading database ... 5%
master: (Reading database ... 10%
master: (Reading database ... 15%
master: (Reading database ... 20%
master: (Reading database ... 25%
master: (Reading database ... 30%
master: (Reading database ... 35%
master: (Reading database ... 40%
master: (Reading database ... 45%
master: (Reading database ... 50%
master: (Reading database ... 55%
master: (Reading database ... 60%
master: (Reading database ... 65%
master: (Reading database ... 70%
master: (Reading database ... 75%
master: (Reading database ... 80%
master: (Reading database ... 85%
master: (Reading database ... 90%
master: (Reading database ... 95%
master: (Reading database ... 100%
master: (Reading database ...
master: 105278 files and directories currently installed.)
master: Preparing to unpack .../00-pigz_2.4-1_amd64.deb ...
master: Unpacking pigz (2.4-1) ...
node2: Get:8 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 aufs-tools amd64 1:4.9+20170918-1ubuntu1 [104 kB]
master: Selecting previously unselected package aufs-tools.
master: Preparing to unpack .../01-aufs-tools_1%3a4.9+20170918-1ubuntu1_amd64.deb ...
node2: Get:9 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 cgroupfs-mount all 1.4 [6,320 B]
node2: Get:10 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 libltdl7 amd64 2.4.6-2 [38.8 kB]
node2: Get:11 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 socat amd64 1.7.3.2-2ubuntu2 [342 kB]
master: Unpacking aufs-tools (1:4.9+20170918-1ubuntu1) ...
master: Selecting previously unselected package cgroupfs-mount.
master: Preparing to unpack .../02-cgroupfs-mount_1.4_all.deb ...
master: Unpacking cgroupfs-mount (1.4) ...
master: Selecting previously unselected package containerd.io.
node2: Get:12 https://download.docker.com/linux/ubuntu bionic/stable amd64 docker-ce-cli amd64 5:18.09.1~3-0~ubuntu-bionic [13.1 MB]
master: Preparing to unpack .../03-containerd.io_1.2.2-1_amd64.deb ...
master: Unpacking containerd.io (1.2.2-1) ...
node2: Get:13 https://download.docker.com/linux/ubuntu bionic/stable amd64 docker-ce amd64 5:18.09.1~3-0~ubuntu-bionic [17.4 MB]
node2: Get:1 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 cri-tools amd64 1.12.0-00 [5,343 kB]
master: Selecting previously unselected package cri-tools.
master: Preparing to unpack .../04-cri-tools_1.12.0-00_amd64.deb ...
master: Unpacking cri-tools (1.12.0-00) ...
node2: Get:3 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubernetes-cni amd64 0.6.0-00 [5,910 kB]
master: Selecting previously unselected package libltdl7:amd64.
master: Preparing to unpack .../05-libltdl7_2.4.6-2_amd64.deb ...
master: Unpacking libltdl7:amd64 (2.4.6-2) ...
master: Selecting previously unselected package docker-ce-cli.
master: Preparing to unpack .../06-docker-ce-cli_5%3a18.09.1~3-0~ubuntu-bionic_amd64.deb ...
master: Unpacking docker-ce-cli (5:18.09.1~3-0~ubuntu-bionic) ...
node2: Get:4 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubelet amd64 1.13.2-00 [19.0 MB]
master: Selecting previously unselected package docker-ce.
master: Preparing to unpack .../07-docker-ce_5%3a18.09.1~3-0~ubuntu-bionic_amd64.deb ...
master: Unpacking docker-ce (5:18.09.1~3-0~ubuntu-bionic) ...
node2: Get:5 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubectl amd64 1.13.2-00 [7,847 kB]
node2: Get:6 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubeadm amd64 1.13.2-00 [7,362 kB]
node2: dpkg-preconfigure: unable to re-open stdin: No such file or directory
node2: Fetched 96.5 MB in 11s (9,095 kB/s)
node2: Selecting previously unselected package pigz.
node2: (Reading database ...
node2: (Reading database ... 5%
node2: (Reading database ... 10%
node2: (Reading database ... 15%
node2: (Reading database ... 20%
node2: (Reading database ... 25%
node2: (Reading database ... 30%
node2: (Reading database ... 35%
node2: (Reading database ... 40%
node2: (Reading database ... 45%
node2: (Reading database ... 50%
node2: (Reading database ... 55%
node2: (Reading database ... 60%
node2: (Reading database ... 65%
node2: (Reading database ... 70%
node2: (Reading database ... 75%
node2: (Reading database ... 80%
node2: (Reading database ... 85%
node2: (Reading database ... 90%
node2: (Reading database ... 95%
node2: (Reading database ... 100%
node2: (Reading database ...
node2: 105278 files and directories currently installed.)
node2: Preparing to unpack .../00-pigz_2.4-1_amd64.deb ...
node2: Unpacking pigz (2.4-1) ...
master: Selecting previously unselected package kubernetes-cni.
master: Preparing to unpack .../08-kubernetes-cni_0.6.0-00_amd64.deb ...
master: Unpacking kubernetes-cni (0.6.0-00) ...
node2: Selecting previously unselected package aufs-tools.
node2: Preparing to unpack .../01-aufs-tools_1%3a4.9+20170918-1ubuntu1_amd64.deb ...
node2: Unpacking aufs-tools (1:4.9+20170918-1ubuntu1) ...
node2: Selecting previously unselected package cgroupfs-mount.
node2: Preparing to unpack .../02-cgroupfs-mount_1.4_all.deb ...
node2: Unpacking cgroupfs-mount (1.4) ...
node2: Selecting previously unselected package containerd.io.
node2: Preparing to unpack .../03-containerd.io_1.2.2-1_amd64.deb ...
node2: Unpacking containerd.io (1.2.2-1) ...
master: Selecting previously unselected package socat.
master: Preparing to unpack .../09-socat_1.7.3.2-2ubuntu2_amd64.deb ...
master: Unpacking socat (1.7.3.2-2ubuntu2) ...
master: Selecting previously unselected package kubelet.
master: Preparing to unpack .../10-kubelet_1.13.2-00_amd64.deb ...
master: Unpacking kubelet (1.13.2-00) ...
node2: Selecting previously unselected package cri-tools.
node2: Preparing to unpack .../04-cri-tools_1.12.0-00_amd64.deb ...
node2: Unpacking cri-tools (1.12.0-00) ...
master: Selecting previously unselected package kubectl.
master: Preparing to unpack .../11-kubectl_1.13.2-00_amd64.deb ...
master: Unpacking kubectl (1.13.2-00) ...
node2: Selecting previously unselected package libltdl7:amd64.
node2: Preparing to unpack .../05-libltdl7_2.4.6-2_amd64.deb ...
node2: Unpacking libltdl7:amd64 (2.4.6-2) ...
node2: Selecting previously unselected package docker-ce-cli.
node2: Preparing to unpack .../06-docker-ce-cli_5%3a18.09.1~3-0~ubuntu-bionic_amd64.deb ...
node2: Unpacking docker-ce-cli (5:18.09.1~3-0~ubuntu-bionic) ...
master: Selecting previously unselected package kubeadm.
master: Preparing to unpack .../12-kubeadm_1.13.2-00_amd64.deb ...
master: Unpacking kubeadm (1.13.2-00) ...
node2: Selecting previously unselected package docker-ce.
node2: Preparing to unpack .../07-docker-ce_5%3a18.09.1~3-0~ubuntu-bionic_amd64.deb ...
node2: Unpacking docker-ce (5:18.09.1~3-0~ubuntu-bionic) ...
master: Setting up aufs-tools (1:4.9+20170918-1ubuntu1) ...
master: Setting up kubernetes-cni (0.6.0-00) ...
master: Setting up containerd.io (1.2.2-1) ...
master: Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service -> /lib/systemd/system/containerd.service.
master: Setting up cri-tools (1.12.0-00) ...
master: Processing triggers for ureadahead (0.100.0-20) ...
master: Setting up socat (1.7.3.2-2ubuntu2) ...
master: Setting up cgroupfs-mount (1.4) ...
master: Setting up kubelet (1.13.2-00) ...
master: Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service -> /lib/systemd/system/kubelet.service.
master: Processing triggers for libc-bin (2.27-3ubuntu1) ...
master: Processing triggers for systemd (237-3ubuntu10.9) ...
master: Setting up libltdl7:amd64 (2.4.6-2) ...
master: Setting up kubectl (1.13.2-00) ...
master: Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
node2: Selecting previously unselected package kubernetes-cni.
node2: Preparing to unpack .../08-kubernetes-cni_0.6.0-00_amd64.deb ...
node2: Unpacking kubernetes-cni (0.6.0-00) ...
node2: Selecting previously unselected package socat.
node2: Preparing to unpack .../09-socat_1.7.3.2-2ubuntu2_amd64.deb ...
node2: Unpacking socat (1.7.3.2-2ubuntu2) ...
node2: Selecting previously unselected package kubelet.
node2: Preparing to unpack .../10-kubelet_1.13.2-00_amd64.deb ...
node2: Unpacking kubelet (1.13.2-00) ...
master: Setting up docker-ce-cli (5:18.09.1~3-0~ubuntu-bionic) ...
master: Setting up kubeadm (1.13.2-00) ...
master: Setting up pigz (2.4-1) ...
master: Setting up docker-ce (5:18.09.1~3-0~ubuntu-bionic) ...
master: update-alternatives: using /usr/bin/dockerd-ce to provide /usr/bin/dockerd (dockerd) in auto mode
master: Created symlink /etc/systemd/system/multi-user.target.wants/docker.service -> /lib/systemd/system/docker.service.
node2: Selecting previously unselected package kubectl.
node2: Preparing to unpack .../11-kubectl_1.13.2-00_amd64.deb ...
node2: Unpacking kubectl (1.13.2-00) ...
master: Created symlink /etc/systemd/system/sockets.target.wants/docker.socket -> /lib/systemd/system/docker.socket.
node2: Selecting previously unselected package kubeadm.
node2: Preparing to unpack .../12-kubeadm_1.13.2-00_amd64.deb ...
node2: Unpacking kubeadm (1.13.2-00) ...
master: Processing triggers for ureadahead (0.100.0-20) ...
master: Processing triggers for libc-bin (2.27-3ubuntu1) ...
master: Processing triggers for systemd (237-3ubuntu10.9) ...
node2: Setting up aufs-tools (1:4.9+20170918-1ubuntu1) ...
node2: Setting up kubernetes-cni (0.6.0-00) ...
node2: Setting up containerd.io (1.2.2-1) ...
node2: Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service -> /lib/systemd/system/containerd.service.
node2: Setting up cri-tools (1.12.0-00) ...
node2: Processing triggers for ureadahead (0.100.0-20) ...
master: ++ apt-mark hold kubelet kubeadm kubectl
node2: Setting up socat (1.7.3.2-2ubuntu2) ...
node2: Setting up cgroupfs-mount (1.4) ...
master: kubelet set on hold.
master: kubeadm set on hold.
master: kubectl set on hold.
master: ++ swapoff -a
master: ++ sed -i '/swap/s/^/#/g' /etc/fstab
master: ++ echo 1
master: ++ '[' false '!=' false ']'
==> master: Running provisioner: shell...
master: Running: inline script
node2: Setting up kubelet (1.13.2-00) ...
master: ++ kubeadm reset -f
master: [preflight] running pre-flight checks
master: [reset] no etcd config found. Assuming external etcd
master: [reset] please manually reset etcd to prevent further issues
master: [reset] stopping the kubelet service
master: [reset] unmounting mounted directories in "/var/lib/kubelet"
master: [reset] deleting contents of stateful directories: [/var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]
master: [reset] deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
master: [reset] deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
master:
master: The reset process does not reset or clean up iptables rules or IPVS tables.
master: If you wish to reset iptables, you must do so manually.
master: For example:
master: iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X
master:
master: If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
master: to reset your system's IPVS tables.
master: ++ kubeadm init --apiserver-advertise-address=192.168.26.10 --pod-network-cidr=10.244.0.0/16 --token yqwhts.q3dgv11alod6rpa5 --token-ttl 0
node2: Created symlink /etc/systemd/system/multi-user.target.wants/kubelet.service -> /lib/systemd/system/kubelet.service.
node2: Processing triggers for libc-bin (2.27-3ubuntu1) ...
node2: Processing triggers for systemd (237-3ubuntu10.9) ...
node2: Setting up libltdl7:amd64 (2.4.6-2) ...
node2: Setting up kubectl (1.13.2-00) ...
node2: Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
master: [init] Using Kubernetes version: v1.13.2
master: [preflight] Running pre-flight checks
master: [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 18.09.1. Latest validated version: 18.06
master: [preflight] Pulling images required for setting up a Kubernetes cluster
master: [preflight] This might take a minute or two, depending on the speed of your internet connection
master: [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
node2: Setting up docker-ce-cli (5:18.09.1~3-0~ubuntu-bionic) ...
node2: Setting up kubeadm (1.13.2-00) ...
node2: Setting up pigz (2.4-1) ...
node2: Setting up docker-ce (5:18.09.1~3-0~ubuntu-bionic) ...
node2: update-alternatives:
node2: using /usr/bin/dockerd-ce to provide /usr/bin/dockerd (dockerd) in auto mode
node2: Created symlink /etc/systemd/system/multi-user.target.wants/docker.service -> /lib/systemd/system/docker.service.
node2: Created symlink /etc/systemd/system/sockets.target.wants/docker.socket -> /lib/systemd/system/docker.socket.
node2: Processing triggers for ureadahead (0.100.0-20) ...
node2: Processing triggers for libc-bin (2.27-3ubuntu1) ...
node2: Processing triggers for systemd (237-3ubuntu10.9) ...
node2: ++ apt-mark hold kubelet kubeadm kubectl
node2: kubelet set on hold.
node2: kubeadm set on hold.
node2: kubectl set on hold.
node2: ++ swapoff -a
node2: ++ sed -i '/swap/s/^/#/g' /etc/fstab
node2: ++ echo 1
node2: ++ '[' false '!=' false ']'
==> node2: Running provisioner: shell...
node2: Running: inline script
node2: ++ kubeadm reset -f
node2: [preflight] running pre-flight checks
node2: [reset] no etcd config found. Assuming external etcd
node2: [reset] please manually reset etcd to prevent further issues
node2: [reset] stopping the kubelet service
node2: [reset] unmounting mounted directories in "/var/lib/kubelet"
node2: [reset] deleting contents of stateful directories: [/var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes]
node2: [reset] deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
node2: [reset] deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
node2:
node2: The reset process does not reset or clean up iptables rules or IPVS tables.
node2: If you wish to reset iptables, you must do so manually.
node2: For example:
node2: iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X
node2:
node2: If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
node2: to reset your system's IPVS tables.
node2: ++ '[' -n '' ']'
node2: ++ kubeadm join --discovery-token-unsafe-skip-ca-verification --token yqwhts.q3dgv11alod6rpa5 192.168.26.10:6443
node2: [preflight] Running pre-flight checks
node2: [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 18.09.1. Latest validated version: 18.06
node2: [discovery] Trying to connect to API Server "192.168.26.10:6443"
node2: [discovery] Created cluster-info discovery client, requesting info from "https://192.168.26.10:6443"
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
master: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
master: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
master: [kubelet-start] Activating the kubelet service
master: [certs] Using certificateDir folder "/etc/kubernetes/pki"
master: [certs] Generating "ca" certificate and key
master: [certs] Generating "apiserver-kubelet-client" certificate and key
master: [certs] Generating "apiserver" certificate and key
master: [certs] apiserver serving cert is signed for DNS names [master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.26.10]
master: [certs] Generating "etcd/ca" certificate and key
master: [certs] Generating "apiserver-etcd-client" certificate and key
master: [certs] Generating "etcd/server" certificate and key
master: [certs] etcd/server serving cert is signed for DNS names [master localhost] and IPs [192.168.26.10 127.0.0.1 ::1]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
master: [certs] Generating "etcd/peer" certificate and key
master: [certs] etcd/peer serving cert is signed for DNS names [master localhost] and IPs [192.168.26.10 127.0.0.1 ::1]
master: [certs] Generating "etcd/healthcheck-client" certificate and key
master: [certs] Generating "front-proxy-ca" certificate and key
master: [certs] Generating "front-proxy-client" certificate and key
master: [certs] Generating "sa" key and public key
master: [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
master: [kubeconfig] Writing "admin.conf" kubeconfig file
master: [kubeconfig] Writing "kubelet.conf" kubeconfig file
master: [kubeconfig] Writing "controller-manager.conf" kubeconfig file
master: [kubeconfig] Writing "scheduler.conf" kubeconfig file
master: [control-plane] Using manifest folder "/etc/kubernetes/manifests"
master: [control-plane] Creating static Pod manifest for "kube-apiserver"
master: [control-plane] Creating static Pod manifest for "kube-controller-manager"
master: [control-plane] Creating static Pod manifest for "kube-scheduler"
master: [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
master: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [Get https://192.168.26.10:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 192.168.26.10:6443: connect: connection refused]
node2: [discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get resource "configmaps" in API group "" in the namespace "kube-public"]
node2: [discovery] Failed to request cluster info, will try again: [configmaps "cluster-info" is forbidden: User "system:anonymous" cannot get resource "configmaps" in API group "" in the namespace "kube-public"]
master: [apiclient] All control plane components are healthy after 20.003519 seconds
master: [uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
master: [kubelet] Creating a ConfigMap "kubelet-config-1.13" in namespace kube-system with the configuration for the kubelets in the cluster
master: [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "master" as an annotation
master: [mark-control-plane] Marking the node master as control-plane by adding the label "node-role.kubernetes.io/master=''"
master: [mark-control-plane] Marking the node master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
master: [bootstrap-token] Using token: yqwhts.q3dgv11alod6rpa5
master: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
master: [bootstraptoken] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
master: [bootstraptoken] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
master: [bootstraptoken] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
master: [bootstraptoken] creating the "cluster-info" ConfigMap in the "kube-public" namespace
master: [addons] Applied essential addon: CoreDNS
master: [addons] Applied essential addon: kube-proxy
master:
master: Your Kubernetes master has initialized successfully!
master:
master: To start using your cluster, you need to run the following as a regular user:
master:
master: mkdir -p $HOME/.kube
master: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
master: sudo chown $(id -u):$(id -g) $HOME/.kube/config
master:
master: You should now deploy a pod network to the cluster.
master: Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
master: https://kubernetes.io/docs/concepts/cluster-administration/addons/
master:
master: You can now join any number of machines by running the following on each node
master: as root:
master:
master: kubeadm join 192.168.26.10:6443 --token yqwhts.q3dgv11alod6rpa5 --discovery-token-ca-cert-hash sha256:eefae1c9f9de2b400647b7d33354949827866fc8556c003dca883b3fc7d6d09f
master: ++ grep -q -- --node-ip= /etc/sysconfig/kubelet
master: grep:
master: /etc/sysconfig/kubelet
master: : No such file or directory
master: ++ sed -i 's/KUBELET_EXTRA_ARGS=/KUBELET_EXTRA_ARGS=--node-ip=192.168.26.10 /' /etc/sysconfig/kubelet
master: sed: can't read /etc/sysconfig/kubelet: No such file or directory
master: ++ systemctl daemon-reload
master: ++ systemctl restart kubelet.service
master: ++ mkdir -p /root/.kube
master: ++ sudo cp -Rf /etc/kubernetes/admin.conf /root/.kube/config
master: +++ id -u
master: +++ id -g
master: ++ sudo chown 0:0 /root/.kube/config
master: ++ '[' flannel == flannel ']'
master: ++ awk '/- --kube-subnet-mgr/{print " - --iface=eth1"}1'
master: ++ kubectl apply -f -
master: ++ curl --retry 5 --fail -s https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
master: clusterrole.rbac.authorization.k8s.io/flannel created
master: clusterrolebinding.rbac.authorization.k8s.io/flannel created
master: serviceaccount/flannel created
master: configmap/kube-flannel-cfg created
master: daemonset.extensions/kube-flannel-ds-amd64 created
master: daemonset.extensions/kube-flannel-ds-arm64 created
master: daemonset.extensions/kube-flannel-ds-arm created
master: daemonset.extensions/kube-flannel-ds-ppc64le created
master: daemonset.extensions/kube-flannel-ds-s390x created
==> master: Running provisioner: shell...
node2: [discovery] Failed to connect to API Server "192.168.26.10:6443": token id "yqwhts" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token
master: Running: inline script
master: secret/kubernetes-dashboard-certs created
master: serviceaccount/kubernetes-dashboard created
master: role.rbac.authorization.k8s.io/kubernetes-dashboard-minimal created
master: rolebinding.rbac.authorization.k8s.io/kubernetes-dashboard-minimal created
master: deployment.apps/kubernetes-dashboard created
master: service/kubernetes-dashboard created
node2: [discovery] Trying to connect to API Server "192.168.26.10:6443"
node2: [discovery] Created cluster-info discovery client, requesting info from "https://192.168.26.10:6443"
node2: [discovery] Failed to connect to API Server "192.168.26.10:6443": token id "yqwhts" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token
node2: [discovery] Trying to connect to API Server "192.168.26.10:6443"
node2: [discovery] Created cluster-info discovery client, requesting info from "https://192.168.26.10:6443"
node2: [discovery] Failed to connect to API Server "192.168.26.10:6443": token id "yqwhts" is invalid for this cluster or it has expired. Use "kubeadm token create" on the master node to creating a new valid token
node2: [discovery] Trying to connect to API Server "192.168.26.10:6443"
node2: [discovery] Created cluster-info discovery client, requesting info from "https://192.168.26.10:6443"
node2: [discovery] Cluster info signature and contents are valid and no TLS pinning was specified, will use API Server "192.168.26.10:6443"
node2: [discovery] Successfully established connection with API Server "192.168.26.10:6443"
node2: [join] Reading configuration from the cluster...
node2: [join] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
node2: [kubelet] Downloading configuration for the kubelet from the "kubelet-config-1.13" ConfigMap in the kube-system namespace
node2: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
node2: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
node2: [kubelet-start] Activating the kubelet service
node2: [tlsbootstrap] Waiting for the kubelet to perform the TLS Bootstrap...
node2: [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "node2" as an annotation
node2:
node2: This node has joined the cluster:
node2: * Certificate signing request was sent to apiserver and a response was received.
node2: * The Kubelet was informed of the new secure connection details.
node2:
node2: Run 'kubectl get nodes' on the master to see this node join the cluster.
node2: ++ KUBELET_EXTRA_ARGS_FILE=/etc/sysconfig/kubelet
node2: ++ '[' '!' -f /etc/sysconfig/kubelet ']'
node2: ++ KUBELET_EXTRA_ARGS_FILE=/etc/default/kubelet
node2: ++ grep -q -- --node-ip= /etc/default/kubelet
node2: ++ sed -i 's/KUBELET_EXTRA_ARGS=/KUBELET_EXTRA_ARGS=--node-ip=192.168.26.12 /' /etc/default/kubelet
node2: ++ systemctl daemon-reload
node2: ++ systemctl restart kubelet.service
make[1]: *** [start] Error 2
make: *** [up] Error 2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment