[8.0-pkg-systest-ubuntu] Network issues while "verify_networks"

Bug #1535283 reported by Paul Karikh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel CI

Bug Description

A job https://packaging-ci.infra.mirantis.net/job/8.0-pkg-systest-ubuntu/1832/ was failed. Looks like there are some problem network interfaces since astute.log has the followinf errors:

`Spawning listener for enp0s6 failed.` and `No route found for IPv6 destination`.
Looks like these errors a happened on the step "verify_networks". More traces are here: https://paste.mirantis.net/show/1736/

Also there are errors like this:

:stderr=>
    "W: GPG error: http://mirror.fuel-infra.org mos8.0-holdback Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08\nW: GPG error: http://mirror.fuel-infra.org mos8.0-security Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08\nW: GPG error: http://mirror.fuel-infra.org mos8.0-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08\nW: GPG error: http://perestroika-repo-tst.infra.mirantis.net mos8.0 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08\n",
   :exit_code=>0}}

But I have not found any signs of connectivity problems or "fetching was failed errors".

Revision history for this message
Paul Karikh (pkarikh) wrote :
tags: added: staging
Maciej Relewicz (rlu)
tags: added: area-ci
Changed in fuel:
importance: Undecided → High
assignee: nobody → Fuel CI (fuel-ci)
milestone: none → 8.0
status: New → Confirmed
Revision history for this message
Dmitry Kaigarodеsev (dkaiharodsev) wrote :

Looks like the issue is outdated and related patchset (https://review.fuel-infra.org/#/c/16140/) has been merged after re-trigger.

Changed in fuel:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.