Hide Forgot
Description of problem: If you have iptables-0:1.4.21-14.el7.x86_64 installed then try to install 'iptables-services' you will encounter depsolving issues. Version-Release number of selected component (if applicable): How reproducible: 100% I believe Steps to Reproduce: 1. yum install iptables-0:1.4.21-14 2. yum install iptables-services 3. Actual results: "Loaded plugins: amazon-id, rhui-lb, search-disabled-repos Resolving Dependencies --> Running transaction check ---> Package iptables-services.x86_64 0:1.4.21-16.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================Package Arch Version Repository Size ================================================================================ Installing: iptables-services x86_64 1.4.21-16.el7 rhel-72 50 k Transaction Summary ================================================================================ Install 1 Package Total download size: 50 k Installed size: 24 k Downloading packages: Running transaction check ERROR with transaction check vs depsolve: iptables = 1.4.21-16.el7 is needed by iptables-services-1.4.21-16.el7.x86_64 You could try running: rpm -Va --nofiles --nodigest Your transaction was saved, rerun it with: yum load-transaction /tmp/yum_save_tx.2016-04-05.15-50.02Wuyy.yumtx Expected results: iptables-services installs Additional info: iptables-1.4.21-16 is available in the repository. # repoquery iptables iptables-services iptables-0:1.4.21-16.el7.i686 iptables-0:1.4.21-16.el7.x86_64 iptables-services-0:1.4.21-16.el7.x86_64
According to the repoquery in your own comment, there is no iptables-1.4.21-14 package in the repository, but there is iptables-1.4.21-16.el7. It seems that you have some special rules in your yum configuration not to use the iptables package form the RHEL repository, which seems to be the source of the issue.
The issue seems to be te non-standard image used originally. Sorry about that. The official RH image works for me. Issue can be closed I think.
*** Bug 1389722 has been marked as a duplicate of this bug. ***