https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-05-30T12:41:45ZopenSUSE Project Management Toolqe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=6377082023-05-30T12:41:45ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Parent task</strong> changed from <i>#119314</i> to <i>#130075</i></li></ul> qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7387092023-11-27T16:41:11Zrainerkoenig
<ul></ul><p>Is this still a valid issue? Can't follow the Bugzilla link, ends up in a 404. <br>
And its for SP5 which is released meanwhile. </p>
qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7468392023-12-19T13:11:10ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Target version</strong> deleted (<del><i>Current</i></del>)</li><li><strong>Parent task</strong> deleted (<del><i>#130075</i></del>)</li></ul> qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7473972023-12-21T02:43:09Zzoecaochcao@suse.com
<ul></ul><p>We may need to update the ticket tittle to 15SP6. <br>
And I update the test step here:</p>
<ul>
<li>Set up RMT server, mirror a product (take sles15sp6 as an example) with recommended modules ('rmt-cli products enable SLES/15.6/x86_64')</li>
<li>Register a SLES 15.6 client via this RMT server with: "SUSEConnect --url [rmt_url] -p SLES/15.6/x86_64 -r [regcode]"</li>
<li>Sync systems from RMT server to SCC: "rmt-cli systems scc-sync"</li>
<li>Open scc.suse.com with the user of the organization that is configured in RMT (from /etc/rmt.conf scc username).</li>
<li>Click 'Proxies', select 'Show details' on your RMT</li>
<li>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.</li>
<li>de-register the client from RMT: "SUSEConnect --de-register"</li>
<li>check whether the system is gone from RMT server by "rmt-cli systems list"</li>
<li>Sync systems from RMT to SCC: "rmt-cli systems scc-sync"</li>
<li>Then check whether the system is not listed in SCC</li>
</ul>
qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7584942024-02-01T08:07:17Zzoecaochcao@suse.com
<ul><li><strong>Subject</strong> changed from <i>SLE15 SP5 Manual testing for RMT regression case </i> to <i>SLE15 SP6 Manual testing for RMT regression case </i></li></ul><p>Regarding the RMT regression tests, I contacted with scc team, and update the test step here:</p>
<ul>
<li>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')</li>
<li>Register some clients via this RMT server with: "SUSEConnect --url [rmt_url] -p SLES/15.x/x86_64 -r [regcode]"</li>
<li>Sync systems from RMT server to SCC: "rmt-cli systems scc-sync"</li>
<li>Open scc.suse.com with the user of the organization that is configured in RMT (from /etc/rmt.conf scc username).</li>
<li>Click 'Proxies', select 'Show details' on your RMT</li>
<li>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.</li>
<li>De-register the client from RMT: "SUSEConnect --de-register"</li>
<li>Check whether the system is gone from RMT server by "rmt-cli systems list"</li>
<li>Sync systems from RMT to SCC: "rmt-cli systems scc-sync"</li>
<li>Then check whether the system is not listed on SCC</li>
<li>Keep some client registration records on SCC</li>
<li>Update the rmt-server to version 2.15</li>
<li>Check whether the registered clients are correctly kept on SCC</li>
</ul>
qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7585962024-02-01T09:33:37ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Tags</strong> set to <i>qe-yam-feb-sprint</i></li><li><strong>Subject</strong> changed from <i>SLE15 SP6 Manual testing for RMT regression case </i> to <i>Manual testing for RMT regression test case </i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/758596/diff?detail_id=711877">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>zoecao</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li><li><strong>Parent task</strong> set to <i>#130075</i></li></ul> qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7586052024-02-01T09:35:38ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" href="/issues/153535">action #153535</a>: SLE 15 SP6 Beta3 - RMT/SMT/SCC status check and Milestone build triggering</i> added</li></ul> qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7600272024-02-05T14:16:11ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7603332024-02-06T08:14:43Zzoecaochcao@suse.com
<ul></ul><p>Already installed a SLES15SP6 beta3 system manually with a local vm, and installed rmt-server-2.14 version.<br>
But I came across the issue in <a href="https://bugzilla.suse.com/show_bug.cgi?id=1218084#c9" class="external">[bsc#1218084]</a>. 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.</p>
qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7609032024-02-07T07:37:54ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Workable</i></li></ul><p>Moving to workable to not forget.</p>
qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7649892024-02-19T10:27:21Zzoecaochcao@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul><p>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.</p>
qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7657482024-02-21T07:17:58Zzoecaochcao@suse.com
<ul></ul><p>The manual testing is finished, filed one bug report <a href="https://bugzilla.suse.com/show_bug.cgi?id=1220109" class="external">[bsc#1220109]</a>, there's still one question need to confirm with scc team, I have sent the test result and my question to scc team.<br>
I will document it in confluence with screenshots.</p>
qe-yam - action #124970: Manual testing for RMT regression test case https://progress.opensuse.org/issues/124970?journal_id=7673292024-02-23T11:36:22Zzoecaochcao@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>The How-to document in confluence with screenshots:<br>
<a href="https://confluence.suse.com/display/qasle/How+to+test+RMT+regression+cases" class="external">https://confluence.suse.com/display/qasle/How+to+test+RMT+regression+cases</a></p>
<p>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.</p>
<p>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.</p>