-
Notifications
You must be signed in to change notification settings - Fork 65
Unable to add Harbor registry #138
Comments
You didn't provide any credentials. |
@AntonioFilipov This is a really bad UX, please reopen or file an enhancement for an improved error message |
@andrewtchin from the title and description of the issue I got the impression that the functionality doesn't work at all, not that the message is not meaningful. Could you please verify that the functionality is working when you provide credentials. If so, we can create another issue for the error message. Thanks. |
@andrewtchin I`ve opened a new issue for improving the error message. Thanks. |
so what is the solution here ... you can't just add it until the UX is fixed ? |
@vmwarelab It worked when I created a new credential using the tab at the top right with the vSphere admin user/pass then selected that credential in the Login credential field it worked. This is probably bad security practice though. |
i did that as well and created a user and set him up as an admin in harbor .. still got the same error |
OVA build https://storage.googleapis.com/vic-product-ova-builds/vic-28d18602-dev.ova with Admiral
357b3933344820434470830d07b4f22fb1a28416370a21d76a7075f71c344625
I verified that Harbor is functional by checking the logs and performing a
docker login
and pushing an image to it, but am unable to add Harbor to AdmiralThe text was updated successfully, but these errors were encountered: