Data dissapearing after upgrade from 4.5.6 to 5.6

[nick.aposto...@gmail.com]

Hello everyone,

I have upgraded one of our systems from sonarqube 4.5.6 to 5.6 following the instructions found here: http://docs.sonarqube.org/display/SONAR/Upgrading

Everything went well, but after the finish of the upgrade, I cannot see any of my old project data, the quality gates etc.

This is unexpected and reading the documentation, i expected the upgrade to preserve the old data.

Is there something obvious I am missing here?

I have not executed any project analysis on this system yet.

Thank you

[G. Ann Campbell]

Hi Nick,

1) Are you sure you pointed the 5.6 instance to your old database? And if so, did you run the database upgrade?

2) Anything unusual in your server logs?

Ann

[Nick Apostolakis]

Hello Ann,

Yes, the 5.6 instance used the old database. If by database upgrade you mean going to the /setup page, i did that.
There were no errors.

I am a bit confused about this, and did not expect to lose the data. There is no harm done, since this dataset was not a production one, but this problem may reappear in the future when we upgrade our prod sonarqube service.

We are using postgresql for the database.

I take it that this is not the expected behavior and it should have preserved the data then?

Thank you

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/WTshBw6lK-Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/3091cc7a-c2fd-4d2d-93ff-e722b23b0484%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Simon Brandhof]

That's an unexpected behaviour. Could you send the logs please ? They should contain the upgrade information.

Thanks

On Thursday, 23 June 2016 17:04:23 UTC+2, Nick Apostolakis wrote:

Hello Ann,

Yes, the 5.6 instance used the old database. If by database upgrade you mean going to the /setup page, i did that.
There were no errors.

I am a bit confused about this, and did not expect to lose the data. There is no harm done, since this dataset was not a production one, but this problem may reappear in the future when we upgrade our prod sonarqube service.

We are using postgresql for the database.

I take it that this is not the expected behavior and it should have preserved the data then?

Thank you

On Thu, Jun 23, 2016 at 3:10 PM, G. Ann Campbell <ann.ca...@sonarsource.com> wrote:

Hi Nick,

1) Are you sure you pointed the 5.6 instance to your old database? And if so, did you run the database upgrade?

2) Anything unusual in your server logs?

Ann

On Wednesday, 22 June 2016 11:46:52 UTC+2, Nick Apostolakis wrote:

Hello everyone,

I have upgraded one of our systems from sonarqube 4.5.6 to 5.6 following the instructions found here: http://docs.sonarqube.org/display/SONAR/Upgrading

Everything went well, but after the finish of the upgrade, I cannot see any of my old project data, the quality gates etc.

This is unexpected and reading the documentation, i expected the upgrade to preserve the old data.

Is there something obvious I am missing here?

I have not executed any project analysis on this system yet.

Thank you

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/WTshBw6lK-Y/unsubscribe.

To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.

[Nick Apostolakis]

Thank you Simon, I will attach the log of that day in this message.

I have trimmed the log and kept only the migration restart.

Everything seemed normal to me, and there were no errors

Please let me know what you think about it

Thanks

To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/3091cc7a-c2fd-4d2d-93ff-e722b23b0484%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/WTshBw6lK-Y/unsubscribe.

To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/0a96880a-277e-435b-a9e3-76d161060c66%40googlegroups.com.

[Simon Brandhof]

Thanks.

No data have been lost as he upgrade has been executed on an empty database ! You should check the JDBC settings in order to be sure to connect to the expected schema (configured URL is jdbc:postgresql://localhost/sonar).

Regards

You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/CAOo8h9OKXoKgUBrMi96Uahiq4NFPkjL30HrOQdTsEtCuygzbAQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

[Nick Apostolakis]

Hello Simon,

The service that have been upgraded to sonarqube 5.6 was created by the restoration of a backup from our production service.

In order to find where the error was, i tried to replicate everything and found that there were some errors during the data restoration phase.

After i made sure that the data were restored properly i was able to complete the migration without any issues.

Thank you for the feedback and your time.

[Simon Brandhof]

Great news. Enjoy version 5.6!

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/CAOo8h9OSbhgj5HjKR7S5MeN5-ro5G--VAoLM7_ABppSYLg%3DuiQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.