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

Installation fails if you decide to install erlang from sources #224

Closed
ecorderob opened this issue Feb 17, 2015 · 7 comments
Closed

Installation fails if you decide to install erlang from sources #224

ecorderob opened this issue Feb 17, 2015 · 7 comments

Comments

@ecorderob
Copy link

Hi,

When I try to install the default erlang packages in my AWS instance (prior to install rabbitmq), the release that is downloaded is 14.04, which is quite old. To be able to work with the latest one, I need to install erlang from sources passing a couple of parameters to the cookbook

default['erlang']['install_method'] = 'source'
default['erlang']['source']['version'] = '17.4'
default['erlang']['source']['url'] = 'url'
default['erlang']['source']['checksum'] = 'xxxxx'

The problem that I face is that when rabbitmq tries to install itself (from RPM) it fails to do it because of the erlang dependencies (does not find the erlang rpm installed).

It would be nice if you could include an option to pass "--nopeds" to the RPM rabbitmq installation so that it would not fail at this point.

@cmluciano
Copy link

I think this is maybe a problem more with the upstream cookbook for erlang. It looks to be hardcoded (as you said with) R15B01. I'm wondering if that cookbook attribute should just be bumped.

Another option is to add an attribute to our cookbook that overrides whatever Erlang version that you want to install. @jjasghar What do you think?

Would activating the ESL attribute do the trick?

@jjasghar
Copy link
Contributor

So I merged this https://github.com/jjasghar/rabbitmq/pull/214/files and if you see it does that ESL trick right? But that's for CentOS 7 specifically.

I haven't tested this on AWS, is it specific to an amazon release? Offically we don't have AWS as part of the kitchen.yml.

@cmluciano
Copy link

That's true, AFAIK AWS uses a RHEL derivative so the repos might be different, yet it should still be able to pull from the "erlang solutions" repo.

@ecorderob Can you give more background on the OS and version that you are using? Potentially cat /etc/redhat_release

@ecorderob
Copy link
Author

Hi @cmluciano I am using the latest Amazon Linux 2014.09. No /etc/redhat_release in that OS.

@jjasghar
Copy link
Contributor

Ah so we've pulled support for Amazon Linux. Right now we only support what we have in the .kitchen.cloud.yml or the .kitchen.yml. If you would like support for Amazon Linux I'm all ears but i'll need you to spear head and take ownership of it.

@cmluciano
Copy link

@ecorderob I added a commit to the upstream erlang cookbook to always include yum-epel and yum-erlang-solutions to RHEL based OSes. Watch for the latest release of the erlang cookbook and see if that works for you. I will try to bring this up in the Chef Office Hours today.

@cmluciano
Copy link

My PR has been merged sous-chefs/erlang#25

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

3 participants