Migrations are Running Successfully, but do not see any changes

OttoDeploy
1

I have been using OttoDeploy and have noticed that migrations are running successfully but when I open up the migrated file (destination), I see that it is still the same as what it used to be before. It seems it is not migrated to a new clone from the source server. I have played around with the settings to no avail. Has anyone run into a situation like this?

2

The same occurs when also running the deploy from the same server to the same server as a test.

For example, DEV->DEV server, same issue occurs as DEV->PROD or a reverse migration from PROD->DEV.

I have noticed that the Install/Replace feature works just fine and can port a whole file across with no issues.

3

Hey Ali,

I have not seen anyone else have an issue like this. Do you have the debug logs for one of the failing deployments?

-Kyle

4

See attached log file.

The deployment is not failing, it is successful, but the deployed file is the old file. Take a look at it as it is driving me mad. If you would like, we can also make a quick teams call so I take you through it.

debug-logs-84.zip (8.5 KB)

5

Hello

The logs look pretty good. They clearly show the files getting cloned, copied and migrated, and then opened.

Have you ever used OttoFMS to do a successful migration? Or is this the first time you have tried it? I am trying to understand if this is something that might be based on this particular file set?

Thanks

Todd

6

hmmm… I do notice that it looks like the migration took about 10 seconds. That is pretty fast., maybe too fast.

How much data is in your production file? How big is the file?

Todd

7

I agree with Todd. Something is a miss that the migrations are too fast to copy the data.

Production File: 116MB
Development File: 379MB

We follow a data seperation model, so these are the front end files only. The same happens with the backend files too. Below is a log of the same. Prod->Dev.

Production File: 2.77gb
Development File: 24gb

We are not moving the data, we are moving the schema across as I tend to keep older and lesser data on the development servers to conserve on space.

debug-logs-85.zip (7.9 KB)

8

This looks very odd. There is no way 2.77 gb of data migrates in 6 or 7 seconds.

Can I ask if you have done any migration successfully, and have it work the way you expect? If you haven’t, I would recommend that you setup a very simple migration maybe with an almost empty brand new file.

    • Put the same file on both dev and prod
    • Make a change to Dev. Maybe just make a change to a layout.
    • Then do a migration
    • And see if the Prod server has the layout change.

Thanks

Todd

9

Hi.

I managed to get past this issue by reinstalling and upgrading the latest version of OttoFMS on the affected server.

It is resolved.

1 Like