https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-03-28T12:45:52ZopenSUSE Project Management ToolopenQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5054932022-03-28T12:45:52Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> set to <i>Ready</i></li></ul> openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5057332022-03-29T07:34:40ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-1 priority-4 priority-default" href="/issues/98832">action #98832</a>: [qac][container][powerVM] rebootmgr fails in PowerVM reconnecting after reboot</i> added</li></ul> openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5059822022-03-29T14:30:01Zmkittlermarius.kittler@suse.com
<ul></ul><p>I've just tried to connect to redcurrant-4.qa.suse.de via SSH and it works besides the fact that I don't know the password. Not sure how we can help here, it looks just like a temporary networking issue, maybe even related to <a class="issue tracker-4 status-3 priority-6 priority-high2 closed child" title="action: Network performance problems, DNS, DHCP, within SUSE QA network auto_review:"(Error connecting to... (Resolved)" href="https://progress.opensuse.org/issues/108845">#108845</a>.</p>
openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5064502022-03-30T09:40:31Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host</i> to <i>Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host size:M</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/506450/diff?detail_id=478742">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5064682022-03-30T10:07:25Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host size:M</i> to <i>Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:M</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Low</i></li></ul> openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5096912022-04-08T14:05:18Zlivdywanliv.dywan@suse.com
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-4 status-1 priority-4 priority-default" href="/issues/109719">action #109719</a>: [qe-core][ppc][hmc] Network issues on ppc64le-hmc workers : "Error connecting to redcurrant-3.qa.suse.de: no route to host"</i> added</li></ul> openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5098292022-04-09T12:15:41Zokurzokurz@suse.com
<ul><li><strong>Parent task</strong> set to <i>#109656</i></li></ul> openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5130642022-04-24T01:01:06Zopenqa_reviewopenqa-review@suse.de
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: RAID0@ppc64le-hmc-4disk<br>
<a href="https://openqa.suse.de/tests/8570565#step/validate_md_raid/1" class="external">https://openqa.suse.de/tests/8570565#step/validate_md_raid/1</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.</p>
openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5141802022-04-28T05:27:54ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>keep happening sporadically and seems unrelated with builds/network/power issues.</p>
openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5145462022-04-29T06:04:27ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>In transactional scenario we saw since a lot of time the same issue in a non-sporadic way:<br>
<a class="issue tracker-4 status-1 priority-4 priority-default" title="action: [qac][container][powerVM] rebootmgr fails in PowerVM reconnecting after reboot (New)" href="https://progress.opensuse.org/issues/98832">#98832</a></p>
openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5193662022-05-14T00:15:14Zopenqa_reviewopenqa-review@suse.de
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: transactional_server_helper_apps@ppc64le-hmc-single-disk<br>
<a href="https://openqa.suse.de/tests/8743569#step/rebootmgr/1" class="external">https://openqa.suse.de/tests/8743569#step/rebootmgr/1</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.</p>
openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5278552022-06-11T00:32:49Zopenqa_reviewopenqa-review@suse.de
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: transactional_server_helper_apps@ppc64le-hmc-single-disk<br>
<a href="https://openqa.suse.de/tests/8752118#step/rebootmgr/1" class="external">https://openqa.suse.de/tests/8752118#step/rebootmgr/1</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.</p>
openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5403342022-07-22T13:37:41Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Ready</i> to <i>future</i></li></ul><p>We within the SUSE QE Tools team currently do not have the capacity to work on this, removing from backlog.</p>
openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=5568162022-09-23T12:37:48ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed" href="/issues/117127">action #117127</a>: Run rebootmgr in transactional_server_helper_apps in PowerVM only in YaST development group</i> added</li></ul> openQA Infrastructure - action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:Mhttps://progress.opensuse.org/issues/109112?journal_id=6114262023-03-09T12:28:20Zokurzokurz@suse.com
<ul><li><strong>Parent task</strong> changed from <i>#109656</i> to <i>#125708</i></li></ul>