App Service fails to start after boot if you have a bridge interface
Description
Problem/Justification
None
Impact
None
Activity
Show:
Bug Clerk April 6, 2024 at 1:15 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Bug Clerk April 6, 2024 at 5:34 AM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Duplicate
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Caleb
CalebReporter
Rob Panizzon
Rob PanizzonLabels
Components
Fix versions
Affects versions
Priority
UndefinedMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created April 6, 2024 at 5:34 AM
Updated May 8, 2024 at 5:55 PM
Resolved April 6, 2024 at 1:14 PM
This is a longstanding issue that was in Cobia (see https://www.truenas.com/community/threads/app-service-fails-to-lookup-bridge-interface-during-boot-after-upgrade-to-tns-23-10-1.115054/page-3#post-817019).
When a bridged interface is defined, and set in the Apps Setting, the apps service fails to start after a reboot.
Error Message is "Error in Apps Service".
Note that this appears to be a timing issue where Kubernetes does not wait for br0 to start. If I run Dragonfish in a VM the problem does not occur.
Host ID: 001f83122764487d65d39a083d78ad55620fff3d92b193d9ebd97de1fd24b04f
Session ID: 23503cd3-41ea-eb1f-f33d-aad7252783c5