George Kraft

Results 13 comments of George Kraft

Thanks for the cdk-field-agent attachment. `kubectl describe po` indicates that pods can't deploy because there are no available nodes: ``` Warning FailedScheduling 2m (x20 over 8m) default-scheduler 0/3 nodes are...

Thanks. Taking a quick glance in the DIR archive, it's hitting the same error: ``` kubelet.daemon[4731]: F0515 15:51:14.982974 4731 kubelet.go:1354] Failed to start ContainerManager failed to get rootfs info: cannot...

> Can yo recommend a single charm that I could use to try and debug the deployment? Afraid not. The fatal error is coming from the kubelet service on the...

This happens when LXD is configured to use the `zfs` or `btrfs` storage backend. You'll need to configure LXD to use the `dir` storage backend instead, then start a new...

@sanjeevshar Can you run the cdk-field-agent script and attach the archive it creates? https://github.com/juju-solutions/cdk-field-agent

Huh, that's weird. No idea what would cause the permissions on controllers.yaml to change like that. Can you try changing the owner back and running the cdk-field-agent script again? ```...

Thanks @sanjeevshar. The relevant error comes from `results-2018-05-10-20-14-04.tar.gz/debug/kubernetes-master/0/debug-20180511001210.tar.gz/kubectl/describe-pods`: ``` Failed create pod sandbox: rpc error: code = Unknown desc = failed pulling image "k8s.gcr.io/pause-amd64:3.1": error pulling image configuration: Get https://storage.googleapis.com/us.artifacts.google-containers.appspot.com/containers/images/sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e:...

@sanjeevshar > 1. Why is the script stuck and waiting for ever. The conjure-up spell is waiting for all of the units to indicate that they're "ready" (workload status is...

@sanjeevshar Thanks for the curl output. The `-k` requirement is definitely unusual. Can you run the same curl command with `-v` and share the SSL output? For example, I see...

@vadoverde Calico/canal doesn't work with the localhost/LXD cloud because it uses and requires privileged Docker containers, which do not work in LXD. I'm pretty sure that's the underlying cause of...