Project

General

Profile

Actions
Copy link

action #104886

closed

[sle][migration][sle15sp4] New feature for rmt - From 2.7.0 on, clients that register to RMT can use a registration code, its consumed subscriptions are showing up correctly in SCC

Added by zoecao over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
zoecao
Category:
New test
Target version:
-
Start date:
2022-01-14
Due date:
% Done:

100%

Estimated time:
12.00 h
Difficulty:

Description

SCC team added some new features to RMT in the area of forwarding more system details to SCC, which would be worth testing:
From 2.7.0 on, clients that register to RMT can use a registration code. This will connect
the product activation to a subscription. This connection gets forwarded to SCC,
so you can test that the client System, its activated products and its consumed subscriptions are showing up
correctly in SCC, under the organization that the RMT is using.

I have confirmed the testing steps with scc team, and will update here after get the final steps because one of the steps still needs to be confirmed.

I will add this case to testopia.

Actions
Copy link
 #1

Updated by zoecao over 2 years ago

Test steps:

  • Set up RMT, mirror SLES 15.3 with recommended modules ('rmt-cli products enable SLES/15.3/x86_64')
  • Register a SLES 15.3 client system to this RMT with: "SUSEConnect --url "
  • Sync systems from RMT to SCC: "rmt-cli systems scc-sync"
  • Open scc.suse.com with a user of the organization that is configured in RMT (from /etc/rmt.conf scc username).
  • Go to '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 system from RMT: "SUSEConnect --de-register"
  • make sure the system is gone from RMT by checking it's not listed anymore "rmt-cli systems list"
  • Sync systems from RMT to SCC: "rmt-cli systems scc-sync"
  • Make sure the system is not listed in SCC anymore
Actions
Copy link
 #2

Updated by zoecao over 2 years ago

  • Category set to New test
Actions
Copy link
 #3

Updated by zoecao over 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10
  • Confirmed the testing steps and respected results;
  • setup a rmt server, the required product repos are mirroring;
  • prepared a vm as the rmt server's client.
Actions
Copy link
 #4

Updated by zoecao over 2 years ago

  • Status changed from In Progress to Rejected

Move to testopia.

Actions
Copy link
 #5

Updated by zoecao over 2 years ago

  • Subject changed from [sle][migration][sle15sp4] New test case for rmt regression testing to [sle][migration][sle15sp4] New feature for rmt - From 2.7.0 on, clients that register to RMT can use a registration code, its consumed subscriptions are showing up correctly in SCC
  • Status changed from Rejected to In Progress
Actions
Copy link
 #6

Updated by leli over 2 years ago

  • Estimated time set to 12.00 h
Actions
Copy link
 #7

Updated by zoecao over 2 years ago

  • % Done changed from 10 to 70

Performed as the steps above, no problem with rmt server side.
While there's a problem with the rmt listed on the scc, the hostname issue.
Will investigate it and confirm it with scc team.

Actions
Copy link
 #8

Updated by zoecao about 2 years ago

Sent email to Thomas to confirm the test results and the problems I found, waiting for reply.

Actions
Copy link
 #9

Updated by zoecao about 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 100

Added a testing scenario, register client with the rmt server and a regcode, check the rmt-client systems list & scc.
Confirmed the test results with scc team via email, close this ticket.

Actions
Copy link

Also available in: Atom PDF