Firewall->Shaper->Rules not showing all pipes and queues in Target selection dropdown when creating new Rule

[denverpilot]

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

• [X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
• [X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug

Only attempted on 24.1.8 (so far)... In Firewall->Shaper->Rules... Rule creation doesn't show all Pipes and Queues that have been created and applied as options for Target.

What I see as the only option is the first Pipe added ONLY, the second Pipe and two Queues are not in the dropdown.

To Reproduce

Simplest way: Set up identical to the screenshots in this tutorial, once at "Rules" the only option available to add to Target will be the Download Pipe. The Upload Pipe, nor the Download or Upload Queues, will be available as selections.

https://maltechx.de/en/2021/03/opnsense-setup-traffic-shaping-and-reduce-bufferbloat/

Expected behavior

Should be able to see and select all Pipes and Queues as Targets in selection dropdown.

Describe alternatives you considered

Attempted a few things like altering the names of pipes and queues to "simple" names in case it's a parsing bug somewhere. Happy to provide any other details needed.

Screenshots

Can add if unclear. Setup is identical to the above tutorial other than different speeds on Pipes.

Relevant log files

N/A

Additional context

N/A

Environment

OpnSense 24.1.8 (amd64)

[denverpilot]

Hmm... apologies... more playing with this, it APPEARS that capital letters in Pipe and Queue names may have been the issue...? Quite odd...

Renaming everything in the example given to things like "up pipe" and "down pipe" and such, SEEMS to have allowed all options to show up in the Target dropdown.

I will play more tomorrow and see if I can reproduce.

[OPNsense-bot]

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.