Bug 683715 indicates that puppet can no longer install DMG files. This most likely has to do with mach contexts, where access to the console context is required to mount .dmg's.
This is not a problem in automation and can be worked around by launching puppet from a Terminal over Screensharing/VNC.
Assignee: jhford → nobody
Priority: -- → P4
On every startup? That seems like a lot of work, but OK.
why don't we use the launchd method to set the proper context? It doesn't make any sense at all to have puppet, which is to be used to automate package installation *without* human interaction, now have a requirement of being launched from a VNC session? Or am I missing something?
Assignee: nobody → jhford
Priority: P4 → P2
we need to talk about this with the other puppet folks on the team, something doesn't feel right (or i'm misunderstanding it)
This doesn't smell right to me either. How was puppet being launched in the bug you reference? We know that OSX security contexts don't play nicely with ssh (e.g. starting buildbot from ssh will result in dns lookup failures), so if puppet is invoked via ssh I wouldn't be surprised if we had problems.
The only time this is an issue is when all of the following conditions are met: 1) puppet is manually launched over ssh 2) puppet needs to install a package from a dmg file This does not affect our automated puppet runs that launch on boot in any way. They start in the correct context and run through to completion, installing pkg+dmg files without issue. The only useful case affected by this issue is the initial sync of a machine to a puppet master. We don't hit this case very frequently. When we need to do an initial sync of puppet, the workaround is to launch puppet manually over screensharing instead of manually over ssh. This has been the case since day one of using pkgdmg as the package provider on OS X. This is not a new defect, it is a corner case that we rarely hit. This issues was mentioned in the other bug solely to alert anyone working on the project of the Screensharing/VNC requirement for initial puppet sync. Because we are going to take a snapshot of the machine post-puppet, this issue is cleanup work. I am prioritizing the bug appropriately, and am removing myself as I don't have time to look into this right now.
Assignee: jhford → nobody
Priority: P2 → P4
Whiteboard: [puppet] → [puppet][cleanup]
Product: mozilla.org → Release Engineering
5 years ago
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.