Re: Command to start/top a cluster gracefully
Am 10.10.2018 um 11:22 schrieb Marc Ledent: > Hi all, > > Is there a command to stop/start an openshift cluster gracefully. "oc cluster" > commands are acting only for a local all-in-one cluster... Do you mean something like this? * Scale all dc/rc/ds to 0 * stop all node processes * stop all master process * stop all etc processes * stop all docker processes * shutdown all machines I don't know a easier way maybe there is a playbook in the ansible repo Regards Aleks > Thanks in advance, > Marc > > > > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: how to disable the ansible service broker?
Hi. Am 10.10.2018 um 17:25 schrieb Marc Boorshtein: > > > Which release is this one? > > > > 3.9 I face similar issue at upgrade process. There is a pull request to fix the handling of the variable https://github.com/openshift/openshift-ansible/pull/9770 I hope this pull request will be fast released. You can try to set the following vars as mentioned in this comment https://github.com/openshift/openshift-ansible/issues/8705#issuecomment-396459919 ``` |openshift_service_catalog_remove=true openshift_enable_service_catalog=true ansible_service_broker_remove=true ansible_service_broker_install=false template_service_broker_remove=true template_service_broker_install=false |``` Regards Aleks || > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
difficulty upgrading from 3.9 to 3.10 with glusterfs.
I'm trying to run the control-plan upgrade and its filing when checking the
health of glsuterfs. Here's the output from ansible:
(1, '\r\n{"msg": "volume heketidbstorage is not ready",
"failed": true, "state": "unknown", "changed": false, "invocation":
{"module_args": {"cluster_name": "storage", "exclude_node": "os.demo.lan",
"oc_namespace": "glusterfs", "oc_conf":
"/etc/origin/master/admin.kubeconfig", "oc_bin": "oc"}}}\r\n',
I ran oc adm migrate storage --include=* --loglevel=2 --confirm --config
/etc/origin/master/admin.kubeconfig which output no errors. How do I
approach debugging this?
Thanks
Marc
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: how to disable the ansible service broker?
Which release is this one? > > > 3.9 ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: OpenShift Origin on AWS
> Oh wow, I figured we’d have to blow away the cluster to get the scaling groups. Was most of the work on the masters? Because I presume you just deleted the 3.6 nodes and recreated them in the scaling group? The masters were ok (they are the only nodes not in a scaling group at the moment), there weren't too many changes to make during the upgrade for them. The majority of the work was getting the AMI just right so new instances in a scaling group could join the cluster without any intervention from us. There were a few bits of trial and error in getting the contents of provisioning_vars.yml suitable for our cluster. As the new node gets its configuration from a configmap on the cluster we spent a bit of time getting that set up along with automating the certificate signing requests so a node could be auto approved. > > (I'm a colleague of Dave Conde by the way so we worked on it together) ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: how to disable the ansible service broker?
Which release is this one? On Wed, Oct 10, 2018 at 1:55 PM Marc Boorshtein wrote: > I added the following to my inventory: > > ansible_service_broker_install=false > ansible_service_broker_remove=true > > and then ran the api-server playbook but its still there. Is there a > different playbook I'm supposed to use? > > Thanks > Marc > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
how to disable the ansible service broker?
I added the following to my inventory: ansible_service_broker_install=false ansible_service_broker_remove=true and then ran the api-server playbook but its still there. Is there a different playbook I'm supposed to use? Thanks Marc ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Command to start/top a cluster gracefully
Hi all, Is there a command to stop/start an openshift cluster gracefully. "oc cluster" commands are acting only for a local all-in-one cluster... Thanks in advance, Marc smime.p7s Description: S/MIME Cryptographic Signature ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
