RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
 journalctl should be case insensitive and couls accept *

Version-Release number of selected component (if applicable):
 systemd 204

How reproducible:
its rfe

Steps to Reproduce:
1. journalctl --unit Network*
2. journalctl --unit Networkmanager

Actual results:
journalctl accepts only strict name of the unit.
Please add some behaviour to be case insensitive
journalctl --unit NetworkManager is only one possible way

Expected results:
journalctl --unit networkmanager
journalctl --unit network*
journalctl --unit Network*


Additional info:

you know, that you have bash completion with <tab> ?

I think that <tab> here is a nice solution and names of unit files are case-sensitive, so this would lead to inconsistency. Also --unit can be specified only once and takes only one argument.

Hello,
please could you consider usage of asterisk or any grepping feature 

some usecase like:

1, you would like service network + NetworkManager:
journalctl --unit [nN]etwork*

2, grep all from log daemons, and you don't know if there is syslog / rsyslog on the system:
sudo journalctl --unit *syslog

3, you are not sure about the right name:
sudo journalctl --unit *vnc

Tab completion is the solution in Fedora for this problem.

The internal structure of the journal index does not easily allow support of wildcards.

The usability issues are better addressed with bash completion, which already works... 

_BUT_ apparently somebody decided, that RHEL-7 should _NOT_ have bash completion at all.

At the end rhel7 has bash-completion, which solves this issue quite nicely.