[foreman-users] Re: Upgrade strategy for 1.4 to 1.14
One important place to look at is provisioning templates. If you did some changes to them, you will need to reapply your changes after migration is complete. The templates were changed since 1.4, so you would have to manually merge your changes and the latest template. On Tuesday, November 29, 2016 at 11:01:49 AM UTC+2, w...@dropbox.com wrote: > > I have inherited a Foreman 1.4 system running on Ubuntu Precise. I would > like to upgrade to the current Ubuntu LTS and current Foreman release. The > current installation uses a postgres database that is hosted on another > system. I do not want to try an in-place upgrade because I don't see a way > to test the upgrade. I have built a new database server. I have loaded the > current Foreman db on the new db server. I have also built a new Foreman > server and installed 1.14 on it, but when I attempt to migrate the database > 'foreman-rake db:migrate' konks over dead with: > > rake aborted! > ActiveRecord::RecordInvalid: Validation failed: Unable to turn on > websockets_encrypt, either websockets_ssl_key or websockets_ssl_cert is > missing > /usr/share/foreman/vendor/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:79:in > > `raise_record_invalid' > ... > > It there a simple solution to this problem? Is this a reasonable > approach? Should I install older versions of Foreman on the new server and > set through the upgrades? > > Thanks in advance for any pointers. > > Bill > -- 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: Katello 3.2 (Malt Liquor) released
Hi, You are completely right. I disabled epel because in the migration from 3.0 to 3.1 it gave me some problems. After enabling it again it works. Thank you On Tuesday, November 29, 2016 at 6:57:19 PM UTC+1, John Mitsch wrote: > > Javier, > > Looks like you are missing the EPEL repo > > yum -y localinstall > http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm > > -John > > > John Mitsch > Red Hat Engineering > (860)-967-7285 > irc: jomitsch > > On Tue, Nov 29, 2016 at 4:06 AM, Javier Vela > wrote: > >> Hi, >> >> Sorry for the late answer. I was expecting gmail to notify me in case of >> any replies. My repositories: >> >> repo id >> repo name >> >> status >> !Default_Organization_ICC_Custom_RHEL_7 >> RHEL 7 >> >> 41 >> !Default_Organization_Puppet_PUppet_Dependencies_RHEL_7 >> PUppet >> Dependencies RHEL 7 >>17 >> !Default_Organization_Puppet_Puppet_RHEL_7 >>Puppet RHEL 7 >> >> 226 >> centos-sclo-rh/x86_64 >> CentOS-7 - SCLo >> rh >> 4,231 >> centos-sclo-sclo/x86_64 >> CentOS-7 - SCLo >> sclo >> 323 >> foreman/x86_64 >>Foreman 1.13 >> >> 432 >> foreman-plugins/x86_64 >>Foreman plugins >> 1.13 >> 288 >> katello/x86_64 >>Katello 3.2 >> >> 33 >> katello-candlepin/x86_64 >>Candlepin: an >> open source entitlement management system. >> 3 >> katello-client/x86_64 >> Katello Client >> 3.2 >>16 >> katello-pulp/x86_64 >> Pulp Community >> Releases >> 49 >> puppetlabs-deps/x86_64 >>Puppet Labs >> Dependencies El 7 - x86_64 >>17 >> puppetlabs-products/x86_64 >>Puppet Labs >> Products El 7 - x86_64 >> 225 >> !rhel-7-server-extras-rpms/x86_64 >> Red Hat >> Enterprise Linux 7 Server - Extras (RPMs) >> 327 >> !rhel-7-server-rh-commo
[foreman-users] Foreman API to delete host certificate
Hi, To clean the host certificate we are using the following puppet command: - *puppet cert clean * - Is there any equivalent Foreman API to do the same? Thanks and Regards, Amrit -- 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] Potential dependency issue: rubygem-sinatra is being orphaned by epel6
According to this: https://lists.fedoraproject.org/archives/list/epel-de...@lists.fedoraproject.org/message/NKNKHYP45GTGUBVLDZJ5AIEURDJ4DDMH/ It looks like rubygem-sinatra has been orphaned for epel6. This is a dependency for foreman-proxy. I'm not sure how big a deal this is, since I'm trying to install the unofficial 1.13 version (from the Redhat/katello guys) on centos6, so I don't know if it affects any other versions/OS's. Heck, I'm not even sure where, exactly, it should be reported :) Is there any hope this will be...'fixed'? Thanks all! David -- 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: Vmware image-based provisioning issue
I ran into that exact same error just today and it ended up being a format error in my user data template. It rendered fine in the web UI, but vmware didn't like it for some reason. Here is the one I am currently using (in Sat 6.2) which is working for me. identity: LinuxPrep: domain: <%= @host.domain%> hostName: <%= @host.shortname%> globalIPSettings: dnsServerList: [<%= @host.primary_interface.subnet.dns_primary %>, <%= @host.primary_interface.subnet.dns_secondary %>] dnsSuffixList: [<%= @host.domain %>] nicSettingMap: <% @host.interfaces.each do |interface| %> - adapter: ip: <%= interface.ip %> subnetMask: <%= interface.subnet.mask %> <% if interface.primary -%>gateway: [<%= interface.subnet.gateway %>]<% end %> <% end %> -- 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: Image Provisioning using VMware template
I got the following user data template to work for vmware image based provisioning without SSH: identity: LinuxPrep: domain: <%= @host.domain%> hostName: <%= @host.shortname%> globalIPSettings: dnsServerList: [<%= @host.primary_interface.subnet.dns_primary %>, <%= @host.primary_interface.subnet.dns_secondary %>] dnsSuffixList: [<%= @host.domain %>] nicSettingMap: <% @host.interfaces.each do |interface| %> - adapter: ip: <%= interface.ip %> subnetMask: <%= interface.subnet.mask %> <% if interface.primary -%>gateway: [<%= interface.subnet.gateway %>]<% end %> <% end %> However, the thing to know is that image based provisioning against vmware without ssh is very limited when compared with traditional cloud-init. You are basically limited to the following properties: https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.wssdk.smssdk.doc%2Fvim.vm.customization.Specification.html Which means you can pass basic network settings to bootstrap the box, but little more. Windows clients can do a little more sysprep related activity, but Linux is limited. This means you will almost certainly need to design some form of "firstboot" process to handle things like re-registration to foreman, initial puppet run, etc. So far the only thing I haven't figured out is how to "phone_home" to complete the build. All I've been able to do is cancel the build in the web UI once it is done. -- 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 3.1] syncing forge modules in an air-gapped environment
Ahhh, yes, that makes sense. Thanks again Jason. On 29 November 2016 at 19:52, 'Jason B. Nance' via Foreman users < foreman-users@googlegroups.com> wrote: > I haven't used the "file" repo type before, but I would guess that the > answer is no as I think the file repo type is raw/unstructured (compared to > the yum/puppet types where you have versions and dependencies and such). > > j > > > -- > *From: *"Jamie Caldwell" > *To: *foreman-users@googlegroups.com > *Sent: *Tuesday, November 29, 2016 11:32:43 AM > *Subject: *Re: [foreman-users] [Katello 3.1] syncing forge modules in an > air-gapped environment > > Cheers Jason. Git it is then ... > On a related note, I also need to source other 'files' from the internet > (for both Katello instances) - such as Debian/Ubuntu packages and > https://maven.apache.org/. Assuming I grab this content outside of > Katello and store it locally, to sync Katello with these 'file' types, do I > also need a PULP_MANIFEST and thus to git-atise that content too? > > Many thanks, > JC. > > On 29 November 2016 at 16:49, 'Jason B. Nance' via Foreman users < > foreman-users@googlegroups.com> wrote: > >> Hi JC, >> >> The missing link is pulp-puppet-module-builder, but you're going to need >> a Git repo (it can be local). Basically you want to grab the modules you >> want, unpack them, commit them to a repository, and run >> pulp-puppet-module-builder (which will repack them, put them in a directory >> you specify, and create PULP_MANIFEST). That process is creating a local >> "forge". Then you can tell Katello to sync your local "forge". >> >> Setting up a local git repo is as simple as: >> >> mkdir /path/to/foo >> cd /path/to/foo >> git init >> git checkout -b master >> cp /some/files /path/to/foo >> git add files >> git commit -m 'initial add' >> >> Then your Git URL for pulp-puppet-module-builder can be /path/to/foo or >> file:///path/to/foo. >> >> Regards, >> >> j >> >> >> >> -- >> *From: *"JC" >> *To: *"Foreman users" >> *Sent: *Tuesday, November 29, 2016 10:00:51 AM >> *Subject: *[foreman-users] [Katello 3.1] syncing forge modules in an >> air-gapped environment >> >> Hi all, >> >> I have two Katello 3.1 servers - K1 faces the internet, K2 is an >> air-gapped environment. >> >> K1 happily syncs with http://forge.puppetlabs.com. I then tarball and >> promote the content under >> >> /var/lib/pulp/published/puppet/http/repos/Default_ >> Organization-Puppet_Forge-Forge/system >> >> to K2, where it is published locally over http. >> >> My attempts to get K2 to sync with this content (via http:// or file:///) >> have been unsuccessful. K2 appeared to want modules.json, so I grabbed >> that ( http://forge.puppetlabs.com/modules.json), and K2 looked happier >> (it knows how many modules there are now), but still no dice. For each >> module it reports: >> >> "exception" => 'Module' object has no attribute 'filename'" >> >> I wondered whether I'm supposed to also provide a PULP_MANIFEST file, >> and whether pulp-puppet-module-builder should be used, but that seems to >> want to face git (which I'm not using). >> >> Any pointers would be much appreciated. >> >> JC. >> >> -- >> 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 a topic in the >> Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/ >> topic/foreman-users/BCtRyud_yco/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. > > -- > 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/BCtRyud_yco/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > foreman-users+unsubscr.
Re: [foreman-users] [Katello 3.1] syncing forge modules in an air-gapped environment
I haven't used the "file" repo type before, but I would guess that the answer is no as I think the file repo type is raw/unstructured (compared to the yum/puppet types where you have versions and dependencies and such). j From: "Jamie Caldwell" To: foreman-users@googlegroups.com Sent: Tuesday, November 29, 2016 11:32:43 AM Subject: Re: [foreman-users] [Katello 3.1] syncing forge modules in an air-gapped environment Cheers Jason. Git it is then ... On a related note, I also need to source other 'files' from the internet (for both Katello instances) - such as Debian/Ubuntu packages and [ https://maven.apache.org/ | https://maven.apache.org/ ] . Assuming I grab this content outside of Katello and store it locally, to sync Katello with these 'file' types, do I also need a PULP_MANIFEST and thus to git-atise that content too? Many thanks, JC. On 29 November 2016 at 16:49, 'Jason B. Nance' via Foreman users < [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > wrote: Hi JC, The missing link is pulp-puppet-module-builder, but you're going to need a Git repo (it can be local). Basically you want to grab the modules you want, unpack them, commit them to a repository, and run pulp-puppet-module-builder (which will repack them, put them in a directory you specify, and create PULP_MANIFEST). That process is creating a local "forge". Then you can tell Katello to sync your local "forge". Setting up a local git repo is as simple as: mkdir /path/to/foo cd /path/to/foo git init git checkout -b master cp /some/files /path/to/foo git add files git commit -m 'initial add' Then your Git URL for pulp-puppet-module-builder can be /path/to/foo or file:///path/to/foo. Regards, j From: "JC" < [ mailto:mr.jamie.caldw...@gmail.com | mr.jamie.caldw...@gmail.com ] > To: "Foreman users" < [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > Sent: Tuesday, November 29, 2016 10:00:51 AM Subject: [foreman-users] [Katello 3.1] syncing forge modules in an air-gapped environment Hi all, I have two Katello 3.1 servers - K1 faces the internet, K2 is an air-gapped environment. K1 happily syncs with [ http://forge.puppetlabs.com/ | http://forge.puppetlabs.com ] . I then tarball and promote the content under /var/lib/pulp/published/puppet/http/repos/Default_Organization-Puppet_Forge-Forge/system to K2, where it is published locally over http. My attempts to get K2 to sync with this content (via http:// or file:/// ) have been unsuccessful. K2 appeared to want modules.json , so I grabbed that ( [ http://forge.puppetlabs.com/modules.json | http://forge.puppetlabs.com/modules.json ] ), and K2 looked happier (it knows how many modules there are now), but still no dice. For each module it reports: "exception" => 'Module' object has no attribute 'filename'" I wondered whether I'm supposed to also provide a PULP_MANIFEST file, and whether pulp-puppet-module-builde r should be used, but that seems to want to face git (which I'm not using). Any pointers would be much appreciated. JC. -- 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 [ mailto:foreman-users+unsubscr...@googlegroups.com | foreman-users+unsubscr...@googlegroups.com ] . To post to this group, send email to [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] . Visit this group at [ https://groups.google.com/group/foreman-users | https://groups.google.com/group/foreman-users ] . For more options, visit [ https://groups.google.com/d/optout | https://groups.google.com/d/optout ] . -- 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/BCtRyud_yco/unsubscribe | https://groups.google.com/d/topic/foreman-users/BCtRyud_yco/unsubscribe ] . To unsubscribe from this group and all its topics, send an email to [ mailto:foreman-users+unsubscr...@googlegroups.com | foreman-users+unsubscr...@googlegroups.com ] . To post to this group, send email to [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] . Visit this group at [ https://groups.google.com/group/foreman-users | https://groups.google.com/group/foreman-users ] . For more options, visit [ https://groups.google.com/d/optout | 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 [ mailto:foreman-users+unsubscr...@googlegroups.com | foreman-users+unsubscr...@googlegroups.com ] . To post to this group, send email to [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ]
Re: [foreman-users] Upgrade strategy for 1.4 to 1.14
The best approach would be to backup whole system first (make a snapshot if you can) and then upgrade directly to 1.14 as you did. If you hit an issue, read through ALL upgrade instructions for each individual version to work on them. I remember we were changing websocket settings, there should be a migration for it. In the worst case you can delete those records (websockets%) from settings table and revert settings.yaml to the defaults. LZ On Tue, Nov 29, 2016 at 10:17 AM, Tomer Brisker wrote: > Hi Bill, > > Upgrades are only tested to work between following minor versions. > The best upgrade path would be to go one version at a time - i.e. 1.4 -> > 1.5 -> 1.6 etc. > > On Tue, Nov 29, 2016 at 12:04 AM, whm via Foreman users < > foreman-users@googlegroups.com> wrote: > >> I have inherited a Foreman 1.4 system running on Ubuntu Precise. I would >> like to upgrade to the current Ubuntu LTS and current Foreman release. The >> current installation uses a postgres database that is hosted on another >> system. I do not want to try an in-place upgrade because I don't see a way >> to test the upgrade. I have built a new database server. I have loaded the >> current Foreman db on the new db server. I have also built a new Foreman >> server and installed 1.14 on it, but when I attempt to migrate the database >> 'foreman-rake db:migrate' konks over dead with: >> >> rake aborted! >> ActiveRecord::RecordInvalid: Validation failed: Unable to turn on >> websockets_encrypt, either websockets_ssl_key or websockets_ssl_cert is >> missing >> /usr/share/foreman/vendor/ruby/2.3.0/gems/activerecord-4.2. >> 7.1/lib/active_record/validations.rb:79:in `raise_record_invalid' >> ... >> >> It there a simple solution to this problem? Is this a reasonable >> approach? Should I install older versions of Foreman on the new server and >> set through the upgrades? >> >> Thanks in advance for any pointers. >> >> Bill >> >> -- >> 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. >> > > > > -- > Have a nice day, > Tomer Brisker > 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. > -- 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: Katello 3.2 (Malt Liquor) released
Javier, Looks like you are missing the EPEL repo yum -y localinstall http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -John John Mitsch Red Hat Engineering (860)-967-7285 irc: jomitsch On Tue, Nov 29, 2016 at 4:06 AM, Javier Vela wrote: > Hi, > > Sorry for the late answer. I was expecting gmail to notify me in case of > any replies. My repositories: > > repo id > repo name > > status > !Default_Organization_ICC_Custom_RHEL_7 > RHEL 7 > > 41 > !Default_Organization_Puppet_PUppet_Dependencies_RHEL_7 > PUppet > Dependencies RHEL 7 >17 > !Default_Organization_Puppet_Puppet_RHEL_7 >Puppet RHEL 7 > > 226 > centos-sclo-rh/x86_64 > CentOS-7 - SCLo > rh > 4,231 > centos-sclo-sclo/x86_64 > CentOS-7 - SCLo > sclo > 323 > foreman/x86_64 > Foreman 1.13 > > 432 > foreman-plugins/x86_64 > Foreman plugins > 1.13 > 288 > katello/x86_64 > Katello 3.2 > > 33 > katello-candlepin/x86_64 > Candlepin: an open > source entitlement management system. > 3 > katello-client/x86_64 > Katello Client > 3.2 >16 > katello-pulp/x86_64 > Pulp Community > Releases > 49 > puppetlabs-deps/x86_64 > Puppet Labs > Dependencies El 7 - x86_64 >17 > puppetlabs-products/x86_64 > Puppet Labs > Products El 7 - x86_64 > 225 > !rhel-7-server-extras-rpms/x86_64 > Red Hat > Enterprise Linux 7 Server - Extras (RPMs) > 327 > !rhel-7-server-rh-common-rpms/7Server/x86_64 >Red Hat > Enterprise Linux 7 Server - RH Common (RPMs) > 209 > !rhel-7-server-rpms/7Server/x86_64 >Red Hat > Enterprise Linux 7 Server (RPMs) >13,407 > rhscl-rh-ror41-epel-7-x86_64 > Ruby on Rails 4.1 > - epel-7-x86_64 > 0 > rhscl-rh-ruby22-epel-7-x86_64 > Ruby 2.2 - > epel-7-x86_64 > 0 > rhscl-ruby193-epel-7-x86_64 > Ruby193 - > epel-7-x86_64 > 0 > rhscl-v8314-epel-7-x86_64 > V8 3.14.5.10 - > epel-7-x86_64 > > Just now softwarecollections is failing, but it used to work. > > Regards > > On Monday, November 21, 2016 at 2:59:36 PM UTC+1, John Mitsch wrote: >> >> Javier, >> >> Thanks for pointing out the katello version missing on the upgrade docs >> >> Can you show yum repolist? >> >> John Mitsch >> Red Hat Engineering >> (860)-967-7285 >> irc: jomitsch >> >> On Mon, Nov 21, 2016 at 5:40 AM, Javier Vela wrote: >> >>> Hi, >>> >>> Upgrading from Katello 3.1 to Katello 3.2 for Red Hat Enterprise Linux 7 >>> following the instructions, I found two problems: >>> >>> In the documentation, this link is wrong: yum update -y >>> http://fedorapeople.org/groups/katello/releases/yum//katello >>> /el7/x86_64/katello-repos-latest.rpm >>> It should be https://fedorapeople.org/groups/katello/releases/yum/3.2/ >>> katello/el7/x86_64/katello-repos-latest.rpm >>> >>> Also, after having the Foreman 1.13 and katello 3.2 repositories added, >>> when running yum update a 'repoview' dependency fails: >>> >>> --> Finished Dependency Resolution >>> Error
Re: [foreman-users] [Katello 3.1] syncing forge modules in an air-gapped environment
Cheers Jason. Git it is then ... On a related note, I also need to source other 'files' from the internet (for both Katello instances) - such as Debian/Ubuntu packages and https://maven.apache.org/. Assuming I grab this content outside of Katello and store it locally, to sync Katello with these 'file' types, do I also need a PULP_MANIFEST and thus to git-atise that content too? Many thanks, JC. On 29 November 2016 at 16:49, 'Jason B. Nance' via Foreman users < foreman-users@googlegroups.com> wrote: > Hi JC, > > The missing link is pulp-puppet-module-builder, but you're going to need a > Git repo (it can be local). Basically you want to grab the modules you > want, unpack them, commit them to a repository, and run > pulp-puppet-module-builder (which will repack them, put them in a directory > you specify, and create PULP_MANIFEST). That process is creating a local > "forge". Then you can tell Katello to sync your local "forge". > > Setting up a local git repo is as simple as: > > mkdir /path/to/foo > cd /path/to/foo > git init > git checkout -b master > cp /some/files /path/to/foo > git add files > git commit -m 'initial add' > > Then your Git URL for pulp-puppet-module-builder can be /path/to/foo or > file:///path/to/foo. > > Regards, > > j > > > > -- > *From: *"JC" > *To: *"Foreman users" > *Sent: *Tuesday, November 29, 2016 10:00:51 AM > *Subject: *[foreman-users] [Katello 3.1] syncing forge modules in an > air-gapped environment > > Hi all, > > I have two Katello 3.1 servers - K1 faces the internet, K2 is an > air-gapped environment. > > K1 happily syncs with http://forge.puppetlabs.com. I then tarball and > promote the content under > > /var/lib/pulp/published/puppet/http/repos/Default_ > Organization-Puppet_Forge-Forge/system > > to K2, where it is published locally over http. > > My attempts to get K2 to sync with this content (via http:// or file:///) > have been unsuccessful. K2 appeared to want modules.json, so I grabbed > that ( http://forge.puppetlabs.com/modules.json), and K2 looked happier > (it knows how many modules there are now), but still no dice. For each > module it reports: > > "exception" => 'Module' object has no attribute 'filename'" > > I wondered whether I'm supposed to also provide a PULP_MANIFEST file, and > whether pulp-puppet-module-builder should be used, but that seems to want > to face git (which I'm not using). > > Any pointers would be much appreciated. > > JC. > > -- > 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 a topic in the > Google Groups "Foreman users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/foreman-users/BCtRyud_yco/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.
Re: [foreman-users] Upgrade 2.3 -> 3.2
In theory yes, but I don't know anyone who has tested that path. If you can clone your system or do a full backup before you try that would be recommended. Otherwise you can try going through the version upgrades incrementally. On Tue, Nov 29, 2016 at 11:07 AM, Kastytis T wrote: > Hi everyone, > > is it safe to perform katello upgrade from version 2.3 to 3.2 ? > > -- > 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] [Katello 3.1] syncing forge modules in an air-gapped environment
Hi JC, The missing link is pulp-puppet-module-builder, but you're going to need a Git repo (it can be local). Basically you want to grab the modules you want, unpack them, commit them to a repository, and run pulp-puppet-module-builder (which will repack them, put them in a directory you specify, and create PULP_MANIFEST). That process is creating a local "forge". Then you can tell Katello to sync your local "forge". Setting up a local git repo is as simple as: mkdir /path/to/foo cd /path/to/foo git init git checkout -b master cp /some/files /path/to/foo git add files git commit -m 'initial add' Then your Git URL for pulp-puppet-module-builder can be /path/to/foo or file:///path/to/foo. Regards, j From: "JC" To: "Foreman users" Sent: Tuesday, November 29, 2016 10:00:51 AM Subject: [foreman-users] [Katello 3.1] syncing forge modules in an air-gapped environment Hi all, I have two Katello 3.1 servers - K1 faces the internet, K2 is an air-gapped environment. K1 happily syncs with [ http://forge.puppetlabs.com/ | http://forge.puppetlabs.com ] . I then tarball and promote the content under /var/lib/pulp/published/puppet/http/repos/Default_Organization-Puppet_Forge-Forge/system to K2, where it is published locally over http. My attempts to get K2 to sync with this content (via http:// or file:/// ) have been unsuccessful. K2 appeared to want modules.json , so I grabbed that ( [ http://forge.puppetlabs.com/modules.json | http://forge.puppetlabs.com/modules.json ] ), and K2 looked happier (it knows how many modules there are now), but still no dice. For each module it reports: "exception" => 'Module' object has no attribute 'filename'" I wondered whether I'm supposed to also provide a PULP_MANIFEST file, and whether pulp-puppet-module-builde r should be used, but that seems to want to face git (which I'm not using). Any pointers would be much appreciated. JC. -- 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 [ mailto:foreman-users+unsubscr...@googlegroups.com | foreman-users+unsubscr...@googlegroups.com ] . To post to this group, send email to [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] . Visit this group at [ https://groups.google.com/group/foreman-users | https://groups.google.com/group/foreman-users ] . For more options, visit [ https://groups.google.com/d/optout | 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] Upgrade 2.3 -> 3.2
Hi everyone, is it safe to perform katello upgrade from version 2.3 to 3.2 ? -- 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] Ubuntu Preseed - Bond/vlans - anyone have a last_command that works for this?
Hello Byron, I am also starting to work on this. I need tagged bridges as well. How far have you progressed? I would like to give a hand if possible. Thanks On Monday, July 18, 2016 at 6:19:34 PM UTC+2, Byron Miller wrote: > > Thanks! i'll see about using this as a base to start from > > On Monday, July 18, 2016 at 10:56:23 AM UTC-5, Greg Sutcliffe wrote: >> >> On 18 July 2016 at 16:50, Byron Miller wrote: >> >>> Anyone have any working hacks to get ubuntu to provision & bring up >>> bonds/tagged vlans? Preseed looks super limited to 1 interface and i've had >>> people recommend writing a "last_command" shell script to do it.. just >>> curious if there is anything out there.. >>> >>> There appears to be support for VLANs in this snippet[1] - I don't see >> bonds, but I'm sure patches would be welcome :) >> >> [1] >> https://github.com/theforeman/community-templates/blob/develop/snippets/preseed_networking_setup.erb >> > -- 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 3.1] syncing forge modules in an air-gapped environment
Hi all, I have two Katello 3.1 servers - K1 faces the internet, K2 is an air-gapped environment. K1 happily syncs with http://forge.puppetlabs.com. I then tarball and promote the content under /var/lib/pulp/published/puppet/http/repos/Default_Organization-Puppet_Forge-Forge/system to K2, where it is published locally over http. My attempts to get K2 to sync with this content (via http:// or file:///) have been unsuccessful. K2 appeared to want modules.json, so I grabbed that ( http://forge.puppetlabs.com/modules.json), and K2 looked happier (it knows how many modules there are now), but still no dice. For each module it reports: "exception" => 'Module' object has no attribute 'filename'" I wondered whether I'm supposed to also provide a PULP_MANIFEST file, and whether pulp-puppet-module-builder should be used, but that seems to want to face git (which I'm not using). Any pointers would be much appreciated. JC. -- 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 documentation moved to theforeman.org
All, The katello.org site has moved all pages and documentation to live under theforeman.org website. You can now find Katello documentation in the plugin section [1]. The katello.org website has been updated to indicate this to users. As well, any old links or bookmarks you may have should redirect you to the new location on theforeman.org for a time. So please update your bookmarks as you are redirected. [1] https://theforeman.org/plugins/katello/ Eric -- 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.
[foreman-users] Re: Error while clustering Foreman | HA Foreman & puppet
> > Hi Chris, >> > grep -i servername /etc/httpd/conf.d/*foreman* /etc/httpd/conf.d/05-foreman.conf: ServerName foremandv.example.com grep: /etc/httpd/conf.d/05-foreman.d: Is a directory /etc/httpd/conf.d/05-foreman-ssl.conf: ServerName foremandv.example.com grep: /etc/httpd/conf.d/05-foreman-ssl.d: Is a directory roothost1 [~] # grep -i SSL /etc/httpd/conf.d/*foreman* grep: /etc/httpd/conf.d/05-foreman.d: Is a directory /etc/httpd/conf.d/05-foreman-ssl.conf: ErrorLog "/var/log/httpd/foreman-ssl_error_ssl.log" /etc/httpd/conf.d/05-foreman-ssl.conf: CustomLog "/var/log/httpd/foreman-ssl_access_ssl.log" combined /etc/httpd/conf.d/05-foreman-ssl.conf: ## SSL directives /etc/httpd/conf.d/05-foreman-ssl.conf: SSLEngine on /etc/httpd/conf.d/05-foreman-ssl.conf: SSLCertificateFile "/etc/puppetlabs/puppet/ssl/certs/foremandv.example.com.pem" /etc/httpd/conf.d/05-foreman-ssl.conf: SSLCertificateKeyFile "/etc/puppetlabs/puppet/ssl/private_keys/foremandv.example.com.pem" /etc/httpd/conf.d/05-foreman-ssl.conf: SSLCertificateChainFile "/etc/puppetlabs/puppet/ssl/certs/ca.pem" /etc/httpd/conf.d/05-foreman-ssl.conf: SSLCACertificateFile "/etc/puppetlabs/puppet/ssl/certs/ca.pem" /etc/httpd/conf.d/05-foreman-ssl.conf: SSLCARevocationFile "/etc/puppetlabs/puppet/ssl/crl.pem" /etc/httpd/conf.d/05-foreman-ssl.conf: SSLCARevocationCheck"chain" /etc/httpd/conf.d/05-foreman-ssl.conf: SSLVerifyClient optional /etc/httpd/conf.d/05-foreman-ssl.conf: SSLVerifyDepth 3 /etc/httpd/conf.d/05-foreman-ssl.conf: SSLOptions +StdEnvVars +ExportCertData /etc/httpd/conf.d/05-foreman-ssl.conf: Include /etc/httpd/conf.d/05-foreman-ssl.d/*.conf /etc/httpd/conf.d/05-foreman-ssl.conf: IncludeOptional /etc/httpd/conf.d/05-foreman-ssl.d/*.conf grep: /etc/httpd/conf.d/05-foreman-ssl.d: Is a directory Yes it rhel 7, as you said these two looks correct. I don't have any foreman severs, am planning to build 2 foreman(WebUI/ENC) servers (clustered) so that both foreman runs on generic (https://foremandv.example.com ) so that load will be distributed to both servers and I have existing highly available puppet setup. I want to integrate this foreman cluster with existing puppet set up. Can you please guide me about the smart proxy errors, how to configure wrt to correct CA cert. Thank you very much !! -- 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] Vmware image-based provisioning issue
Hi, I'ven been following some guidelines i found here and started working with a userdata template for the finishing of provisioning vmware templates However i run in to these error at the moment and i dont get why actually: Failed to create a compute instance X undefined method `length' for nil:NilClass I hope someone here can help me further... ps: been using satellite 6.2 -- 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] Upgrade strategy for 1.4 to 1.14
Hi Bill, Upgrades are only tested to work between following minor versions. The best upgrade path would be to go one version at a time - i.e. 1.4 -> 1.5 -> 1.6 etc. On Tue, Nov 29, 2016 at 12:04 AM, whm via Foreman users < foreman-users@googlegroups.com> wrote: > I have inherited a Foreman 1.4 system running on Ubuntu Precise. I would > like to upgrade to the current Ubuntu LTS and current Foreman release. The > current installation uses a postgres database that is hosted on another > system. I do not want to try an in-place upgrade because I don't see a way > to test the upgrade. I have built a new database server. I have loaded the > current Foreman db on the new db server. I have also built a new Foreman > server and installed 1.14 on it, but when I attempt to migrate the database > 'foreman-rake db:migrate' konks over dead with: > > rake aborted! > ActiveRecord::RecordInvalid: Validation failed: Unable to turn on > websockets_encrypt, either websockets_ssl_key or websockets_ssl_cert is > missing > /usr/share/foreman/vendor/ruby/2.3.0/gems/activerecord- > 4.2.7.1/lib/active_record/validations.rb:79:in `raise_record_invalid' > ... > > It there a simple solution to this problem? Is this a reasonable > approach? Should I install older versions of Foreman on the new server and > set through the upgrades? > > Thanks in advance for any pointers. > > Bill > > -- > 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. > -- Have a nice day, Tomer Brisker 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.
Re: [foreman-users] Re: Katello 3.2 (Malt Liquor) released
Hi, Sorry for the late answer. I was expecting gmail to notify me in case of any replies. My repositories: repo id repo name status !Default_Organization_ICC_Custom_RHEL_7 RHEL 7 41 !Default_Organization_Puppet_PUppet_Dependencies_RHEL_7 PUppet Dependencies RHEL 7 17 !Default_Organization_Puppet_Puppet_RHEL_7 Puppet RHEL 7 226 centos-sclo-rh/x86_64 CentOS-7 - SCLo rh 4,231 centos-sclo-sclo/x86_64 CentOS-7 - SCLo sclo 323 foreman/x86_64 Foreman 1.13 432 foreman-plugins/x86_64 Foreman plugins 1.13 288 katello/x86_64 Katello 3.2 33 katello-candlepin/x86_64 Candlepin: an open source entitlement management system. 3 katello-client/x86_64 Katello Client 3.2 16 katello-pulp/x86_64 Pulp Community Releases 49 puppetlabs-deps/x86_64 Puppet Labs Dependencies El 7 - x86_64 17 puppetlabs-products/x86_64 Puppet Labs Products El 7 - x86_64 225 !rhel-7-server-extras-rpms/x86_64 Red Hat Enterprise Linux 7 Server - Extras (RPMs) 327 !rhel-7-server-rh-common-rpms/7Server/x86_64 Red Hat Enterprise Linux 7 Server - RH Common (RPMs) 209 !rhel-7-server-rpms/7Server/x86_64 Red Hat Enterprise Linux 7 Server (RPMs) 13,407 rhscl-rh-ror41-epel-7-x86_64 Ruby on Rails 4.1 - epel-7-x86_64
[foreman-users] Search empty/null fields
Hello, I need to know how I can search for null values or empty fields.. Like example "version", I tried the commands "facts.myproject_version != "" " and "not has facts.smartdesk_version" but doesn't work. Anyone can help me? tks -- 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] Upgrade strategy for 1.4 to 1.14
I have inherited a Foreman 1.4 system running on Ubuntu Precise. I would like to upgrade to the current Ubuntu LTS and current Foreman release. The current installation uses a postgres database that is hosted on another system. I do not want to try an in-place upgrade because I don't see a way to test the upgrade. I have built a new database server. I have loaded the current Foreman db on the new db server. I have also built a new Foreman server and installed 1.14 on it, but when I attempt to migrate the database 'foreman-rake db:migrate' konks over dead with: rake aborted! ActiveRecord::RecordInvalid: Validation failed: Unable to turn on websockets_encrypt, either websockets_ssl_key or websockets_ssl_cert is missing /usr/share/foreman/vendor/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:79:in `raise_record_invalid' ... It there a simple solution to this problem? Is this a reasonable approach? Should I install older versions of Foreman on the new server and set through the upgrades? Thanks in advance for any pointers. Bill -- 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: Image Provisioning using VMware template
Hi, You should not be using the user-data option, as far as i know this is for cloud-init. What happens when you deselect that choice, fill everything in as needed and just deploy? Not that experienced with the whole satellite product yet, so i hope this can help you out. Kr, On Tuesday, November 8, 2016 at 7:13:07 AM UTC+1, Unix SA wrote: > > Hello, > > I am trying to provision servers using VMware template image, i like to > know procedure on how i can achieve it without SSH. > > I am not sure currently how user-data thing works, i have enabled > check-box so, what i believe is, once image is open, it will configure DHCP > on my server and later it will copy user-data template and complete > provisioning steps ? > > but somehow, after image is opened it does not configure my interface, I > am getting some "globalIPsetting" errors, i think my default template > (which comes with satellite6.2) is not good ? > > can anyone help me with documented procedure on how it can be achieved ? > appreciate any steps to follow. > > > Thanks, > DJ > -- 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] Foreman-GUI play Ansible-Role
Server and client both have ansible ver. 2.2 installed. I selected a ntp-tole and provided it to the cleint-host. If i click on "Play ansible-role" it does nothing. here formeman production log: 2016-11-29 09:45:53 [app] [I] Started GET "/ansible/hosts/128/play_roles" for 192.168.0.6 at 2016-11-29 09:45:53 +0100 2016-11-29 09:45:53 [app] [I] Processing by HostsController#play_roles as HTML 2016-11-29 09:45:53 [app] [I] Parameters: {"id"=>"128"} 2016-11-29 09:45:53 [app] [I] Performing ForemanAnsible::RunPlaybookJob from Inline(ansible) with arguments: "/tmp/foreman-ansible-client-roles20161129-7519-18oll3f", "/tmp/foreman-331b3e32-5486-485f-8216-4cf8de34c066-inventory20161129-7519-6i3owj" 2016-11-29 09:45:53 [foreman_ansible] [I] PID for playbook run for /tmp/foreman-ansible-client-roles20161129-7519-18oll3f /tmp/foreman-331b3e32-5486-485f-8216-4cf8de34c066-inventory20161129-7519-6i3owj: 4453 2016-11-29 09:45:53 [app] [I] Performed ForemanAnsible::RunPlaybookJob from Inline(ansible) in 1.08ms 2016-11-29 09:45:53 [app] [I] Enqueued ForemanAnsible::RunPlaybookJob (Job ID: d6ab0d86-2b90-4946-95f4-4ed7ab82369c) to Inline(ansible) with arguments: "/tmp/foreman-ansible-hhvm1.nodes.rto.de-roles20161129-7519-18oll3f", "/tmp/foreman-331b3e32-5486-485f-8216-4cf8de34c066-inventory20161129-7519-6i3owj" 2016-11-29 09:45:53 [app] [I] Redirected to https://theforeman.nodes.rto.de/hosts/hhvm1.nodes.rto.de 2016-11-29 09:45:53 [app] [I] Completed 302 Found in 44ms (ActiveRecord: 6.9ms) 2016-11-29 09:45:53 [app] [I] Started GET "/hosts/hhvm1.nodes.rto.de" for 192.168.0.6 at 2016-11-29 09:45:53 +0100 2016-11-29 09:45:53 [app] [I] Processing by HostsController#show as HTML 2016-11-29 09:45:53 [app] [I] Parameters: {"id"=>"hhvm1.nodes.rto.de"} 2016-11-29 09:45:53 [app] [I] Rendered hosts/_metrics.html.erb (1.0ms) 2016-11-29 09:45:53 [app] [I] Rendered hosts/show.html.erb within layouts/application (121.5ms) 2016-11-29 09:45:53 [app] [I] Rendered layouts/_application_content.html.erb (0.7ms) 2016-11-29 09:45:53 [app] [I] Rendered home/_user_dropdown.html.erb (3.5ms) 2016-11-29 09:45:53 [app] [I] Read fragment views/tabs_and_title_records-6 (0.6ms) 2016-11-29 09:45:53 [app] [I] Rendered home/_topbar.html.erb (12.7ms) 2016-11-29 09:45:53 [app] [I] Rendered layouts/base.html.erb (14.8ms) 2016-11-29 09:45:53 [app] [I] Completed 200 OK in 172ms (Views: 129.7ms | ActiveRecord: 14.9ms) 2016-11-29 09:45:54 [app] [I] Started GET "/images/avatars/4f0d9e11637861e817b0d619a3a236b2c404087e.jpg" for 192.168.0.6 at 2016-11-29 09:45:54 +0100 There is no file "/tmp/foreman-331b3e32-5486-485f-8216-4cf8de34c066-inventory20161129-7519-6i3owj" in tmp directory. Should both client and server have in /etc/ansbiel/ansible.cfg option activated? [defaults] callback_whitelist = foreman <<--$FQDN? Greets, Denis -- 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.