-
Notifications
You must be signed in to change notification settings - Fork 34
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
Project meta-data gets lost after dump restore #8191
Comments
Wow, how is this possible? This is just a regular node? |
Good question... It's either not included in the dump or (most likely) isn't restored correctly. |
Because dumps-load uses high level Repository API to deal with creation of repositories to avoid reading metadata directly from the dump. Some facts:
|
vbradnitski
added a commit
that referenced
this issue
Jul 7, 2020
vbradnitski
added a commit
that referenced
this issue
Jul 7, 2020
vbradnitski
added a commit
that referenced
this issue
Jul 7, 2020
vbradnitski
added a commit
that referenced
this issue
Jul 8, 2020
rymsha
pushed a commit
that referenced
this issue
Jul 8, 2020
vbradnitski
added a commit
that referenced
this issue
Jul 8, 2020
vbradnitski
added a commit
that referenced
this issue
Jul 8, 2020
rymsha
pushed a commit
that referenced
this issue
Jul 8, 2020
rymsha
pushed a commit
that referenced
this issue
Jul 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After taking a dump and importing it into another instance, project meta-data gets lost on the way. Repositories and data get restored fine, but project meta-data is missing, so projects are not shown anywhere in the UI.
Before dump (target server):
![image](https://user-images.githubusercontent.com/11612490/86243479-c1496780-bba6-11ea-8e2b-c1ca1e6dadde.png)
After dump (source server):
![image](https://user-images.githubusercontent.com/11612490/86243417-a4149900-bba6-11ea-9ed1-2a6ab10139b1.png)
The text was updated successfully, but these errors were encountered: