Skip to content
This repository was archived by the owner on Aug 26, 2021. It is now read-only.

[UX] Improve the error message when adding registry without or with wrong credentials. #142

Open
afilipov1 opened this issue Aug 3, 2017 · 8 comments

Comments

@afilipov1
Copy link
Contributor

The message is not so meaningful.

registryerrormessage

@vmwarelab
Copy link

vmwarelab commented Aug 3, 2017

my creds are correct . this is an issue that i reproduced in my home lab , that one of my field SE are experiencing with one of our " VMware" Customers using the VIC appliance that has both Admiral and Harbor. How can i add harbor to admiral ? what are we doing wrong ?

@andrewtchin
Copy link

@vmwarelab What build are you running? As of build 53aa4b861b7b I'm not able to add Harbor anymore (#145) so I can't test this on new builds

@vmwarelab
Copy link

@andrewtchin thats a strange build number not sure where you got that from

VIC / Harbor 1.1.0-7464
on the console of the vic i see v1.1.0-0-bf760ea

@andrewtchin
Copy link

@vmwarelab gotcha that's an older build we're testing on pre 1.2 dev builds now. I just tried this on vic-v1.1.1-56a309fb which is very close to the build you're using and got the same issue adding Harbor to Admiral by supplying vSphere admin creds

@andrewtchin
Copy link

@vmwarelab I got it - when you deployed the OVA there was a field for registry password - add a credential with username admin and that password then you can add Harbor to Admiral

@vmwarelab
Copy link

vmwarelab commented Aug 3, 2017 via email

@andrewtchin
Copy link

@vmwarelab well if that doesn't work I don't know what to say maybe one of the Admiral developers can comment or try posting in the #admiral Slack channel

@vmwarelab
Copy link

any resolution found on this . thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants