Tails

#1 Updated by intrigeri 2015-10-22 11:39:17

• Parent task set to Feature #5288

#2 Updated by intrigeri 2015-10-22 11:40:07

• Description updated

#3 Updated by intrigeri 2015-10-22 11:40:55

• blocks #8668 added

#4 Updated by bertagaz 2015-11-04 02:31:48

• Status changed from Confirmed to In Progress
• Assignee changed from bertagaz to intrigeri
• % Done changed from 0 to 80
• QA Check set to Ready for QA
• Feature Branch set to puppet-tails:bugfix/10409-reintroduce-old-iso-logic

intrigeri wrote:
> i.e. revert commit c1a1f7f0c9407490dc95784f625d33b54a71f4e8 in puppet-tails.
>
> And while we’re at it 638798d69346619c9da0cc206a3d4b9f7a9e4ff will want a revert as well :)

I’ve merged and deployed the feature branch, a first job is running already and is using the 1.7 iso as —old-iso. No more tao commit trick either.

#5 Updated by intrigeri 2015-11-05 03:05:25

• Status changed from In Progress to Resolved
• % Done changed from 80 to 100
• QA Check changed from Ready for QA to Pass

> I’ve merged and deployed the feature branch, a first
> job is running
> already and is using the 1.7 iso as —old-iso. No more tao commit trick either.

I confirm recent jobs use the right --old-iso. However, I see weird
failures in the affected scenarios, e.g.

https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/16/cucumberTestReport/untrusted-partitions/tails-booting-from-a-dvd-does-not-use-live-systems-stored-on-hard-drives/

… so Cc’ing the CI team. Please drop Redmine from Cc on next reply.