Project

General

Profile

Bug #27955

Give Discovery-menu service more time to detect interface with link up

Added by Rohan Arora 9 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Image
Target version:
Difficulty:
easy
Triaged:
No
Bugzilla link:

Description

Sometimes Link comes up after discovery menu service has already run logic to detect the interface with link. In this case it ends up choosing a random interface.
--------------------------
Sep 11 13:47:00 fdi NetworkManager1784: <info> [1568209620.7466] device (lo): carrier: link connected
Sep 11 13:47:03 fdi /usr/bin/discovery-menu1857: Detecting the first NICs with link
Sep 11 13:47:03 fdi /usr/bin/discovery-menu1857: No interfaces with link found, using 00:XX:XX:XX:XX:XX
Sep 11 13:47:03 fdi NetworkManager1784: <info> [1568209623.9117] device (eno1): carrier: link connected


Related issues

Related to Ansible - Bug #27954: Give Discovery-menu service more time to detect interface with link upDuplicate

Associated revisions

Revision c5903826 (diff)
Added by Rohan Arora 9 months ago

Fixes #27955 - Start discovery-menu service later

History

#1 Updated by Rohan Arora 9 months ago

  • Related to Bug #27954: Give Discovery-menu service more time to detect interface with link up added

#2 Updated by The Foreman Bot 9 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-discovery-image/pull/117 added

#3 Updated by The Foreman Bot 9 months ago

  • Fixed in Releases Discovery Image 3.5.1 added

#4 Updated by Rohan Arora 9 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF