https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-11-27T13:20:39ZopenSUSE Project Management ToolQA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1691182018-11-27T13:20:39Zokurzokurz@suse.com
<ul><li><strong>Copied from</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed" href="/issues/43580">action #43580</a>: The RT product can be tested by release managers or developers before full SLE validation</i> added</li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1692022018-11-27T17:46:39Zokurzokurz@suse.com
<ul></ul><p><a href="https://bugzilla.suse.com/show_bug.cgi?id=1117535" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1117535</a> is a bug I found in the RT staging test example so I guess it <em>does</em> make sense to have that in staging</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1773352019-01-08T15:16:21Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2019-02-12</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1808782019-01-21T13:28:24Zriafarov
<ul><li><strong>Due date</strong> deleted (<del><i>2019-02-12</i></del>)</li></ul><p>Is it confirmed with Jeffrey? I disagree to extend some staging for the RT, only RT specific one. Removing from the sprint for now.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1812112019-01-22T10:56:10Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2019-02-26</i></li><li><strong>Target version</strong> changed from <i>Milestone 22</i> to <i>Milestone 23</i></li></ul><p>riafarov wrote:</p>
<blockquote>
<p>Is it confirmed with Jeffrey?</p>
</blockquote>
<p>It is. We mentioned it as an idea in one of the calls with him, he took the idea and in the end the task bounced back to us over multiple hops of management.</p>
<blockquote>
<p>I disagree to extend some staging for the RT, only RT specific one.</p>
</blockquote>
<p>Sorry, I don't understand. Can you elaborate?</p>
<blockquote>
<p>Removing from the sprint for now.</p>
</blockquote>
<p>ok, fine. Let's try later then :)</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1887682019-02-14T09:50:51Zriafarov
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/188768/diff?detail_id=187187">diff</a>)</li><li><strong>Estimated time</strong> set to <i>5.00 h</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1891462019-02-15T10:01:56Zmloviskamloviska@suse.com
<ul><li><strong>Assignee</strong> set to <i>mloviska</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1891792019-02-15T11:13:07Zmloviskamloviska@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Feedback</i></li></ul><p>mail sent to Coolo and Jeffrey</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1892692019-02-15T14:39:01Zmloviskamloviska@suse.com
<ul></ul><pre><code>In which staging project to schedule (or in all), is something to be discussed with sle-release-coord@suse.de
</code></pre>
<p>So let's wait for Jeffrey's thoughts </p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1930522019-02-26T10:39:00Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2019-02-26</i> to <i>2019-03-26</i></li></ul><p>Got reply from Jeffrey, but not getting answer to our question. If not RT, we can consider any other project e.g. SLED.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1940752019-02-28T13:01:50Zmloviskamloviska@suse.com
<ul></ul><pre><code>Since RT is a small product, I am neutral to have staging test for RT. Please tell if this is easy to setup the testing or not.
Jeffrey
</code></pre>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/25024">@riafarov</a>, <a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a> there is no strong opinion regarding RT and staging. What kind of actions should we take now?</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1941202019-02-28T15:12:05Zokurzokurz@suse.com
<ul></ul><p>I suggest to just add SLE RT as the "second SLE product" in staging.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1969792019-03-08T08:14:18Zmloviskamloviska@suse.com
<ul></ul><p>Jeffrey decided to leave staging as it is for now and enable RT in staging when sle15sp2 comes.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1974262019-03-09T17:57:51Zokurzokurz@suse.com
<ul></ul><p>That's ok however we should add the test scenario nevertheless as decided. The main purpose is to cover "any second SLE product besides SLES", we just picked "SLE RT" as the example.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1979062019-03-12T08:36:16Zmloviskamloviska@suse.com
<ul></ul><p>okurz wrote:</p>
<blockquote>
<p>That's ok however we should add the test scenario nevertheless as decided. The main purpose is to cover "any second SLE product besides SLES", we just picked "SLE RT" as the example.<br>
That is against AC1</p>
</blockquote>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=1980952019-03-12T10:44:23Zokurzokurz@suse.com
<ul></ul><p>I think you have covered AC1 pretty well. So we understood that the RT RM does not care :) Which means we could simply pick "any product". We could select "sles4sap" just as well.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2014462019-03-22T12:18:53Zriafarov
<ul></ul><p>As per our discussion, as we have risk of RT not being available in SLE 15 SP2, we agreed that we should better aim other product which will remain, e.g. HPC, SAP or SLED. I've checked, both are available on staging. Will clarify with Frederic if he is fine with extending staging with such scenario.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2015212019-03-22T16:15:16Zriafarov
<ul><li><strong>Due date</strong> deleted (<del><i>2019-03-26</i></del>)</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Workable</i></li><li><strong>Assignee</strong> deleted (<del><i>mloviska</i></del>)</li><li><strong>Target version</strong> changed from <i>Milestone 23</i> to <i>Milestone 26</i></li></ul><p>As per discussion with Frederic, SAP would be better candidate in his opinion and we also agreed that we should perform that change for SP2 and in case of SAP being chosen one as second product, we need to confirm it with Stefan Weiberg as he is accountable for providing fixes for it.</p>
<p>So, I move it to the product backlog so we can work on it after SP1 is released. We also will have information if RT will be available.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2341642019-08-12T08:42:10Zriafarov
<ul><li><strong>Target version</strong> changed from <i>Milestone 26</i> to <i>Milestone 27</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2436442019-09-16T09:26:52Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 27</i> to <i>Milestone 28</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2519632019-10-22T14:32:37Zriafarov
<ul><li><strong>Target version</strong> changed from <i>Milestone 28</i> to <i>Milestone 29</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2539032019-10-31T08:46:18Zriafarov
<ul><li><strong>Due date</strong> set to <i>2019-12-03</i></li><li><strong>Target version</strong> changed from <i>Milestone 29</i> to <i>Milestone 30+</i></li></ul><p>SLE 15 SP2 online installer doesn't support installation of other products yet.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2585212019-11-19T15:01:23Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2019-12-03</i> to <i>2019-12-17</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2615392019-12-03T13:47:50Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2019-12-17</i> to <i>2020-01-28</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2683542020-01-03T11:02:44Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 30+</i> to <i>Milestone 30</i></li></ul><p>bulk moved to M30 for revisiting</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2714752020-01-15T10:22:52Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2020-01-28</i> to <i>2020-02-11</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2750572020-01-29T10:31:25Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2020-02-11</i> to <i>2020-02-25</i></li></ul> QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2786802020-02-18T12:34:10Zoorlovoorlov@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Rejected</i></li></ul><p>Already implemented in Staging:S: (e.g. <a href="https://openqa.suse.de/tests/3895515" class="external">sles4sap_default_install@64bit</a>).</p>
<p>It is enough to catch issues on early stage.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2786982020-02-18T14:04:01Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Rejected</i> to <i>Workable</i></li></ul><p>But I don't think that counts because :S is <em>only</em> used to stage SLES4SAP changes. One goal for this story to was to test e.g. if the SLES4SAP installer breaks on SLES changes. I guess when we have the sles4sap scenario triggered in all other staging projects we could count this as done.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2787222020-02-18T16:00:21Zriafarov
<ul><li><strong>Subject</strong> changed from <i>[sle][functional][y] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15</i> to <i>[sle][functional] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15</i></li><li><strong>Due date</strong> deleted (<del><i>2020-02-25</i></del>)</li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>okurz wrote:</p>
<blockquote>
<p>But I don't think that counts because :S is <em>only</em> used to stage SLES4SAP changes. One goal for this story to was to test e.g. if the SLES4SAP installer breaks on SLES changes. I guess when we have the sles4sap scenario triggered in all other staging projects we could count this as done.</p>
</blockquote>
<p>For staging projects we always have argument of having more tests vs execution time. Enabling this scenario for all staging will significantly increase load on the workers causing delays in the results. As we didn't see this functionality breaking often to run it for each staging, we also can see that in the installer part we don't miss severe regressions which do not allow testing.</p>
<p>In case we really want to have it covered, we should rather enable separate checks for the limited scope instead of choosing second popular product and enabling it just because we can.<br>
So for qsf-y, we don't see action items remaining here for us and other stakeholders (this was our initiative originally and didn't get much support from other stakeholders).</p>
<p>Assigning it to you, in case you want to act on it.</p>
QA - action #44393: [sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15https://progress.opensuse.org/issues/44393?journal_id=2823072020-03-02T21:40:43Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[sle][functional] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15</i> to <i>[sle][desktop][sles4sap][hpc] staging project for a second SLE product besides SLES, e.g. SLE RT in SLE15</i></li><li><strong>Assignee</strong> deleted (<del><i>okurz</i></del>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Target version</strong> changed from <i>Milestone 30</i> to <i>future</i></li></ul><p>Yes, sounds reasonable. So this could be interesting e.g. for [desktop] or [sles4sap] or [hpc]</p>