Bug #40692
At boot, have MDNS wait for /etc/resolv.conf to be available and valid
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No
Description
I have noticed some errors about unreachable network before pool import that may be related. Attaching a debug to provide a log. Basically the problem I am seeing is that mdns does not work at all upon boot up until I restart a service like smb, or ssh.
Related issues
Associated revisions
Wait for /etc/resolv.conf to be available and valid
Ticket: #38265
(cherry picked from commit fd5b5a434f39c7bc527f6e97b946865160c6d0ca)
(11.1-stable)
Ticket: #40692
PEP8 does not agree with me
(cherry picked from commit 1b2e28c02a1799e4cb57013ca9ac465f4d6e34ed)
(11.1-stable)
Ticket: #40692
Fix some copy over errors
(cherry picked from commit 187f7fdb1f359dae1d24c3dc189a4adf0dd670ac)
(11.1-stable)
Ticket: #40692
flake8 - shut the CI up
(cherry picked from commit efa2e99570d0f69b621aa8480a69456f3c378f62)
(11.1-stable)
Ticket: #40692
History
#1
Updated by John Hixson over 2 years ago
- Copied from Bug #38265: At boot, have MDNS wait for /etc/resolv.conf to be available and valid added
#2
Updated by John Hixson over 2 years ago
11.1-stable PR: https://github.com/freenas/freenas/pull/1638
#4
Updated by Dru Lavigne over 2 years ago
- Status changed from Unscreened to In Progress
- Needs QA changed from No to Yes
- Needs Merging changed from No to Yes
#5
Updated by Dru Lavigne over 2 years ago
- Status changed from In Progress to Ready for Testing
- Needs Merging changed from Yes to No
#7
Updated by Bonnie Follweiler over 2 years ago
- Status changed from Ready for Testing to Passed Testing
- Needs QA changed from Yes to No
Test Passed in FreeNAS-11.1-U6-INTERNAL2
#8
Updated by Dru Lavigne over 2 years ago
- Status changed from Passed Testing to Done