https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-01-22T21:13:12ZopenSUSE Project Management ToolopenQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2737282020-01-22T21:13:12Zokurzokurz@suse.com
<ul><li><strong>Copied from</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed" href="/issues/62243">action #62243</a>: After latest updates, openQA has problematic behavior on Dell Precision 5810</i> added</li></ul> openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2737342020-01-22T21:26:19Zokurzokurz@suse.com
<ul><li><strong>Category</strong> changed from <i>Feature requests</i> to <i>Regressions/Crashes</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>hm, I just have the suspicion that this is a problem that was introduced in the past months, either in our code or the dependencies.</p>
openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2747092020-01-27T14:42:20Zkraihsebastian.riedel@suse.com
<ul></ul><p>There have been no upstream changes from the Mojo side of things in recent months that would seem relevant. Looking at the openQA code, it seems we set the listen address to <code>127.0.0.1</code>, and for a long time (it was switched from <code>localhost</code> 17 months ago).</p>
openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2760622020-02-03T11:08:08Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/276062/diff?detail_id=272678">diff</a>)</li></ul> openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2805762020-02-25T11:36:54Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/280576/diff?detail_id=277306">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2811012020-02-26T15:06:35Zokurzokurz@suse.com
<ul></ul><p>mkittler and me compared the systemd service dependencies to Apache and nginx and found that it's good to rely on nss-lookup.target and maybe also remote-fs.target</p>
openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2812572020-02-27T09:04:13Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed" href="/issues/44105">action #44105</a>: if workercache dies, we get *tons* of incompletes</i> added</li></ul> openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2813682020-02-27T11:49:24Zokurzokurz@suse.com
<ul><li><strong>File</strong> <a href="/attachments/9535">logs</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/9535/logs">logs</a> added</li><li><strong>Status</strong> changed from <i>Workable</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>I tried to simulate the error condition with two mocked systemd services "block.service" and "after-block.service" and then setting nscd.service to start after that. The scheduler started in before and was fine. From original logs on falafel (see attached) I could find that the problem happened when the NIC didn't even have a link yet. Based on that I will just suggest to depend on nss-lookup.target, same as apache2.service does.</p>
<p><a href="https://github.com/os-autoinst/openQA/pull/2782" class="external">https://github.com/os-autoinst/openQA/pull/2782</a> for the webui related service and <a href="https://github.com/os-autoinst/openQA/pull/2783" class="external">https://github.com/os-autoinst/openQA/pull/2783</a> also including worker if we want to.</p>
<p>EDIT: 2020-02-29: Both PRs merged. Let's wait for feedback from production and users.</p>
openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2817942020-02-28T12:06:47Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2020-03-06</i></li></ul> openQA Project - action #62567: openqa services can fail when network is not up (yet) "Can't create listen socket: Address family for hostname not supported"https://progress.opensuse.org/issues/62567?journal_id=2823132020-03-02T21:43:31Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>seems fine, no negative reports received</p>