Project

General

Profile

Actions
Copy link

action #59202

closed

[functional][y] Start using ASSET_ISO_SHA256 validate checksum

Added by riafarov about 5 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
High
Assignee:
riafarov
Category:
Infrastructure
Target version:
QA (public) - future
Start date:
2019-11-07
Due date:
2019-12-03
% Done:

0%

Estimated time:
5.00 h
Difficulty:

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 1 (0 open — 1 closed)

Related to openQA Infrastructure (public) - action #60032: Provide CHECKSUM_ISO parameter to ObsRsync callResolvedandriinikitin2019-11-19

Actions
Actions
Copy link
 #1

Updated by riafarov about 5 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #2

Updated by riafarov about 5 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 5.00 h
Actions
Copy link
 #3

Updated by andriinikitin about 5 years ago

  • Related to action #60032: Provide CHECKSUM_ISO parameter to ObsRsync call added
Actions
Copy link
 #4

Updated by riafarov about 5 years 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. =)

Actions
Copy link

Also available in: Atom PDF