Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Since CUPS 3.0 - the first version without classic driver support - is planned for the autumn/winter in 2022, RHEL 9 will be the last RHEL with drivers and we need to notify customers as many ways as possible.

Together with dkuklinek we urged RHEL Insights rule for gathering and then notifying customers, but only fraction of customers uses Insights, so it would be great if something similar is generated in CUPS as well.

lpadmin command already spawns a warning when an user creates non-ipp-everywhere queue, but we need to cover the following:

1) creating queues via web ui - relevant upstream commits:
https://github.com/OpenPrinting/cups/pull/244
https://github.com/OpenPrinting/cups/pull/242
https://github.com/OpenPrinting/cups/pull/218

2) copying old printers.conf as 'installation' of queues or migration from older RHELs, so no new queues are created, so no warning is spawn - needs to be implemented upstream

Commits implementing warnings during startup:

https://github.com/OpenPrinting/cups/commit/9b19d8b26c740ca1cc1a7c30095fc7cd484760d3
https://github.com/OpenPrinting/cups/commit/2857cd8c5229ec776e47e79fd21d10a573759dcb

I will backport them soon.

Added one more fix from upstream (to don't generate the warning for driverless driver generator via lpadmin):

https://github.com/OpenPrinting/cups/commit/ecd1cc58a5da7d9ea539b6b673b89c3dfb474586

Prepared on private-zdohnal-c9s branch till acks are gathered. The verification will be done manually because it doesn't make sense writing a test for checking warnings.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: cups), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3970