Re: prune tags

2016-06-21 Thread Clayton Coleman
Prune definitely knows that. We also know the time the tag was last updated. On Jun 21, 2016, at 8:57 PM, Philippe Lafoucrière < philippe.lafoucri...@tech-angels.com> wrote: On Tue, Jun 21, 2016 at 2:33 PM, Clayton Coleman wrote: > I don't think we have anything to prune

Re: prune tags

2016-06-21 Thread Philippe Lafoucrière
On Tue, Jun 21, 2016 at 2:33 PM, Clayton Coleman wrote: > I don't think we have anything to prune tags (since we don't know what > tag names to prune). We'd need some way of knowing the tag was "not > important" before it could be pruned. > I would say, if no stream nor

Re: All my ipfailover pods are in "Entering MASTER STATE", it's not fair ?

2016-06-21 Thread Ram Ranganathan
Couldn't figure out if you have a problem or not (or it was just a question) from the email thread. What does "ip addr show" on all the nodes show? This is the nodes where your ipfailover pods are running. Are the VIPs allocated to both nodes (assuming you have from the logs), then it is likely

Re: prune tags

2016-06-21 Thread Clayton Coleman
I don't think we have anything to prune tags (since we don't know what tag names to prune). We'd need some way of knowing the tag was "not important" before it could be pruned. On Tue, Jun 21, 2016 at 2:21 PM, Philippe Lafoucrière wrote: > Hi, > > As we're

prune tags

2016-06-21 Thread Philippe Lafoucrière
Hi, As we're using openshift for continuous deployments, we often have a lot of tags per ImageStream (to test branches). We would love to see these unused tags pruned, like other objects. Is there something in the roadmap? Thanks, Philippe -- Philippe Lafoucrière - CEO

RE: MySQL: Readiness probe failed

2016-06-21 Thread Den Cowboy
So it seems the mysql isn't able to resolve the service name mysql to its IP: because this works inside the container: mysql -u user -h 172.30.183.216 -p password: xx ---> mysql (works) This doesn't work: mysql -u user h mysql -p password: xx --> error unkown mysql server host 'mysql' mysql is

Re: weird issue with etcd

2016-06-21 Thread Julio Saura
etcdctl -C https://openshift-balancer01:2379,https://openshift-balancer02:2379 --ca-file=/etc/origin/master/maer.etcd-ca.crt --cert-file=/etc/origin/master/master.etcd-client.crt --key-file=/etc/origin/master/master.etcd-client.key member list 12c8a31c8fcae0d4: name=openshift-balancer02

Re: weird issue with etcd

2016-06-21 Thread Julio Saura
regarding the certs, i used ansible to install origin so i guess ansible should have done it right … > El 21 jun 2016, a las 15:29, Julio Saura escribió: > > hello > > yes, they are synced with and internal NTP server .. > > gonna try ectdctl thanks! > > >> El 21 jun

Re: MySQL: Readiness probe failed

2016-06-21 Thread Philippe Lafoucrière
Have you tried to raise initialDelaySeconds ? ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: MySQL: Readiness probe failed

2016-06-21 Thread Martin Nagy
Ah, ignore that, I didn't realize the warnings about ioctl are irrelevant. On Tue, Jun 21, 2016 at 4:56 PM, Martin Nagy wrote: > Are you referring to templates in origin/examples/db-templates? > Can you edit the template and remove the '-i' passed to /bin/sh > and see if it

Re: MySQL: Readiness probe failed

2016-06-21 Thread Martin Nagy
Are you referring to templates in origin/examples/db-templates? Can you edit the template and remove the '-i' passed to /bin/sh and see if it helps? On Tue, Jun 21, 2016 at 4:44 PM, Den Cowboy wrote: > I'm using the MySQL template and started it with the right environment

MySQL: Readiness probe failed

2016-06-21 Thread Den Cowboy
I'm using the MySQL template and started it with the right environment variables The MySQL is running fine but I got this error and I'm not able to access my mysql on its service name: mysql -u myuser -h mysql -p password:xxx Readiness probe failed: sh: cannot set terminal process group (-1):

Re: weird issue with etcd

2016-06-21 Thread Julio Saura
hello yes only have two .. i know 3 is the number but i guessed that it might also work with 2 :/ yes both etcd servers can connect between them with the peer port .. i have also checked it .. so maybe is because i only have three etcd? thanks scott!! > El 21 jun 2016, a las 15:19, Scott

Re: weird issue with etcd

2016-06-21 Thread Julio Saura
hello yes, they are synced with and internal NTP server .. gonna try ectdctl thanks! > El 21 jun 2016, a las 15:20, Jason DeTiberus escribió: > > On Tue, Jun 21, 2016 at 7:28 AM, Julio Saura > wrote: >> yes >> >>

Re: weird issue with etcd

2016-06-21 Thread Jason DeTiberus
On Tue, Jun 21, 2016 at 7:28 AM, Julio Saura wrote: > yes > > working > > [root@openshift-master01 ~]# telnet X 2380 > Trying ... > Connected to . > Escape character is '^]'. > ^CConnection closed by foreign host. Have you verified that time is syncd between the

Re: weird issue with etcd

2016-06-21 Thread Scott Dodson
Julio, First, it looks like you've only got two etcd hosts, in order to tolerate failure of a single host you'll want three. >From your master config it looks like your two etcd hosts are openshift-balancer01 and openshift-balancer02, can each of those hosts connect to each other on port 2380?

Re: weird issue with etcd

2016-06-21 Thread Julio Saura
yes working [root@openshift-master01 ~]# telnet X 2380 Trying ... Connected to . Escape character is '^]'. ^CConnection closed by foreign host. > El 21 jun 2016, a las 13:21, Jason DeTiberus > escribió: > > Did you verify

Re: weird issue with etcd

2016-06-21 Thread Jason DeTiberus
Did you verify connectivity over the peering port as well (2380)? On Jun 21, 2016 7:17 AM, "Julio Saura" wrote: > hello > > same problem > > jun 21 13:11:03 openshift-master01 atomic-openshift-master-api[59618]: > F0621 13:11:03.155246 59618 auth.go:141] error #0: dial tcp

Re: weird issue with etcd

2016-06-21 Thread Julio Saura
hello same problem jun 21 13:11:03 openshift-master01 atomic-openshift-master-api[59618]: F0621 13:11:03.155246 59618 auth.go:141] error #0: dial tcp :2379: connection refused ( the one i rebooted ) jun 21 13:11:03 openshift-master01 atomic-openshift-master-api[59618]: error #1: client: