Bug #11866

Cannot download some artifacts from Jenkins

Added by anonym 2016-10-07 12:49:53 . Updated 2016-11-03 09:49:31 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Tails_2.7
Start date:
2016-10-07
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:
270

Description

It seems to affect multiple .mkv files at least, for instance: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/530/artifact/build-artifacts/02%3A47%3A38_VirtualBox_guest_modules_are_available.mkv

With Tor Browser the download just aborts after 32768 bytes. With another browser at 65230 bytes. The difference may just be in how the browser allocate data for .part files.

This is currently making analyzing artifacts for Bug #10502 hard for me.

Subtasks

Related issues

Related to Tails - Bug #11870: Monitor lizard partitions mount state Confirmed 2016-10-08
Blocks Tails - Bug #10502: The test suite sometimes cannot connect to the remote shell Resolved 2015-11-06

History

#1 Updated by anonym 2016-10-07 12:50:07

  • Assignee changed from anonym to bertagaz

Can you have a look?

#2 Updated by anonym 2016-10-07 12:50:25

  • blocks Bug #10502: The test suite sometimes cannot connect to the remote shell added

#3 Updated by anonym 2016-10-07 12:50:43

  • blocks Bug #11090: Deal with September 2016 false positive scenarios added

#4 Updated by anonym 2016-10-07 13:26:24

  • blocked by deleted (Bug #11090: Deal with September 2016 false positive scenarios)

#5 Updated by bertagaz 2016-10-07 13:40:37

  • Status changed from New to In Progress
  • % Done changed from 0 to 50

I’ve restarted our nginx VM, its root partition was mounted RO after some IO errors related to its journal. /var/lib/jenkins/ in the jenkins VM (the partition hosting the artifacts) was also mounted RO after the same kind of errors.

Download of artifacts seems to work now. I’ll let the last test job running, and will reboot the whole host. It has a new kernel anyway.

#6 Updated by anonym 2016-10-07 15:08:58

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 50 to 100
  • QA Check set to Pass

bertagaz wrote:
> I’ve restarted our nginx VM, its root partition was mounted RO after some IO errors related to its journal. /var/lib/jenkins/ in the jenkins VM (the partition hosting the artifacts) was also mounted RO after the same kind of errors.

Got it!

> Download of artifacts seems to work now.

Yes, thanks! => Closing.

#7 Updated by intrigeri 2016-10-07 16:56:20

>> I’ve restarted our nginx VM, its root partition was mounted RO after some IO errors related to its journal.

If this happens again we’ll need to set up a monitoring check for that. Waiting for actual users to complain is no good.

#8 Updated by bertagaz 2016-10-08 10:46:53

intrigeri wrote:
> >> I’ve restarted our nginx VM, its root partition was mounted RO after some IO errors related to its journal.
>
> If this happens again we’ll need to set up a monitoring check for that. Waiting for actual users to complain is no good.

Created Bug #11870.

#9 Updated by bertagaz 2016-10-08 10:49:31

  • related to Bug #11870: Monitor lizard partitions mount state added

#10 Updated by intrigeri 2016-11-03 09:49:31

  • Deliverable for set to 270