openshift / openshift/console

Bug: Error when creating the default pull secret

Open Beginner friendly
#16,700 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
460
Forks
756
Avg merge
4d 2h
Merged PRs (30d)
88

Description

Description

Creating a default pull secret from a newly created Namespace fails.

The UI sends an invalid request while trying to add a value to the imagePullSecrets array. In this case, the target array does not exist yet, but the request attempts to add an item to it. As a result, the API rejects the request and the default pull secret is not created.

Steps to reproduce

  1. Open the console connected to a clean Kubernetes cluster.
  2. Go to Namespaces.
  3. Create a new Namespace.
  4. Open the newly created Namespace details page.
  5. Click the action to create a default pull secret.
  6. Enter a secret name.
  7. Click Save.

Actual result

The operation fails with the following error:

HttpError: the server rejected our request due to an error in our request

Expected result

The default pull secret should be created successfully and displayed on the Namespace page.

Additional details

This was reproduced on the main (49745c2) branch with "pure" k8s cluster.

https://github.com/user-attachments/assets/3a04035a-f6be-4d6e-a3eb-2548cd89bc26

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Namespace details page's action for creating a default pull secret and inspect how the request updates the imagePullSecrets array when the array is absent. Reproduce the steps on a clean Kubernetes cluster, then confirm the request succeeds and the created secret appears on the Namespace page.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, typescript
Domain
api, frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.