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
Not working with CentOS VMs? #17
Comments
Contents of the zip file, from a CentOS 6.6 VM, no
|
Looking at the source code and
It shouldn't download The full URL would be http://rdfepirv2db3prdstr02.blob.core.windows.net/0fa68ca509a643f49117169ef78baf70/Chef.Bootstrap.WindowsAzure_CentosChefClient_europenorth_manifest.xml. |
@trydis azure-chef-extension is not supported for CentOS on azure portal right now. |
Any time frame on when it will be supported? Looks like most (all?) of the code is already in the scripts. Not a big deal, since I can use knife to bootstrap the nodes, just curious 😄 |
No plans to support CentOS as of now. But we'll consider this in future. |
We do need to address this as soon as the Azure portal can handle two different Linux distros. |
The |
@adamedx, can you please add the RPM file to the zip file http://rdfepirv2am2prdstr02.blob.core.windows.net/0fa68ca509a643f49117169ef78baf70/Chef.Bootstrap.WindowsAzure__LinuxChefClient__11.18.6.1 Thank you! |
Hi , I'm Vittorio from Azure support - we are currently discussing this with the respective Microsoft and Chef development teams |
We have started work on this issue. Instead of keeping installers for both |
@tmaierACN as @NimishaS states, this is being worked on. For transparency, the key problem here is mismatch in UX assumptions in Azure Resource manager which assumes that one extension works on all Linux distributions vs. the extension which was originally intended to be published for each distribution. The initial fix will use Chef's public (Internet-based) yum repos to avoid the need to package binaries. We are finalizing a plan to use yum repos internal to Azure to retain the Ubuntu case's performance, reliability, and security benefits of requiring no Internet access to the guest VM. Here is a much longer explanation of the situation: The original motivation for one extension per distro was that the while the extension's code contains installation code that should work an multiple Linux distributions, it also contains chef-client binaries.
Now that we have the yum repository, we can move forward with adding CentOS support without including CentOS binaries and adhere to the design requirement for a generic Linux extension. |
Cool. Thank you for this detailed update, @adamedx. |
So how can I install Chef on Centos using 'CentosChefClient extension' or 'LinuxChefClient extension'? |
@hough01, due to this bug, there isn't a way to do this using the Azure resource manager commands, but we hope to have a fix soon. However, if you have a workstation (Linux or Windows) where you've installed Chef-DK, you can |
|
I've tried creating both CentOS 6.6 and 7.0 VMs through the preview portal and the bootstrapping process fails.
CommandExecution.log
Manually running install.sh
The installer directory only contains
chef-client-latest.deb
.The text was updated successfully, but these errors were encountered: