[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: openshift start => don't generate master-config.yaml, openshift start master --write-config => generate master-config.yaml, it's a bug or a feature ?



start has two modes - "easy", and "serious". Easy takes command like flags, generates temporary config files, and runs.  It does not generate a config file because the flags take precedence.  Serious is that you want to run from config - so --write-config converts your flags and current state to a config file.  You then run with that --config.  We do not support running with both flags and config because it would be easy to get out of sync and have conflicting settings.

On Feb 24, 2016, at 4:04 AM, Stéphane Klein <contact stephane-klein info> wrote:

Hi,

when I execute :

```
# openshift start
# ls openshift.local.config/master/master-config.yaml
ls: cannot access openshift.local.config/master/master-config.yaml: No such file or directory
...

The "master-config.yaml" config file isn't generated.

Same result with :

```
# openshift start master
# ls openshift.local.config/master/master-config.yaml
ls: cannot access openshift.local.config/master/master-config.yaml: No such file or directory
```

But if I execute :

```
# openshift start master --write-config=openshift.local.config/master/
# ls openshift.local.config/master/master-config.yaml
openshift.local.config/master/master-config.yaml
```

The config file is present.

It's a bug or a feature ? If it's a feature, I don't understand why.

This is the version :

```
# openshift version
openshift v1.1.3
kubernetes v1.2.0-origin
etcd 2.2.2+git
```

Best regards,
_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]