#theforeman

/

      • FriedBob joined the channel
      • shlomizadok__ joined the channel
      • shlomizadok__ has quit
      • shlomizadok__ joined the channel
      • jomitsch-afk is now known as jomitsch
      • ebartz_i has quit
      • dcaro joined the channel
      • dcaro has quit
      • ebartz_i joined the channel
      • dcaro joined the channel
      • shlomizadok__ has quit
      • shlomizadok__ joined the channel
      • Philambdo joined the channel
      • renatoarmani joined the channel
      • I-use-foreman joined the channel
      • ebartz_i has quit
      • pgustafs joined the channel
      • I-use-foreman
        Morning all, getting this error when trying to manually run foreman tasks http://pastebin.com/AQsxuziP related to that I filed yesterday I think.. http://projects.theforeman.org/issues/12352
      • khushbu joined the channel
      • khushbu has quit
      • Dominic
        it would need to be run from /usr/share/foreman, plus there are a bunch of other environment variables that the usual init script sets
      • pujan14 joined the channel
      • I-use-foreman
        I created a /etc/foreman/config/logging.yaml (copy out of /etc/foreman/logging.yaml) and ran the command, it seems to be happy now.
      • renatoarmani has quit
      • renatoarmani joined the channel
      • hrmf, and it still pukes when trying to delete a host that has chef params attached to it. Dernit.
      • nagoor has quit
      • pujan14 has quit
      • mhulan
        I-use-foreman: did you try the "service foreman-tasks restart"?
      • tmclaugh[work] joined the channel
      • straylen joined the channel
      • I-use-foreman
        service actually doesn't invoke it. I have to run it manually... this is on an ubuntu 14.04 server... it's like it's not registered as a service....
      • mhulan
        mmoll I thought we had service script for foreman tasks in debs? ^
      • I-use-foreman wonders is she shouldn't be running bleeding edge 1.10rc2 with foreman-chef plugins and that's causing the problems. maybe .92 instead?
      • renatoarmani has quit
      • I-use-foreman
        do you have them in 92? And they're just missing in 1.10rc2?
      • mmoll
        mhulan: we do, sorry ENOTIME at the moment
      • ruby-foreman-tasks
      • I-use-foreman
        ah there we go.
      • mhulan
        mmoll: thanks, now worries
      • I-use-foreman
        I do see that service name.
      • mhulan
        I-use-foreman: yeah, sorry, so after restart it should trigger the pending task that blocks new deletions
      • I-use-foreman: but I wonder how it got to this state in the first place
      • I-use-foreman
        ok it wasn't even started at all. Let's see if this deletes... alrighty. :crosses-fingers:
      • Not sure, it's a bog standard ubuntu install. With a fresh install of 1.10rc2 on it, and forman_chef 0.2.0...
      • and heyt now the host is gone.
      • Hooray.
      • mhulan
        I-use-foreman: cool!
      • I-use-foreman
        so should ruby-foreman-tasks be running by default at startup? Or just invoked as needed? Not sure why it got like this?
      • khushbu_ joined the channel
      • khushbu_ has quit
      • mhulan
        not sure what's better in this case, but definitely it should be documented in installation steps
      • I-use-foreman: what steps did you follow, foreman_chef manual?
      • I-use-foreman
        yes. With some guessing tossed in here and there.
      • I still actually can't get it to download the opscode chef installer bit, or copy the validation.pem over, but it's creating the client/rv under /etc/chef on clients (also ubuntu 14.04) which is good.
      • er client.rb
      • mhulan
        I-use-foreman: I'm happy to improve instructions if you tell me what's missing
      • I-use-foreman: so did you setup all parameters as stated in http://theforeman.org/plugins/foreman_chef/0.2/... ?
      • I-use-foreman
        Let me figure it out, and I can submit up a writeup of what you might want to add in, etc. I'm still new in this foreman_chef process, but I think I can nail it down.
      • discr33t joined the channel
      • walden|afk is now known as walden
      • AphisOne joined the channel
      • mhulan
        I-use-foreman: awesome
      • Dominic
        using the installer ought to enable the ruby-foreman-tasks service at boot
      • I-use-foreman
        I did use the installer, not sure why it didn't enable it at restart, and I've tossed a few restarts at it since...
      • mhulan
        Dominic: seems we miss exception for deb systems? https://github.com/theforeman/puppet-foreman/bl...
      • oh wait, it's there in params.pp
      • Dominic
        yeah, name is passed
      • mhulan
        anyway we should probably document manual setup for users just installing packages only
      • I-use-foreman
        I'm sure part of the pain of what I have is an older chef install, plus ubuntu, etc. But I think I can fully end-end provision if I rip up the templates a up and get it right.
      • felskrone1
        mhulan: that would be awesome :-)
      • ybronhei has quit
      • since we use salt instead of puppet, having all the puppet stuff coming with the installer is a litte annoying :-)
      • maryo joined the channel
      • discr33t
        has anything changed in the windows smart-proxy between 1.8 and 1.9?
      • khushbu joined the channel
      • khushbu has quit
      • I-use-foreman uses chef so puppet and salt just freak me out.
      • mhulan
        felskrone1: you can foreman-installer --no-enable-puppet :-)
      • I-use-foreman
        actually I'll amend that former puppet user, and I still like it, it's just not my current thing that I can use.
      • mhulan
        felskrone1: but I think this will get much better with scenarios support in installer (should be in 1.11)
      • shlomizadok__ has quit
      • felskrone1
        mhulan: true but then i have to do all the ssl stuff and im not too familiar with foreman yet to be able to to that
      • mhulan
        felskrone1: I see, fair point
      • felskrone1
        i actually tried and failed :-)
      • I-use-foreman has left the channel
      • cptweasel joined the channel
      • currently i provision our foreman-server with salt by templating the foreman-installer-answers file and running the installer with salt, which is kinda dirty
      • I-use-foreman joined the channel
      • renatoarmani joined the channel
      • tmclaugh[work] joined the channel
      • pedutang has quit
      • khushbu_ joined the channel
      • khushbu_ has quit
      • renatoarmani has quit
      • Kumudini has quit
      • khushbu_ joined the channel
      • renatoarmani joined the channel
      • khushbu_ has quit
      • neha_ joined the channel
      • khushbu_ joined the channel
      • mlev joined the channel
      • khushbu_ has quit
      • ichimonji10 joined the channel
      • ra30r joined the channel
      • numkem joined the channel
      • khushbu joined the channel
      • discr33t
        does the 1.9 windows smart proxy install successfully as a service?
      • cfoo joined the channel
      • darb is now known as bbuckingham
      • khushbu has quit
      • khushbu_ joined the channel
      • khushbu_ has quit
      • palmertime joined the channel
      • kybaker joined the channel
      • renatoarmani has quit
      • ayerlock joined the channel
      • khushbu_ joined the channel
      • khushbu_ has quit
      • killglance joined the channel
      • renatoarmani joined the channel
      • mlev has left the channel
      • flyinbutrs joined the channel
      • renatoarmani has quit
      • renatoarmani joined the channel
      • i just got a smart-proxy configured on my windows 2012 dhcp server and when i try and import subnets i see an error that says "loaderror - cannot load such file -- win32/open3"
      • khushbu_ joined the channel
      • Claer
        discr33t: what ruby versiondo you have?
      • it changed between versions
      • discr33t
        Claer: i had to do a gem install win32-open3-19 and everything worked
      • Claer: i'm running 1.9 for the smart-proxy
      • Claer
        ok
      • discr33t
        Claer: i guess i missed something in the instructions or a dependency didn't resolve
      • Claer
        normally it should work when you execute bundle install
      • discr33t
        Claer: ok, might just be something i did out of order then or something. . .
      • straylen joined the channel
      • jobewan joined the channel
      • palmertime1 joined the channel
      • palmertime has quit
      • Dominic
        I think there are still some open PRs to fix that
      • jfarschman joined the channel
      • jfarschman is now known as MilesDenver
      • Diar joined the channel
      • Diar
        How do I get foreman to recognise puppet enviroment inheritance, I have tried adding [development] modulepath = /etc/puppet/environments/development/modules:/etc/puppet/environments/common manifestdir = /etc/puppet/environments/development/manifests config_version = [production] modulepath = /etc/puppet/environments/production/modules:/etc/puppet/environments/common manifestdir = /etc/puppet/enviro
      • to puppet.conf
      • I have also tried setting the modules_basedir to the common and environment specific for development and production
      • shaunm joined the channel
      • Dominic
        that ought to work, but it's much easier now with directory environments rather than config envs
      • Diar
        I started off with Directories, but I could not work out how common could be inherited by production and development, it kept appearing as three seprate environments
      • choirboy joined the channel