Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

State of Resource 'kubeadm:config:set-ownership' is Invalid #81

Open
RiskyFeryansyahP opened this issue May 19, 2020 · 2 comments
Open

Comments

@RiskyFeryansyahP
Copy link

I have problem when installing firekube, and i'm getting confuse to read the error info, the error like this :

INFO[2020-05-19T05:06:02Z] State of Resource 'kubeadm:config:set-ownership' is Invalid.
Explanation:
{
 "resource": "kubeadm:config:set-ownership",
 "status": "Invalid",
 "reason": "DependencyInvalid",
 "dependencies": [
  {
   "resource": "kubeadm:config:copy",
   "status": "Invalid",
   "reason": "DependencyInvalid",
   "dependencies": [
    {
     "resource": "kubeadm:run-init",
     "status": "Invalid",
     "reason": "DependencyInvalid",
     "dependencies": [
      {
       "resource": "kubeadm:config:images",
       "status": "Invalid",
       "reason": "ApplyError",
       "error": "command exited with 1"
      }
     ]
    }
   ]
  }
 ]
} 

@dlh
Copy link

dlh commented May 25, 2020

I ran into this issue, too.

Running wksctl apply --verbose output this error:

failed to pull image "k8s.gcr.io/kube-apiserver:v1.14.1": output: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39
, error: exit status 1
ERRO[2020-05-25T12:15:51-04:00] Failed                                        resource="kubeadm:config:images"
failed to pull image "k8s.gcr.io/kube-apiserver:v1.14.1": output: Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.39
, error: exit status 1
: command exited with 1
DEBU[2020-05-25T12:15:51-04:00] running command: sudo -n -- sh -c 'rm -f "/tmp/wks_kubeadm_init_config.yaml"' 
ERRO[2020-05-25T12:15:51-04:00] Failed                                        resource="kubeadm:init"
kubeadm join command not found

The fix for me was to update the docker-ce version in cluster.yaml (I used 19.03.8, see diff below). This issue is related to weaveworks/wksctl#195

I also had to remove the sshKeyPath setting from cluster.yaml, but I was testing the new beta versions of wksctl.

Here's the diff which corrected both issues:

index 41963cc..aeb3a41 100644
--- a/cluster.yaml
+++ b/cluster.yaml
@@ -13,7 +13,7 @@ spec:
     value:
       apiVersion: baremetalproviderspec/v1alpha1
       kind: BareMetalClusterProviderSpec
-      sshKeyPath: cluster-key
+      # sshKeyPath: cluster-key
       user: root
       os:
         files:
@@ -32,5 +32,5 @@ spec:
       cri:
         kind: docker
         package: docker-ce
-        version: 18.09.7
+        version: 19.03.8

@RiskyFeryansyahP
Copy link
Author

thanks so much for answer @dlh

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants