Bug 1276211 - Couldn't connect terminal to pod's container on iPad and iPhone
Couldn't connect terminal to pod's container on iPad and iPhone
Product: OpenShift Origin
Classification: Red Hat
Component: Management Console (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Jessica Forrester
Depends On:
  Show dependency treegraph
Reported: 2015-10-29 01:52 EDT by yapei
Modified: 2015-10-29 09:25 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-29 09:25:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
iPad-Terminal (60.67 KB, image/png)
2015-10-29 02:16 EDT, yapei
no flags Details
iPhone-Terminal (54.68 KB, image/png)
2015-10-29 02:17 EDT, yapei
no flags Details

  None (edit)
Description yapei 2015-10-29 01:52:55 EDT
Description of problem:
For iPad and iPhone, when open the 'Terminal' page of one running pod, it says 'couldn't connect to the container, do you have sufficient privileges?'

Version-Release number of selected component (if applicable):
oc v1.0.6-1053-gbd6a762
kubernetes v1.2.0-alpha.1-1107-g4c8e6f4

How reproducible:

Steps to Reproduce:
1.Create a template
$ oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/sample-app/application-template-stibuild.json
2.Create app from template from web console
3. Wait for all pods to be running
4.Open 'Terminal' page for database-## pod

Actual results:
Error message on terminal page "couldn't connect to the container, do you have sufficient privileges?"

Expected results:
Should successfully connect the terminal to pod's container 

Additional info:
On Mac safari it works as expected
Comment 1 yapei 2015-10-29 02:16 EDT
Created attachment 1087381 [details]
Comment 2 yapei 2015-10-29 02:17 EDT
Created attachment 1087382 [details]
Comment 4 Jessica Forrester 2015-10-29 09:25:02 EDT
This is the known issue with websockets in safari/iOS when the self-signed cert has not been installed.

You can install a cert on iOS by putting the cert file at some location you can hit within the browser.  When iOS safari goes to download it, it will ask you if you want to Install the cert.

The cert you want is the openshift.local.config/master/ca.crt

Once I did this I was able to use the terminal on iOS

Note You need to log in before you can comment on or make changes to this bug.