Project

General

Profile

Actions
Copy link

action #49172

closed

Implement migration test from same version to the same version (bsc#1128459)

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

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
QA - future
Start date:
2019-03-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Inspired by https://bugzilla.suse.com/show_bug.cgi?id=1128459 Some of our customers use this trick to fix the system and recover it from the issues.

It's not common use-case though and is not officially documented, whereas will allow us to catch bugs and identify issues easier, which can be a prerequisite for the actual migration tests.

Actions
Copy link
 #1

Updated by okurz about 5 years ago

  • Target version set to future

cool idea. Do you think we should move it to "[migration]" instead? I would assume that QSF-y would estimate the effort for this one very high as the team is not very experienced with migration tests?

Actions
Copy link
 #2

Updated by riafarov over 3 years ago

  • Project changed from openQA Tests to qe-yam
  • Subject changed from [functional][y] Implement migration test from same version to the same version (bsc#1128459) to Implement migration test from same version to the same version (bsc#1128459)
  • Category deleted (New test)
Actions
Copy link
 #3

Updated by okurz over 2 years ago

  • Priority changed from Normal to Low

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. The ticket will be set to the next lower priority of "Low" as discussed with qe-yast PO oorlov (https://suse.slack.com/archives/C02LECV2R0X/p1636974668013200)

Actions
Copy link
 #4

Updated by JERiveraMoya 3 months ago

  • Status changed from New to Rejected

Backlog clean-up.

Actions
Copy link

Also available in: Atom PDF