Uploaded image for project: 'Red Hat Container Development Kit'
  1. Red Hat Container Development Kit
  2. CDK-57

CDK 2.3 can't start OCP 3.4

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: 2.3.0.GA
    • Fix Version/s: None
    • Component/s: openshift
    • Labels:

      Description

      I'm trying to use OCP 3.4 using the IMAGE_TAG="v3.4.0.39-2" in the Vagrant file.
      If the VM is new, then I can't deploy any app because the docker registry can't be started (TLS problems).

      time="2017-01-20T07:22:20.870941269Z" level=info msg="redis not configured" go.version=go1.7.4 instance.id=868c65f0-28a4-4dca-9705-e3f5372e3d0d 
      time="2017-01-20T07:22:20.8710505Z" level=info msg="Starting upload purge in 7m0s" go.version=go1.7.4 instance.id=868c65f0-28a4-4dca-9705-e3f5372e3d0d 
      time="2017-01-20T07:22:20.894373544Z" level=info msg="using inmemory blob descriptor cache" go.version=go1.7.4 instance.id=868c65f0-28a4-4dca-9705-e3f5372e3d0d 
      time="2017-01-20T07:22:20.894424579Z" level=info msg="OpenShift registry middleware initializing" 
      time="2017-01-20T07:22:20.894435287Z" level=info msg="Using Origin Auth handler" 
      time="2017-01-20T07:22:20.894721078Z" level=debug msg="configured \"openshift\" access controller" go.version=go1.7.4 instance.id=868c65f0-28a4-4dca-9705-e3f5372e3d0d 
      time="2017-01-20T07:22:20.894754334Z" level=debug msg="configured token endpoint at \"/openshift/token\"" 
      time="2017-01-20T07:22:20.894859674Z" level=info msg="listening on :5000, tls" go.version=go1.7.4 instance.id=868c65f0-28a4-4dca-9705-e3f5372e3d0d 
      I0120 07:22:24.884332       1 logs.go:41] http: TLS handshake error from 172.17.0.1:50320: tls: first record does not look like a TLS handshake
      I0120 07:22:28.435249       1 logs.go:41] http: TLS handshake error from 172.17.0.1:50322: tls: first record does not look like a TLS handshake
      I0120 07:22:38.433875       1 logs.go:41] http: TLS handshake error from 172.17.0.1:50332: tls: first record does not look like a TLS handshake
      I0120 07:22:38.435892       1 logs.go:41] http: TLS handshake error from 172.17.0.1:50334: tls: first record does not look like a TLS handshake
      

      If the VM was not a new one but just restarted from OCP 3.3, then deploy fails because of invalid access rights:

      --> Scaling node-1 to 1
      --> Error listing events for replication controller node-1: User "system:serviceaccount:node:deployer" cannot list events in project "node"
      error: couldn't scale node-1 to 1: User "system:serviceaccount:node:deployer" cannot watch replicationcontrollers in project "node"
      

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jeffmaury Jeff MAURY
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: