Cups Adding Safe6 using lpadmin -m everywhere fials with error

Originator:michalm.mac
Number:rdar://49603429 Date Originated:4.4.2019
Status:Open Resolved:
Product:macOS + SDK Product Version:10.14.4
Classification:Serious bug Reproducible:Always
 
Area:
Printing & Faxing

Summary:
We have a SafeQ v6 print server.
We are trying to mass deploy it as a "printer" to our Macs fleet so they can user Secure AirPrint.

Steps to Reproduce:
1. Open Terminal
2. Add Printer with lpadmin -p "SafeQ_Print" -L 'SomeLocation' -D 'SomeName -v 'dnssd://safeqprinter._ipps._tcp.local./?uuid=db0def0a-40e1-11e5-a151-feff819cdc9f' -E -m everywhere
(we alse set some -o options but it does not effect the outcome)

Expected Results:
Printer is added. This is the case with macOS 10.13.6 High Sierra with cups 2.2.5

Actual Results:
Command fails on 10.14 Mojave with cups 2.2.9 with 
lpadmin: Unable to create PPD file: No such file or directory

Version/Build:
10.14.4/18E226

Logs:

cupsctl --debug-logging -> /var/log/cups/error_log
D [04/Apr/2019:13:02:30 +0200] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
D [04/Apr/2019:13:02:36 +0200] cupsdSetBusyState: newbusy="Active clients", busy="Not busy"
D [04/Apr/2019:13:02:36 +0200] [Client 8] Server address is "/private/var/run/cupsd".
D [04/Apr/2019:13:02:36 +0200] [Client 8] Accepted from localhost (Domain)
D [04/Apr/2019:13:02:36 +0200] [Client 8] Waiting for request.
D [04/Apr/2019:13:02:36 +0200] [Client 8] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [04/Apr/2019:13:02:36 +0200] [Client 8] Closing connection.
D [04/Apr/2019:13:02:36 +0200] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"

Sysdiagnose is from 10.14.4 VM (not updated my MacBook because Google auth bug). Problem was observerd on MacBooks with 10.14.0 and 10.14.3

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!