Problem:
After install , i am unable to login
Expected outcome:
Foreman is running at https://ip-10-103-137-91.aws.a.b.c
Foreman and Proxy versions:
Latest
Foreman and Proxy plugin versions:
Other relevant data:
after i ran: #foreman-installer -v
i get:
[ERROR 2018-04-08 06:46:57 verbose] Could not find a suitable provider for foreman_config_entry
[ERROR 2018-04-08 06:46:57 verbose] Could not find a suitable provider for foreman_smartproxy
[ WARN 2018-04-08 06:46:57 verbose] Applied catalog in 304.06 seconds
[ INFO 2018-04-08 06:46:59 verbose] Puppet has finished, bye!
[ INFO 2018-04-08 06:46:59 verbose] Executing hooks in group post
Something went wrong! Check the log for ERROR-level output
* Foreman is running at https://ip-10-103-137-91.aws.a.b.c
Initial credentials are admin / <password>
* Foreman Proxy is running at https://ip-10-103-137-91.aws.a.b.c:8443
* Puppetmaster is running at port 8140
The full log is at /var/log/foreman-installer/foreman.log
[ INFO 2018-04-08 06:46:59 verbose] All hooks in group post finished
[ INFO 2018-04-08 06:46:59 verbose] Installer finished in 315.528113749 seconds
[root@ip-10-103-137-91 yum.repos.d]#
And the web server does not seem to be running at URL: https://ip-10-103-137-91.aws.a.b.c
Last few lines of /var/log/foreman-installer/foreman.log
[ERROR 2018-04-08 14:25:35 main] Execution of '/bin/yum -d 0 -e 0 -y install foreman-proxy' returned 1: Checksum type 'md5' disabled
[ERROR 2018-04-08 14:25:35 main] Package: foreman-proxy-1.16.1-1.el7.noarch (foreman)
[ERROR 2018-04-08 14:25:35 main] Requires: rubygem(rake) >= 0.8.3
[ERROR 2018-04-08 14:25:35 main] You could try using --skip-broken to work around the problem
[ERROR 2018-04-08 14:25:35 main] You could try running: rpm -Va --nofiles --nodigest
[ERROR 2018-04-08 14:25:35 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:285:in `execute'
[ERROR 2018-04-08 14:25:35 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider.rb:101:in `execute'
[ERROR 2018-04-08 14:25:35 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/yum.rb:220:in `install'
[ERROR 2018-04-08 14:25:35 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/package.rb:88:in `block (3 levels) in <module:Puppet>'
[ERROR 2018-04-08 14:25:35 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:491:in `set'
[ERROR 2018-04-08 14:25:35 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:568:in `sync'
[ERROR 2018-04-08 14:25:35 main] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in `sync'
[ INFO 2018-04-08 14:27:55 main] Puppet has finished, bye!
[ INFO 2018-04-08 14:27:55 main] Executing hooks in group post
[DEBUG 2018-04-08 14:27:55 main] Hook /usr/share/foreman-installer/hooks/post/10-post_install_message.rb returned nil
[ INFO 2018-04-08 14:27:55 main] All hooks in group post finished
[DEBUG 2018-04-08 14:27:55 main] Exit with status code: 4 (signal was 4)
[DEBUG 2018-04-08 14:27:55 main] Cleaning /tmp/kafo_puppet20180408-17371-e0gmtd.conf
[DEBUG 2018-04-08 14:27:55 main] Cleaning /tmp/kafo_hiera20180408-17371-mxxc4h
[DEBUG 2018-04-08 14:27:55 main] Cleaning /tmp/kafo_puppet20180408-17371-1kawr6t.conf
[DEBUG 2018-04-08 14:27:55 main] Cleaning /tmp/default_values.yaml
[ INFO 2018-04-08 14:27:55 main] Installer finished in 157.660051257 seconds
Does yum install rubygem-rake work? What version is it? yum info rubygem-rake
just did yum update, and it gives me errors;
--> Finished Dependency Resolution
Error: Package: puppet-server-3.8.7-1.el7.noarch (@puppetlabs-products)
Requires: puppet = 3.8.7-1.el7
Removing: puppet-3.8.7-1.el7.noarch (@puppetlabs-products)
puppet = 3.8.7-1.el7
Obsoleted By: puppet-agent-5.5.0-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-3.5.1-1.el7.noarch (puppetlabs-products)
puppet = 3.5.1-1.el7
Available: puppet-3.6.0-1.el7.noarch (puppetlabs-products)
puppet = 3.6.0-1.el7
Available: puppet-3.6.1-1.el7.noarch (puppetlabs-products)
puppet = 3.6.1-1.el7
Available: puppet-3.6.2-1.el7.noarch (puppetlabs-products)
puppet = 3.6.2-1.el7
Available: puppet-3.6.2-1.el7sat.noarch (rhui-REGION-rhel-server-rh-common)
puppet = 3.6.2-1.el7sat
Available: puppet-3.6.2-3.el7.noarch (epel)
puppet = 3.6.2-3.el7
Available: puppet-3.7.0-1.el7.noarch (puppetlabs-products)
puppet = 3.7.0-1.el7
Available: puppet-3.7.1-1.el7.noarch (puppetlabs-products)
puppet = 3.7.1-1.el7
Available: puppet-3.7.2-1.el7.noarch (puppetlabs-products)
puppet = 3.7.2-1.el7
Available: puppet-3.7.3-1.el7.noarch (puppetlabs-products)
puppet = 3.7.3-1.el7
Available: puppet-3.7.4-1.el7.noarch (puppetlabs-products)
puppet = 3.7.4-1.el7
Available: puppet-3.7.5-1.el7.noarch (puppetlabs-products)
puppet = 3.7.5-1.el7
Available: puppet-3.8.1-1.el7.noarch (puppetlabs-products)
puppet = 3.8.1-1.el7
Available: puppet-3.8.2-1.el7.noarch (puppetlabs-products)
puppet = 3.8.2-1.el7
Available: puppet-3.8.3-1.el7.noarch (puppetlabs-products)
puppet = 3.8.3-1.el7
Available: puppet-3.8.4-1.el7.noarch (puppetlabs-products)
puppet = 3.8.4-1.el7
Available: puppet-3.8.5-1.el7.noarch (puppetlabs-products)
puppet = 3.8.5-1.el7
Available: puppet-3.8.6-1.el7.noarch (puppetlabs-products)
puppet = 3.8.6-1.el7
Available: puppet-agent-5.0.0-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.0.1-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.1.0-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.2.0-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.3.1-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.3.2-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.3.3-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.3.4-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.3.5-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
Available: puppet-agent-5.4.0-1.el7.x86_64 (puppet5)
puppet >= 4.0.0-1.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Where is the puppetlabs-products project coming from? It contains a deprecated version of Puppet (3.8). Can you disable it?
Foreman :: Manual just recommends the Puppet 5 repo, please try with just that
disabled:
# rpm -qa | grep puppet
puppet5-release-5.0.0-1.el7.noarch
puppet-agent-5.5.0-1.el7.x86_64
puppet-agent-oauth-0.5.1-3.el7.noarch
puppetserver-5.3.0-1.el7.noarch
puppetlabs-release-22.0-2.noarch
# rpm -qa | grep foreman
foreman-1.16.1-1.el7.noarch
foreman-selinux-1.16.1-1.el7.noarch
foreman-release-1.16.1-1.el7.noarch
foreman-release-scl-3-1.el7.noarch
foreman-debug-1.16.1-1.el7.noarch
foreman-postgresql-1.16.1-1.el7.noarch
foreman-cli-1.16.1-1.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.11.0-1.el7.noarch
foreman-installer-1.16.1-1.el7.noarch
But now when i run : foreman-installer -v
I get errors:
Something went wrong! Check the log for ERROR-level output
[ERROR 2018-04-10 15:11:58 verbose] /Stage[main]/Puppet::Server::Service/Service[puppetserver]: Failed to call refresh: Systemd restart for puppetserver failed!
[ERROR 2018-04-10 15:11:58 verbose] journalctl log for puppetserver:
[ERROR 2018-04-10 15:11:58 verbose] -- Logs begin at Tue 2018-04-10 14:26:06 UTC, end at Tue 2018-04-10 15:11:58 UTC. --
[ERROR 2018-04-10 15:11:58 verbose] Apr 10 15:07:04 ip-10-103-137-14.aws.x.x.x puppetserver[4021]: Failed to load feature test for posix: can't find user for 0
I found an article: https://karloluiten.nl/fix-puppet-failed-to-load-feature-test-for-posix-cant-find-user-for-0/
The fix recommended is:
Has to do with noexec on /tmp . Fix by editing /etc/sysconfig/puppetserver, add something like “-Djava.io.tmpdir=/var/puppettmp” , mkdir /var/puppettmp, chmod 1777 /var/puppettmp .
But after i apply the changes to /etc/sysconfig/puppetserver, when i run the foreman-installer -v
the changes ( -Djava.io.tmpdir=/var/puppettmp ) are wiped and reverted to default, and puppet server still fails to restart. Any idea how i can permanently modify the configuration and still be able to run foreman-installer?
Now i tried to run it with -i ( interactive)
foreman-installer --enable-foreman-proxy -i
Choose an option from the menu… 53
Result:
Execution of ‘/bin/yum -d 0 -e 0 -y install foreman-proxy’ returned 1: Checksum type ‘md5’ disabled
Failed to get region name from EC2
Package: foreman-proxy-1.16.1-1.el7.noarch (foreman)
Requires: rubygem(rake) >= 0.8.3
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
