openshift / openshift/origin

oc cluster up 3.9 fails on Fedora 29

Open
#21,476 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

lifecycle/frozen
Dominant language
Go
Stars
8.7k
Forks
4.8k
Avg merge
4d 10h
Merged PRs (30d)
53

Description

Running oc cluster up that used to work on Fedora 28 now fails on Fedora 29.

[provide a description of the issue]

Version
# oc version
oc v3.9.0+191fece
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO
Steps To Reproduce
  1. mkdir -p /var/lib/origin/etcd-data
  2. oc cluster up --host-data-dir /var/lib/origin/etcd-data --use-existing-config --public-hostname=master.example.test --version=v3.9.0
Current Result
Using nsenter mounter for OpenShift volumes
Using 127.0.0.1 as the server IP
Starting OpenShift using openshift/origin:v3.9.0 ...
-- Starting OpenShift container ... 
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
   OpenShift server started
-- Adding default OAuthClient redirect URIs ... OK
-- Installing registry ... 
   scc "privileged" added to: ["system:serviceaccount:default:registry"]
-- Installing router ... OK
-- Importing image streams ... OK
-- Importing templates ... OK
-- Importing internal templates ... OK
-- Installing web console ... FAIL
   Error: failed to start the web console server: timed out waiting for the condition
Expected Result

The same as on Fedora 28:

Pulling image openshift/origin:v3.9.0
Pulled 1/4 layers, 31% complete
Pulled 2/4 layers, 76% complete
Pulled 3/4 layers, 85% complete
Pulled 4/4 layers, 100% complete
Extracting
Image pull complete
Using nsenter mounter for OpenShift volumes
Using 127.0.0.1 as the server IP
Starting OpenShift using openshift/origin:v3.9.0 ...
OpenShift server started.

The server is accessible via web console at:
    https://master.example.test:8443

You are logged in as:
    User:     developer
    Password: <any value>

To login as administrator:
    oc login -u system:admin

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the oc cluster up command on Fedora 29 with openshift/origin:v3.9.0, focusing on the web console startup timeout. Compare the output with Fedora 28 and inspect the web console startup logs. Done means the command completes and reports an accessible web console as shown in the expected result.

Written by the indexing model from the issue text.

Assessment

Tech stack
fedora, go, linux
Domain
cli, devops, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.