[foreman-users] "provisioning" IP for Puppet

['Jason B. Nance' via Foreman users]

Hello,

Has anyone happened to already have written some code to get the "provisioning" 
IP (provision: true in the foreman_interfaces array) for a host for use in a 
Puppet ERB template?

Thanks,

j

-- 
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] Remote Database

[Neil Hanlon]

The install scripts don't do a great job of managing. I've actually had to
break candlepin upgrades for it to work on my end. There is a bug
report/enhancement request for this. I'll see if I can dig up the link.

Ultimately, you can point the candlepin.conf to an external server, but you
will have issues during upgrades.

On Mar 28, 2017 14:13,  wrote:

> Hi,
>
> Ideally I would like the option to configure Katello with a remote
> database. This is supported in Foreman, but from what I can see candlepin
> installation scripts are hard coded to assume a local db. Is there any
> technical reason for this? I would have assumed it's just a JDBC connection
> and is agnostic about the location?
>
> Thanks,
>
> Alan
>
> --
> 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] [Katello] Remote Database

[apgriffiths79]

Hi,

Ideally I would like the option to configure Katello with a remote 
database. This is supported in Foreman, but from what I can see candlepin 
installation scripts are hard coded to assume a local db. Is there any 
technical reason for this? I would have assumed it's just a JDBC connection 
and is agnostic about the location?

Thanks,

Alan

-- 
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] Capsule Lifecycle Environments

[John Mitsch]

Hey Jason,

When you promote a composite content view to a lifecycle environment that
has a capsule associated with it, all of the content in the content view
versions associated with that composite content view will be available. In
short, your content views should be fine in Library as long as the
composite content view versions are promoted to the right lifecycle env.

-John

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

On Tue, Mar 28, 2017 at 11:48 AM, 'Jason B. Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> Hello,
>
> I use composite content views which point to content view versions that
> are only promoted to the "Library" environment.  My composite view versions
> are then promoted through the remaining environments in the lifecycle.  My
> question is, on my Capsule(s), do I have to sync the "Library" environment
> since my composite views reference versions that are only in "Library" or
> can I omit the "Library" and content which is referenced will automagically
> get synced?
>
> Regards,
>
> j
>
> --
> 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] Smart-proxy syncing of DRPMs failing

[jpavel]

Katello server 3.3.1
Foreman Proxy 1.14.2

When syncing my katello content, certain repos fail to sync and therefore 
never generate the repomd.xml, and then when servers try to use katello 
content, they fail with a 404 and tell the user to disable the repos.

This is limited, in my environment, to CentOS 7 Extras, Updates, and Plus 
repos. However, subscription-manager behaves in such a way that all 
install/update tasks fail on these errors, instead of skipping the failing 
repo.

>From what I can tell, DRPMs are not correctly linked on the Katello server, 
and so the sync process fails with 404 errors and "[foreman-tasks/action] 
[E] PLP: Importer indicated a failed response 
(Katello::Errors::PulpError)" reported on the Katello server.

The Smart Proxy logs the following error:
Mar 28 13:14:33 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.repomd.alternate:INFO: The content container 
reported: {'downloads': {}, 'total_sources': 0} for base URL: 
https://foreman-01.prod.mcs.som.mob.nuance.com/pulp/repos/nuance_mobility/Development/MCS_Mesos/custom/CentOS_7/Plus_x86_64/
Mar 28 13:14:33 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.sync:INFO: Downloading 9 DRPMs.
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (1): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (2): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (3): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (4): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (5): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (6): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (7): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (8): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:33 smart-proxy-01 pulp: 
requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS 
connection (9): foreman-01.prod.mcs.som.mob.nuance.com
Mar 28 13:14:34 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.sync:ERROR: (4409-85632) 'error_code'
Mar 28 13:14:34 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.sync:ERROR: (4409-85632) Traceback (most 
recent call last):
Mar 28 13:14:34 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.sync:ERROR: (4409-85632)   File 
"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/sync.py", 
line 232, in run
Mar 28 13:14:34 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.sync:ERROR: (4409-85632) 
self.update_content(metadata_files, url)
Mar 28 13:14:34 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.sync:ERROR: (4409-85632)   File 
"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/sync.py", 
line 501, in update_content
Mar 28 13:14:34 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.sync:ERROR: (4409-85632) if 
error[constants.ERROR_CODE] == constants.ERROR_KEY_ID_FILTER:
Mar 28 13:14:34 smart-proxy-01 pulp: 
pulp_rpm.plugins.importers.yum.sync:ERROR: (4409-85632) KeyError: 
'error_code'
Mar 28 13:14:34 smart-proxy-01 pulp: pulp.server.async.tasks:INFO: Task 
failed : [4a88b023-5779-4b03-b1d1-b6c832d89d2b]
Mar 28 13:14:34 smart-proxy-01 pulp: celery.worker.job:ERROR: (4283-85632) 
Task 
pulp.server.managers.repo.sync.sync[4a88b023-5779-4b03-b1d1-b6c832d89d2b] 
raised unexpected: PulpExecutionException('Importer indicated a failed 
response',)
Mar 28 13:14:34 smart-proxy-01 pulp: celery.worker.job:ERROR: (4283-85632) 
Traceback (most recent call last):
Mar 28 13:14:34 smart-proxy-01 pulp: celery.worker.job:ERROR: (4283-85632) 
  File "/usr/lib/python2.7/site-packages/celery/app/trace.py", line 240, in 
trace_task
Mar 28 13:14:34 smart-proxy-01 pulp: celery.worker.job:ERROR: (4283-85632) 
R = retval = fun(*args, **kwargs)
Mar 28 13:14:34 smart-proxy-01 pulp: celery.worker.job:ERROR: (4283-85632) 
  File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 
488, in __call__
Mar 28 13:14:34 smart-proxy-01 pulp: celery.worker.job:ERROR: (4283-85632) 
return super(Task, self).__call__(*args, **kwargs)
Mar 28 13:14:34 smart-proxy-01 pulp: celery.worker.job:ERROR: (4283-85632) 
  File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 
103, in __call__
Mar 28 13:14:34 smart-proxy-01 pulp: celery.worker.job:ERROR: (4283-85632) 
 

Re: [foreman-users] Run job - send sudo password from Foreman

['Jason B. Nance' via Foreman users]

Hi Diggy, 

I don't know of a way of achieving what you are after, however, I question the 
"more secure" sentiment that is driving this. Sudo is specifically designed to 
try and prevent what you are trying to do because it opens up doors for people 
to gleam passwords and leads to other bad habits. In fact, you cannot just 
"pipe" a password to sudo normally (you have to pass the -S flag). 

So I disagree that using NOPASSWD "clearly ... flies in the face of best 
practices". I also disagree that setting PermitRootLogin to no is "as it should 
be". The "without-password" option is perfectly acceptable in many situations 
when using SSH keys - especially when you include "from=" options in your 
authorized_keys file and such. 

If you have company policies which require a specific design that is one thing, 
but in general keep in mind that there are many different levels of "secure" 
and different people/organizations have different needs/tolerances. For 
example, allowing Foreman to ssh directly as root is fine in my case because 
the logging/auditing in Foreman itself is sufficient to meet our compliance 
requirements. 

Regards, 

j 



From: "Diggy"  
To: "Foreman Users"  
Sent: Monday, March 27, 2017 9:54:37 AM 
Subject: [foreman-users] Run job - send sudo password from Foreman 

Hello, all. 
In my Foreman instance, I've set up job execution (Run job) to work. On my 
hosts, I have ssh PermitRootLogin set to no, as it should be. We log into hosts 
with our own usernames, then run commands via sudo. Thus, in order to get Run 
job to work properly, in Foreman I set Administer > Settings > RemoteExecution 
> r emote_execution_effective_user=root, 
remote_execution_effective_user_method=sudo, and 
remote_execution_ssh_user=asudouser. The only way I could see to make this work 
was to set NOPASSWD in asudouser's sudoer file directive. Clearly, this flies 
in the face of best practices. Is there a way for me to pass asudouser's sudo 
password via Foreman, or is there some more secure way to make Run job work? 

Many thanks. 


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

Re: [foreman-users] Changing the grub configuration of a provisioned VM?

[Lukas Zapletal]

Oh that one, I don't know. Anaconda in RHEL can configure something,
but definitely not everything. Do a post install scriplet... It's just
bunch of config files.

LZ

On Tue, Mar 28, 2017 at 12:36 PM, Johannes Kastl  wrote:
> Hi Lukas,
>
> Lukas Zapletal schrieb:
>> There are two templates, one is when you are in BUILD mode, the other
>> is for the non-BUILD mode:
>>
>> provisioning_templates/PXEGrub2/pxegrub2_default_local_boot.erb
>> provisioning_templates/PXEGrub2/pxegrub2_global_default.erb
>
> Correct me if I'm wrong:
> The pxegrub2_default_local_boot does nothing more than chainload the
> bootloader installed on the machine's hard disk (unless it is an EFI
> machine):
>
>> menuentry "Chainload into BIOS bootloader on first disk" {
>>   set root=(hd0,0)
>>   chainloader +1
>> }
>
> (This is actually from the pxegrub2_chainload snippet that gets included
> in the pxegrub2_default_local_boot template)
>
> So with a normal bios boot, it just boots the machine via PXE and tells
> it to chainload the bootloader in the mbr and boot from that.
>
> What I am interested in is the configuration of this bootloader in the
> mbr. I.e. the one, that can be configured on the machine itself
> (/boot/grub/grub.cfg).
>
> I hope I could clarify what I want to achieve.
>
> I tried to do some stuff via preseed, but it never got called
> apparently. I'm debugging this right now, but have not got any clue this
> far.
>
> Johannes
>
> --
> Johannes Kastl
> Linux Consultant & Trainer
> Tel.: +49 (0) 151 2372 5802
> Mail: ka...@b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> --
> 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: Error has occurred while listing VMs = Undefined namespace prefix: //soapenv:Body/*

[Aurélien Le Clainche]

Hello, 

Did you find any solution for you problem ?

Le jeudi 12 mai 2016 15:28:26 UTC+2, Jérémy D a écrit :
>
> Still no solution...
>
> Le lundi 7 mars 2016 10:11:07 UTC+1, herve@kosmos.fr a écrit :
>>
>> Hi Jérémy,
>> Did you find any solution? 
>> We're facing the same problem here, also with an OVH dedicated Cloud...
>>
>>
>> Le mardi 12 janvier 2016 15:16:29 UTC+1, Jérémy D a écrit :
>>>
>>> Hi Kevin
>>>
>>> Listing VM, Create VM i dont try other thing.
>>>
>>> Hosted on dedicated Cloud OVH Yes ! Maybe it's OVH limitation...
>>>
>>>
>>> Jérémy
>>>
>>> Le samedi 9 janvier 2016 07:16:34 UTC+1, Kevin Lan a écrit :

 Jeremy, 

 I facing this issue since a long time, my first question, did you 
 received this message only for listing vms ? or for others tasks ? ( 
 cloning a VM from Template )

 My second one, is the ESX are hosted at OVH through their private cloud 
 ? or is it something you hosted yourself ? 

 While enabled the logs of RBVMOMI i saw that a empty SOAP response 
 causing this in my case since vSphere was trying to get properties datas 
 from vm name. 

 it's a weird issue... 

 On Wednesday, December 16, 2015 at 3:23:15 PM UTC+1, Jérémy D wrote:
>
>
> 2015-12-16T11:50:54 [app] [W] Error has occurred while listing VMs on 
> my_cluster (VMware)
>
>  | Nokogiri::XML::XPath::SyntaxError: Undefined namespace prefix: 
> //soapenv:Body/*
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/nokogiri-1.5.11/lib/nokogiri/xml/node.rb:159:in
>  `evaluate'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/nokogiri-1.5.11/lib/nokogiri/xml/node.rb:159:in
>  `block in xpath'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/nokogiri-1.5.11/lib/nokogiri/xml/node.rb:150:in
>  `map'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/nokogiri-1.5.11/lib/nokogiri/xml/node.rb:150:in
>  `xpath'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/rbvmomi-1.8.2/lib/rbvmomi/trivial_soap.rb:112:in
>  `request'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/rbvmomi-1.8.2/lib/rbvmomi/connection.rb:87:in
>  `call'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/rbvmomi-1.8.2/lib/rbvmomi/basic_types.rb:205:in
>  `_call'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/rbvmomi-1.8.2/lib/rbvmomi/basic_types.rb:74:in
>  `block (2 levels) in init'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/rbvmomi-1.8.2/lib/rbvmomi/basic_types.rb:183:in
>  `_get_property'
>
>  | 
> /usr/share/foreman/vendor/ruby/2.1.0/gems/rbvmomi-1.8.2/lib/rbvmomi/basic_types.rb:35:in
>  `block (2 levels) in init'
>
>  | 
> /usr/share/foreman/app/services/fog_extensions/vsphere/mini_servers.rb:26:in
>  `block in allvmsbyfolder'
>
>  | 
> /usr/share/foreman/app/services/fog_extensions/vsphere/mini_servers.rb:22:in
>  `each'
>
>  | 
> /usr/share/foreman/app/services/fog_extensions/vsphere/mini_servers.rb:22:in
>  `allvmsbyfolder'
>
>  | 
> /usr/share/foreman/app/services/fog_extensions/vsphere/mini_servers.rb:24:in
>  `block in allvmsbyfolder'
>
>  | 
> /usr/share/foreman/app/services/fog_extensions/vsphere/mini_servers.rb:22:in
>  `each'
>
>  | 
> /usr/share/foreman/app/services/fog_extensions/vsphere/mini_servers.rb:22:in
>  `allvmsbyfolder'
>
>  | 
> /usr/share/foreman/app/services/fog_extensions/vsphere/mini_servers.rb:24:in
>  `block in allvmsbyfolder'
>
>  | 
> /usr/share/foreman/app/services/fog_extensions/vsphere/mini_servers.rb:22:in
>  `each'
>
>  | /usr/share/forema
>
> ...



-- 
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] SSH Provisioning

[Tyler Gregory]

That's definitely what I'm doing wrong, but isn't it odd that Foreman runs 
the templates on itself in the absence of a provisioning IP address?

On Tuesday, March 28, 2017 at 4:40:15 AM UTC-5, Lukas Zapletal wrote:
>
> Foreman connects to the IP address that is defined for your 
> provisioning NIC, check the IP and routing from Foreman server. 
>
> LZ 
>
> On Mon, Mar 27, 2017 at 10:37 PM, Tyler Gregory  > wrote: 
> > Hello all, 
> > 
> > I am attempting to use Foreman to provision a Linux VM on VMware, and to 
> use 
> > a finishing script over SSH. The VM deploys fine, but instead of being 
> run 
> > on the VM, the finishing script is run on the Foreman box itself. 
> > 
> > Here's the template: 
> > #!/bin/bash 
> > 
> > wall "Test" 
> > 
> > cat /etc/puppet/puppet.conf << EOF 
> > 
> > [main] 
> > vardir = /var/lib/puppet 
> > logdir = /var/log/puppet 
> > rundir = /var/run/puppet 
> > ssldir = \$vardir/ssl 
> > 
> > [agent] 
> > pluginsync=true 
> > report = true 
> > ignoreschedules = true 
> > ca_server =  
> > certname = <%= @host.name %> 
> > environment = production 
> > server =  
> > 
> > 
> > EOF 
> > 
> > 
> > puppet_unit=puppet 
> > /usr/bin/systemctl list-unit-files | grep -q puppetagent && 
> > puppet_unit=puppetagent 
> > /usr/bin/systemctl enable ${puppet_unit} 
> > /sbin/chkconfig --level 345 puppet on 
> > 
> > 
> > export FACTER_is_installer=true 
> > 
> > 
> > /usr/bin/puppet agent --config /etc/puppet/puppet.conf --onetime --tags 
> > no_such_tag --server  --no-daemonize 
> > 
> > 
> > if [ -f /usr.bin/dnf]; then 
> >   dnf -y update 
> > else 
> >   yum -t -y update 
> > fi 
> > 
> > 
> > sync 
> > 
> > 
> > exit 0 
> > 
> > 
> > I realize there are some errors with the template, and the wall was only 
> > placed there as a troubleshooting measure, but I have no idea what could 
> be 
> > causing Foreman to execute this template on itself instead of on the VM. 
> Any 
> > help is appreciated. 
> > 
> > Thanks, 
> > 
> > Tyler 
> > 
> > -- 
> > 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-user...@googlegroups.com . 
> > To post to this group, send email to forema...@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] Foreman installation issues Centos 7

['Jason Nance' via Foreman users]

Hi Wim,

You have included an option that requires an argument without including the 
argument, so the installer is using the next option as the argument and it is 
throwing off all of your options/arguments.

Check your options against the --help output. A common mistake is to leave out 
a "true" or "false" to the boolean options.

Regards,

J


> On Mar 28, 2017, at 2:44 AM, Wim Van den Borre  
> wrote:
> 
> Hey Everyone,
> 
> I'm trying to install foreman but when i run the installer i get a bunch of 
> these messages, does anyone know what the problem coulde be?
> 
> foreman-installer
> Parameter foreman-foreman-url invalid: ::foreman::params::foreman_url must 
> match one of (?-mix:^https?:\/\/)
> Parameter foreman-puppetrun invalid: "::foreman::params::puppetrun" is not a 
> valid boolean, "::foreman::params::puppetrun" is not a valid boolean
> Parameter foreman-unattended invalid: "::foreman::params::unattended" is not 
> a valid boolean
> Parameter foreman-authentication invalid: "::foreman::params::authentication" 
> is not a valid boolean
> Parameter foreman-passenger invalid: "::foreman::params::passenger" is not a 
> valid boolean, "::foreman::params::passenger" is not a valid boolean
> Parameter foreman-use-vhost invalid: "::foreman::params::use_vhost" is not a 
> valid boolean
> Parameter foreman-ssl invalid: "::foreman::params::ssl" is not a valid boolean
> Parameter foreman-configure-epel-repo invalid: 
> "::foreman::params::configure_epel_repo" is not a valid boolean
> Parameter foreman-configure-scl-repo invalid: 
> "::foreman::params::configure_scl_repo" is not a valid boolean
> Parameter foreman-selinux invalid: "::foreman::params::selinux" is not a 
> valid boolean
> Parameter foreman-gpgcheck invalid: "::foreman::params::gpgcheck" is not a 
> valid boolean
> 
> Kind regards
> -- 
> 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] SSH Provisioning

[Tyler Gregory]

Hello all, 

I am attempting to use Foreman to provision a Linux VM on VMware, and to 
use a finishing script over SSH. The VM deploys fine, but instead of being 
run on the VM, the finishing script is run on the Foreman box itself. 

Here's the template:
#!/bin/bash

wall "Test"

cat /etc/puppet/puppet.conf << EOF

[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = \$vardir/ssl

[agent]
pluginsync=true
report = true
ignoreschedules = true
ca_server = 
certname = <%= @host.name %>
environment = production
server = 


EOF


puppet_unit=puppet
/usr/bin/systemctl list-unit-files | grep -q puppetagent && puppet_unit=
puppetagent
/usr/bin/systemctl enable ${puppet_unit}
/sbin/chkconfig --level 345 puppet on


export FACTER_is_installer=true


/usr/bin/puppet agent --config /etc/puppet/puppet.conf --onetime --tags 
no_such_tag --server  --no-daemonize


if [ -f /usr.bin/dnf]; then
  dnf -y update
else
  yum -t -y update
fi


sync


exit 0


I realize there are some errors with the template, and the wall was only 
placed there as a troubleshooting measure, but I have no idea what could be 
causing Foreman to execute this template on itself instead of on the VM. 
Any help is appreciated.

Thanks,

Tyler

-- 
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 installation issues Centos 7

[Wim Van den Borre]

Hey Everyone,

I'm trying to install foreman but when i run the installer i get a bunch of 
these messages, does anyone know what the problem coulde be?

foreman-installer
Parameter foreman-foreman-url invalid: ::foreman::params::foreman_url must 
match one of (?-mix:^https?:\/\/)
Parameter foreman-puppetrun invalid: "::foreman::params::puppetrun" is not 
a valid boolean, "::foreman::params::puppetrun" is not a valid boolean
Parameter foreman-unattended invalid: "::foreman::params::unattended" is 
not a valid boolean
Parameter foreman-authentication invalid: 
"::foreman::params::authentication" is not a valid boolean
Parameter foreman-passenger invalid: "::foreman::params::passenger" is not 
a valid boolean, "::foreman::params::passenger" is not a valid boolean
Parameter foreman-use-vhost invalid: "::foreman::params::use_vhost" is not 
a valid boolean
Parameter foreman-ssl invalid: "::foreman::params::ssl" is not a valid 
boolean
Parameter foreman-configure-epel-repo invalid: 
"::foreman::params::configure_epel_repo" is not a valid boolean
Parameter foreman-configure-scl-repo invalid: 
"::foreman::params::configure_scl_repo" is not a valid boolean
Parameter foreman-selinux invalid: "::foreman::params::selinux" is not a 
valid boolean
Parameter foreman-gpgcheck invalid: "::foreman::params::gpgcheck" is not a 
valid boolean

Kind regards

-- 
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] Run job - send sudo password from Foreman

[Diggy]

Hello, all.

In my Foreman instance, I've set up job execution (Run job) to work.  On my 
hosts, I have ssh PermitRootLogin set to no, as it should be.  We log into 
hosts with our own usernames, then run commands via sudo.  Thus, in order 
to get Run job to work properly, in Foreman I set Administer > Settings > 
RemoteExecution > remote_execution_effective_user=root, 
remote_execution_effective_user_method=sudo, 
and remote_execution_ssh_user=asudouser.  The only way I could see to make 
this work was to set NOPASSWD in asudouser's sudoer  file directive. 
 Clearly, this flies in the face of best practices.  Is there a way for me 
to pass asudouser's sudo password via Foreman, or is there some more secure 
way to make Run job work?

Many thanks.

-- 
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] Changing the grub configuration of a provisioned VM?

[Johannes Kastl]

Hi Lukas,

Lukas Zapletal schrieb:
> Absolutely you can. It's just a template called "PXEGrub2 default
> local boot" and you can either modify it or use host parameters with
> hostgroups to do per-host or per-group options.

I thought that was modifying the PXE configuration, not the one that the
machine has on its local hard drive after provisioning?

Johannes

-- 
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

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