#Cloud migration failed half of database
80 messages · Page 1 of 1 (latest)
I'll close this since in a new project importing worked (somewhat) fine.
[SOLVED] Cloud migration failed
Cloud migration failed half of database
Read from here
Nevermind, failed again. Missing half of my database.
Current org ID: 66a1236e00237ba3c8ff
Current project ID: hp-main
Error logs:
https://paste.techscode.com/yanopecivapuxar.json
some collections are filled with attributes & documents, like ID: gallery-images
and others are just.. empty, no attributes either.
what version was local?
1.5.7?
the latest official one
ah latest is 1.5.8 but it shouldn't be that much of an issue
i got 1.5.7
that was before or after you upgraded to pro?
I created an org and a project and instead of "deploy to cloud" i used "import data" (or something similiar), and some things did import correctly like.. i think a singular collection did go correct, my smtp data etc. and of course my functions failed, but that's cause they were node 20 (which is the least of my issues, cause just re-deploy)
even though the status is failed as well, the "resolve migration issues" window keeps loading for most of them, probably due to the server error that's in the error log
that's wierd you got an error about the limit of the number of databases becuase it should be unlimited for pro orgs
Did you check this one?
i just deleted the old link, for less confusion
@runic rampart any ideas why databases, functions, and storage has errors like:
"Error occurred while fetching 'databases:' from source with message: 'Call to undefined method Utopia\\Migration\\Exception::getResourceType()'",
"Error occurred while fetching 'functions:' from source with message: 'Call to undefined method Utopia\\Migration\\Exception::getResourceType()'",
"Error occurred while fetching 'storage:' from source with message: 'Call to undefined method Utopia\\Migration\\Exception::getResourceType()'",
?
This should of been fixed in the new release as well
an error in the error handler made it use an old method which wasn't updated, I will soon be assing phpstan to detect these errors in tests ahead of time so this doesn't happen again
So I have to update locally for it to be fixed?
lol, just found out that 1.5.8 isn't even out yet
So, what now?
If you're migrating to cloud, you'll need to wait until cloud is updated
Ya. It doesn't have the patch Bradley was talking about yet
:( Let's hope it's soon then
Can you try again?
Should I delete everything before? Or does it overwrite data
Well, I deleted everything and re-imported to be sure. Even put my functions to node 18 instead of 20, but still failed:
https://paste.techscode.com/sarihikumofasuf.json
Weird... @runic rampart shouldn't the fix be on Cloud now?
the cloud is still on 1.5.8 fyi
Hm, lock file wasn't updated
Making a PR for that now
Is it pushed?
Yeah, it's been merged. We'll be creating a new cloud release sometime today so after that it should work
I'm really sorry about how long this has taken
have you had a chance to try again?
I mean, I did before, but I haven't after bradley said what he said.
should have been released yesterday
will check later
@dim schooner @runic rampart
https://paste.techscode.com/juwuzedazifikal.json
this is annoying lol
Maximum file size looks like a mismatching bucket problem ...
Actually, we had a bug with buckets recently. What's the bucket max file size for your bucket?
It's default on 50 gigs, cause testing purposes, but why doesn't cloud just set it to a value that actually works? There's also a database error in there.
Change it to "Imported with errors", where it says that the storage for example has been changed to a correct size
Can you make sure it's 50,000,000,000 and not 50 * 1024 * 1024?
I already changed it, so i don't know
it was a high number lol
on a new bucket:
Hmmm I wonder if the bug fix hasn't been released yet...either in the console or backend
the bug fix did get released, at least for the massive amount of errors before
so "something" got magically fixed, just these things
Oh no this other bucket max file size bug
Ya but we had a bug where it was 50 * 1024 * 1024 when it needed to be 50 * 1000 * 1000
hm
i did see that flying around, but i thought that was just on storage in an already working cloud environment
the thing i hate the most about this import system currently.. i get an error and the entire migration stops, there's even files that are still shown as "pending"
i can fix the storage issue by just putting it down for myself, but what about that database error?
is that an actual error, or does it need to be fixed
Yes please lower the bucket max file size
Maybe it's an error that prevented other things from continuing...
@runic rampart, thoughts on stuff stuck pending? Also the database error from https://paste.techscode.com/juwuzedazifikal.json:
Error occurred while fetching 'databases:' from source with message: 'Call to a member function getId() on null'
Thinking about this, currently yeah a single fail causes everything else to stop because we can't track dependencies. I've been meaning to implement a depdency map and use that in the codebase so we're not attempting to import things that rely on previously failed resources but I haven't had a chance to get around to it
as for the Call to a member function getId() on null, I'll try and see what I can dig up
Heyo! Any update?
@dim schooner 
Since the waiting took me a bit too long. I imported again, with proper storage file sizes so they import correctly.
However, one thing went wrong, which is the functions.. for not a proper reason. No errors further.
Also, each file imported from self-hosted into the cloud storage bucket, is larger than the actual file. Why?
self hosted
cloud
Is encryption enabled by any chance?
don't think so?
You not sure? Are the settings in both storage buckets the same?
Everything has been imported from self hosted, including the buckets