Skip to content

Add blog post: SCOS upgrade authentication fix #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pskrbasu wants to merge 1 commit into
base: main
Choose a base branch
from
+23 −0
Open

Add blog post: SCOS upgrade authentication fix #118

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions blog/2026/08-13-scos-upgrade-auth-fix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
title: "[Resolved] OKD SCOS upgrades failing with authentication required"
authors: ["pskrbasu"]
date: 2026-08-13
---

If you've been hitting `authentication required` errors when trying to upgrade your OKD SCOS cluster, this has been fixed. Users have confirmed upgrades are working again.

## What happened

The OKD SCOS release payload images on `registry.ci.openshift.org` required authentication to pull, but end-user clusters don't have credentials for this registry. This meant any upgrade attempt would fail with `ImagePullBackOff` / `authentication required`, regardless of the version.

## What was fixed

The image-puller rolebinding for the OKD namespaces has been updated to allow unauthenticated pulls, matching how it already works for OCP.

Fix: [openshift/release#83361](https://github.com/openshift/release/pull/83361)

## What to do

If your upgrade was stuck, retry it — it should work now without any changes on your end.

Tracking issue: [okd-project/okd#2347](https://github.com/okd-project/okd/issues/2347)
Loading