It's hard to say what might be happening without seeing the structure. Can
you share your puppet.conf on the master, and the output of "tree
/etc/puppetlabs/code/environments -d -L 3"?
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To
On 15/10/16 00:33, Jack Watroba wrote:
> I've been trying to setup a foreman installation with a separate
> puppetmaster/puppetca host. I've installed a full foreman installation
> on one server, and then followed the instructions from the "Setting up
> Foreman with external Puppet masters"
Hi Greg,
I wasn't sure about them, here they are:
# tree /etc/puppetlabs/code/environments -d -L 3
/etc/puppetlabs/code/environments
├── common
│ ├── accounts
│ │ ├── files
│ │ ├── lib
│ │ ├── manifests
│ │ ├── spec
│ │ └── templates
│ ├── apache
│ │ ├── files
│ │
On 17/10/16 04:25, Amrit Atmajit wrote:
> Thanks Dominic,
>
> This search option is a proper approach to get active hosts rather than
> "configuration_status_label=Active".
>
> But adding to Vishal's query, our requirement is to list the active
> hosts along with their facts values (like,
All,
Given that Foreman has officially dropped EL6 support for 1.13, we are
providing a set of EL6 builds for existing Foreman users as well as Katello
users who may not have been aware of the impending support drop. The builds
are being hosted with Katello's repositories and are signed by the
Thanks for the info. I was able to setup the new puppetmaster/ca/tftp proxy
by doing this:
1. I generated the first set of certs for the proxy server on the full
installation foreman server with the command 'puppet cert generate
new-proxy-server.example.com'
2. Ran a puppetmaster/ca/tftp
Greetings!
Updating to the latest and greatest foreman - following the outstanding
online documentation and received the following error (please note paste is
with --trace option):
[root@%FOREMANSERVER-EDITED% ~]# foreman-rake db:migrate --trace
** Invoke db:migrate (first_time)
** Invoke
Same boat here. Seems to be a lack of docs on that for some reason...
Pretty excited to get that integration going! Both projects have come so
far!!
On Friday, October 14, 2016 at 5:36:35 PM UTC-4, steved0ca wrote:
>
> Hello,
>
> It looks like it is not possible to add Katello to an existing
Good work from the Red Hat Devs again!
Good teamwork guys!
Cheers,
Matt
Op dinsdag 18 oktober 2016 00:10:28 UTC+2 schreef Eric Helms:
>
> All,
>
> Given that Foreman has officially dropped EL6 support for 1.13, we are
> providing a set of EL6 builds for existing Foreman users as well as
Hi all
Firstly, apologies for the cross-post - both user stories and development
talks are welcome for these CFPs, so it's relevant to both lists.
# FOSDEM - 4 & 5th Feb 2017
The call-for-papers for FOSDEM 17 is now available. As with previous years,
there's both a Configuration Management
Hello,
I'm wondering if anyone else has noticed this problem too, or has a
workaround?
I'm trying to create a new host via GCE compute resource. If I enable
External IP option in VM tab, I'm getting: "Invalid value for field
'resource.networkInterfaces[0].accessConfigs[0]': ''. Specified
Hi All,
I setup a custom fact to display the list of packages. It displays nicely
with a facter command, but does not show up
right in the foreman gui. Any suggestion how to fix the view?
# facter -p packages
[root@ip-172-31-7-124 ~]# facter -p packages
tfm-rubygem-passenger-native-libs
On Monday, October 17, 2016 at 2:53:12 AM UTC-5, Dominic Cleal wrote:
>
> On 14/10/16 22:54, re-g...@wiu.edu wrote:
> > In this thread you are discussing an intentional declaration.
> > But in my issue (see my puppet-user thread) the declaration is
> > unintentional.
> > And we think that
13 matches
Mail list logo
