sync-mirror-pocket fails after 30 minutes

Bug #2020909 reported by Jorge Merlino
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Landscape Server
Confirmed
Undecided
Unassigned

Bug Description

When a sync mirror command is issued and takes longer that 30 minutes to finish (which is not strange when landscape is installed for the first time) the activity shows as failed with result text "No transition: delivered=>delivered".

In the job-handler.log file we can see this error:

'PRECONDITION_FAILED - delivery acknowledgement on channel 1 timed out. Timeout value used: 1800000 ms. This timeout value can be configured, see consumers doc guide to learn more'

so this seems to be by design. Furthermore, after this error is shown, reprepro continues running and eventually the sync process finishes successfully even if it is shown as failed in Landscape.

In conclusion I think that 30 minutes is not long enough for this timeout as sync activities can reasonably take several hours in case of large repositories and not super fast network connections.

information type: Proprietary → Public
Revision history for this message
Steven LaCosse (motosteven) wrote :

I am running into this issue as well with the initial sync with larger repos.
For example when syncing the release of bionic.

Issuing the command:

landscape-api sync-mirror-pocket release bionic ubuntu

fails after 30 min: error log same as Jorge.

(406, 'PRECONDITION_FAILED - delivery acknowledgement on channel 1 timed out. Timeout value used: 1800000 ms. This timeout value can be configured, see consumers doc guide to learn more', 0, 0) content = None

I do not see in the docs to configure this fail, is there a workaround to change the value?

Revision history for this message
Rigoberto Sanchez (sanch1) wrote :

I've hit the same issue, if you look at the activity you can see the progress still going, so it's definitely syncing? but I get those error messages too. Not sure where to change that setting either

Changed in landscape:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.