[foreman-users] Re: Provisioning Setup, not working :(

[Mike Wilson]

Still fighting with this. Anyone have any thoughts? Are we not suppose to 
be able to provision more than one subnet or something? 

-- 
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: The operating system value changes after first puppet run.

[Andrew Schofield]

2 years later and it still doesn't!I've lost a few hours today trying to 
figure this out!

My next question though is how do we do this via the API? Taking a look at 
what is generated by foreman:

2016-09-15T21:46:41 [app] [I] Started PATCH 
"/templates/provisioning_templates/22-Kickstart%20RHEL%20default" for 
127.0.0.1 at 2016-09-15 21:46:41 -0400

2016-09-15T21:46:42 [app] [I] Processing by 
ProvisioningTemplatesController#update as */*

2016-09-15T21:46:42 [app] [I]   Parameters: {"utf8"=>"✓", 
"authenticity_token"=>"RMIiR7+Dn1xqM8EL0IvjeLwKrFvBGkDm+x36bAU1K5k=", 
"provisioning_template"=>{"name"=>"Kickstart RHEL default", "default"=>"1", 
"template"=>"SNIP", "audit_comment"=>"", "snippet"=>"0", 
"template_kind_id"=>"4", "operatingsystem_ids"=>[""], 
"template_combinations_attributes"=>{"1473990106406"=>{"hostgroup_id"=>"1", 
"environment_id"=>"", "_destroy"=>"false"}}, "location_ids"=>["", "1"], 
"organization_ids"=>["", "2"]}, "preview_host_id"=>"2", "mode"=>"ruby", 
"keybinding"=>"Default", "id"=>"22-Kickstart RHEL default"}

It *looks* like this might be done via template_combinations_attributes and 
a PATCH method. Neither of these are documented in the API calls 
at https://theforeman.org/api/1.12/index.html. Does anybody know? Likewise 
for assigning a template to an OS...

On Wednesday, July 16, 2014 at 1:16:11 PM UTC-4, Greg Sutcliffe wrote:
>
> Good stuff! Yeah, that feature doesn't get enough coverage, and it's 
> very useful :) 
>

-- 
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.

[foreman-users] Troubles with calling /api/v2/discovered_hosts/:id/refresh_facts

['Konstantin Orekhov' via Foreman users]

Hello all!

I'm getting the following error when I try to refresh facts of the 
discovered hosts through actual API:

$ curl -kSs -H "Content-Type: application/json" -H 
"Accept:application/json" -u admin:$PASSWORD 
https://localhost/api/v2/discovered_hosts/mac008cfaed69c8/refresh_facts | 
jq '.'
{
  "status": "404",
  "error": "Not Found"
}

This results in these messages in production.log:

2016-09-15 17:14:56 [app] [I] Started GET 
"/api/v2/discovered_hosts/mac008cfafcd2f4/refresh_facts" for 127.0.0.1 at 
2016-09-15 17:14:56 -0700
2016-09-15 17:14:56 [app] [F]
 | ActionController::RoutingError (No route matches [GET] 
"/api/v2/discovered_hosts/mac008cfafcd2f4/refresh_facts"):
 |   actionpack (4.2.5.1) 
lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
 |   actionpack (4.2.5.1) 
lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
 |   railties (4.2.5.1) lib/rails/rack/logger.rb:38:in `call_app'
 |   railties (4.2.5.1) lib/rails/rack/logger.rb:22:in `call'
 |   actionpack (4.2.5.1) 
lib/action_dispatch/middleware/request_id.rb:21:in `call'
 |   rack (1.6.2) lib/rack/methodoverride.rb:22:in `call'
 |   rack (1.6.2) lib/rack/runtime.rb:18:in `call'
 |   activesupport (4.2.5.1) 
lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
 |   actionpack (4.2.5.1) lib/action_dispatch/middleware/static.rb:116:in 
`call'
 |   rack (1.6.2) lib/rack/sendfile.rb:113:in `call'
 |   railties (4.2.5.1) lib/rails/engine.rb:518:in `call'
 |   railties (4.2.5.1) lib/rails/application.rb:165:in `call'
 |   railties (4.2.5.1) lib/rails/railtie.rb:194:in `public_send'
 |   railties (4.2.5.1) lib/rails/railtie.rb:194:in `method_missing'
 |   rack (1.6.2) lib/rack/urlmap.rb:66:in `block in call'
 |   rack (1.6.2) lib/rack/urlmap.rb:50:in `each'
 |   rack (1.6.2) lib/rack/urlmap.rb:50:in `call'
 |   
/usr/share/passenger/phusion_passenger/rack/thread_handler_extension.rb:74:in 
`process_request'
 |   
/usr/share/passenger/phusion_passenger/request_handler/thread_handler.rb:141:in 
`accept_and_process_next_request'
 |   
/usr/share/passenger/phusion_passenger/request_handler/thread_handler.rb:109:in 
`main_loop'
 |   /usr/share/passenger/phusion_passenger/request_handler.rb:455:in 
`block (3 levels) in start_threads'
 |   logging (1.8.2) lib/logging/diagnostic_context.rb:323:in `call'
 |   logging (1.8.2) lib/logging/diagnostic_context.rb:323:in `block in 
create_with_logging_context'
 |

WebUI does not seem to have any problems with that though. I see the 
following in production.log:

2016-09-15 17:14:45 [app] [I] Started GET 
"/discovered_hosts/mac008cfafcd2f4" for 127.0.0.1 at 2016-09-15 17:14:45 
-0700
2016-09-15 17:14:45 [app] [I] Processing by DiscoveredHostsController#show 
as HTML
2016-09-15 17:14:45 [app] [I]   Parameters: {"id"=>"mac008cfafcd2f4"}
2016-09-15 17:14:45 [app] [I]   Rendered 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_discovery-6.0.0/app/views/discovered_hosts/show.html.erb
 
within layouts/application (6.9ms)
2016-09-15 17:14:45 [app] [I]   Rendered 
layouts/_application_content.html.erb (0.5ms)
2016-09-15 17:14:45 [app] [I]   Rendered home/_user_dropdown.html.erb 
(2.1ms)
2016-09-15 17:14:45 [app] [I] Read fragment views/tabs_and_title_records-5 
(0.4ms)
2016-09-15 17:14:45 [app] [I]   Rendered home/_topbar.html.erb (6.7ms)
2016-09-15 17:14:45 [app] [I]   Rendered layouts/base.html.erb (8.0ms)
2016-09-15 17:14:45 [app] [I] Completed 200 OK in 85ms (Views: 16.7ms | 
ActiveRecord: 4.9ms)

Any ideas what I'm doing wrong here? I think I do have proper API call, but 
clearly something is missing:

$ curl -kSs -H "Content-Type: application/json" -H 
"Accept:application/json" -u admin:$PASSWORD https://localhost/api/v2 | jq 
'.' | grep refresh_facts
  "Refreshing the facts of a discovered host": 
"/api/v2/discovered_hosts/:id/refresh_facts",

I have this issue on both 1.11.2 and 1.12.2.

Thanks in advance!

-- 
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.

[foreman-users] Re: Tip: Passing puppetlabs/firewall configuration through Foreman web interface

[Joseph Cunningham]

I know this is an old thread, but following this guide, I'm getting the 
following error when attempting to run puppet agent -t on the client:

Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
no implicit conversion of nil into Hash at 
/etc/puppet/environments/production/modules/firewall_custom/manifests/init.pp:12
 
on node omdapps06.mil.state.or.us
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run


Gist of init.pp is here:
https://gist.github.com/joeywas/d8f0d676b9ef3beb54ae0d617ef69633



On Thursday, April 17, 2014 at 12:49:46 PM UTC-7, Race Boyer wrote:
>
> Thank you very much, this helped a great deal
>
> On Tuesday, November 5, 2013 6:58:47 PM UTC-6, Jack Watroba wrote:
>>
>> We're using the puppetlabs/firewall module and we wanted a way to pass 
>> all of our firewall data through the Foreman web UI for ease of quickly 
>> adding/deleting firewall rules. This is what we came up with, in case 
>> anyone else is interested. 
>>
>>
>> Created a new module: ex. custom_firewall (init.pp, pre.pp, post.pp)
>> *init.pp:*
>>
>> class custom_firewall($firewall_data = false) {
>>
>>   include custom_firewall::pre
>>   include custom_firewall::post
>>   include firewall
>>
>>   resources { "firewall":
>>   purge => true
>>   }
>>
>>   Firewall {
>> before  => Class['custom_firewall::post'],
>> require => Class['custom_firewall::pre'],
>>   }
>>
>>   if $firewall_data != false {
>> create_resources('firewall', $firewall_data)
>>   }
>>
>> }
>>
>>
>> *pre.pp (* Include any default firewall rules you want here that will 
>> load every time regardless. ex. icmp)*:*
>>
>> class custom_firewall::pre {
>>
>>   Firewall {
>> require => undef,
>>   }
>>
>>firewall {'000 accept all icmp':
>> proto   => 'icmp',
>> action  => 'accept',
>>   }
>>
>> }
>>
>>
>> *post.pp *(final line of iptables):
>>
>> class custom_firewall::post {
>>   firewall { '999 drop all':
>> proto   => 'all',
>> action  => 'drop',
>> before  => undef,
>>   }
>> }
>>
>>
>> Now, import the classes into foreman. Under the custom_firewall class, 
>> set the $firewall_data param to yaml. At this point you can pass in any 
>> additional firewall rules via yaml. 
>> ex. 
>> "007 accept tcp tomcat requests": 
>> port: 
>>   - "8080"
>>   - "8009"
>>   - "8999"
>> proto: tcp
>> action: accept
>>
>>
>> Hope this helps. 
>>
>

-- 
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] Validation failed: Description has already been taken, Title has already been taken

[David LeVene]

Hi Tomer,

Thanks for the info. Glad I could help fix a bug for a great product.

Keep up the fantastic work.

Cheers
David

On 14 Sep 2016 4:25 pm, "Tomer Brisker"  wrote:

> Hi David,
>
> Glad to hear this fixed the issue.
>
> When a host reports facts that don't match its current settings, such as a
> different OS, that host will be updated with the new values.
> This is expected behaviour - https://theforeman.org/
> manuals/1.13/index.html#creating-hosts-in-foreman-with-facts
> The 7.2 OS was most likely created by the incorrect fact parsing ignoring
> the second part of the minor version.
>
> Thanks for your help!
> Tomer
>
>
> On Wed, Sep 14, 2016 at 5:01 AM, David LeVene 
> wrote:
>
>> Hi Tomer,
>>
>> Thanks, It works as expected - but what I did notice is that with this
>> change when I've got the Operating systems defined as noted in a previous
>> post, a host was moved from CentOS 7.2 -> CentOS 7.2.1511. What happens
>> when users Patch a host and it goes to the next CentOS version of 7.3.?
>> I presume it will create a new host with that major/minor version.
>>
>> If users have something similar configured, this patch may move hosts to
>> a different OS without their knowledge - This host was the original foreman
>> host, so I suspect it checked in and configured its self before I manually
>> created the other OS's, hence it was working and not reporting errors
>>
>>
>> Results of same host after updating the code:
>>
>> 2016-09-14 11:13:34 [app] [I] Processing by
>> Api::V2::HostsController#facts as JSON
>> 2016-09-14 11:13:34 [app] [I]   Parameters: {"facts"=>"[FILTERED]",
>> "name"=>"testing-dlevene", "certname"=>"testing-dlevene", "apiv"=>"v2",
>> :host=>{"name"=>"testing-dlevene",
>>  "certname"=>"testing-dlevene"}}
>> 2016-09-14 11:13:34 [app] [I] Import facts for 'testing-dlevene'
>> completed. Added: 0, Updated: 6, Deleted 0 facts
>> 2016-09-14 11:13:34 [app] [I] Completed 201 Created in 434ms (Views:
>> 5.5ms | ActiveRecord: 109.2ms)
>>
>> Let me know if there is any further testing you require on my end.
>>
>> Regards
>> David
>>
>>
>> On 13 September 2016 at 18:32, Tomer Brisker  wrote:
>>
>>> Hi David,
>>>
>>> The fix is ready for testing in https://github.com/theforem
>>> an/foreman/pull/3836
>>>
>>> Thanks
>>> Tomer
>>>
>>> On Tue, Sep 13, 2016 at 3:11 AM, David LeVene 
>>> wrote:
>>>
 Hi Tomer,

 Great that you've been able to reproduce it.

 Yep - let me know when I can test it.

 Regards
 David

 On 12 September 2016 at 05:07, Tomer Brisker 
 wrote:

> Thank you for the information David!
>
> I have managed to reproduce the issue locally and will work to resolve
> it.
> It would seem that indeed the cause lies with the OS that has a
> non-numeric minor version (2.1511).
> I will let you know once I have a pull request ready to fix the issue
> so you may test it.
>
> Have a nice week,
> Tomer
>
> On Fri, Sep 9, 2016 at 5:39 AM, David LeVene 
> wrote:
>
>> Hi Tomer,
>>
>> I've just reverted to a database backup which has the issue - and
>> here is the information you requested
>>
>> foreman=# select * from operatingsystems;
>>  id | major |  name  | minor  | nameindicator |
>> created_at | updated_at | release_name |  type
>> |  description  | hosts_count | hostgroups_count | password_hash
>> | title
>> +---+++---+-
>> ---++--+
>> +---+-+-
>> -+---+---
>>   3 | 7 | CentOS | 2  |   | 2016-01-13
>> 02:34:09.557672 | 2016-01-13 02:34:09.557672 |  | Redhat
>> |   |   1 |0 | SHA256
>> |
>> CentOS 7.2
>>   1 | 7 | CentOS | 1  |   | 2015-12-07
>> 03:23:39.087921 | 2015-12-16 06:38:11.025759 |  | Redhat |
>> CentOS Linux 7.1.1503 |   0 |0 | SHA256|
>> CentOS Linux 7.1.1503
>>   2 | 7 | CentOS | 2.1511 |   | 2015-12-16
>> 07:40:19.21053  | 2016-01-13 02:21:43.201217 |  | Redhat |
>> CentOS Linux 7.2.1511 |   6 |0 | SHA256|
>> CentOS Linux 7.2.1511
>> (3 rows)
>>
>>
>> {"name"=>"CentOS", "family"=>"RedHat", "release"=>{"major"=>"7",
>> "minor"=>"2", "full"=>"7.2.1511"}, "lsb"=>{"distcodename"=>"Core",
>> "distid"=>"CentOS", "distdescription"=>"CentOS Linux release 7.2.1511
>> (Core) ", "release"=>":core-4.1-amd64:core-4.1-noarch",
>> "distrelease"=>"7.2.1511", "majdistrelease"=>"7", 
>> "minordistrelease"=>"2"}}
>>
>> 2016-09-09 12:05:52 [app] [I] Import facts for 'testing completed.
>> Added: 0, Upd

[foreman-users] check foreman definitions into git?

[Thomas Cheng]

Is there a project to check foreman configs -- system variables, operating 
systems, networks, hosts, hostgroups, etc -- into git for version control?  
sync back from git to foreman (write operation) is optional as that is kind 
of dangerous operation which could affect all hosts defined.


-- 
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] install doesn't register itself as host

[Stephen Benjamin]

- Original Message -
> From: "Jorick Astrego" 
> To: foreman-users@googlegroups.com
> Sent: Thursday, September 15, 2016 8:15:09 AM
> Subject: [foreman-users] install doesn't register itself as host
> 
> Hi,
> 
> I'm currently installing katello 3.1 with the foreman 1.12 and when I
> run the setup I think it used to register itself (been a while), but now
> it doesn't.
> 
> How can I get it to register as host from install?
> 

The installer by default sets up the katello as a puppet client,
and that's normally how it shows up as a host (usually within 30
minutes of the install completing).

However, it doesn't have an org or location set, are you
sure it's not just hidden by your current context? You can
use the selector in the upper left corner to change to
any context.

- stephen


> 
> 
> 
> Met vriendelijke groet, With kind regards,
> 
> Jorick Astrego
> 
> Netbulae Virtualization Experts
> 
> 
> 
>   Tel: 053 20 30 270  i...@netbulae.euStaalsteden 4-3A
> KvK 08198180
>   Fax: 053 20 30 271  www.netbulae.eu 7547 TA Enschede
> BTW NL821234584B01
> 
> 
> 
> --
> 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.

[foreman-users] Re: Next Foreman Community Demo - Thu 15 Sep 3pm [GMT+1]

[Greg Sutcliffe]

If you couldn't join us live, the recording of this demo is now available.
Thanks as ever to our presenters for an packed demo! Below is the agenda
and timecodes for the various parts:

Community updates/stats - https://youtu.be/GFNPHypFhl4?t=0
Roles for Orgs and Locs - https://youtu.be/GFNPHypFhl4?t=288
RAM field for libvirt, ovirt - https://youtu.be/GFNPHypFhl4?t=732
Ansible playbooks with remote execution - https://youtu.be/GFNPHypFhl4?t=896
Infoblox support in installer - https://youtu.be/GFNPHypFhl4?t=1350
Manual Applicability Generation in Katello -
https://youtu.be/GFNPHypFhl4?t=1665
Applicable Packages api - https://youtu.be/GFNPHypFhl4?t=1747
Auto-generate update descriptions - https://youtu.be/GFNPHypFhl4?t=1856
CCV UI upgrade indicators - https://youtu.be/GFNPHypFhl4?t=2087
Content - RHEL 7 container in an Atomic Host -
https://youtu.be/GFNPHypFhl4?t=2215
OSTree Branch Search - https://youtu.be/GFNPHypFhl4?t=2440
Katello puppet 3 to 4 upgrade via installer -
https://youtu.be/GFNPHypFhl4?t=2545
Omit value checkbox - https://youtu.be/GFNPHypFhl4?t=3032
Rewrite of MS DHCP provider - https://youtu.be/GFNPHypFhl4?t=3151

As ever, feel free to dive in with questions here, on the IRC channel, or
on the YouTube video. Thanks for watching!

Greg

-- 
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.

[foreman-users] Cannot get "Run Puppet" to work in GUI

[Scott Mckeown]

I have read just about every doc I can find on how to get the "run puppet" 
button to work in the web ui with no luck.
I am trying to use the  mcollective provider.

The foreman documentation section only shows a few lines in a couple of 
files to change. 
I have made all of the stated changes, still not working. 

Is there a better guide to get this working?

Thanks
Scott

-- 
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.

[foreman-users] install doesn't register itself as host

[Jorick Astrego]

Hi,

I'm currently installing katello 3.1 with the foreman 1.12 and when I
run the setup I think it used to register itself (been a while), but now
it doesn't.

How can I get it to register as host from install?





Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts 



Tel: 053 20 30 270  i...@netbulae.euStaalsteden 4-3A
KvK 08198180
Fax: 053 20 30 271  www.netbulae.eu 7547 TA Enschede
BTW NL821234584B01



-- 
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] Applicable vs Installable errata

[Walden Raines]

Hey Edgars,

Sorry for the delay in my response but I have two more questions.

1.  Does the kernel errata mentioned below show up as applicable or installable 
on the errata list page (/errata)?
2.  Just making sure everything is plugged in but you did publish a new version 
of the CV after creating the filter(s), correct?

Thanks,
Walden


- Original Message -
From: "Edgars M." 
To: "Foreman users" 
Sent: Tuesday, September 13, 2016 3:31:23 AM
Subject: Re: [foreman-users] [Katello] Applicable vs Installable errata

Hi Walden

I took one content host and compared web gui and API results, here is what 
I see:

WebGUI:




And this is if I call API:


[em@katello.local ~]$ curl 
https://katello.local/api/v2/hosts/291/errata?errata_restrict_applicable=true 
-u em | python -m json.tool | grep errata_id
Enter host password for user 'em':
  % Total% Received % Xferd  Average Speed   TimeTime Time 
 Current
 Dload  Upload   Total   SpentLeft 
 Speed
100 593570 593570 0  74973  0 --:--:-- --:--:-- --:--:-- 
74945
"errata_id": "RHSA-2016:1664",
"errata_id": "RHSA-2015:1623",
"errata_id": "RHBA-2015:1827",
"errata_id": "RHBA-2016:1185",
"errata_id": "RHBA-2015:1466",
"errata_id": "RHSA-2015:1272",
"errata_id": "RHSA-2016:1406",
"errata_id": "RHSA-2016:0855",
"errata_id": "RHSA-2015:2636",
"errata_id": "RHBA-2015:1992",
"errata_id": "RHSA-2016:0494",
"errata_id": "RHBA-2016:0150",
"errata_id": "RHSA-2016:0715",


[em@katello.local ~]$ curl 
https://katello.local/api/v2/hosts/291/errata?errata_restrict_installable=true 
-u em | python -m json.tool | grep errata_id
Enter host password for user 'em':
  % Total% Received % Xferd  Average Speed   TimeTime Time 
 Current
 Dload  Upload   Total   SpentLeft 
 Speed
100 593570 593570 0  15410  0 --:--:--  0:00:03 --:--:-- 
15409
"errata_id": "RHSA-2016:1664",
"errata_id": "RHSA-2015:1623",
"errata_id": "RHBA-2015:1827",
"errata_id": "RHBA-2016:1185",
"errata_id": "RHBA-2015:1466",
"errata_id": "RHSA-2015:1272",
"errata_id": "RHSA-2016:1406",
"errata_id": "RHSA-2016:0855",
"errata_id": "RHSA-2015:2636",
"errata_id": "RHBA-2015:1992",
"errata_id": "RHSA-2016:0494",
"errata_id": "RHBA-2016:0150",
"errata_id": "RHSA-2016:0715",



As you can see result is the same. Please file a bug if you know what is 
wrong.


Edgars



pirmdiena, 2016. gada 12. septembris 17:15:14 UTC+2, Walden Raines rakstīja:
>
> Hey Edgars, 
>
> The documentation is correct so if you are seeing non-installable errata 
> show up on that page then it is a bug. 
>
> Out of curiosity, if you go to 
> /api/v2/hosts/2/errata?errata_restrict_applicable=true do you see a list of 
> errata without kernel updates? 
>
> I think I see what the bug is and am happy to file it unless you want to. 
>
> Thanks, 
> Walden 
>
> - Original Message - 
> From: "Edgars M." > 
> To: "Foreman users" > 
> Sent: Monday, September 12, 2016 10:17:06 AM 
> Subject: [foreman-users] [Katello] Applicable vs Installable errata 
>
> Hi 
>
> I have question regarding Applicable and Installable errata on content 
> hosts. This is from documentation: 
>
> With regard to Content Hosts, Errata is divided into two distinct 
> > classifications depending on whether or not the Errata is present in the 
> > Content Host’s Lifecycle Environment and Content View: 
> > 
> >- Applicable: the errata applies to one or more Content Hosts 
> >- Installable: the errata applies to one or more Content Hosts and is 
> >present in the Content Host’s Lifecycle Environment and Content View 
> > 
> > 
> As far as I understand errata which is filtered out of Content View (not 
> present in CV) is not Installable errata, but is Applicable errata. Am I 
> right? But the thing is - when I go to Content Host -> Errata, where I can 
> see Installable errata I see all erratas including those I have filtered 
> out of CV. Is it a bug and GUI shows Applicable errata instead of 
> Installable? Or bug in documentation? 
>
> For example, I have filtered out all kernel packages from CV. So these 
> packages should be Applicable but not Installable, but here is what I see: 
>
> <
> https://lh3.googleusercontent.com/-IB4y-cgbTQo/V9a4ShuQ7JI/ADM/43cr_J6ORWo6LjwIjyPLXgvgioY4Iey3QCLcB/s1600/errata.JPG>
>  
>
>
>
> I see all kernel packages as installable, although I have filtered them 
> out 
> and when I do yum check-update they do not appear as available update. 
>
>
> Katello 

Re: [foreman-users] Ubuntu Desktop-Unattended installation

[Dominic Cleal]

On 15/09/16 13:11, Akash Kaveti wrote:
> Hello,
> 
> I am trying to install ubuntu desktop, but I have succeeded. I have
> tried different mirrors but I ended up with Ubuntu server.
> Would be very much greatful, if any one can help.

Try updating the package list (via tasksel) in the preseed file, i.e.
the line at
https://github.com/theforeman/community-templates/blob/develop/preseed/provision.erb#L132.
Edit your preseed via Foreman's provisioning templates UI.

See
https://help.ubuntu.com/lts/installation-guide/amd64/apbs04.html#preseed-pkgsel
for a list of standard tasks.

-- 
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: "No root file system is defined" error using preseed atomic partitioning scheme

[Akash Kaveti]

Thank you so much for the response. :)

On Wednesday, September 14, 2016 at 4:40:14 PM UTC+2, Hauke Behrens wrote:
>
>
>
> On 09/14/2016 03:04 PM, Akash Kaveti wrote: 
> > Hello Again, 
> > 
> > It is working now, I have check the syslog, the device I am trying to 
> > install is not there it seems, 
> > so I gave /dev/sdb, it is working now. 
>
> Glad I could help. :-) 
>
>
> > It is working for the current host, but what about the other hosts, Why 
> > cant I use "/d-i partman/early_command string debconf-set 
> > partman-auto/disk "$(list-devices disk | head -n1)/" 
>
> It's always hard to guess what device is getting used. 
> If you have a usb-stick plugged-in with the e.g. a formean-boot-iso, 
> that might be /dev/sda and your "real" hard-disk might be /dev/sdb/. 
>
> In that case "head -n2" will do the trick. 
> When using raid-devices this might be different too. 
>
> Also check out this thread: 
>
> https://groups.google.com/forum/#!topic/foreman-users/uKuY4YJuy7E 
>
> Hauke 
>
> -- 
> bytemine GmbH, Im Technologiepark 4, 26129 Oldenburg 
> Support: 0441-309197-42 --- Vertrieb: 0441-309197-69 
> GF: Felix Kronlage -- AG in Oldenburg -- HRB 203 940 
> https://www.bytemine.net --- VAT-Number: DE267286778 
>

-- 
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.

[foreman-users] Ubuntu Desktop-Unattended installation

[Akash Kaveti]

Hello,

I am trying to install ubuntu desktop, but I have succeeded. I have tried 
different mirrors but I ended up with Ubuntu server.
Would be very much greatful, if any one can help.

Thank you.

-- 
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.

[foreman-users] getting smart_class_variables via API

[Adam Winberg]

I'm trying to retrieve values for a specific smart_class_variable via API,
but not getting any results. The user I am using to do this has the
'viewer' role which has worked in the past, but somewhere along the line it
stopped working - unfortunately I cant say which update exactly which
introduced the change.

I am now running on 1.12.2.

This is my request:

GET /api/smart_class_parameters/1426

A simple 'GET'. Results in:

{"message":"Smart class parameter not found by id '1426'"}


I have tried to add numerous types of permission filters to my user to no
luck. The only way I can get it to work is to tick the 'administrator' box
for the user.

Am I missing something here? Is it a bug or am I just doing it wrong?

Regards
Adam W

-- 
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] Docker Plugin Permission denied

[Thomas Bendler]

Hi Adam,

thanks for the hint, I'll try this as well.

Regards Thomas

2016-09-12 9:12 GMT+02:00 Adam Ruzicka :

> Hi,
>
> Set selinux to permissive solved the problem.
>
>
> Disabling SELinux solves the issue, however there are more sophisticated
> ways of dealing with this. The root cause is SELinux not allowing the web
> server process to open outgoing connections to ports not marked as
> http_port_t. If you don't care about SELinux at all and you're ok with
> having it set to permissive, feel free to stop reading here.
>
> You could either allow it to open outgoing connections anywhere by setting
> a SELinux bool
> setsebool -P httpd_can_network_connect 1
>
> Or by marking the docker port as http_port_t
> semanage port -a -t http_port_t -p tcp $DOCKER_PORT
>
> Adam
>
> On Thu, Sep 8, 2016 at 5:54 PM, Thomas Bendler 
> wrote:
>
>> Hi Adam,
>>
>> thanks a lot, this was indeed the problem. Set selinux to permissive
>> solved the problem.
>>
>> Regards Thomas
>>
>> 2016-09-08 11:07 GMT+02:00 Adam Ruzicka :
>>
>>> Hello,
>>> it might be a SELinux issue. Could you check /var/log/audit/audit.log
>>> for lines containing the port number? If it is a SELinux issue you should
>>> see something like this there
>>>
>>> type=AVC msg=audit(1473324981.209:1007): avc:  denied  { name_connect }
>>> for  pid=4380 comm="diagnostic_con*" dest=4243
>>> scontext=system_u:system_r:passenger_t:s0 
>>> tcontext=system_u:object_r:unreserved_port_t:s0
>>> tclass=tcp_socket
>>>
>>>
>>> Adam
>>>
>>> On Thu, Sep 8, 2016 at 10:43 AM, Thomas Bendler <
>>> thomas.bend...@gmail.com> wrote:
>>>
 Hi @all,

 I try to setup the docker plugin on foreman but didn't get it up and
 running so far. I have two CentOS 7 boxes, one running foreman and one
 running docker. I've modified the docker sysconfig file to start docker
 with the remote API:

 thbe@docker1.domain.local ~$ curl -XGET http://localhost:4243/version

 {"Version":"1.10.3","ApiVersion":"1.22","GitCommit":"d381c64
 -unsupported","GoVersion":"go1.6.3","Os":"linux","Arch":"amd
 64","KernelVersion":"3.10.0-327.28.2.el7.x86_64","BuildTime"
 :"2016-08-04T13:21:17.566257784+00:00","PkgVersion":"docker-
 common-1.10.3-46.el7.centos.10.x86_64"}

 thbe@docker1.domain.local ~$

 [...]

 thbe@manage1.domain.local ~$ curl -XGET http://docker1.domain.local:42
 43/version

 {"Version":"1.10.3","ApiVersion":"1.22","GitCommit":"d381c64
 -unsupported","GoVersion":"go1.6.3","Os":"linux","Arch":"amd
 64","KernelVersion":"3.10.0-327.28.2.el7.x86_64","BuildTime"
 :"2016-08-04T13:21:17.566257784+00:00","PkgVersion":"docker-
 common-1.10.3-46.el7.centos.10.x86_64"}

 thbe@manage1.domain.local ~$

 It work from the docker host and the foreman host, so far so good.
 Checking if additional operations work looks also good:

 thbe@manage1.domain.local ~$ curl -XPOST http://docker1.domain.local:42
 43/images/create?fromImage=centos:7

 {"status":"Trying to pull repository docker.io/library/centos ... "}

 {"status":"Pulling from docker.io/library/centos","id":"7"}

 {"status":"Pulling fs layer","progressDetail":{},"id":"8d30e94188e7"}

 {"status":"Downloading","progressDetail":{"current":526329,"
 total":70591526},"progress":"[\u003e
 ] 526.3 kB/70.59 MB","id":"8d30e94188e7"}

 [...]

 {"status":"Extracting","progressDetail":{"current":70591526,
 "total":70591526},"progress":"[==\u003e]
 70.59 MB/70.59 MB","id":"8d30e94188e7"}

 {"status":"Pull complete","progressDetail":{},"id":"8d30e94188e7"}

 {"status":"Pull complete","progressDetail":{},"id":"8d30e94188e7"}

 {"status":"Digest: sha256:2ae0d2c881c7123870114fb
 9cc7afabd1e31f9888dac8286884f6cf59373ed9b"}

 {"status":"Status: Downloaded newer image for docker.io/centos:7"}

 thbe@manage1.domain.local ~$

 But when I create the compute resource in foreman (without
 user/password/email), I get:

 Permission denied - connect(2) for 192.168.XXX.XXX:4243 (Errno::EACCES)

 ​If I use my Docker Hub credentials for user/password/email, I got the
 same error:

 Permission denied - connect(2) for 192.168.XXX.XXX:4243 (Errno::EACCES)

 Anyone any idea how can fix this?​

 ​Regards Thomas​
 --
 Linux ... enjoy the ride!

 --
 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

Re: [foreman-users] Puppet Server Stop After OS Update

[Dominic Cleal]

On 14/09/16 18:23, Marcio Costa wrote:
> Hello. Im using Centos 7.2 and after an update, the puppet servers stop
> loading.  I have this error:

It's likely that you updated to Puppet Server 2.6.0.

> Sep 14 14:13:15 java: Exception in thread "main"
> *java.lang.IllegalArgumentException: service
> :puppetlabs.trapperkeeper.services.status.status-service/status-service
> does not appear in configuration*

Add to /etc/puppetlabs/puppetserver/conf.d/web-routes.conf:

"puppetlabs.trapperkeeper.services.status.status-service/status-service":
"/status"

> I have modified the file *web-routes.conf.erb* and added the text:
> (https://github.com/theforeman/puppet-puppet/blob/master/templates/server/puppetserver/conf.d/web-routes.conf.erb#L17-L21)
[..]
> Still not working.   I appreciate any help.
> Thank you.

The file I'm guessing you might have edited (hard to say without knowing
the full path) is part of the Foreman installer. Did you _run_ the
Foreman installer after editing it?

You would need to run it with --puppet-server-puppetserver-version=2.6.0
to apply this 2.6-style configuration.

-- 
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] Could not find kernel image: linux

[Lukas Zapletal]

> And now I'm just stuck in a loop if I enter kickstart_cmdline again. It
> just reinstalls everything and reboots, landing me back at the boot: prompt.
> 
> I'm sure this is user error but I'm not sure where or what to look for.

It is, but its not your fault :-)

You happened to clone/update git in a short few days window when there
was a typo, DEFAULT linux is incorrect, it should read something else
(the first LABEL entry).

Synchronization of Foreman templates from community-templates in
713be41b fixes it, but git merge won't help you - you need to delete the
Kickstart PXELinux template and re-seed your database in order to have
it recreated.

As an alternative, you can use foreman templates plugin to reseed your
templates:

https://github.com/theforeman/foreman_templates

Make sure you give it an empty prefix, otherwise you will end up with
zillions of copies prefixed with "Community" and your old one will be
unchanged.

Beware, this will overwrite all your templates to match our upstream!
Seeding is perhaps safer for you, but this is a good exercise, because
people tend to upgrade Foreman from git or RPM but templates are usually
unchanged for years and then we have reports that something does not
work (because of very outdated template).

-- 
Later,
 Lukas #lzap Zapletal

-- 
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: Unattended_Url versus firewalls

[Lukas Zapletal]

> Does this setting on the Proxy make it's way into the Boot Disks?  That's 
> how we have to provision at the moment.  We're finding the central 
> unattended_url and foreman_url settings are used when creating the ISO 
> images.  We can't use DHCP/PXE provisioning at all.  Some network zones 
> don't even have DNS, so we have to use IP addresses to point at 
> Satellite/Proxy.

Yes, use Host/Full host or special Subnet image in order to proxy through.

-- 
Later,
 Lukas #lzap Zapletal

-- 
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.