[foreman-users] ActiveRecord::UnknownAttributeError: unknown attribute 'provision_method' for Host::Managed

Hello there! I'm having an isolated issue on one of the Foreman (separate) instances, where I can't deploy Libvirt VMs into compute resources anymore. A standard procedure (through UI): New Host put a hostname for a new VM pick a compute resource to deploy on At this point I see that

Re: [foreman-users] Re: Foreman users @ Puppetconf (17th-21st Oct) event?

Present! which Pavillon is RedHat booth? Also there is Charlie's pub which is on premises (nice beers!). On Wednesday, October 19, 2016 at 9:19:10 AM UTC-7, Ashton Davis wrote: > > You've got time! Grab a plane! :) > See everyone tonight! I'm excited. > > > Ashton Davis > *Account Solutions

Re: [foreman-users] Foreman remote execution fails

Thanks for the insight, i didn't knew it has separate logs. i have enabled debug log, and it seems like foreman-proxy is trying to access the remote host with different IP ( it resolves to the host secondary IP ) which results in connection error. i have tried it with several hosts which have

[foreman-users] Errors with virt-who

Hi, In the foreman/production.log, there is errors with virt-who config for VMware ESX : [foreman-tasks/action] [E] Validation failed: Architecture can't be blank, Operatingsystem can't be blank (ActiveRecord::RecordInvalid) [katello/cp_proxy] [E] ForemanTasks::TaskError: Task

[foreman-users] Re: Foreman remote execution fails

Yes, the root user on the remote host has foreman-proxy ssh public key, anything else i might have missed ? On Wednesday, October 19, 2016 at 3:54:06 PM UTC+3, Duncan Innes wrote: > > Is the target host configured to accept the SSH connection from the proxy? > > >

[foreman-users] Re: Foreman remote execution fails

Is the target host configured to accept the SSH connection from the proxy? https://theforeman.org/plugins/foreman_remote_execution/0.3/index.html#2.2RemoteHostsConfiguration On Wednesday, 19 October 2016 13:00:17 UTC+1, Dor Azoulay wrote: > > > i have just installed the latest version of foreman

[foreman-users] Hammer

Hi, I have installed foreman 1.13, configured Puppet smart proxy and VMware compute resource (with virtual distributed switch). I am able to create host using UI successfully and all functionality is working fine. But, when I try creating the same via "hammer", I am encountering below error.

Re: [foreman-users] Foreman remote execution fails

Hello, from what you posted it seems that there is a problem with opening the SSH connection from proxy to the target host. Could you please check /var/log/foreman-proxy/smart_proxy_dynflow_core.log? There could be something helpful there (it is a log file of a smart proxy helper process which

[foreman-users] Foreman remote execution fails

i have just installed the latest version of foreman (1.13.0) on Centos 7.2. everything works well except when i am trying to run remote execution on a machine (installed via foreman-installer) it fails with : 1: Error initializing command: Net::SSH::ConnectionTimeout -

[foreman-users] activationkey registrations failing with 'undefined method 'systems' for Katello::HostCollection

Full debug log of attempted registration using an activationkey that previously worked. Same machine - same key http://paste.awesom.eu/raw/8ucZ -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop

[foreman-users] activationkeys failing to register with 'undefined method systems for Katello::HostColleciton:uuid'

My activationkeys are no longer registering clients to Foreman - here is a debug log taken from production.log when I attempt to register a previously successfully registered client using the same activationkey http://paste.awesom.eu/raw/8ucZ -- You received this message because you are

[foreman-users] Re: Hammer CLI, oVirt and templates

On Tuesday, October 18, 2016 at 3:35:19 PM UTC+2, dav...@billymob.com wrote: > > > Is this an Hammer bug? Has anyone got this working? > > Solved. I have to specify in the Instance Type the 2-disks template, specifying only the image wasn't enough. I guess the confusion (at least for me) comes

Re: [foreman-users] Upgrade Failure on db:migrate v1.7.5 to 1.13 - what now?

You got me! I totally missed that!! :( And perhaps I spoke too soon - Got another error.. :( :( I ran the command you pasted, everything ran successfully. I attempted to step to foreman-rake db:seed and received notice I had 63 pending transactions. So I ran the following:

Re: [foreman-users] Upgrade Failure on db:migrate v1.7.5 to 1.13 - what now?

Thank you for the reply - wonder why this did not show up in search results. If appears to have run successfully w/o a restoration of the DB. I would like to request the upgrade documetnation be updated on the foreman site to reflect the version step-up needing to take place. Happy to submit

[foreman-users] disabling oauth causes Foreman_proxy registration attempts to fail

When I have foreman::oauth_active set to false, install attempts result in the following error: /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman2.domain]: Could not evaluate: Proxy foreman2.domain cannot be retrieved: unknown error (response 401)