Input installed from content pack shows inconsistent running state and does not receive messages #25425

Expected Behavior

After uploading and installing a content pack containing an input, the created input should behave consistently across the UI.

If the input is shown as "running" in the inputs overview, it should actually be running and able to receive messages. The detail page should show the same state.

Current Behavior

After uploading and installing a content pack containing an input:

• the input is shown as "running" in the overview
• the input does not collect any messages
• when opening the input details, the state is shown as "Not running"

This is surprising and misleading because the overview and detail page contradict each other, while there is no visible indication that the input configuration is invalid or failed to start.

Possible Solution

Investigate whether inputs created through content pack installation are:

• not actually started after installation
• reported with an incorrect state in the inputs overview
• missing required runtime configuration or node assignment
• failing silently without surfacing an error in the UI

It would also help to:

• make the state reporting consistent between overview and detail page
• surface a clear error or warning if the input failed to start correctly
• validate content-pack-created inputs after installation

Steps to Reproduce (for bugs)

1. Create a content pack that contains an input
2. Upload and install the content pack in Graylog
3. Open the inputs overview and observe that the input is shown as "running"
4. Send messages to the input and observe that no messages are collected
5. Open the input details page
6. Observe that the input state is shown as "Not running"

Context

This is confusing because the UI suggests that the input is working, while in practice it does not receive any messages. The contradictory status between overview and detail page makes it difficult to understand whether the problem is with the content pack, the input state handling, or the UI reporting.

Your Environment

• Graylog Version: 7.1 alpha 3

Checklist

[] This issue fix need to be backported.
[] Does this issue have security implications?