-
Notifications
You must be signed in to change notification settings - Fork 25
Vagrant provisioning fails with unsupported version of mysql #36
Comments
Hi, thanks for the issue. Can you try to set node[alfresco][mysql_version] = '5.5' If that works we can use that default if platform is Ubuntu 12 |
Yup. I edited
That fixes the install for mysql. But now the provisioning fails with problems installing tomcat:
|
You can override additional_tomcat_packages defined in https://github.com/maoo/chef-alfresco/blob/master/attributes/tomcat.rb My apologies for these regressions on master, I'm working on centos now. You can still use tag 0.4.2 though. Thanks a lot for the valuable feedback! |
I've tried several variations for
The first four all fail with something along the lines of "No version specified, and no candidate version available for ...". The last fails with:
I'll do a clean checkout and try using the centos64 box for vagrant. |
No luck using the centos64 box profile either:
Fails with:
|
I'll try to reproduce the issue as soon as chef-alfresco is stable (still implementing haproxy configurations). In the meantime, consider adding tag: "chef-alfresco-0.4.2" to chef-alfresco on https://github.com/maoo/alfresco-boxes/blob/master/common/Berksfile If you rather want to checkout the latest developments on chef-alfresco, I'd advise to check it out and use Kitchen to run locally. |
Thanks @maoo. I don't have any experience using Kitchen. I'll have a go at pinning chef-alfresco to that tag. |
Hi, I'm also getting an issue about my_sql with the latest version of vagrant file: |
Can you please test on the master now? Never faced this issue anymore, since the last chef-alfresco releases (0.6.x) |
Steps to reproduce:
Then fails with:
The text was updated successfully, but these errors were encountered: