On Thu, Sep 14, 2017 at 3:29 PM, Lalatendu Mohanty <[email protected]> wrote:
> > > On Thu, Sep 14, 2017 at 11:01 PM, Burr Sutter <[email protected]> wrote: > >> I think that was it...i had not encounted a timeout issue like that >> before and the error message is less than ideal :-) >> >> is there a way to offer the user a better error message? >> > > What is your suggestion about the error message? Also error comes from oc > binary. So we should raise the issue with OpenShift project. > Instead of " server took too long " we could say " it appears your token has timed out, please login in again" I have no idea where the Origin folks keep their jira/bz/issues tracker, please do file a bug with them. > > -Lala > >> >> On Thu, Sep 14, 2017 at 12:33 PM, Praveen Kumar < >> [email protected]> wrote: >> >>> On Wed, Sep 13, 2017 at 1:57 AM, Burr Sutter <[email protected]> wrote: >>> > "error: server took too long to respond with version information." >>> > >>> > >>> > ./minishift version >>> > >>> > minishift v1.5.0+ae62cf2 >>> > >>> > >>> > ./minishift oc-env >>> > >>> > export PATH="/Users/burr/.minishift/cache/oc/v3.6.0:$PATH" >>> > >>> > >>> > oc version >>> > >>> > oc v3.6.0+c4dd4cf >>> > >>> > kubernetes v1.6.1+5115d708d7 >>> > >>> > features: Basic-Auth >>> > >>> > error: server took too long to respond with version information. >>> >>> >>> Burr, looks like oc login timeout happened can you try below steps. >>> >>> $ minishift ip >>> $ oc login <minishift-ip>:8443 >>> $ oc version >>> >>> >>> >>> -- >>> Praveen Kumar >>> http://fedoraproject.org/wiki/User:Kumarpraveen >>> http://fedoraproject.org/ >>> http://kumar-pravin.blogspot.com >>> >> >> >> _______________________________________________ >> Container-tools mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/container-tools >> >> >
_______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
