Re: [foreman-users] Re: Foreman Proxy is not recognized

2016-07-28 Thread Sai Krishna 
puppet cert generate new-puppetmaster.example.com

am generating new certs for puppetmaster on foreman server and replacing 
new certs in puppetmaster  is this correct way ? 

Please advice
Sai Krishna

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Katello 2.4 > 3.0 - Virtual Datacenter Subscription Issue(s)

2016-07-28 Thread John Mitsch 
You are most welcome! Glad to hear the subscriptions are showing now. I'll
comment back if I find the issue or if I can't find it we can file a new
one.

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Thu, Jul 28, 2016 at 2:21 PM, Barry Gestwicki 
wrote:

> HI John!
>
> You're a savior!  I've taken the steps you've suggested, and the derived
> subscriptions for "guest of " now show up on the "Red Hat
> Subscriptions" page!  However, this also facilitated my ability to attempt
> to add them to an Activation Key, but after attempting to add two out of
> the bunch to a key, I get the error message outlined in Bug #13844, which
> is "Katello::Resources::Candlepin::ActivationKey: 400 Bad Request
> {"displayMessage":"Product ID \"RH2RN\" has already been registered
> with this activation
> key","requestUuid":"6b2cf4a2-d2de-4bac-ab89-fd4d61300810"} (POST
> /candlepin/activation_keys/4c5fab9c5482bd090154878a21c702dc/product/RH2RN)".
> As such, this appears to have not yet been fixed, however unfortunate...
>
> However, that falls outside the scope of this particular string, and
> you've provided me with a sufficient workaround to address the core issue
> of not even being able to see nor manage the derived subscriptions, so a
> tremendous "Thanks!" for that!  ;-)  Now on to updating said bug report in
> an effort to get it re-opened...  :-)  Thanks again, John!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: Foreman Proxy is not recognized

2016-07-28 Thread Sai Krishna 
/etc/foreman-proxy/settings.d/puppet_proxy_puppet_api.yml 

>
>>- ---
>>- # URL of the puppet master itself for API requests.
>>- :puppet_url: https://puppetmaster:8140
>>-  # SSL certificates used to access the puppet API
>>- :puppet_ssl_ca: /etc/puppetlabs/puppet/ssl/certs/ca.pem
>>- :puppet_ssl_cert: /etc/puppetlabs/puppet/ssl/certs/puppetmaster.pem
>>- :puppet_ssl_key: 
>>/etc/puppetlabs/puppet/ssl/private_keys/puppetmaster.pem
>>
>> Here the paths are different from settings.yml  is this causing any cert 
issue ?

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Katello 2.4 > 3.0 - Virtual Datacenter Subscription Issue(s)

2016-07-28 Thread John Mitsch 
Barry,

I believe this is a reported issue, I am digging around for the related bug
and will post if I find something.

Can you do this:
# foreman-rake console
> Katello::Subscription.import_all
> Katello::Pool.import_all

and then see if the missing subscriptions show?

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Thu, Jul 28, 2016 at 12:26 PM, Barry Gestwicki 
wrote:

> I hesitate to post on here for issues I’m experiencing until I’ve
> thoroughly troubleshot them, but I’m banging my head against a wall here,
> so here I go…  :-)  I initially installed Katello 2.4 on a RHEL7 system,
> and as we have a small set of Virtual Datacenter Licenses, I followed the
> steps outlined in https://access.redhat.com/solutions/659563 in order to
> facilitate the use of them in Katello.  I was successfully able to attach
> the VDC subscription to ten ESXi hosts, and I could see the derived
> subscriptions on the “*Red Hat Subscriptions*” page underneath the
> primary *“**Red Hat Enterprise Linux for Virtual Datacenters, Standard**”
> *entry.  However, I quickly found that I was unable to add all the
> derived subscriptions to a given Activation Key, as it reported an error
> that basically indicated the derived subscriptions shared the same Product
> ID and would not allow duplicate additions.  This particular phenomenon
> appears to have been documented in
> http://projects.theforeman.org/issues/13844, so I had been watching it
> intently, and based on a recent update, this particular issue has
> reportedly been fixed in Katello 3.0.
>
>
>
> All that being said, I had updated said Katello instance to version 3,
> hopeful to take advantage of the bug fix, among other benefits.  However,
> a few things were immediately obvious to me : 1) After the upgrade, none of
> the VDC subscriptions stayed attached to my ESXi hosts.  This was easily
> remedied by going back through the process of attaching the VDC
> subscription to our ESXi hosts, but an odd outcome, nonetheless.  However,
> after doing so, I found that the derived subscriptions were not appearing
> on the “*Red Hat Subscriptions*” page as they were in Katello 2.4.  As I
> suspected, that also meant that they are unavailable for me to attach to an
> Activation Key.  Even more confounding, if I were to hop on a guest of
> one of the subscribed ESXi hosts and execute “subscription-manager list
> --available”, I could actually see that DERIVED SKU license was available
> for me to use if I wanted to manually do so, just not within the context of
> Katello.
>
>
>
> *TL;DR* - In Katello 2.4, I was able to attach VDC subscriptions to ESXi
> hypervisors, and view the derived subscriptions in both “*Red Hat
> Subscriptions*” and “*Activation Keys*” > “*Subscriptions*” > "*Add*",
> but was unable to add multiple derived subscriptions due to the duplicate
> Product ID issue reported in http://projects.theforeman.org/issues/13844.
> This has reportedly been fixed in Katello 3.0, but unfortunately an
> upgrade from 2.4 to 3.0 has resulted in a different issue where the derived
> licenses are not visible on the “*Red Hat Subscriptions Page*”, nor the 
> “*Activation
> Keys*” one, but can be seen directly from the “*subscription-manager*”
> command on a subscribed hypervisor guest.
>
>
>
> My intent with this is to see if there’s anyone else out there
> experiencing the same behavior, as well as possibly getting some advice on
> a fix from the experts out there, and/or get some confirmation that this is
> a legitimate bug that deserves to be reported (Hopefully with a fix in 3.1
> if so!  :-)).  Thanks to anyone who may be able to provide some insight
> and/or assistance!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] [katello] Cannot Register Content Hosts

2016-07-28 Thread apgriffiths79 
certificate and key were missing from /etc/pki/pulp. Seems like this step 
was missed/failed during the install - maybe due to system clock being out?

I've put some in place (and fixed system clock) and can register new hosts 
now, but the two broken hosts are completely wedged. Any way to forcibly 
remove them?


On Thursday, 28 July 2016 15:55:20 UTC+1, John Mitsch wrote:
>
> Do you see anything related in /var/log/messages?
>
> John Mitsch
> Red Hat Engineering
> (860)-967-7285
> irc: jomitsch
>
> On Thu, Jul 28, 2016 at 10:37 AM,  
> wrote:
>
>> The Action is Actions::Pulp::Consumer::Create. I tried doing a resume on 
>> the task and the error is now 409 Conflict. There is a large backtrace.
>>
>> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in
>>  
>> `return!'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.7.2/lib/runcible/base.rb:79:in
>>  
>> `block in get_response'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in
>>  
>> `call'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:228:in
>>  
>> `process_result'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/rbovirt-0.0.37/lib/restclient_ext/request.rb:50:in
>>  
>> `block in transmit'
>> /opt/rh/rh-ruby22/root/usr/share/ruby/net/http.rb:853:in `start'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/rbovirt-0.0.37/lib/restclient_ext/request.rb:44:in
>>  
>> `transmit'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in
>>  
>> `execute'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in
>>  
>> `execute'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.6.7/lib/restclient/resource.rb:67:in
>>  
>> `post'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.7.2/lib/runcible/base.rb:78:in
>>  
>> `get_response'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.7.2/lib/runcible/base.rb:66:in
>>  
>> `call'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.7.2/lib/runcible/resources/consumer.rb:20:in
>>  
>> `create'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/pulp/consumer/create.rb:13:in
>>  
>> `run'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/action.rb:506:in
>>  
>> `block (3 levels) in execute_run'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:26:in
>>  
>> `call'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:26:in
>>  
>> `pass'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware.rb:17:in
>>  
>> `pass'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware.rb:30:in
>>  
>> `run'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:22:in
>>  
>> `call'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:26:in
>>  
>> `pass'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware.rb:17:in
>>  
>> `pass'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/middleware/remote_action.rb:16:in
>>  
>> `block in run'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/middleware/remote_action.rb:40:in
>>  
>> `block in as_remote_user'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/models/katello/concerns/user_extensions.rb:20:in
>>  
>> `cp_config'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/middleware/remote_action.rb:27:in
>>  
>> `as_cp_user'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/middleware/remote_action.rb:39:in
>>  
>> `as_remote_user'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.2/app/lib/actions/middleware/remote_action.rb:16:in
>>  
>> `run'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:22:in
>>  
>> `call'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:26:in
>>  
>> `pass'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware.rb:17:in
>>  
>> `pass'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/action/progress.rb:30:in
>>  
>> `with_progress_calculation'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/action/progress.rb:16:in
>>  
>> `run'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:22:in
>>  
>> `call'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware/stack.rb:26:in
>>  
>> `pass'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.11/lib/dynflow/middleware.rb:17:in
>>

Re: [foreman-users] undefined method `join' for #, receiving salt states from smartproxy

2016-07-28 Thread Stephen Benjamin 


- Original Message -
> From: "Tom K." 
> To: "Foreman users" 
> Sent: Wednesday, July 27, 2016 10:17:12 AM
> Subject: [foreman-users] undefined method `join' for #, receiving 
> salt states from smartproxy
> 
> Hi,
> 
> I've a running Foreman 1.11.3 and a Smartyproxy 1.11.3 on 2 different
> machines. The Smartproxy serves the salt-api/saltmaster. Now, if I query
> from Foreman the states of the Saltmaster SmartyProxy, nothing happens.
> 
> Sometimes a popup appears with the message
> 
> Error: ERF12-4701 [ProxyAPI::ProxyException]: Unable to fetch Salt states
> list ([ProxyAPI::ProxyException]: ERF12-7301 [ProxyAPI::ProxyException]:
> Unable to fetch Salt environments list ([RestCli...) for proxy
> https:/fosp-saltmaster-001:8443/salt/
> 
> 
> In the *forman-proxy.log* on the smartproxy tells me
> 
> E, [2016-07-27T10:05:26.163632 #2422] ERROR -- : undefined method `join'
> for # (NoMethodError)
> /usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/showexceptions.rb:37:in
> `rescue in call'
> /usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/showexceptions.rb:21:in
> `call'
> /usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/base.rb:124:in `call'
> /usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/base.rb:1417:in `block in
> call'
> /usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/base.rb:1499:in `synchronize'
> /usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/base.rb:1417:in `call'
> /usr/share/gems/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
> /usr/share/gems/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
> /usr/share/gems/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
> /usr/share/gems/gems/rack-1.6.4/lib/rack/builder.rb:153:in `call'
> /usr/share/gems/gems/rack-1.6.4/lib/rack/handler/webrick.rb:88:in `service'
> /usr/share/ruby/webrick/httpserver.rb:138:in `service'
> /usr/share/ruby/webrick/httpserver.rb:94:in `run'
> /usr/share/ruby/webrick/server.rb:295:in `block in start_thread'
> 
> 
> 
> The */var/log/foreman/production.log* throws
> 
> 2016-07-27 10:10:48 [app] [W] ProxyAPI operation FAILED
>  | ProxyAPI::ProxyException: ERF12-4701 [ProxyAPI::ProxyException]: Unable
> to fetch Salt states list ([ProxyAPI::ProxyException]: ERF12-7301
> [ProxyAPI::ProxyException]: Unable to fetch Salt environments list
> ([RestCli...) for proxy https:/fosp-saltmaster-001:8443/salt/
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_salt-5.0.1/app/lib/proxy_api/salt.rb:43:in
> `rescue in states_list'
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_salt-5.0.1/app/lib/proxy_api/salt.rb:35:in
> `states_list'
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_salt-5.0.1/app/controllers/foreman_salt/state_importer.rb:16:in
> `fetch_states_from_proxy'
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_salt-5.0.1/app/controllers/foreman_salt/salt_modules_controller.rb:60:in
> `import'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/action_controller/metal/implicit_render.rb:4:in
> `send_action'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:189:in
> `process_action'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:10:in
> `process_action'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:20:in
> `block in process_action'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in
> `call'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in
> `call'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
> `block in halting_and_conditional'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
> `call'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
> `block in halting_and_conditional'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
> `call'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
> `block in halting_and_conditional'
>  | 
> /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
> `call'
> 
> 
> 
> 
> What's my problem? What can I do... I've really no idea


Fetching the salt environment or salt states list requires the proxy be 
configured to talk to the salt-api. See section 2.1.3
in the latest manual: http://theforeman.org/plugins/foreman_salt/

Troubleshooting steps:
- Look in /var/log/foreman-proxy/proxy.log, and /var/log/salt/* for any 
errors.
- Does the API user have the @runner permission in /etc/salt/master?
- Is the salt-api service started?
- Is

Re: [foreman-users] yum update, package fails "requested range not satisfiable"

2016-07-28 Thread Eric D Helms 
Dylan,

Can you wget the package from the HTTP repository published by Katello that
should have the RPM? Can you yum localinstall from the published HTTP
repository on Katello?


Eric

On Wed, Jul 27, 2016 at 8:20 PM, Dylan Baars  wrote:

> Hi,
>
> we have synced (and been syncing) the Jenkins LTS release for RH for
> months now, which is this repo http://pkg.jenkins-ci.org/redhat-stable/
> They have added a new RPM, jenkins-2.7.1-1.1.noarch.rpm
>  and
> our local katello has synced that, however now when trying to run a "yum
> update" I get
>
> jenkins-2.7.1-1.1.noarch.rpm   FAILED
>
> https://wellkatello.niwa.local/pulp/repos/NIWA/Dev-Server/CentOS7_Server/custom/Jenkins/Jenkins_LTS/jenkins-2.7.1-1.1.noarch.rpm:
> [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable ]
>  0.0 B/s |0 B  --:--:-- ETA
> Trying other mirror.
>
>
> Error downloading packages:
>   jenkins-2.7.1-1.1.noarch: [Errno 256] No more mirrors to try.
>
> I can manually download the file from the pkg.jenkins-ci.org repo and do
> a "yum localinstall" - works fine. What's happening with the above?
>
> Dylan
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] foreman 1.11.3: 'attached_devices' key is no longer present in $foreman_interfaces global variable

2016-07-28 Thread Herwig Bogaert 
The problem is also present in 1.11.4.
I will keep you posted once we have move to 1.12.x.

Best regards

2016-07-28 10:37 GMT+02:00 Dominic Cleal :

> On 28/07/16 09:34, herwig.boga...@viaa.be wrote:
> > Hi Dominic
> >
> > Unfortunately, I cannot reproduce the problem on 1.12.x now.
> > Our foreman/puppet infra is running on Debian wheezy which is not
> > supported by foreman 1.12.x
> > Upgrading the foreman infra to Debian Jessie is planned later this year,
> > but is not possible at this moment.
> >
> > If you tell me that the problem will not be fixed in 1.11.x, then i will
> > implement some temporary workaround.
>
> It's very unlikely at this point - the last patch release I expected to
> do is now out (1.11.4) and without investigating in more detail, I'm
> unsure what the bug is caused/fixed by.
>
> --
> Dominic Cleal
> domi...@cleal.org
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/foreman-users/O7TP1b0sAh4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 


 Herwig Bogaert
 Senior Systems Engineer

 VIAA vzw* | Sassevaartstraat 46/209 | 9000 Gent | België | www.viaa.be
*
 T: +32 9 298 05 01 *|* M: +32 478 42 22 55


 
 
 

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: Foreman Proxy is not recognized

2016-07-28 Thread Dominic Cleal 
On 27/07/16 21:43, Sai Krishna wrote:
> *[ERROR 2016-07-27 16:13:21 main] Errors encountered during run:*
> *[ERROR 2016-07-27 16:13:21 main]  Evaluation Error: Error while
> evaluating a Function Call, undefined class/module HighLine:: at
> /usr/share/gems/gems/kafo-0.9.1/modules/kafo_configure/manifests/init.pp:14:3
> on node puppetserver.com*

This appears similar to http://projects.theforeman.org/issues/15111, so
ensure ruby-kafo is at least version 0.8.2, preferably the latest we
ship (0.9.x).

-- 
Dominic Cleal
domi...@cleal.org

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Re: Foreman Proxy is not recognized

2016-07-28 Thread Dominic Cleal 
On 27/07/16 20:27, Sai Krishna wrote:
> I have changed the /etc/foreman-proxy/settings.yml file. I have change
> trusted host and foreman_url from puppetmaster to foremanvers FQDN. is
> this a wrong move ?
> 
> # the hosts which the proxy accepts connections from
> # commenting the following lines would mean every verified SSL
> connection allowed
> :trusted_hosts:
>   - foremansever.com
> 
> # Endpoint for reverse communication
> :foreman_url: https://foremanserver.com
> 
> I have generated new smart proxy certificates from foreman server and
> replaced the /etc/puppetlabs/ssl/certs/ca.pem, puppetserver.pem,
> /etc/puppetlabs/ssl/private_keys/puppetserver.pem
>  
> Still do I need to change anything. Please advice. 

That sounds correct, but what happens now? It's unclear from your
message whether this works or if you still receive an error. Also verify
that those paths are the ones referenced in settings.yml.

-- 
Dominic Cleal
domi...@cleal.org

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] foreman 1.11.3: 'attached_devices' key is no longer present in $foreman_interfaces global variable

2016-07-28 Thread Dominic Cleal 
On 27/07/16 15:23, herwig.boga...@viaa.be wrote:
> Hi 
> 
> I use the $foreman_interfaces global variable in the puppet manifests
> that configure the network interfaces of a host.
> 
> After upgrading to foreman 1.11.3 (from foreman 1.9) the
> 'attached_devices' key is no longer present in the $foreman_interfaces
> hash for interfaces of type bond.

If you can reproduce the problem on Foreman 1.12.x, please do file a bug
in the issue tracker. The ENC output was refactored a little in 1.12 so
it may now work.

-- 
Dominic Cleal
domi...@cleal.org

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.