Bug 24222 - puppet client commands does not run
Summary: puppet client commands does not run
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-22 13:31 CET by eric gerbier
Modified: 2019-01-27 11:23 CET (History)
9 users (show)

See Also:
Source RPM: puppet-6.0.3-1.mga7
CVE:
Status comment:


Attachments

Description eric gerbier 2019-01-22 13:31:30 CET
Description of problem:

on client side, all puppet commands (as 'puppet agent -t' ) died with the following error :

cannot load such file -- semantic_puppet


Version-Release number of selected component (if applicable):
6.0.3-1

How reproducible:


Steps to Reproduce:
1. urpmi puppet
2. puppet agent -t
3.


the puppet documentation tells ( https://puppet.com/docs/puppet/4.9/release_notes.html ) :

PUP-4742: A dependency is added on the semantic_puppet gem >= 0.1.3’, ‘< 2’ because this is required for issues with semantic version comparison functions and types.

so I just install  it with :
gem install semantic_puppet

and now the puppet commands are working

so it seems to be a dependency missing in puppet rpm
Comment 1 Marja Van Waes 2019-01-22 15:40:08 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package.

Also CC'ing a bunch of committers.

CC: (none) => bruno, geiger.david68210, guillomovitch, luigiwalser, mageia, marja11, pterjan, tmb
Assignee: bugsquad => pkg-bugs

Comment 2 eric gerbier 2019-01-24 13:17:59 CET
Any puppet command is failing. A better test is the simple command :
puppet help
Comment 3 Dave Hodgins 2019-01-25 01:49:37 CET
In addition to the ruby semantic_puppet package missing from cauldron, the
puppet package is missing a requires for ruby, which was present in the Mageia 6
version.

CC: (none) => davidwhodgins

Comment 4 Guillaume Rousse 2019-01-27 11:23:18 CET
Both issues fixed in 6.0.3-2.mga7.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.