You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What kops version are you running? The command kops version, will display
this information.
kops version
Version 1.8.0-beta.1 (git-0a2f949fd)
What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.
What commands did you run? What is the simplest way to reproduce this issue?
Concourse CI was running the equivalent of
kops --state ${KOPS_STATE} -v8 update cluster ${KOPS_CLUSTER_NAME}
What happened after the commands executed?
The command breaks with a kops segfault for the dev environment but the same code from the same github shasum completes successfully for the prod account.
What did you expect to happen?
Expected the dev update cluster command to complete successfully and show me what would kops change.
Please provide your cluster manifest. Execute kops get --name my.example.com -oyaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.
Cluster manifest:
... but does not address why the resource was nil ...
Which resource from the kops cluster manifest, do you think kops thinks it is nil for this dev cluster manifest ?
I've diff-ed the prod [1] and dev cluster manifests and apart from differences in resource names they have the same resources.
[1] context: the prodkops cluster update without --yes works fine.
justinsb
added a commit
to justinsb/kops
that referenced
this issue
Dec 1, 2017
kops
version are you running? The commandkops version
, will displaythis information.
kubectl version
will print theversion if a cluster is running or provide the Kubernetes version specified as
a
kops
flag.What happened after the commands executed?
The command breaks with a
kops
segfault for thedev
environment but the same code from the same github shasum completes successfully for theprod
account.What did you expect to happen?
Expected the
dev
update cluster command to complete successfully and show me what would kops change.Please provide your cluster manifest. Execute
kops get --name my.example.com -oyaml
to display your cluster manifest.You may want to remove your cluster name and other sensitive information.
Cluster manifest:
-v 10
flag.https://gist.github.com/stefancocora/ab2cb02cdd045ec404a318f36816280e
Concourse CI logs:
Possibly related to:
The text was updated successfully, but these errors were encountered: