No. I don't recall adding any exception or special config to my system...
➜ OpenShift curl -v -XGET -H "User-Agent: oc/v1.1.2 (darwin/amd64)
openshift/2711160" https://mgmt.os.gu.edu:443/
* Trying 141.161.99.87...
* Connected to mgmt.os.gu.edu (141.161.99.87) port 443 (#0)
* TLS 1.2 connecti
What does the curl call without -k show?
Wondering if your system CA bundle is unhappy with the proxy cert. Did you
have to add exceptions for your browsers?
On Feb 28, 2016, at 3:38 PM, Mohamed Lrhazi
wrote:
Very weird... looks like my own exact curl is behaving differently?
On Sun, Feb 28,
Very weird... looks like my own exact curl is behaving differently?
On Sun, Feb 28, 2016 at 3:37 PM, Mohamed Lrhazi <
mohamed.lrh...@georgetown.edu> wrote:
> ➜ OpenShift oc login https://mgmt.os.gu.edu -u ml623 --loglevel=18
> I0228 15:35:03.590599 30156 loader.go:241] Config loaded from file
➜ OpenShift oc login https://mgmt.os.gu.edu -u ml623 --loglevel=18
I0228 15:35:03.590599 30156 loader.go:241] Config loaded from file
/Users/mohamed/.kube/config
I0228 15:35:03.590934 30156 loader.go:241] Config loaded from file
/Users/mohamed/.kube/config
I0228 15:35:03.591206 30156 loader
What about a curl with the :443 port included?
On Feb 28, 2016, at 3:28 PM, Mohamed Lrhazi
wrote:
a GET curl request also works, instead of HEAD:
➜ curl https://mgmt.os.gu.edu:443/ -i
HTTP/1.1 200 OK
Content-Type: application/json
Date: Sun, 28 Feb 2016 20:27:13 GMT
Content-Length: 204
{
"
a GET curl request also works, instead of HEAD:
➜ curl https://mgmt.os.gu.edu:443/ -i
HTTP/1.1 200 OK
Content-Type: application/json
Date: Sun, 28 Feb 2016 20:27:13 GMT
Content-Length: 204
{
"paths": [
"/api",
"/api/v1",
"/controllers",
"/healthz",
"/healthz/ping",
"/h
Thanks Jordan.. Here it is:
➜ oc login https://mgmt.os.gu.edu -u ml623 --loglevel=8
I0228 15:23:13.811505 30087 loader.go:241] Config loaded from file
/Users/mohamed/.kube/config
I0228 15:23:13.811805 30087 loader.go:241] Config loaded from file
/Users/mohamed/.kube/config
I0228 15:23:13.812
What do you see with --loglevel=8?
On Feb 28, 2016, at 3:01 PM, Mohamed Lrhazi
wrote:
Hello,
My oc on OS X, works if I point directly to the real IP/port of the origin
server (port 8443)... but if I tried using a VIP which terminates SSL, the
re-encrypts to the server on 8443.. I get this erro
Hello,
My oc on OS X, works if I point directly to the real IP/port of the origin
server (port 8443)... but if I tried using a VIP which terminates SSL, the
re-encrypts to the server on 8443.. I get this error:
➜ oc login https://mgmt.os.gu.edu -u ml623
Unable to connect to the server: read tc
Thanks!
On Sun, Feb 28, 2016 at 10:11 AM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
> Hi Mohamed, your accessModes don't match.
> You're asking for
>
> spec:
> accessModes:
> - "ReadWriteOnce"
>
> while your pv is accepting "RWX" ("ReadWriteMany").
>
> You can edit
Hi Mohamed, your accessModes don't match.
You're asking for
spec:
accessModes:
- "ReadWriteOnce"
while your pv is accepting "RWX" ("ReadWriteMany").
You can edit your pv to add "ReadWriteMany" in the access modes, and it
will bind it right away.
Hello everyone,
I tried to create a cluster on Openstack. I used command below, openstack heat
stack has been created without pb. In the created Neurtron subnet, DNS is
8.8.8.8 and 8.8.4.4 which is correct. But the DNS host created in this cluster
(hostname is e2e-dns) use itself as nameserver
12 matches
Mail list logo
