diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2017-10-16 08:28:27 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-16 08:28:27 -0700 |
| commit | 7359d9902a2d7d701c0e32d6bc6a341b3eea4e13 (patch) | |
| tree | 1841801f551b28618f0e96d38a6f2f97eadaa5cc /inventory/byo/hosts.byo.glusterfs.registry-only.example | |
| parent | 27321df000f4789fa3876fdb43e4b083fe55bdcb (diff) | |
| parent | 8b45cff69c9ab5f99ef57911a483da5d8bd13c72 (diff) | |
| download | openshift-7359d9902a2d7d701c0e32d6bc6a341b3eea4e13.tar.gz openshift-7359d9902a2d7d701c0e32d6bc6a341b3eea4e13.tar.bz2 openshift-7359d9902a2d7d701c0e32d6bc6a341b3eea4e13.tar.xz openshift-7359d9902a2d7d701c0e32d6bc6a341b3eea4e13.zip | |
Merge pull request #5733 from ingvagabund/data-migrate-of-embedded-etcd-not-allowed
Automatic merge from submit-queue.
data migration of embedded etcd not allowed
The v2->v3 migration of an embedded etcd is depricated. Instead, one needs to run:
1. `playbooks/byo/openshift-etcd/embedded2external.yml` to migrate the embedded etcd to an external one (see https://github.com/openshift/openshift-ansible/pull/5672)
2. then `playbooks/byo/openshift-etcd/migrate.yml` to migrate the v2 data to v3 data
Diffstat (limited to 'inventory/byo/hosts.byo.glusterfs.registry-only.example')
0 files changed, 0 insertions, 0 deletions