#10710 Need help with restarting deployment of oraculum-redis on the oc3 cluster
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by frantisekz.

NOTE

If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.

Describe what you would like us to do:


I'd need some help with restarting oraculum-redis deployment which got somehow stuck and I am not able to pull the latest redis container and/or just simply attempt to restart the deployment.

Local oc console fails me with:

Logged into "https://os.fedoraproject.org:443" as "frantisekz" using the token provided.

You have access to the following projects and can switch between them with 'oc project <projectname>':

  * oraculum
    testdays

Using project "oraculum".
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x4145bc]

When do you need this to be done by? (YYYY/MM/DD)


asap please :)


oc creashing like that usually means you are using the ocp4 'oc' on a ocp3.11 cluster. ;) (or vice versa).

I tried to set this image to import, but:

  ! error: Import failed (Unauthorized): you may not have access to the Docker image "quay.io/bitnami/redis:latest"
      12 seconds ago
  * quay.io/bitnami/redis@sha256:fe6397590f45217abac71acddca86a95d1d980971ddd3b43eb761e49f6eeaac3
      15 months ago

perhaps that image isn't open/available anymore? ;(

Hmm, thanks, I should have checked that, sorry for bothering @kevin

The bitmani containers indeed all disappeared from quay (https://community.bitnami.com/t/repositories-no-longer-available-at-quay-io/105179/2 , I wonder if it could have something to do with them being bought by vmware...).

I know dockerhub is bad idea to use on openshift due to throttling, I have switched it to gcr ( https://pagure.io/fedora-infra/ansible/c/6350c8b9c4049f0452565df490ed9f21f912e042?branch=main ) which seems not to impose too restrictive rate limiting and worked well, do you have any opinion if it's good/bad idea @kevin ?

Thanks!

Yeah, I don't know off hand... I would think gcr would be fine. ;) You might ask on the infrastructure list and see if anyone has other thoughts?

Also, @zlopez is looking at adding redis to the-new-hotness also... might be good to use the same thing there you are using here. ;)

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

oc creashing like that usually means you are using the ocp4 'oc' on a ocp3.11 cluster. ;) (or vice versa).

Crashing DevTools don't look good at all, especially if they bring infra components down (#10712). Should this be reported?

@kevin thanks for pinging me, I will look at redis deployment in oraculum.

Log in to comment on this ticket.

Metadata