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
chef plugin does not work properly #2202
Comments
Launchpad user Mike Moulton(mmoulton) wrote on 2011-09-08T21:29:18.605019+00:00 Launchpad attachments: A patch for cc_chef.py |
Launchpad user Mike Moulton(mmoulton) wrote on 2011-09-08T21:30:21.340921+00:00 Launchpad attachments: Test user-data. You will need to fill out the org specific areas for your chef server instance. |
Launchpad user Avishai Ish-Shalom(avishai-ish-shalom) wrote on 2011-09-08T22:35:00.272923+00:00 398 fixed runlist format in the initial json file. The attached patch is unusable, perhaps our versions differ. did you test the version from my branch? |
Launchpad user Scott Moser(smoser) wrote on 2011-09-08T22:35:18.796041+00:00 Could you please quickly test the deb attached? |
Launchpad user Scott Moser(smoser) wrote on 2011-09-08T22:35:41.492047+00:00 Launchpad attachments: trunk build of revno 442 |
Launchpad user Avishai Ish-Shalom(avishai-ish-shalom) wrote on 2011-09-08T22:41:20.206167+00:00 Merged main branch into my branch, the patch was already applied there. Fixed another minor issue with multiple runlist items not being written in the correct format. |
Launchpad user Scott Moser(smoser) wrote on 2011-09-08T23:11:43+00:00 On Thu, 8 Sep 2011, avishai wrote:
Please test trunk at revision 443, and report in bug. Thank you. |
Launchpad user Mike Moulton(mmoulton) wrote on 2011-09-11T07:50:47.274907+00:00 I have introduces a merge request found at: https://code.launchpad.net/~mmoulton/cloud-init/chef/+merge/74900 This merge request fully supports the Chef plugin within the Beta 1 of Oneiric for both the 'gems' and 'packages' install types. |
Launchpad user Scott Moser(smoser) wrote on 2011-09-12T12:54:09.863524+00:00 I want 11.04 chef support to work, and ideally to be sane such that its configuration will be the same as we ship for 12.04. However, We're well past Feature Freeze in Ubuntu for 11.10. I'm OK to pull changes into cloud-init trunk, which will then be brought in early to 12.04. The 'environment' and 'node_name' changes in addition to the general re-formating don't really qualify as bug fixes. I've believe the chef plugin should now be functional for what it was originally proposed in the archive with version 0.6.1-0ubuntu17 . If that is not the case, please open a bug describing what is wrong, and a merge proposal to fix those things. |
Launchpad user Scott Moser(smoser) wrote on 2011-09-12T13:03:05.892093+00:00 To be clear, the window is shrinking quickly, so lets please focus on getting a functional chef right now., if we don't have one. |
Launchpad user Avishai Ish-Shalom(avishai-ish-shalom) wrote on 2011-09-12T13:30:28.503882+00:00 This "feature" is critical for proper chef support. When I initially wrote the plugin chef was at branch 0.9.x which did not require environments to be defined. Current and future chef versions (0.10.x) do require that. I'm tracking this under https://bugs.launchpad.net/cloud-init/+bug/798844 |
Launchpad user Avishai Ish-Shalom(avishai-ish-shalom) wrote on 2011-09-12T13:32:14.899533+00:00 sorry, tracking under https://bugs.launchpad.net/cloud-init/+bug/845208 |
This bug was originally filed in Launchpad as LP: #845161
Launchpad details
Launchpad user Mike Moulton(mmoulton) wrote on 2011-09-08T21:29:18.605019+00:00
The chef plugin developed by 'avishai' located in the branch 'lp:~avishai-ish-shalom/cloud-init/chef' has some issues as it stands in the Beta 1 release of oneiric.
Per the discussion here: https://code.launchpad.net/~avishai-ish-shalom/cloud-init/chef/+merge/66528 I have produced a patch to the head of the branch that resolves some syntactical issues. This patch applied to the 'lp:~avishai-ish-shalom/cloud-init/chef' branch produces a working version of the chef plugin.
The text was updated successfully, but these errors were encountered: