Bug 1733892
| Summary: | [IPI on OSP]Image registry pod cannot be running | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
| Component: | Image Registry | Assignee: | Corey Daley <cdaley> |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.0 | CC: | adam.kaplan, aos-bugs, mfedosin, wjiang |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:33:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1733867 | ||
| Bug Blocks: | |||
Verified on 4.2.0-0.nightly-2019-08-15-232721
➜ ~ oc describe co image-registry
Name: image-registry
Namespace:
Labels: <none>
Annotations: <none>
API Version: config.openshift.io/v1
Kind: ClusterOperator
Metadata:
Creation Timestamp: 2019-08-16T07:04:58Z
Generation: 1
Resource Version: 12613
Self Link: /apis/config.openshift.io/v1/clusteroperators/image-registry
UID: 28c0eb74-bff4-11e9-8abc-fa163e1e8b2b
Spec:
Status:
Conditions:
Last Transition Time: 2019-08-16T07:05:52Z
Message: The registry is ready
Reason: Ready
Status: True
Type: Available
Last Transition Time: 2019-08-16T07:05:52Z
Message: The registry is ready
Reason: Ready
Status: False
Type: Progressing
Last Transition Time: 2019-08-16T07:04:58Z
Status: False
Type: Degraded
Extension: <nil>
Related Objects:
Group: rbac.authorization.k8s.io
Name: system:registry
Resource: clusterroles
Group: rbac.authorization.k8s.io
Name: registry-registry-role
Resource: clusterrolebindings
Group:
Name: registry
Namespace: openshift-image-registry
Resource: serviceaccounts
Group:
Name: serviceca
Namespace: openshift-image-registry
Resource: configmaps
Group:
Name: image-registry-certificates
Namespace: openshift-image-registry
Resource: configmaps
Group:
Name: image-registry-private-configuration
Namespace: openshift-image-registry
Resource: secrets
Group: config.openshift.io
Name: cluster
Resource: images
Group: apps
Name: node-ca
Namespace: openshift-image-registry
Resource: daemonsets
Group:
Name: image-registry
Namespace: openshift-image-registry
Resource: services
Group: apps
Name: image-registry
Namespace: openshift-image-registry
Resource: deployments
Versions:
Name: operator
Version: 4.2.0-0.nightly-2019-08-15-232721
Events: <none>
➜ ~ oc get pods -n openshift-image-registry
NAME READY STATUS RESTARTS AGE
cluster-image-registry-operator-84db8757f6-gjhgg 2/2 Running 0 41m
image-registry-784b5b9484-94xfk 1/1 Running 0 41m
node-ca-75tht 1/1 Running 0 41m
node-ca-9v224 1/1 Running 0 41m
node-ca-bvjqc 1/1 Running 0 41m
node-ca-lb2b4 1/1 Running 0 41m
node-ca-nhflr 1/1 Running 0 41m
node-ca-pml5s 1/1 Running 0 38m
➜ ✗ oc new-app centos/ruby-25-centos7~https://github.com/sclorg/ruby-ex.git
--> Found container image cb490f3 (4 months old) from Docker Hub for "centos/ruby-25-centos7"
Ruby 2.5
--------
Ruby 2.5 available as container is a base platform for building and running various Ruby 2.5 applications and frameworks. Ruby is the interpreted scripting language for quick and easy object-oriented programming. It has many features to process text files and to do sy
stem management tasks (as in Perl). It is simple, straight-forward, and extensible.
Tags: builder, ruby, ruby25, rh-ruby25
* An image stream tag will be created as "ruby-25-centos7:latest" that will track the source image
* A source build using source code from https://github.com/sclorg/ruby-ex.git will be created
* The resulting image will be pushed to image stream tag "ruby-ex:latest"
* Every time "ruby-25-centos7:latest" changes a new build will be triggered
* This image will be deployed in deployment config "ruby-ex"
* Port 8080/tcp will be load balanced by service "ruby-ex"
* Other containers can access this service through the hostname "ruby-ex"
--> Creating resources ...
imagestream.image.openshift.io "ruby-25-centos7" created
imagestream.image.openshift.io "ruby-ex" created
buildconfig.build.openshift.io "ruby-ex" created
deploymentconfig.apps.openshift.io "ruby-ex" created
service "ruby-ex" created
--> Success
Build scheduled, use 'oc logs -f bc/ruby-ex' to track its progress.
Application is not exposed. You can expose services to the outside world by executing one or more of the commands below:
'oc expose svc/ruby-ex'
Run 'oc status' to view your app.
➜ ~ oc get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ruby-ex-1-build 0/1 Completed 0 6m5s 10.129.2.9 wjosp0816d-p6jqc-worker-np44n <none> <none>
ruby-ex-1-deploy 0/1 Completed 0 5m6s 10.129.2.10 wjosp0816d-p6jqc-worker-np44n <none> <none>
ruby-ex-1-dq4vs 1/1 Running 0 5m5s 10.129.2.11 wjosp0816d-p6jqc-worker-np44n <none> <none>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922 |
From the discussion with Wenjing Zheng I got that you don't set neither Project Domain ID nor Name in the clouds.yaml file. But it's necessary if you do not provide the Project ID, but just its Name. Since project names are not unique globally Keystone also needs a Domain the Project belongs to. If the information is not provided, then Swift fails to authenticate. The clouds.yaml file given to me by Wenjing Zheng: clouds: openstack: auth: auth_url: xxx username: xxx password: xxx project_name: xxx user_domain_name: xxx region_name: regionOne interface: public indentity_api_version: 3 A fixed clouds.yaml clouds: openstack: auth: auth_url: xxx username: xxx password: xxx project_name: xxx user_domain_name: xxx project_domain_name: xxx <- This line is important, normally the value is the same as for user_domain_name region_name: regionOne interface: public indentity_api_version: 3