Hi all,
I need to install about 60 perl rpm packages and there is one particular module that fell through the crack for yum module.
On the 20 nodes that I applied this module, all of them still do not have this perl-Parse-CPAN-meta rpm packaged installed.
Here is one such node:
[root@m-dev-bst-hadoop01 ~]# yum search all perl-Parse-CPAN-meta
Loaded plugins: security
============ Matched: perl-Parse-CPAN-meta =============
perl-Parse-CPAN-Meta.x86_64 : Parse META.yml and other
Please ignore the Meta/meta. I checked and this problem still holds.
[root@m-dev-bst-hadoop07 ~]# yum search perl-Parse-CPAN-Meta
Loaded plugins: security
====================== N/S Matched: perl-Parse-CPAN-Meta =======================
perl-Parse-CPAN-Meta.x86_64 : Parse META.yml and other similar CPAN metadata
: files
Name and summary matches only, use “search all” for everything.
[root@m-dev-bst-hadoop07 ~]# rpm -q perl-Parse-CPAN-Meta
package perl-Parse-CPAN-Meta is not installed
Thank you.
What happens when you yum install it manually on that box?
Also, you abbreviated the playbook output, could you run it in verbose mode and include the output, perhaps using gist or pastebin?
Hi Micheal,
It is great to speak to you again. I hope that your company is doing great. Wish you the best of lucks.
Here is the node that I tried to install but failed. I installed this perl rpm manually and it went well.
[root@m-dev-bst-hadoop07 ~]# yum install perl-Parse-CPAN-Meta
Loaded plugins: security
Setting up Install Process
Resolving Dependencies
→ Running transaction check
—> Package perl-Parse-CPAN-Meta.x86_64 1:1.40-131.el6_4 will be installed
→ Finished Dependency Resolution
Dependencies Resolved
So you said it was on a different box, could it be because the box is using a different yum repository or perhaps the mirror is missing the package?
Hi Michael,
This is in private network where we have one repository. All machines do not have direct connection to the Internet to fetch packages from EPEL or similar.
This happened only within ansible-playbook run and I could install the rpm package just fine from the CLI. This has happened to 20 nodes that do have the same private repository. I just did the same to another set of th
All of this appears to be more than just a coincident to me. I am not sure what is the error.
I tried to install this with task using yum module with just “name=perl-Parse-CPAN-Meta state=latest” on another 30 nodes and here is one output.
ok: [m-prd-bst-hadoop25] => {“changed”: false, “item”: “”, “msg”: “”, “rc”: 0, “results”: [“All packages providing perl-Parse-CPAN-Meta are up to date”]}
[root@m-prd-bst-hadoop25 ~]# rpm -q perl-Parse-CPAN-Meta
package perl-Parse-CPAN-Meta is not installed
[root@m-prd-bst-hadoop25 ~]# yum install perl-Parse-CPAN-Meta
Loaded plugins: security
Setting up Install Process
Resolving Dependencies
→ Running transaction check
—> Package perl-Parse-CPAN-Meta.x86_64 1:1.40-131.el6_4 will be installed
→ Finished Dependency Resolution
Dependencies Resolved
This seems very odd. A couple of possibilities occur:
-
Corrupted rpmdb and inconsistent yum metadata. Try ‘yum clean all; rpmdb --rebuild’.
-
Some other package other than perl-Parse-CPAN-Meta is ‘providing’ perl-Parse-CPAN-Meta – perhaps a local custom meta package.
-
Inventory host/group names (or even .ssh/config Host lines) are screwed up and ansible is not talking to the host you think you are (okay, this ones a little crazy).
K
Hi Kahlil,
"rpm -q --provides perl " shows that perl rpm provides perl-Parse-CPAN-Meta.
Thanks.
Steven.