action #59202

[functional][y] Start using ASSET_ISO_SHA256 validate checksum

Added by riafarov 4 months ago. Updated 3 months ago.

Status:RejectedStart date:07/11/2019
Priority:HighDue date:03/12/2019
Assignee:riafarov% Done:

0%

Category:InfrastructureEstimated time:5.00 hours
Target version:QA - future
Difficulty:
Duration: 19

Description

Motivation

ASSET_ISO_SHA256

We have calculated MD5 checksum, but iso images already have asset with sha256 checksum

What we need is to calculate SHA256 now on the worker side.

We already have checksum calculated with sha256: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/data_integrity_utils.pm#L68

We should keep old behavior for the jobs which are still triggered by rsync.pl

riafarov will confirm how name of the variable will look like for ISO_1, etc.

Acceptance criteria

  1. sha256 checksum is validated with sha256

Related issues

Related to openQA Infrastructure - action #60032: Provide CHECKSUM_ISO parameter to ObsRsync call Resolved 19/11/2019

History

#1 Updated by riafarov 4 months ago

  • Priority changed from Normal to High

#2 Updated by riafarov 3 months ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 5.00

#3 Updated by andriinikitin 3 months ago

  • Related to action #60032: Provide CHECKSUM_ISO parameter to ObsRsync call added

#4 Updated by riafarov 3 months ago

  • Status changed from Workable to Rejected
  • Assignee set to riafarov

Was implemented by Andrii https://github.com/andrii-suse/openqa-trigger-from-obs/pull/11 Thanks to him, less work for us. =)

Also available in: Atom PDF