Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    bcarriou
    @bcarriou
    This service is not stable, almost every week there is a problem while we are paying for this one ...
    Jérémy Levilain
    @IamBlueSlime
    Our push/pull requests are failing a lot since this morning (random 500 errors), any incident on OVH's side?
    2 replies
    Stephane Delval
    @scndel
    Hi, anyone using the default Trivy (or other) image scanner ? We've just upgraded to plan M but it's stays in unhealthy status. Do we have to change the endpoint (currently https://harbor-trivy) ?
    screenshot
    1 reply
    Alexander Kauerz
    @0xErnie
    Good Morning,
    since we are switching to habour 2.0.1 yesterday, errors ( 503, unexpected EOF) are raining on us when we push new images.
    At the start everything was fine, but since we started our gitlab piplines most jobs fail even with 8 retries after 2 minutes of waiting between the 7th and 8th try..
    5 replies
    Jarek Rozanski
    @jarek_rozanski:matrix.org
    [m]

    Repost from ovh/kubernetes channel:

    👋 Something is funny with Harbor/Private Registry. Cannot connect (503 Service temporarily unavailable) despite OVH console stating "OK" status.

    The status page show no indication of issue http://travaux.ovh.net/?project=36&status=all&perpage=50
    Jarek Rozanski
    @jarek_rozanski:matrix.org
    [m]
    Still down. That's a bit sad given this is supposed to be delivery and deployment mechanism for Kubernetes. It is not marked as Alpha release and yet it is down for 8h (and counting)
    Joël LE CORRE
    @jlecorre_gitlab
    Hello @jarek_rozanski:matrix.org
    Could you send me your registry ID in private please?
    Simon Guyennet
    @sguyennet
    @jarek_rozanski:matrix.org It should be fixed. You pod was in crashloop because it wasn't able to mount a secret.
    1 reply
    tsn77130
    @tsn77130
    hello, we have again some errors when pull/push on registry, could someone please take a look ?
    tsn77130
    @tsn77130
    ID is xe1pyfka.gra5.container-registry.ovh.net
    SebastienJardin
    @SebastienJardin
    Hello @tsn77130 sorry to ear that, i'm going to check
    tsn77130
    @tsn77130
    @SebastienJardin have you found something ?
    SebastienJardin
    @SebastienJardin
    No sorry :/
    i continue in dm
    Mircea Negreanu
    @mircea.negreanu_gitlab
    Hi, we have a problem with our container registry. When we push we receive the following error: "UNKNOWN: unknown error; map[DriverName: s3aws Path: /docker/registry/v2/repositories/...". Is there anything we can do?
    Mircea Negreanu
    @mircea.negreanu_gitlab
    Mircea Negreanu
    @mircea.negreanu_gitlab
    The fourth time worked. I'm curios if the problem is solvable.
    Jérémie MONSINJON
    @jMonsinjon

    @mircea.negreanu_gitlab Unfortunatly this problem is not easily solvable.
    I'm still investigating on some specific cases, I will probably open a dedicated travaux task...

    The 's3aws PathNotFound' is linked to an issue with our backend storage, and we can't change it for now. So we will try to reduce as much as we can the impact and the frequency.

    1 reply
    Giorgos Kantiotis
    @Arcturusk_gitlab
    Hello anyone here ?
    Jérémy Levilain
    @IamBlueSlime
    Hi my registry does not recognize any user and pushs/pulls fails with 503
    :arrow_up: and looks like anybody can register to my registry. I really hope that its data is not flushed...
    Jérémy Levilain
    @IamBlueSlime
    :arrow_up: still down, opened a ticket right now, but maybe someone from OVH here will be faster?
    3 replies
    Rémy Tinco
    @RemyTinco
    :arrow_up: Having a Registry down for 3 days, especially during the Monday morning with all company stakeholder is a big backslash for OVH trust here :/
    FYI, this is currently below the 99,99% SLA specified in the contract (Article 7) and I worry that nobody panics more than that
    Jérémy Levilain
    @IamBlueSlime
    :arrow_up: Simon has fixed the issue, thanks a lot!
    Anthony Deroche
    @AnthonyDeroche
    Hello, i'm experiencing a lot of 502 errors on harbor registry both on pull/push ERROR: error pulling image configuration: received unexpected HTTP status: 502 Bad Gateway. I must have to retry clients (docker, skopeo) multiple times. Is this an ongoing issue ?
    3 replies
    Rémy Tinco
    @RemyTinco
    Hello, 502 errors on the registry also here :/ Need help
    1 reply
    Escaflow
    @Escaflow
    Hello, we can't delete some empty Projects: "Deleted failed or partly failed"
    1 reply
    DevOps at TauRes
    @DevOps-TauRes
    Our new Harbor (newest available version) gets a lot of 503 errors in Frontend and at the end also in pipelines.
    Whats going on there?
    1 reply
    André Veelken
    @ae-v
    And it's impossible to login at the web interface.
    1 reply
    crumohr
    @crumohr
    Urgent! It seems like the constraints that you put on your Harbor-Pods @OVH are to tight, we have the 503 problem after each push of a larger image. Please check, wether you guys @OVH see evicted pods. This service is otherwise unusable for us. We have massive problems with this since v2 of this service.
    3 replies
    Chris Rumohr
    @crumohr:matrix.org
    [m]
    We have already resolved the issue, thank you very much!
    kiorky
    @kiorky:matrix.org
    [m]
    hi, is there any plan to make container registries available in another AZ than GRA soon ?
    Idea was to have two registries, in two differents AZ and the second one would be a mirror (with replication rules) of the former.
    Seems that's not possible.
    3 replies
    @thcdrt: thx i already saw it, but did not noticed anything on that specific question.
    kiorky
    @kiorky:matrix.org
    [m]
    maybe a (non engaging) ETA in "monthes", year, 2years, 3years ?
    2 replies
    @thcdrt: What is prepared if there is a fire at GRA that completly destroys the registries cluster ?
    kiorky
    @kiorky:matrix.org
    [m]
    @thcdrt: Do you have any details for the PRA question ?
    Jérémy Levilain
    @IamBlueSlime
    Hi, my registry is having 502 Bad Gateway since this morning, impossible to login to the Docker API. The UI works fine. Could someone take a look at it? (MP me for IDs)
    1 reply
    Thomas Coudert
    @thcdrt
    Hello, we want to warn our customers having registries in Harbor 2.0 that some of you may have issues with your robots accounts. If it happens to you, you should regenerate it.
    We're sorry for the inconvenience.
    Thomas,
    OVH Managed Registry Team
    Hummer12007
    @Hummer12007
    Hi, container registry seems to break if I use a CNAME to point to its domain
    1 reply
    Irwin Lourtet
    @ilourt
    Hi I also have problem to pushed to my registry since this morning.
    1 reply
    Colin GILLE
    @Congelli501
    Hi, we have problems pulling our images. Is there anything going on ?
    ERROR: Job failed (system failure): failed to pull image "xxxxxx.gra5.container-registry.ovh.net/xxx/xxx:latest" with specified policies [always]: Error response from daemon: Get https://xxxxxx.gra5.container-registry.ovh.net/v2/xxx/xxx/manifests/latest: received unexpected HTTP status: 503 Service Temporarily Unavailable (manager.go:214:0s)
    3 replies
    Thomas Coudert
    @thcdrt
    Hello,
    We have a Network issue at OVH, your registries could be unreachable we'll keep you updated when we have more information.
    Thomas,
    OVH
    Thomas Coudert
    @thcdrt
    For french speakers: https://twitter.com/olesovhcom/status/1448196879020433409
    Traduction: A human error during configuration of network in our Datacenter in VintHill (US) has impacted all OVH backbone. We are isolating it to fix the configuration
    Thomas Coudert
    @thcdrt
    Faulty router has been isolated, everything is coming back slowly.
    Thomas Coudert
    @thcdrt
    Around 2/3 of Managed Private Registries are back, we are still on it.
    Thomas Coudert
    @thcdrt
    All registries in version 2 are back.
    Some registries in v1 are still down, and should be up in several minutes.
    Thomas Coudert
    @thcdrt
    All registries are back online.
    If you still encounter some issues, feel free to contact us here.
    We're sorry for the inconvenience.
    Thomas,
    OVH
    tsn77130
    @tsn77130
    I've still problems with mine
    error pulling image configuration: Get "https://storage.GRA.cloud.ovh.net/84bfb275-a86f-4707-802b-4efc5050a519/files/docker/registry/v2/blobs/sha256/20/200117eb6cb0c14ca74b52a5e2daa9f355e6fb811b4cd2d0d54a7a82cb37d820/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=xxx%2F20211013%2FGRA%2Fs3%2Faws4_request&X-Amz-Date=20211013T093524Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=sss": read tcp 192.168.50.58:49664->87.98.187.201:443: read: connection reset by pee
    4 replies