Ohai!
I tried to deploy magento [
https://supermarket.getchef.com/cookbooks/magento] on aws Linux template getting following error.
Recipe: magento::default
* user[magento] action create
- create user user[magento]
Recipe: php-fpm::repository
* yum_repository[remi] action addRecipe: <Dynamically Defined Resource>
* template[/etc/yum.repos.d/remi.repo] action create
- create new file /etc/yum.repos.d/remi.repo
- update content in file /etc/yum.repos.d/remi.repo from none to 455d89
--- /etc/yum.repos.d/remi.repo 2014-07-11 07:20:49.943908715 +0000
+++ /tmp/chef-rendered-template20140711-7615-181biix 2014-07-11 07:20:49.947908716 +0000
@@ -1 +1,12 @@
+# This file was generated by Chef
+# Do NOT modify this file by hand.
+
+[remi]
+name=Remi
+baseurl=
http://rpms.famillecollet.com/enterprise/$releasever/remi/$basearch/
+enabled=1
+gpgcheck=1
+gpgkey=
http://rpms.famillecollet.com/RPM-GPG-KEY-remi +mirrorlist=
http://rpms.famillecollet.com/enterprise/$releasever/remi/mirror
+sslverify=1
- change mode from '' to '0644'
* execute[yum-makecache-remi] action run
================================================================================
Error executing action `run` on resource 'execute[yum-makecache-remi]'
================================================================================
Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of yum -q makecache --disablerepo=* --enablerepo=remi ----
STDOUT: Could not retrieve mirrorlist
http://rpms.famillecollet.com/enterprise/2014.03/remi/mirror error was
14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
STDERR:
http://rpms.famillecollet.com/enterprise/2014.03/remi/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
One of the configured repositories failed (Remi),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable remi
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=remi.skip_if_unavailable=true
failure: repodata/repomd.xml from remi: [Errno 256] No more mirrors to try.
---- End output of yum -q makecache --disablerepo=* --enablerepo=remi ----
Ran yum -q makecache --disablerepo=* --enablerepo=remi returned 1
Resource Declaration:
---------------------
# In /var/chef/cookbooks/yum/providers/repository.rb
53: execute "yum-makecache-#{new_resource.repositoryid}" do
54: command "yum -q makecache --disablerepo=* --enablerepo=#{new_resource.repositoryid}"
55: action :nothing
56: end
57:
Compiled Resource:
------------------
# Declared in /var/chef/cookbooks/yum/providers/repository.rb:53:in `block in class_from_file'
execute("yum-makecache-remi") do
action [:nothing]
retries 0
retry_delay 2
guard_interpreter :default
command "yum -q makecache --disablerepo=* --enablerepo=remi"
backup 5
returns 0
cookbook_name :"php-fpm"
end
================================================================================
Error executing action `add` on resource 'yum_repository[remi]'