When redeploying the chart core and registry stop working

[jchanam]

Hi,
When redeploying the chart with helm upgrade, both core and registry stops working.

core logs:

2018-12-10T16:00:24Z [DEBUG] [authenticator.go:126]: Registered authencation helper for auth mode: db_auth
2018-12-10T16:00:24Z [DEBUG] [authenticator.go:126]: Registered authencation helper for auth mode: ldap_auth
2018-12-10T16:00:24Z [DEBUG] [authenticator.go:126]: Registered authencation helper for auth mode: uaa_auth
2018-12-10T16:00:24Z [DEBUG] [init.go:37]: topic StartReplication is subscribed
2018-12-10T16:00:24Z [DEBUG] [init.go:37]: topic OnPush is subscribed
2018-12-10T16:00:24Z [DEBUG] [init.go:37]: topic OnDeletion is subscribed
2018-12-10T16:00:24Z [INFO] Config path: /etc/core/app.conf
2018-12-10T16:00:24Z [INFO] initializing configurations...
2018-12-10T16:00:24Z [INFO] key path: /etc/core/key
2018-12-10T16:00:24Z [INFO] initializing client for adminserver http://harbor-harbor-adminserver ...
2018-12-10T16:00:24Z [FATAL] [main.go:87]: failed to initialize configurations: http error: code 401, message Unauthorized

It seems it has to be something in common with the autogenerated secret, but I'm not 100% sure.

registry status:

Unable to mount volumes for pod "harbor-harbor-registry-...": timeout expired waiting for volumes to attach or mount for pod "harbor"/"harbor-harbor-registry-....". list of unmounted volumes=[registry-data]

I have the persistence enabled. The only way I find to solve this, is changing the accessMode to readWriteMany (changing also the storage class to one that allows RWX). Is there other approach better to fix this?

Thanks!

[ywk253100]

For core, can you try to check the value of environment variable CORE_SECRET in core and adminserver, are they same?

For registry, any other detail logs or information?

[ywk253100]

And are you using the latest code and images? We have added the annotation checksum in #96, the deployments should be recreated when you upgrading.

[jchanam]

Hi @ywk253100,

The env variable reference the same secret, but when upgrading the chart, the adminserver is not restarted. I've found out that it's missing another checksum regarding the core secret, as it's being used.

For registry I can tell you that using my approach with RWX, it's working.

The images are the ones from this release: https://github.com/goharbor/harbor/releases/tag/v1.7.0-rc1
I've downloaded the offline installer, imported the tgz with the images, retagged them and uploaded to my private repo so I can use them. The version of the chart I'm using is 11ec211 (the latest available).