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

Can login to Registry tab but cant login to Management tab of unified OVA #91

Closed
frapposelli opened this issue Apr 28, 2017 · 3 comments

Comments

@frapposelli
Copy link
Contributor

@lgayatri commented on Fri Apr 28 2017

If you are reporting a problem, please make sure the following information are provided:

root@localhost [ /admiral ]# docker --version
Docker version 1.12.6, build 78d1802
root@localhost [ / ]# docker-compose version
docker-compose version 1.11.1, build 7c5d5e4
docker-py version: 2.0.2
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.1t  3 May 2016
root@localhost [ /admiral ]# docker ps
CONTAINER ID        IMAGE                                     COMMAND                  CREATED             STATUS              PORTS                                                  NAMES
6f1f1301187f        vmware/harbor-jobservice:v1.1.0           "/harbor/harbor_jobse"   2 days ago          Up 2 days                                                                  harbor-jobservice
ac1436de8edb        vmware/nginx:1.11.5-patched               "nginx -g 'daemon off"   2 days ago          Up 2 days           0.0.0.0:443->443/tcp, 80/tcp, 0.0.0.0:4443->4443/tcp   nginx
0fe989008560        vmware/notary-photon:server-0.5.0         "/usr/bin/env sh -c '"   2 days ago          Up 2 days                                                                  notary-server
8707ee796bd1        vmware/harbor-ui:v1.1.0                   "/harbor/harbor_ui"      2 days ago          Up 2 days                                                                  harbor-ui
bbf0d5f2e259        vmware/notary-photon:signer-0.5.0         "/usr/bin/env sh -c '"   2 days ago          Up 2 days                                                                  notary-signer
a6fca0023106        vmware/registry:photon-2.6.0              "/entrypoint.sh serve"   2 days ago          Up 2 days           5000/tcp                                               registry
7239c211e592        vmware/harbor-notary-db:mariadb-10.1.10   "/docker-entrypoint.s"   2 days ago          Up 2 days           3306/tcp                                               notary-db
ac6cce68cb43        vmware/harbor-db:v1.1.0                   "docker-entrypoint.sh"   2 days ago          Up 2 days           3306/tcp                                               harbor-db
64f642fe76e8        vmware/harbor-adminserver:v1.1.0          "/harbor/harbor_admin"   2 days ago          Up 2 days                                                                  harbor-adminserver
b2108710b32f        vmware/harbor-log:v1.1.0                  "/bin/sh -c 'crond &&"   2 days ago          Up 2 days           127.0.0.1:1514->514/tcp                                harbor-log

Support bundle attached.

I can access https://10.133.154.169/harbor/projects
Cant access https://10.133.154.169:8282/#/home -> was accessible until today morning.

harbor-accessible
admiral-inaccessible
vm-2017-04-28.26334.tar.gz

@lazarin
Copy link
Contributor

lazarin commented May 4, 2017

From the attached log bundle I was not able to pull any information related to admiral.
Anyway on the other environment reported we were able to capture a heapdump leading to an issue in xenon.
We bumped the version to 1.4.2 and pushed vmware/admiral:vic_v1.1.1 to dockerhub.
I'll leave this open for a couple of days, please update in case of issues.

@lgayatri
Copy link

lgayatri commented May 4, 2017

It is a debug-ability issue if support bundle does not capture required logs. I opened #92 based on the above comment.

@lgayatri
Copy link

Verified on Build: vic-v1.1.1-rc2-1f1711a0.ova.
Issue fixed and could not be reproduced.

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