Bug #12332

[OPS] puppet messages on ci.curoverse.com about gem issues

Added by Javier Bértoli over 3 years ago. Updated over 3 years ago.

Status:
Duplicate
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
09/26/2017
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

When running puppet on ci.curoverse.com, it throws a lot of notices like

...
Ignoring RedCloth-4.2.9 because its extensions are not built.  Try: gem pristine RedCloth --version 4.2.9
Ignoring byebug-3.5.1 because its extensions are not built.  Try: gem pristine byebug --version 3.5.1
Ignoring curb-0.8.8 because its extensions are not built.  Try: gem pristine curb --version 0.8.8
Ignoring executable-hooks-1.3.2 because its extensions are not built.  Try: gem pristine executable-hooks --version 1.3.2
Ignoring fast_stack-0.1.0 because its extensions are not built.  Try: gem pristine fast_stack --version 0.1.0
Ignoring ffi-1.9.10 because its extensions are not built.  Try: gem pristine ffi --version 1.9.10
Ignoring ffi-1.9.6 because its extensions are not built.  Try: gem pristine ffi --version 1.9.6
Ignoring ffi-1.9.3 because its extensions are not built.  Try: gem pristine ffi --version 1.9.3
Ignoring gem-wrappers-1.2.7 because its extensions are not built.  Try: gem pristine gem-wrappers --version 1.2.7
Ignoring json-1.8.2 because its extensions are not built.  Try: gem pristine json --version 1.8.2
Ignoring nokogiri-1.6.6.4 because its extensions are not built.  Try: gem pristine nokogiri --version 1.6.6.4
Ignoring nokogiri-1.6.5 because its extensions are not built.  Try: gem pristine nokogiri --version 1.6.5
Ignoring nokogiri-1.6.4.1 because its extensions are not built.  Try: gem pristine nokogiri --version 1.6.4.1
Ignoring nokogiri-1.6.1 because its extensions are not built.  Try: gem pristine nokogiri --version 1.6.1
Ignoring oj-2.11.2 because its extensions are not built.  Try: gem pristine oj --version 2.11.2
Ignoring oj-2.11.1 because its extensions are not built.  Try: gem pristine oj --version 2.11.1
...

Although it runs and finishes OK. Maybe some issue with RVM? Or some broken gems dir after ruby upgrade?

History

#1 Updated by Javier Bértoli over 3 years ago

  • Status changed from New to Duplicate
  • Assigned To set to Javier Bértoli
  • Target version changed from Kanban to 2017-09-27 Sprint

It all seems to be the same issue as #12217. Closing this one.

Also available in: Atom PDF