Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

cups_queue fails when trying to manage an ipp:// queue #28

Closed
lesinigo opened this issue Nov 21, 2017 · 3 comments
Closed

cups_queue fails when trying to manage an ipp:// queue #28

lesinigo opened this issue Nov 21, 2017 · 3 comments
Assignees
Labels

Comments

@lesinigo
Copy link

Given Ubuntu 16.04 LTS with Puppet 4.10.9 and CUPS 2.1.3-4ubuntu0.3 and leoarnold/cups v2.0.1

When I apply the manifest

include '::cups'

with this hiera data

cups::default_queue: MyPrinter
cups::web_interface: true
cups::resources:
  MyPrinter:
    ensure: printer
    uri: 'ipp://192.168.10.20/printers/MyPrinter'
    make_and_model: 'Generic PostScript Printer'

In order to configure a generic PS printer that will send everything to another cups host

Then I get the error message:

Error: Execution of '/usr/sbin/lpadmin -E -p MyPrinter -o printer-is-shared=false' returned 1: lpadmin: Cannot change printer-is-shared for remote queues.

As far as I can tell, the cups_queue resource insists on setting the printer-is-shared attribute, but it cannot be set with IPP queues.

I get the exact same behavior with shared: true and shared: false.
It seems to me that cups_queue should not try to set that parameter at all if the uri starts with ipp:// or one of its variations (ipps and so on...)

@leoarnold
Copy link
Owner

Wow, thank you for digging up the underlying CUPS issue! I'll just remove that default value.

Nevertheless, if you want to create a Generic PostScript Printer, you'll still have to add model: drv:///sample.drv/generic.ppd.

@leoarnold leoarnold self-assigned this Nov 21, 2017
@leoarnold leoarnold added the bug label Nov 21, 2017
@leoarnold
Copy link
Owner

This issue is fixed in release 2.0.2, available now in the Forge and as a GitHub release.

@lesinigo
Copy link
Author

Tested and working perfectly in the use case of this issue using release 2.0.2 from the forge.
Thank you so much for the quick response!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants