-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
harbor v2.9.0 migration error, jinja template typo/bug #19320
Comments
hi @drshawnkwang To clarify, the specific problem encountered during the migration from v2.8.2 to v2.9.0? |
Thanks @drshawnkwang for catching this. @MinerYang Please validate the issue on our end. If it is an problem, we should await the release of v2.9.1 to address it. cc @YangJiao0817 it needs test case. |
introduced by this PR Thanks @drshawnkwang , we are now fixing it. |
As a workaround, when you do the harbor.yml migrate, please refer to the following steps.
step2 run migrate script
step3 add
|
We're having issues upgrading from 2.8.4 to 2.90 (see [related issue(https://github.com//issues/19398)).
|
If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior:
Expected: Updating harbor to version 2.9.0 using prepare container and migrate command works
Actual behavior:
docker run -it --rm -v /:/hostfs goharbor/prepare:v2.9.0 migrate -i ./harbor.yml
harbor.yml
contains object storage configurationError message
Looking at the jinja template on GitHub
Looking at this code, there is both the word
disable
anddisabled
in the jinja. Someone probably needs to change this so only one word is used. (probablydisable
?)Remediation: Modify
harbor.yml.jinja
to use the keyworddisable
ordisabled
consistently.Steps to reproduce the problem:
Configure
harbor.yml
to use object storage, withredirect: disable
, run the prepare & migration docker command.Versions:
Please specify the versions of following systems.
Additional context:
The text was updated successfully, but these errors were encountered: