New in Foreman Community Demo: BYOP (Bring Your Own Problem) Pilot

[nofaralfasi]

We’re piloting a new segment in upcoming Foreman community demos: BYOP - Bring Your Own Problem.

What is BYOP?

A short live troubleshooting section where one community member shares their environment and a real issue they’re facing.

Format

• 10–15 minutes max
• 1 participant per demo
• Goal: clarify root cause and define next steps (not always full resolution in-session)

Good candidates

• Issues others may also face
• Reproducible setup or clear symptoms
• You can share relevant versions/logs/screenshots safely

Who can present a BYOP case

Anyone running Foreman in a real environment and willing to share:

• setup/context (sanitized)
• symptoms
• what was already tried

How to apply

Reply in this thread (or DM) with:

1. Foreman version + deployment context
2. Short issue description
3. Reproduction steps (if available)
4. Logs/screenshots (sanitized)
5. What outcome you want from the session

[ananace]

Since we were somewhat guilty about this even being a thing…

Foreman version + deployment context:

• Foreman: 3.19.0
• foreman_discovery: 26.1.3

Short issue description:

Foreman Discovery does not even attempt to map subnets for interfaces other then the primary.

Reproduction steps (if available):

• Discover a host with more then one active interface. E.g. a main interface and a BMC interface.

Logs/screenshots (sanitized):

What outcome you want from the session:

Validation of problem statement.