Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

packstack: Error: yum update -y kernel iputils iproute returned 1 instead of one of [0]

I couldnt find a solution. I am using packstack on a fedora 20 machine, so this cant be an optional channel problem. The logs specify a 'unknown' repo problem. I have attached them below. Current release in icehouse as of May 16 2014

Applying 10.106.240.209_prescript.pp
10.106.240.209_prescript.pp:                      [ ERROR ]            
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 10.106.240.209_prescript.pp
Error: yum update -y kernel iputils iproute returned 1 instead of one of [0]

Log file: prescript.pp.log

Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Notice: Compiled catalog for localhost.localdomain in environment production in 0.83 seconds
Notice: /Stage[main]/Firewall::Linux::Redhat/Service[iptables]/ensure: ensure changed 'stopped' to 'running'
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: Loaded plugins: langpacks, priorities, refresh-packagekit
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:  One of the configured repositories failed (Unknown),
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:  and yum doesn't have enough cached data to continue. At this point the only
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:  safe thing yum can do is fail. There are a few ways to work "fix" this:
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:      1. Contact the upstream for the repository and get them to fix the problem.
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:      2. Reconfigure the baseurl/etc. for the repository, to point to a working
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         upstream. This is most often useful if you are using a newer
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         distribution release than is supported by the repository (and the
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         packages for the previous distribution release still work).
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:      3. Disable the repository, so yum won't use it by default. Yum will then
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         just ignore the repository until you permanently enable it again or use
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         --enablerepo for temporary usage:
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:             yum-config-manager --disable <repoid>
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:      4. Configure the failing repository to be skipped, if it is unavailable.
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         Note that yum will try to contact the repo. when it runs most commands,
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         so will have to try and fail each time (and thus. yum will be be much
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         slower). If it is a very temporary problem though, this is often a nice
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         compromise:
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: Cannot retrieve metalink for repository: fedora/20/x86_64. Please verify its path and try again
Error: yum update -y kernel iputils iproute returned 1 instead of one of [0]
Error: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: change from notrun to 0 failed: yum update -y kernel iputils iproute returned 1 instead of one of [0]
Notice: /Stage[main]/Packstack::Netns/Notify[packstack_info]: Dependency Exec[netns_dependecy_install] has failures: true
Warning: /Stage[main]/Packstack::Netns/Notify[packstack_info]: Skipping because of failed dependencies
Notice: Finished catalog run in 587.97 seconds

packstack: Error: yum update -y kernel iputils iproute returned 1 instead of one of [0]

I couldnt find a solution. I am using packstack on a fedora 20 machine, so this cant be an optional channel problem. The logs specify a 'unknown' repo problem. I have attached them below. Current release in icehouse as of May 16 20142014. Kidnly help !

Applying 10.106.240.209_prescript.pp
10.106.240.209_prescript.pp:                      [ ERROR ]            
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 10.106.240.209_prescript.pp
Error: yum update -y kernel iputils iproute returned 1 instead of one of [0]

Log file: prescript.pp.log

Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Notice: Compiled catalog for localhost.localdomain in environment production in 0.83 seconds
Notice: /Stage[main]/Firewall::Linux::Redhat/Service[iptables]/ensure: ensure changed 'stopped' to 'running'
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: Loaded plugins: langpacks, priorities, refresh-packagekit
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:  One of the configured repositories failed (Unknown),
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:  and yum doesn't have enough cached data to continue. At this point the only
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:  safe thing yum can do is fail. There are a few ways to work "fix" this:
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:      1. Contact the upstream for the repository and get them to fix the problem.
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:      2. Reconfigure the baseurl/etc. for the repository, to point to a working
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         upstream. This is most often useful if you are using a newer
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         distribution release than is supported by the repository (and the
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         packages for the previous distribution release still work).
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:      3. Disable the repository, so yum won't use it by default. Yum will then
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         just ignore the repository until you permanently enable it again or use
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         --enablerepo for temporary usage:
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:             yum-config-manager --disable <repoid>
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:      4. Configure the failing repository to be skipped, if it is unavailable.
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         Note that yum will try to contact the repo. when it runs most commands,
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         so will have to try and fail each time (and thus. yum will be be much
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         slower). If it is a very temporary problem though, this is often a nice
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:         compromise:
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns:             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: 
Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: Cannot retrieve metalink for repository: fedora/20/x86_64. Please verify its path and try again
Error: yum update -y kernel iputils iproute returned 1 instead of one of [0]
Error: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: change from notrun to 0 failed: yum update -y kernel iputils iproute returned 1 instead of one of [0]
Notice: /Stage[main]/Packstack::Netns/Notify[packstack_info]: Dependency Exec[netns_dependecy_install] has failures: true
Warning: /Stage[main]/Packstack::Netns/Notify[packstack_info]: Skipping because of failed dependencies
Notice: Finished catalog run in 587.97 seconds