cancel
Showing results for 
Search instead for 
Did you mean: 
root_user
Cadet
Cadet
  • 2,013 Views

Issue when pushing new ImageStream - DO288 course

I'm having this issue when trying to build any application on course DO288. I already deleted and recreated the entire lab setup but it doesn't gets better. 

 

.....
STEP 9: CMD /usr/libexec/s2i/run
STEP 10: COMMIT temp.builder.openshift.io/username-probes/probes-1:261f2be0
Getting image source signatures
Copying blob sha256:5b6b46f31018cc1b533427832cffa833c7fe543a481fbb2a27eda74f8e9d37d8
Copying blob sha256:e6338cb596e5ce58d0a41af85821eb42f75045b355f31a139b7778e61af86717
Copying blob sha256:077890f7cb5fcaa6b1ad5483c48ab0ae8c9e6c5c32c13e06dc7a102669c7ee44
Copying blob sha256:2c08f8fc35457eaa49b1face4be6a6902e232ccc24d46f5520d288299525915a
Copying blob sha256:a95550892f9570a36c7df3550e0dd577e76a44b2c5429dd85aeb8a9d03f6afc5
Copying blob sha256:eee77a1bac927057c5f5268ef68fda6459ba134ae9243a28117f80dfe21f7c5b
Copying config sha256:f2a4b34efcc33b86c80e373434cec60e545388a86f602a5f06cb48d84ee4717d
Writing manifest to image destination
Storing signatures
--> f2a4b34efcc
f2a4b34efcc33b86c80e373434cec60e545388a86f602a5f06cb48d84ee4717d

Pushing image image-registry.openshift-image-registry.svc:5000/username-probes/probes:latest ...
Getting image source signatures
Copying blob sha256:eee77a1bac927057c5f5268ef68fda6459ba134ae9243a28117f80dfe21f7c5b
Copying blob sha256:1f209e06e85d1c9a1b44b7a5b87360d7976245957624fcb9eededb7b5a8a0651
Copying blob sha256:a8d8a88bbf1f0800d17bbd5bf3d3d8de6d755ccabfd019abf042f9f1b6c88d19
Copying blob sha256:15038f2f96bce3594a690ae501b9a380434face93ca0940d6a34ef5020f311f9
Copying blob sha256:1255769d9dc0e834961b135c84a9e76c70b55c7176f8982192e579916737f7f4
Copying blob sha256:0a2284aba01f1b65e6cf64dad35426b5c36d18c12a9006d958a134cec6fe8e9c
Successfully pushed image-registry.openshift-image-registry.svc:5000/username-probes/probes:latest
Warning: Push failed, retrying in 5s ...
Getting image source signatures
Copying blob sha256:eee77a1bac927057c5f5268ef68fda6459ba134ae9243a28117f80dfe21f7c5b
Copying blob sha256:0a2284aba01f1b65e6cf64dad35426b5c36d18c12a9006d958a134cec6fe8e9c
Copying blob sha256:1255769d9dc0e834961b135c84a9e76c70b55c7176f8982192e579916737f7f4
Copying blob sha256:1f209e06e85d1c9a1b44b7a5b87360d7976245957624fcb9eededb7b5a8a0651
Copying blob sha256:a8d8a88bbf1f0800d17bbd5bf3d3d8de6d755ccabfd019abf042f9f1b6c88d19
Copying blob sha256:15038f2f96bce3594a690ae501b9a380434face93ca0940d6a34ef5020f311f9
Successfully pushed image-registry.openshift-image-registry.svc:5000/username-probes/probes:latest
Warning: Push failed, retrying in 5s ...
Getting image source signatures
Copying blob sha256:eee77a1bac927057c5f5268ef68fda6459ba134ae9243a28117f80dfe21f7c5b
Copying blob sha256:a8d8a88bbf1f0800d17bbd5bf3d3d8de6d755ccabfd019abf042f9f1b6c88d19
Copying blob sha256:15038f2f96bce3594a690ae501b9a380434face93ca0940d6a34ef5020f311f9
Copying blob sha256:0a2284aba01f1b65e6cf64dad35426b5c36d18c12a9006d958a134cec6fe8e9c
Copying blob sha256:1f209e06e85d1c9a1b44b7a5b87360d7976245957624fcb9eededb7b5a8a0651
Copying blob sha256:1255769d9dc0e834961b135c84a9e76c70b55c7176f8982192e579916737f7f4
Successfully pushed image-registry.openshift-image-registry.svc:5000/username-probes/probes:latest
Warning: Push failed, retrying in 5s ...
Registry server Address:
Registry server User Name: serviceaccount
Registry server Email: serviceaccount@example.org
Registry server Password: <<non-empty>>
error: build error: Failed to push image: error copying layers and metadata from "containers-storage:[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.imagestore=/var/lib/shared]image-registry.openshift-image-registry.svc:5000/username-probes/probes:latest" to "docker://image-registry.openshift-image-registry.svc:5000/username-probes/probes:latest": Error writing blob: Error initiating layer upload to /v2/username-probes/probes/blobs/uploads/ in image-registry.openshift-image-registry.svc:5000: received unexpected HTTP status: 500 Internal Server Error

Labels (1)
0 Kudos
3 Replies
apoczeka
Cadet
Cadet
  • 1,990 Views

I have the same. I think there is a problem with internal image registry. Hope its gets fixed quickly.

0 Kudos
ricardodacosta
Moderator
Moderator
  • 1,973 Views

The output suggests that the username which you are using is “username”. The username which you should be using is found in the “OpenShift Details” section in your lab environment page. Seeing this makes me curious as to your lab setup.

Please remove the password but share the contents of /usr/local/etc/ocp4.config and env | grep RHT_
ericbos
Flight Engineer
Flight Engineer
  • 1,847 Views

I have seen similar errors in my CRC environment when I was preparing for EX180. 

Next day I tried again and it worked fine. I don't remember if I did anything other than a shutdown, maybe I ran crc cleanup.

I believe that the s2i process takes a lot of resources, my machine has an i7 processor with 16GB RAM and is running RHEL 8.2

Join the discussion
You must log in to join this conversation.