Launchpad itself

Branch upgrade never seems to complete

Asked by Lars Helge Øverland

Yesterday morning (May 4, 08:00) I started an upgrade of our trunk (by clicking on the "upgrade this branch" button in the code page) and it still says "An upgrade of this branch is in progress."

https://code.launchpad.net/~dhis2-devs-core/dhis2/trunk

- For how long can we expect the upgrade to be in progress?

- What are the implications of a pending process, ie. is the branch locked for writing and/or reading?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Aaron Bentley
Solved:
Last query:
Last reply:
Revision history for this message
Best Aaron Bentley (abentley) said : 		#1

I investigated, and here's what I believe happened.
1. The upgrade started at 09:40:13 UTC
2. The database connection was killed due to inactivity/timeout
3. The upgrade completed at 10:57:47 UTC.
4. Because there was no database connection, we were unable to indicate that the upgrade was complete, and generated OOPS-1950UBJ1 when we tried to do so.

So the branch actually was upgraded, but is showing incorrect data on the page. I'll try to get that corrected.

Revision history for this message
Lars Helge Øverland (larshelge) said : 		#2

Thanks a lot for following up on this Aaron, thats a relief.

With inactivity do you refer to the user of the web interface? Does one have
to keep the LP web session alive throughout the whole process? Sounds a bit
counter intuitive since the upgrade-button request returns immediately and
the process takes a long time...

Lars
On 5 May 2011 18:02, "Aaron Bentley" <email address hidden>
wrote:
> Your question #156031 on Launchpad itself changed:
> https://answers.launchpad.net/launchpad/+question/156031
>
> Status: Open => Answered
>
> Aaron Bentley proposed the following answer:
> I investigated, and here's what I believe happened.
> 1. The upgrade started at 09:40:13 UTC
> 2. The database connection was killed due to inactivity/timeout
> 3. The upgrade completed at 10:57:47 UTC.
> 4. Because there was no database connection, we were unable to indicate
 that the upgrade was complete, and generated OOPS-1950UBJ1 when we tried to
do so.
>
> So the branch actually was upgraded, but is showing incorrect data on
> the page. I'll try to get that corrected.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
 https://answers.launchpad.net/launchpad/+question/156031/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/launchpad/+question/156031
>
> You received this question notification because you asked the question.

Revision history for this message
Lars Helge Øverland (larshelge) said : 		#3

Thanks Aaron Bentley, that solved my question.

Revision history for this message
Aaron Bentley (abentley) said : 		#4

The inactivity timeout is a server-side issue, and not related to the web interface. I've filed bug 777958 to track it.

Revision history for this message
Aaron Bentley (abentley) said : 		#5

The erroneous "An upgrade of this branch is in progress." message should be gone from all branches now.

Revision history for this message
Lars Helge Øverland (larshelge) said : 		#6

Great thanks.