Project

General

Profile

Actions

Bug #10483

closed

Instalation problem

Added by Mateusz . about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

During installation now instance a FOREMAN on OS Centos 7.1 (1503) I have a error: (I used command: foreman-installer)
[ INFO 2015-05-12 07:27:35 verbose] /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:92:in `execute'
[ INFO 2015-05-12 07:27:35 verbose] /usr/bin/puppet:8:in `<main>'
[ INFO 2015-05-12 07:27:35 verbose] Puppet has finished, bye!
[ INFO 2015-05-12 07:27:35 verbose] Executing hooks in group post
Something went wrong! Check the log for ERROR-level output * Foreman is running at https://foreman.lcl.lp
Initial credentials are admin / uhyvK3wSeoGv3ufM * Foreman Proxy is running at https://foreman.lcl.lp:8443 * Puppetmaster is running at port 8140
The full log is at /var/log/foreman-installer/foreman-installer.log
[ INFO 2015-05-12 07:27:35 verbose] All hooks in group post finished
[ERROR 2015-05-12 07:27:35 verbose] Repeating errors encountered during run:
[ERROR 2015-05-12 07:27:35 verbose] Class['apache::version']: Unparsable $::operatingsystemrelease: at /usr/share/foreman-installer/modules/apache/manifests/version.pp:10 on node foreman.lcl.lp
[ERROR 2015-05-12 07:27:35 verbose] Class['apache::version']: Unparsable $::operatingsystemrelease: at /usr/share/foreman-installer/modules/apache/manifests/version.pp:10 on node foreman.lcl.lp

[root@foreman ~]#


Files

facter --json.txt facter --json.txt 4.51 KB Mateusz ., 05/12/2015 10:36 AM
Actions #1

Updated by Dominic Cleal about 9 years ago

  • Status changed from New to Need more information

Could you attach the output of "facter --json" please?

Actions #2

Updated by Mateusz . about 9 years ago

No problem. In attach to this post I added a file with output this command.

Actions #3

Updated by Dominic Cleal about 9 years ago

Something's wrong between the OS release info and Facter being able to read it - perhaps Facter needs updating, or you're hitting this bug with the initial CentOS 7.1 release: http://lists.centos.org/pipermail/centos-announce/2015-April/021010.html

I'd suggest a "yum upgrade centos-release" as your first point of call in case you hit that bug, and if that still doesn't work, upgrade Facter.

The issue is that "operatingsystemrelease" isn't in the Facter output.

Actions #4

Updated by Mateusz . about 9 years ago

Problem solved.
This bug was root cause in this case.
Thanks for help.

Actions #5

Updated by Dominic Cleal about 9 years ago

  • Status changed from Need more information to Resolved

Thanks for confirming!

Actions

Also available in: Atom PDF