#theforeman

Hi, on centos 7, i changed the repo for foreman from 1.9 to latest and when i try to do an update to get to 1.13 or 1.14, i get many error of missing dependency ruby22, i didn't find on the installation documentation how to resolve it.

toordog: update to 1.10.x first, then 1.11.x and so on, it's not supported to jump over more than one release (and even known to fail in quite some situations), the update notes of the respective version to update to should have additional information, if that should be needed

aww that's a painful process :s

i'd rather uninstall all and reinstall

is there any good reason to go from 1.9 to 1.13^

toordog: not really... it's the only way to have some confidence in the upgrade process, as anything else would need to be tested and thought of, additionally

toordog: check the release notes of the versions...

toordog: and of course, there are not updates for anything below 1.13 anymore

i'm only asking about something major enough that i shouldn't do otherwise than run 1.13

ok

whats the best way to install foreman if you already have a puppet master?

im having issues setting up foreman-proxy on my puppet4 instance

just put the version inside puppet.yml but i get ERROR because puppet_url is expected

but this should be detected by version am i right?

hi

I have install foreman-1.14-rc.but I can not login when I input "admin/changme"

who knows password ?

afaik, the password is generated during install and shown at the end, when the installation finished

xjg: you can also run 'foreman-rake permissions:reset username=admin password=changeme' (or whatever username password) to reset it

rofl____: read https://www.theforeman.org/manuals/1.13/#3.2.3I...

dlobato: that is a general reset of foremans admin account?

Elwood_5G: yeah, it'd work for any username actually not just admin

if you don't provide username and pass it'll create a random password for the admin

.. something to keep in mind

btw is anybody working on a plugin to create networks on various hypervisors?

dLobatog: thanks

i have a smartproxy running on my puppet master now

with puppet and puppetca capabilities

should this add all my puppethosts automatically to foreman?

rofl____: not until you run puppet on all of your hosts

dLobatog: i have run on some

but seems there is some trouble detecting environments

E, [2016-12-30T09:27:14.761748 ] ERROR -- : Failed to initialize puppet class cache, will use lazy initialization instead

E, [2016-12-30T09:27:14.664818 ] ERROR -- : Error while retrieving puppet classes for 'production' environment

rofl____: set the log_level to debug and restart the proxy

does it look like a ACL issue?

rofl____: possibly, journalctl -l -u puppetserver will tell you

D, [2016-12-30T09:30:05.814526 ] DEBUG -- : 403 Forbidden request: /puppet/v3/environment_classes (method :get). Please see the server logs for details. (Proxy::Error::HttpError)

rofl____: yeah, check your auth.conf to allow that request

http://projects.theforeman.org/projects/foreman... contains some info, I just saw the manual doesn't have it, i'll put it there too

hi

[root@foreman.server.com script]# ./foreman-rake permissions:reset username=admin password=changeme

rake aborted!

dLobatog: cheers, fixed that issue

but i still cant import the environments

is there any config for importing? i get 404 on /puppet/environments

Error: ERF12-2749 [ProxyAPI::ProxyException]: Unable to get environments from Puppet ([RestClient::NotFound]: 404 Not Found) for proxy

Error: ERF12-2749 has a wiki page - see http://theforeman.org/projects/foreman/wiki/ERF...

right

i dont get any logs in foreman-proxy.log though

with debug on

rofl____: /var/log/foreman-proxy/proxy.log

xjg: no './' at the beginning

xjg: is that a development installation?

dLobatog: is there a way to set a timeout for puppet requests?

D, [2016-12-30T10:15:37.291908 ] DEBUG -- : Puppet is taking too long to respond,

so it gave foreman a 503

yes I install from source code

xjg: ok, then just run 'rake permissions:reset username=admin' from the foreman directory

my new test 1.13.3 test system is a real problem compared to other releases, I don't see anything in the release notes that suggests I need to approach this different. It appears that every action around a host tries to create a new dhcp lease, which then errors saying there is a conflict (which there is because it's already created it) the provisioning script calls home to finish the build but doesn't

remove the tftp build tokens so next time it reboots it provisions again

I use the same build script to build the 1.13.3 test system as the 1.13.1 previous test system, .1 was working

hi

Spring was unable to find your config/application.rb file. Your project root was detected at /data/usr_data/foreman-1.13.3/bin, so spring looked for /data/usr_data/foreman-1.13.3/bin/config/application.rb but it doesn't exist. You can configure the root of your application by setting Spring.application_root in config/spring.rb

xjg: thats an odd location

(as in path)

he's installing it from source

why ?

that seems an unusual thing to do with the packages being available

xjg: are you running rake from /data/usr_data/foreman-1.13.3/?

yes

ikonia: ¯\_(ツ)_/¯

xjg: try 'bin/rake' or 'bundle exec rake' instead.. I'm not sure why is it not loading rake if you're on that directory

Ok