UnAuthenticated Registry Deprecation: registry.svc.ci.openshift.org

[ArthurVardevanyan]

registry.svc.ci.openshift.org has been moved to registry.ci.openshift.org:

REF:

• https://bugzilla.redhat.com/show_bug.cgi?id=1951571
• https://bugzilla.redhat.com/show_bug.cgi?id=1951572

PR: https://github.com/openshift/assisted-service/pull/6553

[ArthurVardevanyan]

Build Contains PR with update, but still logs same issue: https://amd64.origin.releases.ci.openshift.org/releasestream/4.17.0-0.okd-scos/release/4.17.0-0.okd-scos-2024-07-15-192426

error="pull secret for new cluster is invalid: pull secret must contain auth for \"registry.ci.openshift.org\"

[rccrdpccl]

/cc @danmanor

[danmanor]

@ArthurVardevanyan thank you, can you please provide more details on how did you got this log? what actions have you taken ?

[danmanor]

what was the log before the change ?

[ArthurVardevanyan]

Same log before change.

This comes from installing the CI builds of OKD via agent based installer.

The stable builds pull from quay.io without issue.

Configs: https://github.com/ArthurVardevanyan/HomeLab/tree/main/sandbox/kubevirt/okd/configs

[titou10titou10]

This seems to address the problem described here for OKD/SCOS/UPI/ABI install: https://github.com/okd-project/okd/discussions/1964

Failed to register cluster with assisted-service: AssistedServiceError Code: 400 Href:  ID: 400 Kind: Error Reason: pull secret for new cluster is invalid: pull secret must contain auth for \"registry.ci.openshift.org\""

But it does not... I tried to installregistry.ci.openshift.org/origin/release-scos:4.17.0-0.okd-scos-2024-07-16-072426that includes #6552/#6553 and it fails the exact same way

You have all the installation details with agent/install config files and logs etc in https://github.com/okd-project/okd/discussions/1964

[danmanor]

Thank you, I will look into it

[danmanor]

commented here - https://github.com/okd-project/okd/discussions/1964

[ArthurVardevanyan]

https://github.com/openshift/assisted-service/pull/6642

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.