Project

General

Profile

Actions

action #124970

closed

coordination #130075: [epic] Milestone testing for SLE 15 SP6

Manual testing for RMT regression test case

Added by zoecao over 1 year ago. Updated 4 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Target version:
-
Start date:
2023-02-23
Due date:
% Done:

0%

Estimated time:

Description

Motivation

One of the rmt regression cases is not automated, need to test it manually. Testing steps:
https://bugzilla.suse.com/tr_show_case.cgi?case_id=1769991

Acceptance criteria

AC1: Test functionality for milestone
AC2: Document in confluence with screenshot (hidding sensitive info) so it is easier to follow by everyone next time.

Additional information


Related issues 1 (0 open1 closed)

Related to qe-yam - action #153535: SLE 15 SP6 Beta3 - RMT/SMT/SCC status check and Milestone build triggeringResolvedzoecao2023-12-11

Actions
Actions #1

Updated by JERiveraMoya about 1 year ago

  • Parent task changed from #119314 to #130075
Actions #2

Updated by rainerkoenig 7 months ago

Is this still a valid issue? Can't follow the Bugzilla link, ends up in a 404.
And its for SP5 which is released meanwhile.

Actions #3

Updated by JERiveraMoya 6 months ago

  • Priority changed from Normal to Low
  • Target version deleted (Current)
  • Parent task deleted (#130075)
Actions #4

Updated by zoecao 6 months ago

We may need to update the ticket tittle to 15SP6.
And I update the test step here:

  • Set up RMT server, mirror a product (take sles15sp6 as an example) with recommended modules ('rmt-cli products enable SLES/15.6/x86_64')
  • Register a SLES 15.6 client via this RMT server with: "SUSEConnect --url [rmt_url] -p SLES/15.6/x86_64 -r [regcode]"
  • Sync systems from RMT server to SCC: "rmt-cli systems scc-sync"
  • Open scc.suse.com with the user of the organization that is configured in RMT (from /etc/rmt.conf scc username).
  • Click 'Proxies', select 'Show details' on your RMT
  • Check if the registered system is visible, it's activations are listed, it is connected to the used subscription, and the 'last seen at' date matches with the time the registration happened.
  • de-register the client from RMT: "SUSEConnect --de-register"
  • check whether the system is gone from RMT server by "rmt-cli systems list"
  • Sync systems from RMT to SCC: "rmt-cli systems scc-sync"
  • Then check whether the system is not listed in SCC
Actions #5

Updated by zoecao 5 months ago

  • Subject changed from SLE15 SP5 Manual testing for RMT regression case to SLE15 SP6 Manual testing for RMT regression case

Regarding the RMT regression tests, I contacted with scc team, and update the test step here:

  • Set up RMT server (rmt-server 2.14 version), mirror a product (take sles15sp6 as an example) with recommended modules ('rmt-cli products enable SLES/15.x/x86_64')
  • Register some clients via this RMT server with: "SUSEConnect --url [rmt_url] -p SLES/15.x/x86_64 -r [regcode]"
  • Sync systems from RMT server to SCC: "rmt-cli systems scc-sync"
  • Open scc.suse.com with the user of the organization that is configured in RMT (from /etc/rmt.conf scc username).
  • Click 'Proxies', select 'Show details' on your RMT
  • Check if the registered system is visible, it's activations are listed, it is connected to the used subscription, and the 'last seen at' date matches with the time the registration happened.
  • De-register the client from RMT: "SUSEConnect --de-register"
  • Check whether the system is gone from RMT server by "rmt-cli systems list"
  • Sync systems from RMT to SCC: "rmt-cli systems scc-sync"
  • Then check whether the system is not listed on SCC
  • Keep some client registration records on SCC
  • Update the rmt-server to version 2.15
  • Check whether the registered clients are correctly kept on SCC
Actions #6

Updated by JERiveraMoya 5 months ago

  • Tags set to qe-yam-feb-sprint
  • Subject changed from SLE15 SP6 Manual testing for RMT regression case to Manual testing for RMT regression test case
  • Description updated (diff)
  • Status changed from New to In Progress
  • Assignee set to zoecao
  • Priority changed from Low to Normal
  • Parent task set to #130075
Actions #7

Updated by JERiveraMoya 5 months ago

  • Related to action #153535: SLE 15 SP6 Beta3 - RMT/SMT/SCC status check and Milestone build triggering added
Actions #8

Updated by JERiveraMoya 5 months ago

  • Priority changed from Normal to Low
Actions #9

Updated by zoecao 5 months ago

Already installed a SLES15SP6 beta3 system manually with a local vm, and installed rmt-server-2.14 version.
But I came across the issue in [bsc#1218084]. I used another organization group given by scc team in the before, but I can not check the rmt server registration status for this group. Will contact with scc team about this.

Actions #10

Updated by JERiveraMoya 5 months ago

  • Status changed from In Progress to Workable

Moving to workable to not forget.

Actions #11

Updated by zoecao 4 months ago

  • Status changed from Workable to In Progress

The issue of bsc#1218084 is gone, I switched to the organization which could mirror more products, and mirrored SLES15SP6. And tested system sync function on rmt-server-2.14 version, with continue the rest of testing.

Actions #12

Updated by zoecao 4 months ago

The manual testing is finished, filed one bug report [bsc#1220109], there's still one question need to confirm with scc team, I have sent the test result and my question to scc team.
I will document it in confluence with screenshots.

Actions #13

Updated by zoecao 4 months ago

  • Status changed from In Progress to Resolved

The How-to document in confluence with screenshots:
https://confluence.suse.com/display/qasle/How+to+test+RMT+regression+cases

And de-registered the RMT server I setup for testing as well as the clients, and removed the VMs of the rmt server. Close this ticket now.

BTW: The steps I write in document is regular testing steps. On this ticket the testing is a little special that I tested two version of rmt-server which is to verify a fix on newer version based on scc team's requirements. No need to test this all the time.

Actions

Also available in: Atom PDF