Error During Deployment
Closed this issue · 12 comments
I am trying to deploy this module, it looks absolutely awesome, but I've hit a snag and I'm not sure what else I can do to troubleshoot.
Please see my current PP file here: https://goput.it/ykq.txt
And the output from my client here: https://goput.it/dyp.txt
Any suggestions you would have would be greatly appreciated.
Cheers
Kirk
Hey there,
I have a machine here which is having the exact same issue. I will take a look at it later today, I think it's an actual bug where the lpadmin options don't get parsed correctly. Is this on OSX Lion by any chance?
No, it's Ubuntu 10.04.4 LTS.
I would be happy to help you with the debugging process if you would like to work with me on finding out what's going wrong (provide a module with more verbose debug output, or something along those lines).
Is there any ETA on this fix? I would really like to implement this ASAP, or else I'll have to resort to syncing CUPS configuration files again.
I'm in the process of converting the functionality of the new server toward modular functionality on a new Puppet server and we're making that migration now with 30 new laptops. I'd like to do everything right this time around, but if doing it wrong is what it takes then it has to get done...
Thanks.
Kirk
I'll get an Ubuntu 10.0.4.4 LTS VM running today and see what I can get out of it. One of the puppet guys had said they fixed a bug but I haven't got any code for it yet.
See ody's code over here, he did a branch with all of the fixes, but i need to bug him about a pull request on that branch:
Thank you, I appreciate your willingness to look into this promptly for me. I will have a look at the link you posted and see if his branch fixes the problem I'm having.
Please let me know if you have any further updates on the bug with your branch.
Thanks,
Kirk
ody has contacted me and it might be a few days until the changes are submitted to me.
Any update as to the status of this fix?
I just got back to this. Ody seems to be busy on some other modules.
I've taken your .pp file and put it into my testing manifest, applied it to Ubuntu 10.0.4.4 LTS VM, and all of the printers are created ok, which doesnt help me reproduce the problem of course.
lt looks a bit like lpadmin tries to add the printer, and then via lpstat we try to get the result of that change, but the printer doesn't exist (lpadmin failed for some reason). I'll try to replicate the problem here.
Interesting... Fortunately I have found an alternative way to get this done. I am now syncing a client.conf to my computers which tells the computers to connect to the CUPS server. Now instead of managing printers on the computer, I have a central CUPS server which all the computers use. It provides the end result I wanted - of centrally managed printers - but a little less flexibility perhaps in customizing printers on the clients. I still think your module is worth looking into, but for now my urgency is diminished. I was not aware that CUPS could do that when I set out.
Cheers
Kirk
On May 23, 2012, at 9:19 PM, "mosen" reply@reply.github.com wrote:
I just got back to this. Ody seems to be busy on some other modules.
I've taken your .pp file and put it into my testing manifest, applied it to Ubuntu 10.0.4.4 LTS VM, and all of the printers are created ok, which doesnt help me reproduce the problem of course.
lt looks a bit like lpadmin tries to add the printer, and then via lpstat we try to get the result of that change, but the printer doesn't exist (lpadmin failed for some reason). I'll try to replicate the problem here.
Reply to this email directly or view it on GitHub:
#2 (comment)
Sorry I couldn't have it fixed in time, but the module will keep improving over time no doubt!