[foreman-users] Re: Unable to install foreman-proxy 1.12

[Brandon]

Seems these aren't available in the epel anymore?  So find somewhere you 
can install them from:
rubygem-rack-test-0.6.1-1.el6.noarch.rpm   which is a dependency for ->
rubygem-sinatra-1.0-2.el6.noarch.rpm


On Tuesday, June 6, 2017 at 7:40:13 AM UTC-4, Flamarion Jorge wrote:
>
> I've got the same issue, if someone know how to fix, it will be very 
> helpful.
>
> Yes, I need to install The Foreman 1.12 on RHEL6 :)
>
> Thanks,
>
> Flamarion Jorge
>
>
> On Tuesday, February 21, 2017 at 9:24:03 AM UTC+1, Neeraj Harikrishnan 
> wrote:
>>
>>
>> I am having trouble installing (Reinstalling) Foreman-proxy 
>>
>> The puppet script foreman-installer does not seem to take care of all 
>> dependencies. I am down to one dependency that I am unable to install 
>>
>> [root@ yum.repos.d]# yum install foreman-proxy
>>
>> Loaded plugins: fastestmirror, protectbase, security
>>
>> Setting up Install Process
>>
>> Loading mirror speeds from cached hostfile
>>
>>  * centosplus: mirror.cs.vt.edu
>>
>>  * contrib: distro.ibiblio.org
>>
>>  * extras: centos.mirrors.hoobly.com
>>
>> 0 packages excluded due to repository protections
>>
>> Resolving Dependencies
>>
>> --> Running transaction check
>>
>> ---> Package foreman-proxy.noarch 0:1.12.4-1.el6 will be installed
>>
>> --> Processing Dependency: rubygem(sinatra) for package: 
>> foreman-proxy-1.12.4-1.el6.noarch
>>
>> --> Finished Dependency Resolution
>>
>> Error: Package: foreman-proxy-1.12.4-1.el6.noarch (foreman)
>>
>>Requires: rubygem(sinatra)
>>
>>  You could try using --skip-broken to work around the problem
>>
>>  You could try running: rpm -Va --nofiles --nodigest
>>
>>
>>
>> [root@ yum.repos.d]# rpm -qa |grep sinatra
>>
>> ruby193-rubygem-sinatra-1.3.2-12.sc1.el6.noarch
>>
>> sclo-ror42-rubygem-sinatra-1.4.6-4.el6.noarch
>>
>>
>> [root@saba3 yum.repos.d]# gem list
>>
>>
>> *** LOCAL GEMS ***
>>
>>
>> ansi (1.4.3)
>>
>> bundler (1.5.2)
>>
>> bundler_ext (0.3.0)
>>
>> clamp (1.0.0)
>>
>> docker-api (1.33.0)
>>
>> excon (0.54.0)
>>
>> fast_gettext (1.1.0)
>>
>> ffi (1.0.9)
>>
>> gettext (3.2.2)
>>
>> gettext-setup (0.13)
>>
>> gssapi (1.1.2)
>>
>> hashie (2.0.5)
>>
>> hiera (3.2.2)
>>
>> highline (1.6.21)
>>
>> json (1.4.6)
>>
>> json_pure (1.8.6)
>>
>> kafo (0.9.2)
>>
>> kafo_parsers (0.1.6, 0.1.2)
>>
>> kafo_wizards (0.0.1)
>>
>> little-plugger (1.1.3)
>>
>> locale (2.1.2)
>>
>> logging (1.8.2)
>>
>> multi_json (1.10.1)
>>
>> net-http-persistent (2.9.4)
>>
>> passenger (4.0.18)
>>
>> powerbar (1.0.17)
>>
>> rack (1.6.5, 1.1.0)
>>
>> rack-protection (1.5.3)
>>
>> rake (0.8.7)
>>
>> rdoc (3.12)
>>
>> rkerberos (0.1.3)
>>
>> rubyipmi (0.10.0)
>>
>> sinatra (1.0)
>>
>> text (1.3.1)
>>
>> thor (0.18.1)
>>
>> tilt (2.0.6)
>>
>>
>> Any help will be greatly appreciated.
>>
>>
>> Thanks 
>> Neeraj
>>
>

-- 
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: Foreman and Katello EL6 Deprecations

[Michael Bassler]

>
> We will be working on a strategy to help users migrate their EL6 
> installations to EL7 and please reach out to us if you have questions 
> regrading this.
>

I have an existing EL6 installation that I wish ti migrate to EL7, is there 
some documentation that I can look at work someone specifically I should 
talk to in order to get an idea on what this process is. 

Thank You
Michael 

On Thursday, December 1, 2016 at 7:31:49 AM UTC-8, Eric Helms wrote:
>
> All,
>
> There have been comments and release notes around EL6 support but I wanted 
> to take the time to make sure users see the information and are aware of 
> the deprecations.
>
> As of Foreman 1.13, EL6 was officially dropped as a supported operating 
> system. An official repository of EL6 builds exists for 1.13 extending the 
> life of Foreman on EL6 for that release and that release alone.
>
> The Katello 3.2 release is the last release stream that will have support 
> for EL6. For Katello 3.3 and beyond, only EL7 releases will be made 
> available. We will be working on a strategy to help users migrate their EL6 
> installations to EL7 and please reach out to us if you have questions 
> regrading this.
>
> Further, we recommend ALL new installs of 1.13 or 3.2 be done on an EL7 
> box.
>
> To reiterate, Foreman 1.14 and Katello 3.2 will NOT be provided on EL6. 
> The 1.13 and 3.2 streams will continue to receive updates per our normal 
> support policy.
>
> -- 
> Eric D. Helms
> Red Hat Engineering
>
>

-- 
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] [Katello] Continue to have Actions::Katello::Host::UploadPackageProfile backfilled

[nhanlon]

So mostly we use foreman/katello just for syncing operating systems out to 
capsules/smart proxies, and for managing system lifecycle (basically, just 
kickstarts). I went last week to add a XenServer 7.2 OS into my Katello 
Products, and started having tons of issues, specifically in that I had 
20k+ 'Actions::Katello::Host::UploadPackageProfile' tasks sitting in my 
list as state = running, result = pending--but not doing anything at all.

To be honest, I don't really care why they're not working--I just want them 
to stop being scheduled at all. Today I've shut off foreman-tasks and 
pulp_workers and tried to set all these tasks which were running/pending to 
stopped/error, and that worked. Seemed to help out with the issues of 
Foreman. However I still had some tasks that weren't being scheduled, so I 
checked and sure enough, foreman tasks was running, as was pulp, but it was 
complaining about not having a dynflow environment. Restarting foreman 
tasks and waiting a few minutes helped, at which point I started seeing 
stuff like this spam my production.log, and tons of 
Actions::Katello::Host::UploadPackageProfile 
tasks being scheduled again--with dates from *months* ago.

2017-06-13 03:35:21  [foreman-tasks/dynflow] [D]  Step 
a4967ad4-cd92-4ed3-af38-a88a4c7d35ef: 4 got event 
Dynflow::Action::Polling::Poll
2017-06-13 03:35:21  [foreman-tasks/dynflow] [D]  Step 
c0e798bf-a9f9-40c7-9d55-75d686454f42: 4 suspended >>   running in phase 
 Run Actions::Pulp::Consumer::GenerateApplicability
2017-06-13 03:35:21  [foreman-tasks/dynflow] [D]  Step 
df8fcf4c-0de7-4cca-8aaf-f38adcd2b6ec: 4   running >> suspended in phase 
 Run Actions::Pulp::Consumer::GenerateApplicability
2017-06-13 03:35:21  [foreman-tasks/dynflow] [D]  Step 
a4967ad4-cd92-4ed3-af38-a88a4c7d35ef: 4 suspended >>   running in phase 
 Run Actions::Pulp::Consumer::GenerateApplicability
2017-06-13 03:35:21  [foreman-tasks/dynflow] [D]  Step 
f96f15cb-5933-4b18-956d-a2e4c7052004: 4 suspended >>   running in phase 
 Run Actions::Pulp::Consumer::GenerateApplicability
2017-06-13 03:35:21  [foreman-tasks/dynflow] [D]  Step 
dc8976be-99e7-4dc4-8a3f-893d3687a1cc: 4   running >> suspended in phase 
 Run Actions::Pulp::Consumer::GenerateApplicability
2017-06-13 03:35:23  [katello/pulp_rest] [D] RestClient.get 
"https://c4katello02.c4./pulp/api/v2/tasks/41b06756-a517-415b-bcb9-9002dc0e5fec/",
 
"Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, 
deflate", "accept"=>"application/json", "content_type"=>"application/json"
 | \nRestClient.get 
"https://c4katello02.c4./pulp/api/v2/tasks/ed6df62c-4f20-41c7-a0e1-4fb1cf280e34/",
 
"Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, 
deflate", "accept"=>"application/json", "content_type"=>"application/json"
 | \n# => 200 OK | application/json 326 bytes
 | 
2017-06-13 03:35:23  [foreman-tasks/dynflow] [D]  Step 
c0e798bf-a9f9-40c7-9d55-75d686454f42: 4   running >> suspended in phase 
 Run Actions::Pulp::Consumer::GenerateApplicability
2017-06-13 03:35:23  [katello/pulp_rest] [D] RestClient.get 
"https://c4katello02.c4./pulp/api/v2/tasks/41b06756-a517-415b-bcb9-9002dc0e5fec/",
 
"Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, 
deflate", "accept"=>"application/json", "content_type"=>"application/json"
 | \nRestClient.get 
"https://c4katello02.c4./pulp/api/v2/tasks/ed6df62c-4f20-41c7-a0e1-4fb1cf280e34/",
 
"Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, 
deflate", "accept"=>"application/json", "content_type"=>"application/json"
 | \n# => 200 OK | application/json 326 bytes
 | \n# => 200 OK | application/json 328 bytes
 | 
2017-06-13 03:35:23  [katello/pulp_rest] [D] RestClient.get 
"https://c4katello02.c4./pulp/api/v2/tasks/41b06756-a517-415b-bcb9-9002dc0e5fec/",
 
"Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, 
deflate", "accept"=>"application/json", "content_type"=>"application/json"
 | \nRestClient.get 
"https://c4katello02.c4./pulp/api/v2/tasks/ed6df62c-4f20-41c7-a0e1-4fb1cf280e34/",
 
"Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, 
deflate", "accept"=>"application/json", "content_type"=>"application/json"
 | \n# => 200 OK | application/json 326 bytes
 | \n# => 200 OK | application/json 328 bytes
 | \n# => 200 OK | application/json 328 bytes
 | 
2017-06-13 03:35:23  [foreman-tasks/dynflow] [D]  Step 
f96f15cb-5933-4b18-956d-a2e4c7052004: 4   running >> suspended in phase 
 Run Actions::Pulp::Consumer::GenerateApplicability
2017-06-13 03:35:23  [foreman-tasks/dynflow] [D]  Step 
a4967ad4-cd92-4ed3-af38-a88a4c7d35ef: 4   running >> suspended in phase 
 Run Actions::Pulp::Consumer::GenerateApplicability
2017-06-13 03:35:23  [foreman-tasks/dynflow] [D]  Step 
1391dcca-6002-434c-a66d-b1dfe4d4628b: 4 got event 
Dynflow::Action::Polling::Poll
2017-06-13 03:35:23  [foreman-tasks/dynflow] [D]  

Re: [foreman-users] discovered host not getting grub2 tftp files created for PXE after being discovered

[Robert Anderson]

Any timeframe on when the building infrastructure will be fixed and 9.1
released?  Any info is helpful.  Thank you.


Thanks,
Robert Anderson

On Tue, Jun 13, 2017 at 6:54 AM, Lukas Zapletal  wrote:

> This (*) will be fixed in Discovery 9.1, we are delayed with the release
> due to issues with building infrastructure. Stay tuned.
>
> (*) It's actually similar bug
> http://projects.theforeman.org/issues/19313 it's for auto-provisioning
> only.
>
> On Mon, Jun 12, 2017 at 7:50 PM, Robert Anderson 
> wrote:
> > discovered host not getting grub2 tftp files created after being
> discovered
> > and auto-rebooted for PXE
> >
> > --
> > 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.
>
>
>
> --
> Later,
>   Lukas @lzap Zapletal
>
> --
> 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/aGGcaS1xlvE/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.
>

-- 
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: Domain is not set from a host group

[Ido Kaplan]

Ok, thank you for the update.
Is there a fix for this issue?
When it should be released?

On Monday, June 12, 2017 at 9:16:37 AM UTC+3, Ido Kaplan wrote:
>
> Hi,
>
> Foreman version 1.14.3, Discovery plugin version 8.0.1.
>
> During provisioning a server with multiple interfaces, domain is not set 
> from a host group.
> Error - Failed to save: Domain can't be blank, Interfaces.domain can't 
> find domain with this id
> The same issue like this bug - http://projects.theforeman.org/issues/19445
> Can you please advise?
>
> 2017-06-11 13:41:16 f825c503 [app] [I] Started GET 
> "/discovered_hosts/mac/edit?utf8=%E2%9C%93%5Bhostgroup_id%5D=1"
>  
> for 1.1.1.1 at 2017-06-11 13:41:16 +
> 2017-06-11 13:41:16 f825c503 [app] [I] Processing by 
> DiscoveredHostsController#edit as HTML
> 2017-06-11 13:41:16 f825c503 [app] [I]   Parameters: {"utf8"=>"✓", 
> "host"=>{"hostgroup_id"=>"1"}, "id"=>"mac"}
> 2017-06-11 13:41:16 f825c503 [sql] [D]   
> ActiveRecord::SessionStore::Session Load (0.9ms)  SELECT  "sessions".* FROM 
> "sessions" WHERE "sessions"."session_id" = $1  ORDER BY "sessions"."id" ASC 
> LIMIT 1  [["session_id", "f825c5039243217a9989ad65570411fe"]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   User Load (0.8ms)  SELECT  
> "users".* FROM "users" WHERE "users"."id" = $1 LIMIT 1  [["id", 3]]
> 2017-06-11 13:41:16 f825c503 [app] [D] Setting current user thread-local 
> variable to admin
> 2017-06-11 13:41:16 f825c503 [sql] [D]   AuthSource Load (0.7ms)  SELECT  
> "auth_sources".* FROM "auth_sources" WHERE "auth_sources"."id" = $1 LIMIT 
> 1  [["id", 1]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Host::Discovered Load (0.9ms)  
> SELECT  "hosts".* FROM "hosts" WHERE "hosts"."type" IN ('Host::Discovered') 
> AND "hosts"."id" = $1  ORDER BY hosts.created_at DESC LIMIT 1  [["id", 0]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Host::Discovered Load (1.0ms)  
> SELECT  "hosts".* FROM "hosts" WHERE "hosts"."type" IN ('Host::Discovered') 
> AND "hosts"."name" = $1  ORDER BY hosts.created_at DESC LIMIT 1  [["name", 
> "mac"]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Nic::Base Load (0.9ms)  SELECT 
> "nics".* FROM "nics" WHERE "nics"."host_id" = $1  ORDER BY 
> "nics"."identifier" ASC  [["host_id", 12]]
> 2017-06-11 13:41:16 f825c503 [sql] [D](0.2ms)  BEGIN
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Subnet Load (0.7ms)  SELECT  
> "subnets".* FROM "subnets" WHERE "subnets"."id" = $1 AND "subnets"."type" = 
> $2  ORDER BY vlanid LIMIT 1  [["id", 1], ["type", "Subnet::Ipv4"]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Nic::Base Load (0.6ms)  SELECT 
> "nics".* FROM "nics" WHERE "nics"."ip" = $1  [["ip", "2.2.2.2"]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Nic::Base Load (0.6ms)  SELECT 
> "nics".* FROM "nics" WHERE "nics"."domain_id" IS NULL AND "nics"."name" = 
> $1  [["name", "mac"]]
> 2017-06-11 13:41:16 f825c503 [sql] [D] Using host queue
> 2017-06-11 13:41:16 f825c503 [sql] [D] Using host queue
> 2017-06-11 13:41:16 f825c503 [sql] [D] Using host queue
> 2017-06-11 13:41:16 f825c503 [sql] [D] Using host queue
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Nic::Base Load (0.5ms)  SELECT 
> "nics".* FROM "nics" WHERE "nics"."ip" = $1  [["ip", "192.168.0.120"]]
> 2017-06-11 13:41:16 f825c503 [sql] [D] Using host queue
> 2017-06-11 13:41:16 f825c503 [sql] [D] Using host queue
> 2017-06-11 13:41:16 f825c503 [sql] [D] Using host queue
> 2017-06-11 13:41:16 f825c503 [sql] [D](0.4ms)  COMMIT
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Hostgroup Load (0.8ms)  SELECT  
> "hostgroups".* FROM "hostgroups" WHERE "hostgroups"."title" = $1  ORDER BY 
> hostgroups.title LIMIT 1  [["title", "1"]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Hostgroup Load (0.9ms)  SELECT  
> "hostgroups".* FROM "hostgroups" WHERE "hostgroups"."id" = $1  ORDER BY 
> hostgroups.title LIMIT 1  [["id", 1]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Hostgroup Load (1.0ms)  SELECT  
> "hostgroups".* FROM "hostgroups" WHERE "hostgroups"."id" = $1  ORDER BY 
> hostgroups.title LIMIT 1  [["id", 1]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Architecture Load (0.7ms)  
> SELECT  "architectures".* FROM "architectures" WHERE "architectures"."id" = 
> $1 LIMIT 1  [["id", 1]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Operatingsystem Load (0.8ms)  
> SELECT  "operatingsystems".* FROM "operatingsystems" WHERE 
> "operatingsystems"."id" = $1  ORDER BY "operatingsystems"."title" ASC LIMIT 
> 1  [["id", 1]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Domain Load (0.7ms)  SELECT  
> "domains".* FROM "domains" WHERE "domains"."id" = $1  ORDER BY 
> domains.name LIMIT 1  [["id", 1]]
> 2017-06-11 13:41:16 f825c503 [sql] [D]   Subnet Load (0.7ms)  SELECT  
> "subnets".* FROM "subnets" WHERE "subnets"."id" = $1  ORDER BY vlanid LIMIT 
> 1  [["id", 1]]
> 2017-06-11 13:41:16 f825c503 [app] [I]   Rendered hosts/_progress.html.erb 
> (0.2ms)
> 2017-06-11 13:41:16 f825c503 [app] [D] Setting current organization 
> 

Re: [foreman-users] Re: fqdn not getting appended to hostname pattern after discovered host transitions to All Hosts

[Lukas Zapletal]

We experienced this in 9.0.0 but this seems to be fixed in 9.1
upcoming discovery release, it's delayed hold on.

http://projects.theforeman.org/issues/19445

LZ

On Mon, Jun 12, 2017 at 7:26 PM, Robert Anderson  wrote:
> Where can I find the primary interface inside of the Host Group in the Web
> UI?  I go to:
>
> Hostgroups->Name->Network tab->Domain (my fqdn is there)
>
> I don't see any other association besides that.  I must be missing
> something.  Please explain how I get to the primary interface of the Host
> Group.
>
> The fqdn is still not being tacked on after being found and put into All
> Hosts
>
>
> Thanks,
> Robert Anderson
>
> On Fri, Jun 9, 2017 at 7:02 AM, Lukas Zapletal  wrote:
>>
>> Domain should be included automatically when hostgroup you assign to
>> it has it on primary interface.
>>
>> LZ
>>
>> On Thu, Jun 8, 2017 at 8:12 PM, Robert Anderson 
>> wrote:
>> > by FQDN I mean Domain which is associated to the Host Group which is
>> > being
>> > applied via the Discovery rule
>> >
>> >
>> > On Thursday, June 8, 2017 at 2:09:11 PM UTC-4, Robert Anderson wrote:
>> >>
>> >> My hostname pattern does not include anything to declare the FQDN
>> >> (based
>> >> on the help it would seem unnecessary).  However, when the discovered
>> >> host
>> >> goes from Discovered to All Hosts the FQDN is not included
>> >> automatically.
>> >> What am I missing?
>> >>
>> >> Version 1.14.0
>> >> Discovery plugin 8
>> >
>> > --
>> > 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.
>>
>>
>>
>> --
>> Later,
>>   Lukas @lzap Zapletal
>>
>> --
>> 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/FwvnJx_lnG8/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.
>
>
> --
> 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.



-- 
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] discovered host not getting grub2 tftp files created for PXE after being discovered

[Lukas Zapletal]

This (*) will be fixed in Discovery 9.1, we are delayed with the release
due to issues with building infrastructure. Stay tuned.

(*) It's actually similar bug
http://projects.theforeman.org/issues/19313 it's for auto-provisioning
only.

On Mon, Jun 12, 2017 at 7:50 PM, Robert Anderson  wrote:
> discovered host not getting grub2 tftp files created after being discovered
> and auto-rebooted for PXE
>
> --
> 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.



-- 
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] can no longer provision discovered hosts

[Lukas Zapletal]

This will be fixed in Discovery 9.1, we are delayed with the release
due to issues with building infrastructure. Stay tuned.

LZ

On Tue, Jun 13, 2017 at 12:27 AM, Asher Schaffer  wrote:
> Running foreman 1.15.0 on Ubuntu 16.04
>
> Currently discovered hosts are showing up fine, if I attempt to provision
> one I go to the normal provision screen, enter all the info, template
> resolution works correct, but as soon as I hit submit I get  the following
> error: "Host not found Please try to update your request"
>
> I have noticed on the logs the following error on every page but I'm not
> sure if it's related.
> 2017-06-12T15:12:47 20482c08 [app] [I] Started GET
> "/javascripts/locale/en/app.js" for 10.180.112.106 at 2017-06-12 15:12:47
> -0700
> 2017-06-12T15:12:47 20482c08 [app] [F]
>  | ActionController::RoutingError (No route matches [GET]
> "/javascripts/locale/en/app.js"):
>  |   lib/middleware/tagged_logging.rb:18:in `call'
>  |
>  |
>
> Any thoughts on what to look into at this point, I can't find any other
> errors, it has been a while since I tried to provision a discovered host,
> but it was working when I was running 1.14.3
>
> --
> 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.



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

[foreman-users] Re: Missing registered smart proxy foreman.domain, please ensure it is registered

[marian . thieme]

Hello Mario,

If I understand you correctly you say in case of provisioning using using 
features like pxe boot and dhcp a smart proxy with this particular feature 
set (tftp, dns, dhcp) is required. But it can be a different host, right ?

Am Montag, 12. Juni 2017 21:08:58 UTC+2 schrieb Mario Gamboa:
>
> That's correct if you want to provisioning or distribute repos you can use 
> the smartproxy  but if you want to provisioning in the same foreman network 
> you need the smart proxy because the proxy host the services of dhcp tftp  
> dns plus any plugin you want to have
>  
>
> On Monday, June 12, 2017 at 6:36:57 PM UTC+2, marian...@gmail.com wrote:
>>
>> Hello,
>>
>>
>> I have the following setup:
>>
>> Host1: mysql/maria DB
>> Host2: foreman
>> Host3: smart proxy + puppetmaster
>> Host4: smart proxy + puppet ca
>>
>> I added/registered both smart proxies (host 3 and 4) to foreman. They 
>> show up below "Infrastructure->Smart proxies". 
>>
>> in foreman UI in Provisioning setup ("Infrastructure->Provisioning 
>> setup") foreman insists on the following prerequisite:
>> 1.) ... 
>> 2.) Missing registered smart proxy foreman.domain (== host 2), please 
>> ensure it is registered
>> 3.) ...
>>
>> As far as I understand, I dont need smart proxy on foreman. Is that 
>> correct ?
>>
>> I am using centos 7.3, foreman 1.15, puppet 4.10.1, puppet server 2.7.2
>>
>> Regards,
>> Marian
>>
>>

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