Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operator deployment fails post-v20180108-190394d #292

Closed
cwbeitel opened this issue Jan 11, 2018 · 2 comments
Closed

Operator deployment fails post-v20180108-190394d #292

cwbeitel opened this issue Jan 11, 2018 · 2 comments

Comments

@cwbeitel
Copy link
Contributor

On deployment with helm

helm install $CHART -n tf-job --wait --replace --set rbac.install=true,cloud=gke

observed the following error from tf job operator

> kubectl logs tf-job-operator-6b964974b6-fbskz
flag provided but not defined: -controller-config-file
Usage of /opt/mlkube/tf_operator:
  -alsologtostderr
    	log to standard error as well as files
  -chaos-level int
    	DO NOT USE IN PRODUCTION - level of chaos injected into the TfJob created by the operator. (default -1)
  -controller_config_file string
    	Path to file containing the controller config.
  -gc-interval duration
    	GC interval (default 10m0s)
  -log_backtrace_at value
    	when logging hits line file:N, emit a stack trace
  -log_dir string
    	If non-empty, write log files in this directory
  -logtostderr
    	log to standard error instead of files
  -stderrthreshold value
    	logs at or above this threshold go to stderr
  -v value
    	log level for V logs
  -version
    	Show version and quit
  -vmodule value
    	comma-separated list of pattern=N settings for file-filtered logging

Last tfjob operator version that does not create an error is the following:

https://storage.googleapis.com/tf-on-k8s-dogfood-releases/v20180108-190394d-dirty-e3b0c44/tf-job-operator-chart-0.2.0-v20180108-190394d-dirty-e3b0c44.tgz

Related to #290 @jlewi @gaocegege

@jlewi jlewi mentioned this issue Jan 11, 2018
4 tasks
@gaocegege
Copy link
Member

@jlewi
Copy link
Contributor

jlewi commented Jan 15, 2018

Yes.

@jlewi jlewi closed this as completed Jan 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants