Origin: Error creating image secret

Created on 27 Aug 2018 · 9Comments · Source: openshift/origin

When I try to create an images secret in GUI I receive an error:

An error occurred while creating the secret. Reason: Secret "registry" is invalid: data[.dockercfg]: Required value

Version

openshift v3.10.0+dd10d17

oc v3.10.0+dd10d17
kubernetes v1.10.0+b81c8f8
features: Basic-Auth GSSAPI Kerberos SPNEGO

Steps To Reproduce

In the UI navigate to Resources/Secrets
Select Image Secret
For Authentication Type select Configuration File
Open the config.json file in $HOME/.docker
Finish via Create

Current Result

An error occurred while creating the secret. Reason: Secret "registry" is invalid: data[.dockercfg]: Required value

Expected Result

The secret is created like in release 3.9 were it was working in the same way.

Additional Information

Creating the secret via cmd is working with the same file

oc create secret generic secret --from-file=.dockerconfigjson=$HOME/.docker/config.json --type=kubernetes.io/dockerconfigjson

lifecyclrotten siuser-interface

Source

nightman68

👍3

All 9 comments

Also reproducible with openshift v3.11.0-alpha.0+5a0e291-1298

jmwilkinson on 14 Sep 2018

@openshift/sig-user-interface

jwforres on 1 Oct 2018

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 on 30 Dec 2018

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 on 29 Jan 2019

Seeing this issue in the UI as well in OpenShift Online

nccurry on 23 Feb 2019

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-bot on 26 Mar 2019

@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/test-infra repository.