Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upgrade failed from 1.3.0 to 1.3.1 due to "Harbor Data is not present in /storage/data/harbor, can't continue with upgrade operation" #1321

Closed
reasonerjt opened this issue Jan 22, 2018 · 3 comments
Closed

Upgrade failed from 1.3.0 to 1.3.1 due to "Harbor Data is not present in /storage/data/harbor, can't continue with upgrade operation" #1321

reasonerjt opened this issue Jan 22, 2018 · 3 comments
Assignees
@andrewtchin
Labels
status/needs-attention The issue needs to be discussed by the team

Comments

@reasonerjt
Copy link
Contributor

reasonerjt commented Jan 22, 2018 •
edited
Loading

Pre upgrade version : https://storage.googleapis.com/vic-product-ova-releases/vic-v1.3.0-3033-f8cc7317.ova
Current 1.3.1 version : https://storage.cloud.google.com/vic-product-ova-builds/vic-stage-3191-v1.3.1-dev-3191-06ca9cf3.ova

IP : 10.197.37.182.eng.vmware.com - root/Admin!23

root@vic-st-h2-182 [ /etc/vmware/upgrade ]# ./upgrade.sh
Enter vCenter Server FQDN or IP: wdc-stvc3944-146-dhcp15.eng.vmware.com
Enter vCenter Administrator Username: [email protected]
Enter vCenter Administrator Password:
If using an external PSC, enter the FQDN of the PSC instance (leave blank otherwise):
If using an external PSC, enter the PSC Admin Domain (leave blank otherwise):

-------------------------
Starting upgrade 2018-01-22 13:39:29 +0000 UTC
Detected old OVA's version as 1.2.x. Upgrade will perform data migration, but previous component logs won't be transferred.
If the version of the old OVA is not 1.2.x, please enter n and contact VMware support:
Do you wish to proceed with a 1.2.x to 1.3.x upgrade? [y/n]
y
Continuing with upgrade

Preparing upgrade environment
Disabling and stopping Admiral and Harbor path startup
Finished preparing upgrade environment

-------------------------
Starting Admiral Upgrade 2018-01-22 13:39:29 +0000 UTC

Performing pre-upgrade checks
Starting Admiral upgrade
Updating Admiral configuration

-------------------------
Starting Harbor Upgrade 2018-01-22 13:39:29 +0000 UTC

Performing pre-upgrade checks
Harbor Data is not present in /storage/data/harbor, can't continue with upgrade operation

upgrade.log
@reasonerjt
Copy link
Contributor Author

Carried from goharbor/harbor#4099

@AngieCris AngieCris added status/needs-attention The issue needs to be discussed by the team team/lifecycle status/needs-estimation The issue needs to be estimated by the team labels Jan 22, 2018
@AngieCris
Copy link
Contributor

Cc: @andrewtchin

@andrewtchin andrewtchin self-assigned this Jan 22, 2018
@andrewtchin andrewtchin removed the status/needs-estimation The issue needs to be estimated by the team label Jan 22, 2018
@reasonerjt reasonerjt mentioned this issue Jan 23, 2018
Closed
@lgayatri
Copy link

goharbor/harbor#4099 was filed against harbor but this issue is related to the upgrade script of vic-product. Hence the issue was opened here.

@andrewtchin andrewtchin mentioned this issue Jan 25, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andrewtchin andrewtchin

Labels
status/needs-attention The issue needs to be discussed by the team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@andrewtchin @reasonerjt @AngieCris @lgayatri