Re: [foreman-users] [Katello] Applicable vs Installable errata

2016-09-16 Thread Edgars M.
Hi

1. It shows as installable
2. Yes, published and promoted

I filed a bug http://projects.theforeman.org/issues/16544

Edgars

ceturtdiena, 2016. gada 15. septembris 15:30:39 UTC+2, Walden Raines 
rakstīja:
>
> Hey Edgars, 
>
> Sorry for the delay in my response but I have two more questions. 
>
> 1.  Does the kernel errata mentioned below show up as applicable or 
> installable on the errata list page (/errata)? 
> 2.  Just making sure everything is plugged in but you did publish a new 
> version of the CV after creating the filter(s), correct? 
>
> Thanks, 
> Walden 
>
>
> - Original Message - 
> From: "Edgars M." > 
> To: "Foreman users" > 
> Sent: Tuesday, September 13, 2016 3:31:23 AM 
> Subject: Re: [foreman-users] [Katello] Applicable vs Installable errata 
>
> Hi Walden 
>
> I took one content host and compared web gui and API results, here is what 
> I see: 
>
> WebGUI: 
>
> <
> https://lh3.googleusercontent.com/-PeF_S4vcO5M/V9epm1vXo3I/ADc/INhpPG345xkJYTn2ge-Ek_KV-IqpvkxjACLcB/s1600/errata.installable.JPG>
>  
>
>
>
> And this is if I call API: 
>
>
> [em@katello.local ~]$ curl 
>
> https://katello.local/api/v2/hosts/291/errata?errata_restrict_applicable=true 
> -u em | python -m json.tool | grep errata_id 
> Enter host password for user 'em': 
>   % Total% Received % Xferd  Average Speed   TimeTime Time 
>  Current 
>  Dload  Upload   Total   SpentLeft 
>  Speed 
> 100 593570 593570 0  74973  0 --:--:-- --:--:-- --:--:-- 
> 74945 
> "errata_id": "RHSA-2016:1664", 
> "errata_id": "RHSA-2015:1623", 
> "errata_id": "RHBA-2015:1827", 
> "errata_id": "RHBA-2016:1185", 
> "errata_id": "RHBA-2015:1466", 
> "errata_id": "RHSA-2015:1272", 
> "errata_id": "RHSA-2016:1406", 
> "errata_id": "RHSA-2016:0855", 
> "errata_id": "RHSA-2015:2636", 
> "errata_id": "RHBA-2015:1992", 
> "errata_id": "RHSA-2016:0494", 
> "errata_id": "RHBA-2016:0150", 
> "errata_id": "RHSA-2016:0715", 
>
>
> [em@katello.local ~]$ curl 
>
> https://katello.local/api/v2/hosts/291/errata?errata_restrict_installable=true
>  
> -u em | python -m json.tool | grep errata_id 
> Enter host password for user 'em': 
>   % Total% Received % Xferd  Average Speed   TimeTime Time 
>  Current 
>  Dload  Upload   Total   SpentLeft 
>  Speed 
> 100 593570 593570 0  15410  0 --:--:--  0:00:03 --:--:-- 
> 15409 
> "errata_id": "RHSA-2016:1664", 
> "errata_id": "RHSA-2015:1623", 
> "errata_id": "RHBA-2015:1827", 
> "errata_id": "RHBA-2016:1185", 
> "errata_id": "RHBA-2015:1466", 
> "errata_id": "RHSA-2015:1272", 
> "errata_id": "RHSA-2016:1406", 
> "errata_id": "RHSA-2016:0855", 
> "errata_id": "RHSA-2015:2636", 
> "errata_id": "RHBA-2015:1992", 
> "errata_id": "RHSA-2016:0494", 
> "errata_id": "RHBA-2016:0150", 
> "errata_id": "RHSA-2016:0715", 
>
>
>
> As you can see result is the same. Please file a bug if you know what is 
> wrong. 
>
>
> Edgars 
>
>
>
> pirmdiena, 2016. gada 12. septembris 17:15:14 UTC+2, Walden Raines 
> rakstīja: 
> > 
> > Hey Edgars, 
> > 
> > The documentation is correct so if you are seeing non-installable errata 
> > show up on that page then it is a bug. 
> > 
> > Out of curiosity, if you go to 
> > /api/v2/hosts/2/errata?errata_restrict_applicable=true do you see a list 
> of 
> > errata without kernel updates? 
> > 
> > I think I see what the bug is and am happy to file it unless you want 
> to. 
> > 
> > Thanks, 
> > Walden 
> > 
> > - Original Message - 
> > From: "Edgars M." > 
> > To: "Foreman users" > 
> > Sent: Monday, September 12, 2016 10:17:06 AM 
> > Subject: [foreman-users] [Katello] Applicable vs Installable errata 
> > 
> > Hi 
> > 
> > I have question regarding Applicable and Installable errata on content 
> > hosts. This is from documentation: 
> > 
> > With regard to Content Hosts, Errata is divided into two distinct 
> > > classifications depending on whether or not the Errata is present in 
> the 
> > > Content Host’s Lifecycle Environment and Content View: 
> > > 
> > >- Applicable: the errata applies to one or more Content Hosts 
> > >- Installable: the errata applies to one or more Content Hosts and 
> is 
> > >present in the Content Host’s Lifecycle Environment and Content 
> View 
> > > 
> > > 
> > As far as I understand errata which is filtered out of Content View (not 
> > present in CV) is not Installable errata, but is Applicable errata. Am I 
> > right? But the thing is - when I go to Content Host -> Errata, where I 
> can 
> > see Installable errata I see all erratas including those I have filtered 
> > out of CV. Is it a bug

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

2016-09-16 Thread Lukas Zapletal
> I'm getting the following error when I try to refresh facts of the 
> discovered hosts through actual API:
> 
> $ curl -kSs -H "Content-Type: application/json" -H 
> "Accept:application/json" -u admin:$PASSWORD 
> https://localhost/api/v2/discovered_hosts/mac008cfaed69c8/refresh_facts | 
> jq '.'
> {
>   "status": "404",
>   "error": "Not Found"
> }

This API call is not HTTP GET but HTTP PUT.

Unfortunately we don't publish API docs of plugins:

https://theforeman.org/api/1.12/index.html

You need to dig in the source codes, but its very readable.

https://github.com/theforeman/foreman_discovery/blob/develop/app/controllers/api/v2/discovered_hosts_controller.rb#L173-L180

-- 
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: Provisioning Setup, not working :(

2016-09-16 Thread Lukas Zapletal
> Still fighting with this. Anyone have any thoughts? Are we not suppose to 
> be able to provision more than one subnet or something? 

Please report a bug.

https://github.com/theforeman/foreman_setup/issues

Note this plugin won't help you setting up *additional* provisioning
network, it can only help you with *initial* provisioning setup. It uses
our installer to do the configuration and it only supports one DHCP network.

In this case, I suggest you to add the network manually.

-- 
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] Cannot get "Run Puppet" to work in GUI

2016-09-16 Thread Dominic Cleal
On 15/09/16 16:41, Scott Mckeown wrote:
> 
> I have read just about every doc I can find on how to get the "run
> puppet" button to work in the web ui with no luck.
> I am trying to use the  mcollective provider.
> 
> The foreman documentation section only shows a few lines in a couple of
> files to change. 
> I have made all of the stated changes, still not working. 
> 
> Is there a better guide to get this working?

I don't know about a guide, but if you can more precisely show what
isn't working, including showing the smart proxy logs, any errors and
the relevant/changed configuration files, somebody may be able to help.

-- 
Dominic Cleal
domi...@cleal.org

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


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

2016-09-16 Thread Dominic Cleal
On 15/09/16 23:57, Joseph Cunningham wrote:
> I know this is an old thread, but following this guide, I'm getting the
> following error when attempting to run puppet agent -t on the client:
> 
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER: no implicit conversion of nil into Hash at
> /etc/puppet/environments/production/modules/firewall_custom/manifests/init.pp:12
> on node omdapps06.mil.state.or.us
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
> 
> 
> Gist of init.pp is here:
> https://gist.github.com/joeywas/d8f0d676b9ef3beb54ae0d617ef69633

Line 12 is the create_resources() call, which uses $firewall_data from
the class parameter. If that is nil, then it's likely that the parameter
isn't correctly set in Foreman.

View the ENC output (the YAML button on the host page) and ensure
firewall_data is listed below the firewall_custom class name with the
YAML representing your firewall resources/rules, else ensure it's set in
the smart class parameter in Foreman.

-- 
Dominic Cleal
domi...@cleal.org

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


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

2016-09-16 Thread Akash Kaveti
Thank you Dominic, That worked.

On Thursday, September 15, 2016 at 2:38:11 PM UTC+2, Dominic Cleal wrote:
>
> On 15/09/16 13:11, Akash Kaveti wrote: 
> > Hello, 
> > 
> > I am trying to install ubuntu desktop, but I have succeeded. I have 
> > tried different mirrors but I ended up with Ubuntu server. 
> > Would be very much greatful, if any one can help. 
>
> Try updating the package list (via tasksel) in the preseed file, i.e. 
> the line at 
>
> https://github.com/theforeman/community-templates/blob/develop/preseed/provision.erb#L132.
>  
>
> Edit your preseed via Foreman's provisioning templates UI. 
>
> See 
>
> https://help.ubuntu.com/lts/installation-guide/amd64/apbs04.html#preseed-pkgsel
>  
> for a list of standard tasks. 
>
> -- 
> Dominic Cleal 
> dom...@cleal.org  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


Re: [foreman-users] check foreman definitions into git?

2016-09-16 Thread Anurag
On Thu, Sep 15, 2016 at 10:43 PM, Thomas Cheng 
wrote:

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

Not sure if there's a separate project for this, but have you tried
extracting these data points via hammer cli? For example:
$ hammer --csv host list

Anurag

-- 
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: Tip: Passing puppetlabs/firewall configuration through Foreman web interface

2016-09-16 Thread Joseph Cunningham
Dominic, that was it!   The value I was using in foreman to override the 
smart class parameter was not properly formatted yaml (i was missing 
indents)

Thank you!

On Friday, September 16, 2016 at 2:15:51 AM UTC-7, Dominic Cleal wrote:
>
> On 15/09/16 23:57, Joseph Cunningham wrote: 
> > I know this is an old thread, but following this guide, I'm getting the 
> > following error when attempting to run puppet agent -t on the client: 
> > 
> > Info: Retrieving pluginfacts 
> > Info: Retrieving plugin 
> > Info: Loading facts 
> > Error: Could not retrieve catalog from remote server: Error 400 on 
> > SERVER: no implicit conversion of nil into Hash at 
> > 
> /etc/puppet/environments/production/modules/firewall_custom/manifests/init.pp:12
>  
>
> > on node omdapps06.mil.state.or.us 
> > Warning: Not using cache on failed catalog 
> > Error: Could not retrieve catalog; skipping run 
> > 
> > 
> > Gist of init.pp is here: 
> > https://gist.github.com/joeywas/d8f0d676b9ef3beb54ae0d617ef69633 
>
> Line 12 is the create_resources() call, which uses $firewall_data from 
> the class parameter. If that is nil, then it's likely that the parameter 
> isn't correctly set in Foreman. 
>
> View the ENC output (the YAML button on the host page) and ensure 
> firewall_data is listed below the firewall_custom class name with the 
> YAML representing your firewall resources/rules, else ensure it's set in 
> the smart class parameter in Foreman. 
>
> -- 
> Dominic Cleal 
> dom...@cleal.org  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


[foreman-users] how to upgrade 1.12.1 to 1.12.2

2016-09-16 Thread Erik Hjelmås
Hi, 

sorry but Im not able to figure out how to do this, I use the 
foreman-installer, and Ive tried
foreman-installer --foreman-version=latest
but foreman still says 1.12.1 (login page and ~foreman/VERSION)

any help greatly appreciated, 

have a good weekend everyone, 

/Erik

-- 
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] Troubles with calling /api/v2/discovered_hosts/:id/refresh_facts

2016-09-16 Thread 'Konstantin Orekhov' via Foreman users

>
>
> > $ curl -kSs -H "Content-Type: application/json" -H 
> > "Accept:application/json" -u admin:$PASSWORD 
> > https://localhost/api/v2/discovered_hosts/mac008cfaed69c8/refresh_facts 
> | 
> > jq '.' 
> > { 
> >   "status": "404", 
> >   "error": "Not Found" 
> > } 
>
> This API call is not HTTP GET but HTTP PUT. 
>
>
Thanks, Lukas, it certainly works now. I thought of that, but "GET" method 
in production.log from a WebUI threw me off the right course.
 

-- 
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] Adding tftp / pxe target

2016-09-16 Thread 'Jason B. Nance' via Foreman users
Hello,

After I installed and configured (all via the web UI) Katello 3.1 / Foreman 
1.12 and synced CentOS 7 repositories it seems that all of the tftp/pxe stuff 
necessary to do pxe installs of CentOS was automagically setup for me.

For example, /var/lib/tftpboot/boot contains:

CentOS-7-x86_64-initrd.img
CentOS-7-x86_64-vmlinuz

...and 
/var/lib/pulp/published/yum/http/repos/My_Org/Library/custom/centos/c7/LiveOS/squashfs.img
 exists.

I'm trying to add pxe boot/install support for OEL 7.  I created similar 
products, content views, media, and OS as I have for CentOS.  I used host 
discovery to create a new host entry and selected the OEL stuff I setup.  
/var/lib/tftpboot/boot/OracleLinux-7-x86_64-initrd.img and 
OracleLinux-7-x86_64-vmlinuz where created for me, but they were 0 byte files.  
So I manually replaced those files with the appropriate ones from the OEL 
"boot" CD.

However, the installer now fails because 
/var/lib/pulp/published/yum/http/repos/My_Org/Library/custom/oel/o7/LiveOS/squashfs.img
 doesn't exist.

What is supposed to create those files?  Is there a hammer command I should run 
or something?

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

2016-09-16 Thread Andrew Schofield
Ok, for anybody who is curious.

Doing a PUT to /provisioning_templates/:id with

{"provisioning_template" : {"template_combinations_attributes" : 
[{"hostgroup_id" : "73"}, {"hostgroup_id" : "77"}, {"hostgroup_id" : "81"}, 
{"hostgroup_id" : "85"}]}}

Seems to do this trick.

On Thursday, September 15, 2016 at 9:58:37 PM UTC-4, Andrew Schofield wrote:

> 2 years later and it still doesn't!I've lost a few hours today trying to 
> figure this out!
>
> My next question though is how do we do this via the API? Taking a look at 
> what is generated by foreman:
>
> 2016-09-15T21:46:41 [app] [I] Started PATCH 
> "/templates/provisioning_templates/22-Kickstart%20RHEL%20default" for 
> 127.0.0.1 at 2016-09-15 21:46:41 -0400
>
> 2016-09-15T21:46:42 [app] [I] Processing by 
> ProvisioningTemplatesController#update as */*
>
> 2016-09-15T21:46:42 [app] [I]   Parameters: {"utf8"=>"✓", 
> "authenticity_token"=>"RMIiR7+Dn1xqM8EL0IvjeLwKrFvBGkDm+x36bAU1K5k=", 
> "provisioning_template"=>{"name"=>"Kickstart RHEL default", "default"=>"1", 
> "template"=>"SNIP", "audit_comment"=>"", "snippet"=>"0", 
> "template_kind_id"=>"4", "operatingsystem_ids"=>[""], 
> "template_combinations_attributes"=>{"1473990106406"=>{"hostgroup_id"=>"1", 
> "environment_id"=>"", "_destroy"=>"false"}}, "location_ids"=>["", "1"], 
> "organization_ids"=>["", "2"]}, "preview_host_id"=>"2", "mode"=>"ruby", 
> "keybinding"=>"Default", "id"=>"22-Kickstart RHEL default"}
>
> It *looks* like this might be done via template_combinations_attributes 
> and a PATCH method. Neither of these are documented in the API calls at 
> https://theforeman.org/api/1.12/index.html. Does anybody know? Likewise 
> for assigning a template to an OS...
>
> On Wednesday, July 16, 2014 at 1:16:11 PM UTC-4, Greg Sutcliffe wrote:
>>
>> Good stuff! Yeah, that feature doesn't get enough coverage, and it's 
>> very useful :) 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


Re: [foreman-users] Adding tftp / pxe target

2016-09-16 Thread 'Jason B. Nance' via Foreman users
It has become apparent to me that the bigger issue here is that the Yum repos 
I'm syncing for OEL from Oracle aren't kickstart trees, so they are missing 
files such as squashfs.img.  My first thought after that realization was to 
just slap the missing files into /var/lib/pulp/..., but that felt like a recipe 
for future problems.  Now the path I'm headed down is to mount the installation 
DVD and sync it.

If anyone has had to deal with OEL or just has another idea in general I'm open.

Big thanks to stbenjam in IRC for the info and ideas.

j


- Original Message -
From: "'Jason B. Nance' via Foreman users" 
To: foreman-users@googlegroups.com
Sent: Friday, September 16, 2016 2:30:53 PM
Subject: [foreman-users] Adding tftp / pxe target

Hello,

After I installed and configured (all via the web UI) Katello 3.1 / Foreman 
1.12 and synced CentOS 7 repositories it seems that all of the tftp/pxe stuff 
necessary to do pxe installs of CentOS was automagically setup for me.

For example, /var/lib/tftpboot/boot contains:

CentOS-7-x86_64-initrd.img
CentOS-7-x86_64-vmlinuz

...and 
/var/lib/pulp/published/yum/http/repos/My_Org/Library/custom/centos/c7/LiveOS/squashfs.img
 exists.

I'm trying to add pxe boot/install support for OEL 7.  I created similar 
products, content views, media, and OS as I have for CentOS.  I used host 
discovery to create a new host entry and selected the OEL stuff I setup.  
/var/lib/tftpboot/boot/OracleLinux-7-x86_64-initrd.img and 
OracleLinux-7-x86_64-vmlinuz where created for me, but they were 0 byte files.  
So I manually replaced those files with the appropriate ones from the OEL 
"boot" CD.

However, the installer now fails because 
/var/lib/pulp/published/yum/http/repos/My_Org/Library/custom/oel/o7/LiveOS/squashfs.img
 doesn't exist.

What is supposed to create those files?  Is there a hammer command I should run 
or something?

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.

-- 
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: how to upgrade 1.12.1 to 1.12.2

2016-09-16 Thread Michael Hurn
Hi Erik,
It looks like you may have gone too deep with Foreman.

The manual gives us a very good guide.

https://theforeman.org/manuals/1.12/index.html#3.6Upgrade

In short on RedHat/CentOS systems stop foreman & proxy, run yum upgrade and 
restart Foreman.
I have upgraded Foreman a few times. I think my first upgrade we to Foreman 
1.4.2.


On Friday, September 16, 2016 at 1:13:44 PM UTC-4, Erik Hjelmås wrote:

> Hi, 
>
> sorry but Im not able to figure out how to do this, I use the 
> foreman-installer, and Ive tried
> foreman-installer --foreman-version=latest
> but foreman still says 1.12.1 (login page and ~foreman/VERSION)
>
> any help greatly appreciated, 
>
> have a good weekend everyone, 
>
> /Erik
>

-- 
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: how to upgrade 1.12.1 to 1.12.2

2016-09-16 Thread Erik Hjelmås
thanks Michael, you are absolutely correct, 

I was under the impression that puppet (foreman-installer) would take care 
of upgrading as well, but not so (yes I should have rtfm more carefully), a 
simple apt-get update/upgrade did the upgrade and foreman-installer ran 
also successfully afterwards

/Erik

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