Project

General

Profile

Actions

action #94453

closed

[sle][migration][sle15sp4] do not need check susefirewall status after migration to 15spx from 11spx or 12spx

Added by coolgw almost 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-06-22
Due date:
% Done:

100%

Estimated time:
8.00 h
Difficulty:

Actions #1

Updated by hjluo almost 3 years ago

  • Assignee set to hjluo

if > 15GA & is migration case after migration then start configure susefirewall-to-firewall. No need to check susefirewall/firewall status

Actions #2

Updated by leli almost 3 years ago

  • Subject changed from [sle][Migration][SLE15SP4] do not need check susefirewall status after migration to 15spx from 11spx or 12spx to [sle][migration][sle15sp4] do not need check susefirewall status after migration to 15spx from 11spx or 12spx
  • Assignee deleted (hjluo)
  • Priority changed from Normal to High
Actions #3

Updated by leli almost 3 years ago

  • Assignee set to hjluo
Actions #4

Updated by leli almost 3 years ago

  • Estimated time set to 8.00 h
Actions #5

Updated by hjluo almost 3 years ago

  • % Done changed from 0 to 10

./hj-tools/hj-branch.sh -b fwall -j 5991265 -s "_GROUP=0"
https://openqa.nue.suse.com/t6312188

Actions #6

Updated by hjluo almost 3 years ago

sle11sp4 regcode is not working now. wait for scc team to provide a new one.

Actions #7

Updated by hjluo almost 3 years ago

  • Status changed from New to Rejected
  • % Done changed from 10 to 100

After discussing with gaowei, we decided to reject this ticket.
the reason is as follow:
OpenQA script only has an issue for 11sp4->15sp3, BUT since 11sp4 will out of lifecycle in the next project, so we do not need to take any action now. This scenario(11sp4->15spx) will not running on OpenQA for next project {SLES15SP4}.

Actions

Also available in: Atom PDF