Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pallet can't use instances for which it can't detect the packager #275

Open
thearthur opened this issue Aug 20, 2013 · 2 comments
Open

Pallet can't use instances for which it can't detect the packager #275

thearthur opened this issue Aug 20, 2013 · 2 comments

Comments

@thearthur
Copy link
Contributor

neither (group-spec .... :packager :aptitude) nor (node-spec .... :packager :apt) seem to have any effect on specifying the packager to use for a node.

We have many instances for which pallet does not detect the packager, which we can't use with the latest version of pallet which now ignores setting the packager explicitly.

the workaround for this is to hack the default packager to be :apt

(alter-var-root (var pallet.compute/packager-map) assoc {:os :unrecognized} :apt)

@hugoduncan
Copy link
Member

Pallet should now be dynamically determining the packager. It runs an internal :pallet/os phase to achieve this. Is the phase not getting run, or is it failing to detect the os correctly?

@thearthur
Copy link
Contributor Author

I don't yet know if it is failing because it is not running or it runs and fails?

This bug it about the inability to override it's decision. If overriding it is not allowed then the :packager key should be removed from group-spec. If it is allowed then it would be nice if the :packager key was used instead of the calculated result.

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

No branches or pull requests

2 participants