[foreman-users] Re: Setup 802.3ad bond during PXE

[Duncan Innes]

We regularly do PXE provisioning over ports that are generally configured 
for bonding.  The network guys have to set the force-up parameter (forgive 
me if that's not absolutely accurate, but they translate my non-network 
speak and get it working).  This is on Juniper switches.

The result is that the PXE can happen over one of the ports for a limited 
time after the port comes up (the time here is configurable) before it 
reverts to bonding-only operation. 

D

On Wednesday, 25 October 2017 17:12:08 UTC+1, Jagga Soorma wrote:
>
> Hello, 
>
> I have to provision a server via foreman that has lacp setup on the 2 
> switch ports it is connected to and the default fallback timeout is 
> set too high which I cannot control.  This means that I cannot 
> provision the host using a single nic and have to setup a bond during 
> the pxe process.  I have tried to setup the bond in the interfaces 
> section of my host when creating it in foreman but during pxe bootup 
> it does not even seem to load the bonding driver and no bond interface 
> is setup.  Is this even possible using foreman?  If so, can someone 
> help me with this please.  I have a urgent need to get this server up 
> and any assistance would be greatly appreciated! 
>
> Thanks in advance. 
> -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.

[foreman-users] Re: Pulp internal server error

[Duncan Innes]

Same happened to me yesterday, but I had forgotten to run:

foreman-installer --scenario katello --upgrade

Did you run this part?  If not, this would be the reason for your problem. 
 You could verify this by looking at /var/log/foreman/production.log.  Your 
500 errors will look similar to:

2017-07-17 12:35:53 37103215 [app] [I] Started GET 
"/katello/sync_management" for 192.168.122.1 at 2017-07-17 12:35:53 +0100
2017-07-17 12:35:53 37103215 [app] [I] Processing by 
Katello::SyncManagementController#index as HTML
2017-07-17 12:35:53 37103215 [app] [I] Current user: admin (administrator)
2017-07-17 12:35:53 37103215 [katello/pulp_rest] [E] RestClient.post 
"https://katello.innes.net/pulp/api/v2/repositories/search/;, 614 byte(s) 
length, "Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, 
deflate", "Content-Length"=>"614", "accept"=>"application/json", 
"content_type"=>"application/json"
 | \n# => 500 InternalServerError | text/html 531 bytes
 | 
2017-07-17 12:35:53 37103215 [app] [I] Completed 500 Internal Server Error 
in 49ms (ActiveRecord: 4.1ms)
2017-07-17 12:35:53 37103215 [app] [F] 
 | RestClient::InternalServerError (500 Internal Server Error):
 |   katello (3.4.2) app/models/katello/glue/pulp/repos.rb:53:in 
`prepopulate!'
 |   katello (3.4.2) app/helpers/katello/sync_management_helper.rb:38:in 
`collect_repos'
 |   katello (3.4.2) 
app/controllers/katello/sync_management_controller.rb:29:in `index'
 |   app/controllers/concerns/application_shared.rb:15:in `set_timezone'
 |   app/controllers/concerns/foreman/controller/topbar_sweeper.rb:12:in 
`set_topbar_sweeper_controller'
 |   katello (3.4.2) lib/katello/params_parser_wrapper.rb:12:in `call'
 |   lib/middleware/catch_json_parse_errors.rb:8:in `call'
 |   lib/middleware/tagged_logging.rb:18:in `call'
 | 
 | 

You see Katello is being referenced as (3.4.2) rather than (3.4.3).

Posting this part of your production.log will also help diagnose the 
problem if this isn't the cause.

D

On Tuesday, 18 July 2017 08:48:11 UTC+1, Arsène Gschwind wrote:
>
> Hi all,
>
> I'm pretty new to Katello and Foreman and since I've updated pulp to the 
> latest version I'm not able to use any function/feature of it, 
> Katello/foreman throws always the following error:
>
> There was an issue with the backend service pulp: 500 Internal Server Error
>
>
> I've tried to debug what's going on but could locate anything in the logs 
> so far.
>
> Here the version I'm running:
> katello-3.4.3-1.el7.noarch
> foreman-1.15.2-1.el7.noarch
> pulp-client-1.0-1.noarch
> pulp-docker-plugins-2.4.0-2.el7.noarch
> pulp-katello-1.0.2-1.el7.noarch
> pulp-puppet-plugins-2.13.2-1.el7.noarch
> pulp-puppet-tools-2.13.2-1.el7.noarch
> pulp-rpm-plugins-2.13.2-1.el7.noarch
> pulp-selinux-2.13.2-1.el7.noarch
> pulp-server-2.13.2-1.el7.noarch
>
> Thanks for any help to debug that problem.
>
> rgds,
> Arsène
>

-- 
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] Vertical Nav demo

[Duncan Innes]

Is there any way to leave a semi-interactive demo of the vertical nav for 
users to see?

I put together an amateur patternfly demo for Rockstor in my fork of the 
patternfly repo 
(https://rawgit.com/duncaninnes/patternfly/master/tests/rockstor5.html#). 
 It's not great, but allowed people to see what patternfly could bring.

If the demo videos and screenshots for vertical nav were done in a similar 
way, are they available to actually interact with?

Duncan 

-- 
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 not showing available Updates

[Duncan Innes]

I've done this a few times and not noticed that the client was subscribed 
to the wrong view (i.e. a view that didn't have the new RPMs).

What does yum update on the client say?  Does it show the new nginx as 
available for upgrade?  Is it showing you the repositories that you expect 
from your Katello?

On Tuesday, 6 June 2017 07:18:56 UTC+1, Tim Hofmann wrote:
>
> Hi Eric,
>
> thanks for your answer.
>
> - Check. Katello Agent is installed and Running. UI also indicates that.
> - Yes, the outdatet nginx is listed under installed packages.
> - Yes, the content Host is registered to a Content View (via Activation 
> Key). Auto-Attach is disabled and all needed Subsrciptions are added.
>
> I already tried to restart the goferd agent and checked the logs. No Error 
> or hint is logged :-(
>
> Tim
>
> Am Samstag, 3. Juni 2017 17:29:09 UTC+2 schrieb Eric Helms:
>>
>> Howdy Tim,
>>
>> Let's check a few items to narrow down what the issue might be:
>>
>>  * you've got katello-agent installed on the host and goferd is running; 
>> does the UI indicate that it knows katello-agent is installed?
>>  * if you look at the package list for the content host do you see the 
>> outdated nginx listed?
>>  * The content host is currently registered to a content view that 
>> contains the EPEL repository? (I assume yes since yum update picks up the 
>> update but just checking)
>>
>> You could try restarting goferd on the host.
>>
>> Eric
>>
>> On Jun 3, 2017 10:07 AM, "Tim Hofmann"  wrote:
>>
>> Hey guys,
>>
>> i got a strange issue. I did a fresh install of katello 3.4 on CentOS 7.
>> On a second CentOs 7 VM i installed an outdated nginx version.
>> On the next step i added the EPEL Repo's to Katello synced them and added 
>> my Outdated nginx VM. I also installed the katello agent on this vm.
>>
>> The Problem is now that katello isnt't showing up any availible updates 
>> for my outdated nginx VM (on yum update the newer version on nginx is 
>> showing up).
>>
>> Is this by design or i am doing something wrong?
>>
>> thanks in advance and sorry for my bad english :-/
>>
>> -- 
>> 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.
>>
>>
>>

-- 
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.4 (Oud Bruin) Released!

[Duncan Innes]

They've changed now.  Might I have been hitting a cache?

On Tuesday, 30 May 2017 13:30:53 UTC+1, Eric Helms wrote:
>
> Duncan,
>
> Can you point me to which website page/link you are meaning?
>
> On Tue, May 30, 2017 at 8:20 AM, Duncan Innes <dun...@innes.net 
> > wrote:
>
>> The install docs are still referencing 3.3 as the latest stable versions 
>> and referring to 3.4 as 3.4-RC.
>>
>>
>> On Monday, 29 May 2017 05:32:56 UTC+1, Eric Helms wrote:
>>>
>>> All,
>>>
>>> We are happy to announce the GA of Katello 3.4. Highlights of the 
>>> release:
>>>
>>>  * Better file repository content management
>>>  * Advanced repository syncing options for recovery and repair
>>>  * UI overhaul
>>>  * Content view force republishing
>>>  * Candlepin 2.0 support
>>>  * Pulp 2.12.2
>>>
>>> Release Notes:
>>>
>>> https://theforeman.org/plugins/katello/3.4/release_notes/release_notes.html
>>>
>>> Installation:
>>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>>
>>> Upgrade:
>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>>
>>> See the changelog for detailed feature issues and bug fixes:
>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md 
>>>
>>> Bug reporting
>>> =
>>> If you come across a bug in your testing, please file it and note the
>>> version of Katello or Foreman that you're using in the report.
>>>
>>> http://projects.theforeman.org/projects/katello/issues/new
>>>
>>> -- 
>>> Eric D. Helms
>>> Red Hat Engineering
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to foreman-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.
>>
>
>
>
> -- 
> Eric D. Helms
> Red Hat Engineering
>

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

Re: [foreman-users] Pulp repo question

[Duncan Innes]

I'm using the following details in my kickstart to reference the Katello 
repo:

repo --name=base 
--baseurl=http://katello.innes.net/pulp/repos/Innes/Library/custom/CentOS/CentOS_7_Base/

which is a repo synched from:

https://www.mirrorservice.org/sites/mirror.centos.org/7.3.1611/os/x86_64/

The repodata folder 
at 
http://katello.innes.net/pulp/repos/Innes/Library/custom/CentOS/CentOS_7_Base/repodata/
 
looks to be OK:

Pulp Repository Content

Parent Directory
09c8cf47ffd4374eae88e90cea8c92db1d46d9f8e9482b0f088c24ecd78f5ef0-primary.xml.gz
32d1bd57e5b4d4d808067410f828bd5510a30fe2d1aa07cf3656f16e477ff013-updateinfo.xml.gz
36d3b10fb997c1ac060e94aa18ffb5b8b24f92847b04c1e43b6273066227cca4-comps.xml
9cade24107fa18e444f2c8368769551823acc2737263696c2d76347d4aa51caf-other.xml.gz
a201db3450a1b11073fb0e43c1b1ce0995ca7284220bc7634a601467461209a4-updateinfo.xml.gz
a27718cc28ec6d71432e0ef3e6da544b7f9d93f6bb7d0a55aacd592d03144b70-comps.xml
d5f936c0bdab52caa62fb9a06aa407f1969e34ca6489b6301cb0a5b6d021a9b3-filelists.xml.gz
f84b9f6fb20edbd5bc5f02fadf6a19b82bc8177abff708f0f5989549b50841f0-updateinfo.xml.gz
repomd.xml

Am I looking in the wrong place here?

On Monday, 8 May 2017 11:22:55 UTC+1, Sean O'Keeffe wrote:
>
> That's just an API for adding additional groups. For a long time any yum 
> repo Pulp syncs it should also copy the package groups defined, I guess 
> your problem might be the source you are syncing from doesn't have any 
> package group defined in the metadata?
>
> On Mon, May 8, 2017 at 10:34 AM, Duncan Innes <dun...@innes.net 
> > wrote:
>
>> So will the package groups be created automatically for each repo in 
>> 3.4?  Or is it just that the API is available for use?
>>
>> I'll be rebuilding from scratch on 3.4 soon, so am not worried about the 
>> state of my 3.3 system.
>>
>> On Monday, 8 May 2017 09:06:14 UTC+1, Sean O'Keeffe wrote:
>>>
>>> Pulp does support package groups creation..
>>>
>>> In Katello 3.4 (to be released) there's an API:
>>> POST API at /katello/api/package_groups for creation and a DELETE API 
>>> at /katello/api/package_groups for deletion.
>>>
>>> In Katello3.3 you can:
>>> Step 1:
>>> pulp-admin rpm repo uploads group \
>>>  --user-visible=true \
>>>  --repo-id=rhel-ebi-package-groups \
>>>  --group-id=package-group-gpfs-client-4.1.0-8 \
>>>  --name="Package Group for GPFS 4.1.0-8 clients" \
>>>  --description="Package Group for GPFS 4.1.0-8 clients" \
>>>  --mand-name=gpfs.docs \
>>>  --mand-name=gpfs.gpl \
>>>  --mand-name=gpfs.msg.en_US \
>>>  --mand-name=gpfs.base \
>>>  --mand-name=gpfs.gskit \ 
>>>  --mand-name=gpfs.ext
>>>
>>> Step 2:
>>> foreman-rake console
>>> > Katello::PackageGroup.import_all
>>>
>>> Step 3:
>>> Force regenerate repo metadata
>>>
>>>
>>> On Wed, May 3, 2017 at 12:45 PM, Lukas Zapletal <lz...@redhat.com> 
>>> wrote:
>>>
>>>> I think that Pulp does not support creating packagegroups, you will
>>>> only find these on original DVDs or kickstart repositories on CDN.
>>>> Better to ask at pulp-users tho.
>>>>
>>>> LZ
>>>>
>>>> On Wed, Apr 26, 2017 at 10:29 AM, Duncan Innes <dun...@innes.net> 
>>>> wrote:
>>>> > Hi,
>>>> >
>>>> > This week has seen me building bespoke LiveCD images for a client to 
>>>> allow
>>>> > specific firmware bundles to be installed on hardware.  To do this I 
>>>> was
>>>> > using the older method:
>>>> >
>>>> > livecd-creator --config=centos.ks -f LiveCD
>>>> >
>>>> > to create my LiveCD.iso.  The Foreman/Katello/Pulp side of my 
>>>> questions
>>>> > comes from the kickstart file I was using.  I tried to use the Pulp 
>>>> repos
>>>> > that I had created in my Katello system.  They're perfectly viewable 
>>>> in a
>>>> > browser and look just like what a repo is supposed to look like.  But 
>>>> when I
>>>> > ran the livecd-creator command, I got complaints that the core group
>>>> > couldn't be found.  When I change the kickstart to point at internet 
>>>> CentOS
>>>> > repos, or even the copy of the CentOS DVD which I also serve via http,
>>>> > things worked fine.
>>>> >
>>>> > I didn't have time to figure out why the Katello repos were failing.  
>>>> But is
>>>&

Re: [foreman-users] Pulp repo question

[Duncan Innes]

So will the package groups be created automatically for each repo in 3.4? 
 Or is it just that the API is available for use?

I'll be rebuilding from scratch on 3.4 soon, so am not worried about the 
state of my 3.3 system.

On Monday, 8 May 2017 09:06:14 UTC+1, Sean O'Keeffe wrote:
>
> Pulp does support package groups creation..
>
> In Katello 3.4 (to be released) there's an API:
> POST API at /katello/api/package_groups for creation and a DELETE API at 
> /katello/api/package_groups for deletion.
>
> In Katello3.3 you can:
> Step 1:
> pulp-admin rpm repo uploads group \
>  --user-visible=true \
>  --repo-id=rhel-ebi-package-groups \
>  --group-id=package-group-gpfs-client-4.1.0-8 \
>  --name="Package Group for GPFS 4.1.0-8 clients" \
>  --description="Package Group for GPFS 4.1.0-8 clients" \
>  --mand-name=gpfs.docs \
>  --mand-name=gpfs.gpl \
>  --mand-name=gpfs.msg.en_US \
>  --mand-name=gpfs.base \
>  --mand-name=gpfs.gskit \ 
>  --mand-name=gpfs.ext
>
> Step 2:
> foreman-rake console
> > Katello::PackageGroup.import_all
>
> Step 3:
> Force regenerate repo metadata
>
>
> On Wed, May 3, 2017 at 12:45 PM, Lukas Zapletal <lz...@redhat.com 
> > wrote:
>
>> I think that Pulp does not support creating packagegroups, you will
>> only find these on original DVDs or kickstart repositories on CDN.
>> Better to ask at pulp-users tho.
>>
>> LZ
>>
>> On Wed, Apr 26, 2017 at 10:29 AM, Duncan Innes <dun...@innes.net 
>> > wrote:
>> > Hi,
>> >
>> > This week has seen me building bespoke LiveCD images for a client to 
>> allow
>> > specific firmware bundles to be installed on hardware.  To do this I was
>> > using the older method:
>> >
>> > livecd-creator --config=centos.ks -f LiveCD
>> >
>> > to create my LiveCD.iso.  The Foreman/Katello/Pulp side of my questions
>> > comes from the kickstart file I was using.  I tried to use the Pulp 
>> repos
>> > that I had created in my Katello system.  They're perfectly viewable in 
>> a
>> > browser and look just like what a repo is supposed to look like.  But 
>> when I
>> > ran the livecd-creator command, I got complaints that the core group
>> > couldn't be found.  When I change the kickstart to point at internet 
>> CentOS
>> > repos, or even the copy of the CentOS DVD which I also serve via http,
>> > things worked fine.
>> >
>> > I didn't have time to figure out why the Katello repos were failing.  
>> But is
>> > there any obvious reason that I couldn't be using my Katello repos in 
>> this
>> > way?
>> >
>> > The kickstart file was using the URL shown in "Published At" in `hammer
>> > repository info --id=1`.  It's an on-demand repo, but I've installed 
>> many
>> > systems with much larger %packages sections than this LiveCD.
>> >
>> > It's a Foreman 1.14.3 & Katello 3.3.1 system.
>> >
>> > Cheers
>> >
>> > Duncan
>> >
>> > --
>> > 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-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.
>>
>
>

-- 
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] Pulp repo question

[Duncan Innes]

Hi,

This week has seen me building bespoke LiveCD images for a client to allow 
specific firmware bundles to be installed on hardware.  To do this I was 
using the older method:

livecd-creator --config=centos.ks -f LiveCD

to create my LiveCD.iso.  The Foreman/Katello/Pulp side of my questions 
comes from the kickstart file I was using.  I tried to use the Pulp repos 
that I had created in my Katello system.  They're perfectly viewable in a 
browser and look just like what a repo is supposed to look like.  But when 
I ran the livecd-creator command, I got complaints that the core group 
couldn't be found.  When I change the kickstart to point at internet CentOS 
repos, or even the copy of the CentOS DVD which I also serve via http, 
things worked fine.

I didn't have time to figure out why the Katello repos were failing.  But 
is there any obvious reason that I couldn't be using my Katello repos in 
this way?

The kickstart file was using the URL shown in "Published At" in `hammer 
repository info --id=1`.  It's an on-demand repo, but I've installed many 
systems with much larger %packages sections than this LiveCD.

It's a Foreman 1.14.3 & Katello 3.3.1 system.

Cheers

Duncan

-- 
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.3.1 released!

[Duncan Innes]

It looks like you're correct about this.  I'm waiting a potential patch to 
remote execution that should get past this.  Upgrading to the latest 
release of remote execution isn't possible at this point due to another 
outstanding issue.  In the meantime, my test system is offline.

Perhaps the patched remote execution plugin could be released with 3.3.1 
and the fully updated plugin waits until everything is working again?

D

On Thursday, 23 March 2017 22:46:08 UTC, Jason B. Nance wrote:
>
> FYI, I opened http://projects.theforeman.org/issues/19015 for this.
>
>
>
> --
> *From: *"Jason Nance" <ja...@tresgeek.net >
> *To: *"Foreman Users" <forema...@googlegroups.com >
> *Sent: *Thursday, March 23, 2017 5:32:40 PM
> *Subject: *Re: [foreman-users] Re: Katello 3.3.1 released!
>
> So does this mean that you can't upgrade to 3.3 if you have the remote 
> execution plugin installed/enabled?  I'm running into the same error.
>
> In my case I'm attempting to upgrade to get a newer Pulp to resolve this:
>
> https://pulp.plan.io/issues/2344
>
> ...which basically allows Pulp to work with a proxy when the upstream is 
> https.
>
>
>
> --
> *From: *"Eric D Helms" <ericd...@gmail.com >
> *To: *"Foreman Users" <forema...@googlegroups.com >
> *Sent: *Thursday, March 23, 2017 8:56:06 AM
> *Subject: *Re: [foreman-users] Re: Katello 3.3.1 released!
>
> I believe this is the key error "ArgumentError: Unknown key: 
> :host_action_button. Valid keys are: :provided_inputs, :description" which 
> comes from foreman_remote_execution having an older release. This is fixed 
> in master of the plugin but releasing a newer version is blocked by other 
> issues that are being worked on.
>
> On Thu, Mar 23, 2017 at 9:14 AM, Duncan Innes <dun...@innes.net 
> > wrote:
>
>> I'm not skilled in diagnosing log files, but I see the following in 
>> katello.1.log and katello.log:
>>
>>1. [ INFO 2017-03-22 10:58:20 main] Upgrade Step: migrate_foreman...
>>2. [ERROR 2017-03-22 10:58:25 main]
>>3. [ERROR 2017-03-22 10:58:31 main] API controllers newer than Apipie 
>>cache! Run apipie:cache rake task to regenerate cache.
>>4. rake aborted!
>>
>> Is this the source of the problem, or just a symptom of an underlying 
>> issue?
>>
>> Duncan
>>
>> On Wednesday, 22 March 2017 12:21:15 UTC, Duncan Innes wrote:
>>>
>>>
>>> Apologies, forgot about my pastebin account until midway through 
>>> splitting initial log file:
>>> [root@katello ~]# cd /var/log/foreman-installer/
>>> [root@katello foreman-installer]# ls -lrt
>>> total 3572
>>> -rw-r--r--. 1 root root   0 Feb 28 21:47 foreman.2.log
>>> -rw-r--r--. 1 root root   0 Feb 28 21:48 katello.6.log
>>> -rw-r--r--. 1 root root   15751 Feb 28 21:50 katello.5.log
>>> -rw-r--r--. 1 root root 2172590 Feb 28 23:27 katello.4.log
>>> -rw-r--r--. 1 root root8553 Mar 22 10:47 foreman.1.log   <- 
>>> http://pastebin.com/ep4HajV5
>>> -rw-r--r--. 1 root root1212 Mar 22 10:47 foreman.log <- 
>>> http://pastebin.com/TVixt0eK
>>> -rw-r--r--. 1 root root 1338785 Mar 22 10:48 katello.3.log   <- 
>>> http://pastebin.com/530ih26P
>>> -rw-r--r--. 1 root root8624 Mar 22 10:49 katello.2.log   <- 
>>> http://pastebin.com/d7RLn3Hw
>>> -rw-r--r--. 1 root root   49047 Mar 22 10:55 katello.1.log   <- 
>>> http://pastebin.com/G0EFGwCa
>>> -rw-r--r--. 1 root root   48628 Mar 22 10:58 katello.log <- 
>>> http://pastebin.com/UDTTjrwU
>>> [root@katello foreman-installer]# 
>>>
>>>
>>> On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote:
>>>>
>>>> What errors?
>>>>
>>>  
>>>
>> -- 
>> 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.
>>
>
>
>
> -- 
> Eric D. Helms
> Red Hat Engineering
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to foreman-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.
>
>

-- 
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.3.1 released!

[Duncan Innes]

I'm not skilled in diagnosing log files, but I see the following in 
katello.1.log and katello.log:


   1. [ INFO 2017-03-22 10:58:20 main] Upgrade Step: migrate_foreman...
   2. [ERROR 2017-03-22 10:58:25 main]
   3. [ERROR 2017-03-22 10:58:31 main] API controllers newer than Apipie 
   cache! Run apipie:cache rake task to regenerate cache.
   4. rake aborted!
   
Is this the source of the problem, or just a symptom of an underlying issue?

Duncan

On Wednesday, 22 March 2017 12:21:15 UTC, Duncan Innes wrote:
>
>
> Apologies, forgot about my pastebin account until midway through splitting 
> initial log file:
>
> [root@katello ~]# cd /var/log/foreman-installer/
> [root@katello foreman-installer]# ls -lrt
> total 3572
> -rw-r--r--. 1 root root   0 Feb 28 21:47 foreman.2.log
> -rw-r--r--. 1 root root   0 Feb 28 21:48 katello.6.log
> -rw-r--r--. 1 root root   15751 Feb 28 21:50 katello.5.log
> -rw-r--r--. 1 root root 2172590 Feb 28 23:27 katello.4.log
> -rw-r--r--. 1 root root8553 Mar 22 10:47 foreman.1.log   <- 
> http://pastebin.com/ep4HajV5
> -rw-r--r--. 1 root root1212 Mar 22 10:47 foreman.log <- 
> http://pastebin.com/TVixt0eK
> -rw-r--r--. 1 root root 1338785 Mar 22 10:48 katello.3.log   <- 
> http://pastebin.com/530ih26P
> -rw-r--r--. 1 root root8624 Mar 22 10:49 katello.2.log   <- 
> http://pastebin.com/d7RLn3Hw
> -rw-r--r--. 1 root root   49047 Mar 22 10:55 katello.1.log   <- 
> http://pastebin.com/G0EFGwCa
> -rw-r--r--. 1 root root   48628 Mar 22 10:58 katello.log <- 
> http://pastebin.com/UDTTjrwU
> [root@katello foreman-installer]# 
>
>
> On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote:
>>
>> What errors?
>>
>  
>

-- 
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.3.1 released!

[Duncan Innes]

Apologies, forgot about my pastebin account until midway through splitting 
initial log file:

[root@katello ~]# cd /var/log/foreman-installer/
[root@katello foreman-installer]# ls -lrt
total 3572
-rw-r--r--. 1 root root   0 Feb 28 21:47 foreman.2.log
-rw-r--r--. 1 root root   0 Feb 28 21:48 katello.6.log
-rw-r--r--. 1 root root   15751 Feb 28 21:50 katello.5.log
-rw-r--r--. 1 root root 2172590 Feb 28 23:27 katello.4.log
-rw-r--r--. 1 root root8553 Mar 22 10:47 foreman.1.log   
<- http://pastebin.com/ep4HajV5
-rw-r--r--. 1 root root1212 Mar 22 10:47 foreman.log 
<- http://pastebin.com/TVixt0eK
-rw-r--r--. 1 root root 1338785 Mar 22 10:48 katello.3.log   
<- http://pastebin.com/530ih26P
-rw-r--r--. 1 root root8624 Mar 22 10:49 katello.2.log   
<- http://pastebin.com/d7RLn3Hw
-rw-r--r--. 1 root root   49047 Mar 22 10:55 katello.1.log   
<- http://pastebin.com/G0EFGwCa
-rw-r--r--. 1 root root   48628 Mar 22 10:58 katello.log 
<- http://pastebin.com/UDTTjrwU
[root@katello foreman-installer]# 


On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote:
>
> What errors?
>
 

-- 
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.3.1 released!

[Duncan Innes]

On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote:
>
> What errors?
>

 Continued: (full log available at http://pastebin.com/UDTTjrwU)


[ INFO 2017-03-22 10:55:36 main] Executing hooks in group pre
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/10-reset_feature.rb returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/11-clear_pulp_data_feature.rb 
returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/12-clear_puppet_environments_feature.rb
 
returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/15-check_java.rb returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/16-set_umask.rb returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/17-memory_check.rb returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/18-vm_overcommit.rb returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/19-devlog.rb returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/20-certs_update.rb returned nil
[DEBUG 2017-03-22 10:55:36 main] Hook 
/usr/share/katello-installer-base/hooks/pre/29-remove_package_httpd_conf.rb 
returned ["pulp.conf"]
[ INFO 2017-03-22 10:55:36 main] Upgrading...
[ INFO 2017-03-22 10:55:36 main] Upgrade Step: stop_services...
[DEBUG 2017-03-22 10:55:48 main] Redirecting to /bin/systemctl stop 
 foreman-tasks.service

Redirecting to /bin/systemctl stop  httpd.service

Redirecting to /bin/systemctl stop  pulp_celerybeat.service

Redirecting to /bin/systemctl stop  foreman-proxy.service

Redirecting to /bin/systemctl stop  pulp_streamer.service

Redirecting to /bin/systemctl stop  pulp_resource_manager.service

Redirecting to /bin/systemctl stop  smart_proxy_dynflow_core.service

Redirecting to /bin/systemctl stop  pulp_workers.service

Redirecting to /bin/systemctl stop  tomcat.service

Redirecting to /bin/systemctl stop  squid.service

Redirecting to /bin/systemctl stop  qdrouterd.service

Redirecting to /bin/systemctl stop  qpidd.service

Success!

[ INFO 2017-03-22 10:55:48 main] Upgrade Step: start_databases...
[DEBUG 2017-03-22 10:55:58 main] Redirecting to /bin/systemctl start 
 mongod.service

Redirecting to /bin/systemctl start  postgresql.service

Success!

[ INFO 2017-03-22 10:55:58 main] Upgrade Step: update_http_conf...
[DEBUG 2017-03-22 10:55:58 main] 
[ INFO 2017-03-22 10:55:58 main] Upgrade Step: migrate_pulp...
[DEBUG 2017-03-22 10:55:58 main] 
[DEBUG 2017-03-22 10:55:58 main] 
[DEBUG 2017-03-22 10:55:58 main] 1023

[DEBUG 2017-03-22 10:55:59 main] Attempting to connect to localhost:27017
Attempting to connect to localhost:27017
Write concern for Mongo connection: {}
Loading content types.
Loading type descriptors []
Parsing type descriptors
Validating type descriptor syntactic integrity
Validating type descriptor semantic integrity
Loading unit model: docker_blob = pulp_docker.plugins.models:Blob
Loading unit model: docker_manifest = pulp_docker.plugins.models:Manifest
Loading unit model: docker_image = pulp_docker.plugins.models:Image
Loading unit model: docker_tag = pulp_docker.plugins.models:Tag
Loading unit model: puppet_module = pulp_puppet.plugins.db.models:Module
Loading unit model: erratum = pulp_rpm.plugins.db.models:Errata
Loading unit model: distribution = pulp_rpm.plugins.db.models:Distribution
Loading unit model: srpm = pulp_rpm.plugins.db.models:SRPM
Loading unit model: package_group = pulp_rpm.plugins.db.models:PackageGroup
Loading unit model: package_category = 
pulp_rpm.plugins.db.models:PackageCategory
Loading unit model: iso = pulp_rpm.plugins.db.models:ISO
Loading unit model: package_environment = 
pulp_rpm.plugins.db.models:PackageEnvironment
Loading unit model: drpm = pulp_rpm.plugins.db.models:DRPM
Loading unit model: package_langpacks = 
pulp_rpm.plugins.db.models:PackageLangpacks
Loading unit model: rpm = pulp_rpm.plugins.db.models:RPM
Loading unit model: yum_repo_metadata_file = 
pulp_rpm.plugins.db.models:YumMetadataFile
Updating the database with types []
Found the following type definitions that were not present in the update 
collection [puppet_module, drpm, package_langpacks, erratum, docker_blob, 
docker_manifest, yum_repo_metadata_file, package_group, package_category, 
iso, package_environment, docker_tag, srpm, rpm, distribution, docker_image]
Updating the database with types [puppet_module, drpm, package_langpacks, 
erratum, docker_blob, docker_manifest, yum_repo_metadata_file, 
package_group, package_category, iso, package_environment, docker_tag, 
distribution, rpm, srpm, docker_image]
Content types loaded.
Ensuring the admin role and user are in place.
Admin role and user are in place.
Beginning database migrations.
Migration package pulp.server.db.migrations is up to date at 

Re: [foreman-users] Re: Katello 3.3.1 released!

[Duncan Innes]

On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote:
>
> What errors?
>

Following comes from /var/log/foreman-installer/katello.log

[root@katello ~]# cat /var/log/foreman-installer/katello.log 
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/01-migrate_legacy_foreman_installer_config.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/10-migrate_legacy_capsule_config.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/11-migrate_legacy_katello_config.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/01-helpers.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/10-reset_hook.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/11-clear_pulp_data_hook.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/12-clear_puppet_environments.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/17-disable_system_checks.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/18-force_upgrade_hooks.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/20-certs_update.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/30-upgrade.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/31-upgrade-puppet.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/init/10-puppet-profile-on-el6.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/10-reset_feature.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/11-clear_pulp_data_feature.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/12-clear_puppet_environments_feature.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/15-check_java.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/16-set_umask.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/17-memory_check.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/18-vm_overcommit.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/19-devlog.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/20-certs_update.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/29-remove_package_httpd_conf.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/30-upgrade.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/post/10-post_install.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/post/29-create_package_httpd_conf.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/post/30-upgrade.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/post/31-upgrade-puppet.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_validations/10-check_foreman_proxy_pulp.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_validations/11-check_proxy_url.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_validations/12-check_capsule_tar.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_commit/05-puppet_certs_exist.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/01-migrate_legacy_foreman_installer_config.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/10-migrate_legacy_capsule_config.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/pre_migrations/11-migrate_legacy_katello_config.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/01-helpers.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/10-reset_hook.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/11-clear_pulp_data_hook.rb
[DEBUG 2017-03-22 10:55:35 main] Loading hook 
/usr/share/katello-installer-base/hooks/boot/12-clear_puppet_environments.rb
[DEBUG 2017-03-22 

[foreman-users] Re: Katello 3.3.1 released!

[Duncan Innes]

Should I be running

foreman-installer --scenario katello --upgrade

after my yum update when upgrading from 3.3 to 3.3.1? 

I'm getting errors during Upgrade Step: migrate_foreman

D

-- 
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.3 building CentOS 7 hosts

[Duncan Innes]

I've taken the rather extreme option of deleting the "CentOS-*.repo" files 
from /etc/yum.repos.d/ at the start of the %post section.  Bit harsh, but 
it proved the theory was sound.  I can now perform successful builds with 
no external access.

This can't be the 'right' way to do it though.  Is this the way the 
subscription_manager_registration snippet is supposed to work?

On Wednesday, 1 March 2017 12:10:15 UTC, Duncan Innes wrote:
>
> Do you do that during kickstart or once booted?  I think at the point of 
> trying to install subscription-manager, my hosts only have the external 
> repos configured, so there's no way to satisfy the install internally.
>
> I've edited the Katello Kickstart Default template to include 
> subscription-manager in the initial %packages list.  This means it's 
> already there when the subscription_manager_registration snippet is run. 
>  But the yum commands still fail if I remove internet access as I've not 
> "enabled=0" to all the external repos at this point.
>
> Shouldn't the subscription_manager_registration snippet be capable of 
> installing subscription-manager without internet access?
>
> D
>
> On Wednesday, 1 March 2017 11:00:46 UTC, Lachlan Musicman wrote:
>>
>> I don't know if there's an automagic way to do it, but I use ansible to 
>> change all files in /etc/yum.repos.d/ except "redhat.repo". In each file 
>> change any enabled =1 to enabled = 0.
>>
>> cheers
>> L.
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this 
>> way."
>>
>> - Grace Hopper
>>
>> On 1 March 2017 at 21:55, Duncan Innes <dun...@innes.net> wrote:
>>
>>> Hi,
>>>
>>> I've built a new Katello 3.3 system and loaded it up with CentOS 7, 
>>> EPEL, and Katello Client 3.3 channels.  The various repositories have been 
>>> synched (although lazy sync). Content View, Activation Key etc created.
>>>
>>> When I build a new system, however, the installation of 
>>> subscription-manager appears to be heading out to the internet rather than 
>>> finding the relevant packages from the Katello server.  The top of my 
>>> install.post.log reads:
>>>
>>> updating system time
>>> Loaded plugins: fastestmirror
>>> Determining fastest mirrors
>>>  * base: *mirror.sax.uk.as61049.net <http://mirror.sax.uk.as61049.net>*
>>>  * extras: *mirror.bytemark.co.uk <http://mirror.bytemark.co.uk>*
>>>  * updates: *mirrors.coreix.net <http://mirrors.coreix.net>*
>>> Resolving Dependencies
>>> --> Running transaction check
>>> ---> Package subscription-manager.x86_64 0:1.17.15-1.el7.centos will be 
>>> installed
>>> --> Processing Dependency: python-rhsm >= 1.17.0 for package: 
>>> subscription-manager-1.17.15-1.el7.centos.x86_64
>>> --> Processing Dependency: usermode for package: 
>>> subscription-manager-1.17.15-1.el7.centos.x86_64
>>> --> Processing Dependency: python-ethtool for package: 
>>> subscription-manager-1.17.15-1.el7.centos.x86_64
>>> --> Processing Dependency: python-dmidecode for package: 
>>> subscription-manager-1.17.15-1.el7.centos.x86_64
>>> --> Processing Dependency: python-dateutil for package: 
>>> subscription-manager-1.17.15-1.el7.centos.x86_64
>>> --> Running transaction check
>>> ---> Package python-dateutil.noarch 0:1.5-7.el7 will be installed
>>> ---> Package python-dmidecode.x86_64 0:3.10.13-11.el7 will be installed
>>> --> Processing Dependency: libxml2-python for package: 
>>> python-dmidecode-3.10.13-11.el7.x86_64
>>> --> Processing Dependency: libxml2mod.so()(64bit) for package: 
>>> python-dmidecode-3.10.13-11.el7.x86_64
>>> ---> Package python-ethtool.x86_64 0:0.8-5.el7 will be installed
>>> --> Processing Dependency: libnl.so.1()(64bit) for package: 
>>> python-ethtool-0.8-5.el7.x86_64
>>> ---> Package python-rhsm.x86_64 0:1.17.9-1.el7 will be installed
>>> --> Processing Dependency: python-rhsm-certificates = 1.17.9-1.el7 for 
>>> package: python-rhsm-1.17.9-1.el7.x86_64
>>> --> Processing Dependency: m2crypto for package: 
>>> python-rhsm-1.17.9-1.el7.x86_64
>>> ---> Package usermode.x86_64 0:1.111-5.el7 will be installed
>>> --> Running transaction check
>>> ---> Package libnl.x86_64 0:1.1.4-3.el7 will be installed
>>> ---> Package libxml2-python.x86_64 0:2.9.1-6.el7_2.3 will be installed
>>> ---> Package m2crypto.x86

Re: [foreman-users] Katello 3.3 building CentOS 7 hosts

[Duncan Innes]

Do you do that during kickstart or once booted?  I think at the point of 
trying to install subscription-manager, my hosts only have the external 
repos configured, so there's no way to satisfy the install internally.

I've edited the Katello Kickstart Default template to include 
subscription-manager in the initial %packages list.  This means it's 
already there when the subscription_manager_registration snippet is run. 
 But the yum commands still fail if I remove internet access as I've not 
"enabled=0" to all the external repos at this point.

Shouldn't the subscription_manager_registration snippet be capable of 
installing subscription-manager without internet access?

D

On Wednesday, 1 March 2017 11:00:46 UTC, Lachlan Musicman wrote:
>
> I don't know if there's an automagic way to do it, but I use ansible to 
> change all files in /etc/yum.repos.d/ except "redhat.repo". In each file 
> change any enabled =1 to enabled = 0.
>
> cheers
> L.
>
> --
> The most dangerous phrase in the language is, "We've always done it this 
> way."
>
> - Grace Hopper
>
> On 1 March 2017 at 21:55, Duncan Innes <dun...@innes.net > 
> wrote:
>
>> Hi,
>>
>> I've built a new Katello 3.3 system and loaded it up with CentOS 7, EPEL, 
>> and Katello Client 3.3 channels.  The various repositories have been 
>> synched (although lazy sync). Content View, Activation Key etc created.
>>
>> When I build a new system, however, the installation of 
>> subscription-manager appears to be heading out to the internet rather than 
>> finding the relevant packages from the Katello server.  The top of my 
>> install.post.log reads:
>>
>> updating system time
>> Loaded plugins: fastestmirror
>> Determining fastest mirrors
>>  * base: *mirror.sax.uk.as61049.net <http://mirror.sax.uk.as61049.net>*
>>  * extras: *mirror.bytemark.co.uk <http://mirror.bytemark.co.uk>*
>>  * updates: *mirrors.coreix.net <http://mirrors.coreix.net>*
>> Resolving Dependencies
>> --> Running transaction check
>> ---> Package subscription-manager.x86_64 0:1.17.15-1.el7.centos will be 
>> installed
>> --> Processing Dependency: python-rhsm >= 1.17.0 for package: 
>> subscription-manager-1.17.15-1.el7.centos.x86_64
>> --> Processing Dependency: usermode for package: 
>> subscription-manager-1.17.15-1.el7.centos.x86_64
>> --> Processing Dependency: python-ethtool for package: 
>> subscription-manager-1.17.15-1.el7.centos.x86_64
>> --> Processing Dependency: python-dmidecode for package: 
>> subscription-manager-1.17.15-1.el7.centos.x86_64
>> --> Processing Dependency: python-dateutil for package: 
>> subscription-manager-1.17.15-1.el7.centos.x86_64
>> --> Running transaction check
>> ---> Package python-dateutil.noarch 0:1.5-7.el7 will be installed
>> ---> Package python-dmidecode.x86_64 0:3.10.13-11.el7 will be installed
>> --> Processing Dependency: libxml2-python for package: 
>> python-dmidecode-3.10.13-11.el7.x86_64
>> --> Processing Dependency: libxml2mod.so()(64bit) for package: 
>> python-dmidecode-3.10.13-11.el7.x86_64
>> ---> Package python-ethtool.x86_64 0:0.8-5.el7 will be installed
>> --> Processing Dependency: libnl.so.1()(64bit) for package: 
>> python-ethtool-0.8-5.el7.x86_64
>> ---> Package python-rhsm.x86_64 0:1.17.9-1.el7 will be installed
>> --> Processing Dependency: python-rhsm-certificates = 1.17.9-1.el7 for 
>> package: python-rhsm-1.17.9-1.el7.x86_64
>> --> Processing Dependency: m2crypto for package: 
>> python-rhsm-1.17.9-1.el7.x86_64
>> ---> Package usermode.x86_64 0:1.111-5.el7 will be installed
>> --> Running transaction check
>> ---> Package libnl.x86_64 0:1.1.4-3.el7 will be installed
>> ---> Package libxml2-python.x86_64 0:2.9.1-6.el7_2.3 will be installed
>> ---> Package m2crypto.x86_64 0:0.21.1-17.el7 will be installed
>> ---> Package python-rhsm-certificates.x86_64 0:1.17.9-1.el7 will be 
>> installed
>> --> Finished Dependency Resolution
>>
>> Dependencies Resolved
>>
>>
>> 
>>  Package Arch  Version   
>>  Repository
>>   
>>  Size
>>
>> 
>> Installing:
>>  subscription-managerx86_641.17.15-1.el7.centos   base   
>>  883 k
>> Installing for dependencies:
&

[foreman-users] Katello 3.3 building CentOS 7 hosts

[Duncan Innes]

Hi,

I've built a new Katello 3.3 system and loaded it up with CentOS 7, EPEL, 
and Katello Client 3.3 channels.  The various repositories have been 
synched (although lazy sync). Content View, Activation Key etc created.

When I build a new system, however, the installation of 
subscription-manager appears to be heading out to the internet rather than 
finding the relevant packages from the Katello server.  The top of my 
install.post.log reads:

updating system time
Loaded plugins: fastestmirror
Determining fastest mirrors
 * base: *mirror.sax.uk.as61049.net*
 * extras: *mirror.bytemark.co.uk*
 * updates: *mirrors.coreix.net*
Resolving Dependencies
--> Running transaction check
---> Package subscription-manager.x86_64 0:1.17.15-1.el7.centos will be 
installed
--> Processing Dependency: python-rhsm >= 1.17.0 for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64
--> Processing Dependency: usermode for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64
--> Processing Dependency: python-ethtool for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64
--> Processing Dependency: python-dmidecode for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64
--> Processing Dependency: python-dateutil for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64
--> Running transaction check
---> Package python-dateutil.noarch 0:1.5-7.el7 will be installed
---> Package python-dmidecode.x86_64 0:3.10.13-11.el7 will be installed
--> Processing Dependency: libxml2-python for package: 
python-dmidecode-3.10.13-11.el7.x86_64
--> Processing Dependency: libxml2mod.so()(64bit) for package: 
python-dmidecode-3.10.13-11.el7.x86_64
---> Package python-ethtool.x86_64 0:0.8-5.el7 will be installed
--> Processing Dependency: libnl.so.1()(64bit) for package: 
python-ethtool-0.8-5.el7.x86_64
---> Package python-rhsm.x86_64 0:1.17.9-1.el7 will be installed
--> Processing Dependency: python-rhsm-certificates = 1.17.9-1.el7 for 
package: python-rhsm-1.17.9-1.el7.x86_64
--> Processing Dependency: m2crypto for package: 
python-rhsm-1.17.9-1.el7.x86_64
---> Package usermode.x86_64 0:1.111-5.el7 will be installed
--> Running transaction check
---> Package libnl.x86_64 0:1.1.4-3.el7 will be installed
---> Package libxml2-python.x86_64 0:2.9.1-6.el7_2.3 will be installed
---> Package m2crypto.x86_64 0:0.21.1-17.el7 will be installed
---> Package python-rhsm-certificates.x86_64 0:1.17.9-1.el7 will be 
installed
--> Finished Dependency Resolution

Dependencies Resolved


 Package Arch  VersionRepository
  
 Size

Installing:
 subscription-managerx86_641.17.15-1.el7.centos   base   
 883 k
Installing for dependencies:
 libnl   x86_641.1.4-3.el7base   
 128 k
 libxml2-python  x86_642.9.1-6.el7_2.3base   
 247 k
 m2cryptox86_640.21.1-17.el7  base   
 429 k
 python-dateutil noarch1.5-7.el7  base 
85 k
 python-dmidecodex86_643.10.13-11.el7 base 
82 k
 python-ethtool  x86_640.8-5.el7  base 
33 k
 python-rhsm x86_641.17.9-1.el7   base   
 116 k
 python-rhsm-certificatesx86_641.17.9-1.el7   base 
38 k
 usermodex86_641.111-5.el7base   
 193 k

Transaction Summary

Install  1 Package (+9 Dependent packages)

Total download size: 2.2 M
Installed size: 9.2 M
Downloading packages:
warning: 
/var/cache/yum/x86_64/7/base/packages/python-dmidecode-3.10.13-11.el7.x86_64.rpm:
 
Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
Public key for python-dmidecode-3.10.13-11.el7.x86_64.rpm is not installed

Total  933 kB/s | 2.2 MB  00:02 

Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Importing GPG key 0xF4A80EB5:
 Userid : "CentOS-7 Key (CentOS 7 Official Signing Key) 
"
 Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5
 Package: centos-release-7-3.1611.el7.centos.x86_64 (@anaconda)
 From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : python-dateutil-1.5-7.el7.noarch   
 1/10 
  Installing : usermode-1.111-5.el7.x86_64 
2/10 
  Installing : libnl-1.1.4-3.el7.x86_64   
 3/10 
  

[foreman-users] Remote Execution vs re-built systems

[Duncan Innes]

Am I missing something here?

I deployed a client from my Katello 3.3 RC2.  I have successfully run 
remote commands on this client.  I rebuild the client via the "Build" 
button on the Host page.  I try to run remote commands again, but these 
fail due to:

Error initializing command: Net::SSH::HostKeyMismatch - fingerprint 
84:2f:bc:c8:79:b8:2e:f8:50:8c:a0:66:39:62:88:d3 does not match for 
"192.168.122.5"

This particular client is using the same MAC, IP Address, Hostname etc. as 
the original.

When I remove the offending (old) key 
from /usr/share/foreman-proxy/.ssh/known_hosts the remote execution works 
again.

I can understand this being the case, but wondering if I've forgotten to do 
something.  Shouldn't the old keys be removed from foreman-proxy 
known_hosts when the rebuild is executed?  Or at the "Informing Foreman 
that we are built" stage? Or when the new client registers with Katello?

Haven't tested this against a plain Foreman server, but I would suggest the 
behaviour would be the same.

Unless I've done something wrong obviously.

Cheers

Duncan

-- 
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: CentOS 7.3 and Anaconda memory requirements

[Duncan Innes]

I get pane is dead sometimes with VMs that have 2Mb or more Ram. I have 
fixed it by completely wiping the underlying storage - somehow anaconda 
appeared to care about what was on the drive, despite installs being a 
"clearpart --all". I didn't think it was a Ram based issue.

My storage here is using LVs assigned to each VM.

On Friday, 13 January 2017 09:25:36 UTC, Lukas Zapletal wrote:
>
> Hello, 
>
> I noticed that CentOS 7.3 Anaconda requires more memory than 7.2. I 
> used to test unattended installations with 800 MB, but now this fails 
> randomly ("pane is dead" or random freeze) and I need to create at 
> least 1.1 GB. 
>
> Anyone have similar experiences? 
>
> -- 
> 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] GUI Problem with Foreman

[Duncan Innes]

The %packages section of the kickstart template you are using needs to be 
edited to add the relevant desktop package group. Can't remember off the top of 
my head, but I *think* it's @gnome-desktop or @kde-desktop.

You might also need something in the %post section to ensure the 
graphical.target is reached by systemd (I've not installed RHEL7/CentOS desktop 
systems from Satellite, so not sure about this part) 

-- 
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-installer --scenario katello SUCCESS BUT cannot register the server it was run on

[Duncan Innes]

>
>
> > 
> > Is the right answer! Boy do I feel foolish. 
>
> Lol, don't, org/locs aren't a good user experience. Unless someone 
> tells you about that org/location selector, it's hard to discover 
> where those hosts go. 
>
>
What gets me is the apparent lack of an attempt at logic.  If there is only 
1 Org created, it might not be the worst logic to register against that Org 
rather than leaving it hanging.  Or against the Org which was defined by 
--foreman-initial-organization?

Not sure I would do the same for Loc as that seems a different question to 
me.

Is it hard to figure out when the Katello server checks in for the first 
time?

-- 
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: foreman-installer --scenario katello SUCCESS BUT cannot register the server it was run on

[Duncan Innes]

On Wednesday, 21 December 2016 12:52:40 UTC, Duncan Innes wrote:
>
>
>
> Also seeing the following in 
> /var/log/puppetlabs/puppetserver/puppetserver.log when I run the puppet 
> agent command:
>
> 2016-12-21 12:47:40,724 WARN  [qtp1406891402-75] [c.p.p.ShellUtils] 
> Executed an external process which logged to STDERR: Could not send facts 
> to Foreman: Permission denied - /etc/puppetlabs/puppet/ssl/client_key.pem
>  
>

Ignore this.  A new clea build with the latest Foreman release shows no 
sign of this error.  Host appears as expected.  Sorry for noise.

D 

-- 
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: foreman-installer --scenario katello SUCCESS BUT cannot register the server it was run on

[Duncan Innes]

On Wednesday, 21 December 2016 12:45:34 UTC, Duncan Innes wrote:
>
> Something might be going wrong with this latest release.  I'm testing the 
> latest Katello/Foreman release too and the server does not manage to 
> register to itself.
>
> Running the puppet command suggested above gives:
>
> root@katello ~]# puppet agent -t --server `hostname -f`
> Warning: Unable to fetch my node definition, but the agent run will 
> continue:
> Warning: Error 500 on SERVER: Server Error: Failed to find 
> katello.innes.net via exec: Execution of '/etc/puppetlabs/puppet/node.rb 
> katello.innes.net' returned 1: 
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
> Server Error: Failed when searching for node katello.innes.net: Failed to 
> find katello.innes.net via exec: Execution of 
> '/etc/puppetlabs/puppet/node.rb katello.innes.net' returned 1: 
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
> [root@katello ~]# 
>
> This is a Puppet 4 build I've installed.
>

Also seeing the following in 
/var/log/puppetlabs/puppetserver/puppetserver.log when I run the puppet 
agent command:

2016-12-21 12:47:40,724 WARN  [qtp1406891402-75] [c.p.p.ShellUtils] 
Executed an external process which logged to STDERR: Could not send facts 
to Foreman: Permission denied - /etc/puppetlabs/puppet/ssl/client_key.pem

2016-12-21 12:47:40,726 ERROR [qtp1406891402-75] [puppetserver] Puppet 
Server Error: Failed to find katello.innes.net via exec: Execution of 
'/etc/puppetlabs/puppet/node.rb katello.innes.net' returned 1: 
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:44:in
 
`execute'
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:14:in
 
`initialize_execution_stub'
org/jruby/RubyProc.java:281:in `call'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:194:in 
`execute'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:33:in
 
`execute'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/exec.rb:19:in 
`find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:17:in
 
`find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in
 
`find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:121:in
 
`do_find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in
 
`call'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in 
`override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in `override'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
 
`call'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in 
`process'
org/jruby/RubyArray.java:1613:in `each'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in 
`process'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in 
`process'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in 
`process'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
 
`process'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
 
`profile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in 
`profile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in
 
`process'
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
 
`handleRequest'
Puppet$$Server$$Master_505362540.gen:13:in `handleRequest'
request_handler_core.clj:273:in `invoke'
jruby_request.clj:46:in `invoke'
jruby_request.clj:31:in `invoke'
request_handler_service.clj:34:in `handle_request'
request_handler.clj:3:in `invoke'
request_handler.clj:3:in `invoke'
core.clj:2515:in `invoke'
ring_middleware.clj:284:in `invoke'
core.clj:168:in `invoke'
core.clj:211:in `invoke'
core.clj:45:in `invoke'
core.clj:343:in `invoke'
core.clj:51:in `invoke'
ringutils.clj:83:in `invoke'
master_core.clj:411:in `invoke'
ring.clj:21:in `invoke'
ring.clj:12:in `invoke'
comidi.clj:249:in `invoke'
jetty9_core.clj:424:in `invoke'
normalized_uri_helpers.clj:80:in `invoke'
2016-12-21 12:47:41,309 WARN  [qtp1406891402-73] [c.p.p.ShellUtils] 
Executed an external process which logged to STDERR: Could not send facts 
to Foreman: Permission denied - /etc/puppetlabs/puppet/ssl/client_key.pem

2016-12-21 12:47:41,317 ERROR [qtp1406891402-73] [puppetserver] Puppet 
Failed when searching for node katello.innes.net: Failed to find 
katello.innes.net via exec: Execution of '/etc/puppetlabs/puppet/node.rb 
katello.i

Re: [foreman-users] Re: foreman-installer --scenario katello SUCCESS BUT cannot register the server it was run on

[Duncan Innes]

Something might be going wrong with this latest release.  I'm testing the 
latest Katello/Foreman release too and the server does not manage to 
register to itself.

Running the puppet command suggested above gives:

root@katello ~]# puppet agent -t --server `hostname -f`
Warning: Unable to fetch my node definition, but the agent run will 
continue:
Warning: Error 500 on SERVER: Server Error: Failed to find 
katello.innes.net via exec: Execution of '/etc/puppetlabs/puppet/node.rb 
katello.innes.net' returned 1: 
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
Server Error: Failed when searching for node katello.innes.net: Failed to 
find katello.innes.net via exec: Execution of 
'/etc/puppetlabs/puppet/node.rb katello.innes.net' returned 1: 
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
[root@katello ~]# 

This is a Puppet 4 build I've installed.

-- 
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] Remote Execution public key

[Duncan Innes]

Bingo - 9090 it is.  I'll submit a change for the documentation.

On Wednesday, 16 November 2016 12:03:38 UTC, Adam Ruzicka wrote:
>
> Looking at recently installed machine I can see that the default https 
> port for smart proxy was changed from 8443 to 9090, check which port your 
> proxy should listen on with cat /etc/foreman-proxy/settings.yml | grep 
> https_port.
>
> Hope this helps
>
> Adam
>
> On Wed, Nov 16, 2016 at 12:51 PM, Duncan Innes <dun...@innes.net 
> > wrote:
>
>> Built my test rig with the latest Katello 3.2 release and looking into 
>> the Remote Execution plugin.  I can get it working by manually copying the 
>> .pub key into the client's authorized_keys file, but I'm not seeing the key 
>> published via the API as is claimed in the manual:
>>
>>
>> https://theforeman.org/plugins/foreman_remote_execution/0.3/index.html#2.2RemoteHostsConfiguration
>>
>> claims
>>
>> curl https://myproxy.example.com:8443/ssh/pubkey >> 
>> ~/.ssh/authorized_keys
>>
>> is a method for pulling the relevant key onto the host.  But I get 
>> nothing back from that URL and can find nothing in the API docs about 
>> pubkey.  Has this method been dropped?
>>
>> Cheers
>>
>> D
>>
>> -- 
>> 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.
>>
>
>

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

[foreman-users] Re: Foreman remote execution fails

[Duncan Innes]

Is the target host configured to accept the SSH connection from the proxy?

https://theforeman.org/plugins/foreman_remote_execution/0.3/index.html#2.2RemoteHostsConfiguration

On Wednesday, 19 October 2016 13:00:17 UTC+1, Dor Azoulay wrote:
>
>
> i have just installed the latest version of foreman (1.13.0) on Centos 7.2.
> everything works well except when i am trying to run remote execution on a 
> machine (installed via foreman-installer) it fails with : 
>
> 1:
> Error initializing command: Net::SSH::ConnectionTimeout - 
> Net::SSH::ConnectionTimeout
> 2:
> Exit status: EXCEPTION
>
> basically it says "pending" on the job status and after about 2 minutes it 
> throws the above message on the host details.
>
> it seems the remote host doesn't get the request for some reason.
>
> all features are enabled on the smart proxy section.
> FW & Selinux are disabled.
>
> according to foreman-proxy logs there is nothing suspicious:
>
> accept: 192.168.249.222:49686 
> D, [2016-10-19T11:35:35.979099 #5730] DEBUG -- : Rack::Handler::WEBrick is 
> invoked. 
> D, [2016-10-19T11:35:35.988823 #5730] DEBUG -- : verifying remote client 
> 192.168.220.222 against trusted_hosts ["foreman.example.com"] 
> D, [2016-10-19T11:35:35.991867 #5730] DEBUG -- : Proxy request from 
> foreman.example.com:8443/dynflow/tasks/count to https://
> foreman.example.com:8008/tasks/
> count 
> D, [2016-10-19T11:35:36.081274 #5730] DEBUG -- : Proxy request status 200 
> - # 
> I, [2016-10-19T11:35:36.082396 #5730]  INFO -- : 192.168.220.222 - - 
> [19/Oct/2016:11:35:36 +] "GET /dynflow/tasks/count?state=running 
> HTTP/1.1" 200 29 0.0939 
>
> D, [2016-10-19T11:35:36.123514 #5730] DEBUG -- : close: 
> 192.168.220.222:49686 
> D, [2016-10-19T11:35:36.343377 #5730] DEBUG -- : accept: 
> 192.168.220.222:49688 
> D, [2016-10-19T11:35:36.349244 #5730] DEBUG -- : Rack::Handler::WEBrick is 
> invoked. 
> D, [2016-10-19T11:35:36.350386 #5730] DEBUG -- : verifying remote client 
> 192.168.220.222 against trusted_hosts ["foreman.example.com"] 
> D, [2016-10-19T11:35:36.350751 #5730] DEBUG -- : Proxy request from 
> foreman.example.com:8443/dynflow/tasks/ to 
> https://foreman.example.com:8008/tasks/ 
>
> D, [2016-10-19T11:35:36.852074 #5730] DEBUG -- : Proxy request status 200 
> - # 
> I, [2016-10-19T11:35:36.852681 #5730]  INFO -- : 192.168.220.222 - - 
> [19/Oct/2016:11:35:36 +] "POST /dynflow/tasks/ HTTP/1.1" 200 50 0.5026 
>
> D, [2016-10-19T11:35:36.893861 #5730] DEBUG -- : close: 
> 192.168.220.222:49688 
> D, [2016-10-19T11:36:36.346125 #5730] DEBUG -- : accept: 
> 192.168.220.222:49697 
> D, [2016-10-19T11:36:36.352459 #5730] DEBUG -- : Rack::Handler::WEBrick is 
> invoked. 
> D, [2016-10-19T11:36:36.353314 #5730] DEBUG -- : verifying remote client 
> 192.168.220.222 against trusted_hosts ["foreman.example.com"] 
> D, [2016-10-19T11:36:36.353691 #5730] DEBUG -- : Proxy request from 
> foreman.example.com:8443/dynflow/tasks/1063de40-3671-4a2d-9370-22068b642009/status
>  
> to http
> s://foreman.example.com:8008/tasks/1063de40-3671-4a2d-9370-22068b642009/status
>  
>
> D, [2016-10-19T11:36:36.406618 #5730] DEBUG -- : Proxy request status 200 
> - # 
> I, [2016-10-19T11:36:36.407055 #5730]  INFO -- : 192.168.220.222 - - 
> [19/Oct/2016:11:36:36 +] "GET 
> /dynflow/tasks/1063de40-3671-4a2d-9370-22068b642009/status
> HTTP/1.1" 200 1882 0.0539 
>
> D, [2016-10-19T11:36:36.447722 #5730] DEBUG -- : close: 
> 192.168.220.222:49697 
>
>
> any ideas what could be the reason ? is it possibly a bug ?
>

-- 
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: Katello 3.2 RC1 released

[Duncan Innes]

Just built new test system from this RC and had to increase the vRAM on my 
guest.

Is it now a hard requirement to have 8Gb free RAM for the install?  My test 
KVM guests have 8Gb total which has always been fine until now.

Don't mind providing more RAM, but I didn't think the install would refuse 
on a memory check like this.

D

On Friday, 23 September 2016 16:49:31 UTC+1, John Mitsch wrote:
>
> We are happy to announce the first release candidate for Katello 3.2
> (Malt Liquor).
>
> One notable change in 3.2 is the support of Puppet 4. More info about 
> upgrading to Puppet 4 can be found here:
>
> http://www.katello.org/docs/nightly/upgrade/puppet.html
>
> Your help is appreciated to ensure our GA release is solid, by either
> installing a new instance or upgrading a test server.
>
> A list of the changes in Katello 3.2 is in our release notes:
> http://www.katello.org/docs/3.2/release_notes/release_notes.html
>
>
> Installation or Upgrade
> ==
>
> For installation, please see the instructions at:
>
>   Server:  http://www.katello.org/docs/3.2/installation/index.html
>   Capsule:  http://www.katello.org/docs/3.2/installation/capsule.html
>
> For those testing upgrades, please use the instructions below and file
> any issues you encounter. Please note that there are separate upgrade
> instructions for the Katello server and Capsules:
>
>   Server:  http://www.katello.org/docs/3.2/upgrade/index.html
>   Capsule:  http://www.katello.org/docs/3.2/upgrade/capsule.html
>
> Bug reporting
> ===
> If you come across a bug in your testing, please file it and note the
> version of Katello that you're using in the report and set the release
> to 3.2.0.
>
>   http://projects.theforeman.org/projects/katello/issues/new
>
> John Mitsch
> Red Hat Engineering
> (860)-967-7285
> irc: jomitsch
>

-- 
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: Sending Test E-mail

[Duncan Innes]

Seeing this in the mail group, I realise I should have used a more suitable 
subject line!

On Monday, 26 September 2016 16:02:50 UTC+1, Duncan Innes wrote:
>
> In the user e-mail preferences screen it's possible to send a test e-mail 
> to the users account.
>
> Is it possible to do this via hammer at all?  I looked around, but didn't 
> see anything.
>
> D
>

-- 
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] Sending Test E-mail

[Duncan Innes]

In the user e-mail preferences screen it's possible to send a test e-mail 
to the users account.

Is it possible to do this via hammer at all?  I looked around, but didn't 
see anything.

D

-- 
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: Outstanding errat report

[Duncan Innes]

You using the API for this or querying the database?  Querying the database 
is the way to insanity . . .

I did this for Satellite 5.x, but haven't looked at it for 
Katello/Satellite6 yet.  Not sure if all the queries are in place yet. 
 There was a ticket raised for querying the outstanding packages on a host 
based on the Errata that are in Library rather than the hosts own 
environment.  This would allow you to see outstanding Errata as they come 
into Katello/Satellite before they're promoted through your environments. 
 Have now been asked to look into this for work on our Satellite 6.2 
install, so will share what I can.

On Friday, 26 August 2016 14:22:01 UTC+1, Craig Elston wrote:
>
> Can anyone point me in the right direction? 
>
> I am looking to query outstanding errata per host/content host/system 
> directly from the foreman database. I have a requirement to have weekly 
> reports sent to a team of engineers.
>
> I have been able to find most of the fields that I need, but the errata 
> per server is eluding me.
>
> Any help would be appreciated.
>
> Craig Elston
>

-- 
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.1 RC1 Released

[Duncan Innes]

Sorry - for installation.

Was just taking the Foreman installation OS options as examples here.

Ideally I'd run Katello on a CentOS7 guest, but the host OS will be Fedora 
24 for which I'll be trying to get libvirt smart-proxy working.

D

On Monday, 18 July 2016 14:09:13 UTC+1, Eric Helms wrote:
>
> For installation purposes or client support?
>
> On Jul 18, 2016 8:10 AM, "Duncan Innes" <dun...@innes.net > 
> wrote:
>
>> Hi,
>>
>> Is Katello 3.1 not going to support the same OS platforms as Foreman 1.12 
>> is doing?
>>
>> i.e. Fedora 24 for my purpose, but others may look to Debian & Ubuntu
>>
>> Cheers
>>
>> Duncan
>>
>> On Monday, 11 July 2016 13:52:50 UTC+1, jsherril wrote:
>>>
>>>
>>> We are happy to announce the first release candidate for Katello 3.1 
>>> (California Common). 
>>>
>>> Your help is appreciated to ensure our GA release is solid, by either 
>>> installing a new instance or upgrading a test server. 
>>>
>>> A list of the changes in Katello 3.1 is in our release notes: 
>>> http://www.katello.org/docs/3.1/release_notes/release_notes.html 
>>>
>>>
>>> Installation or Upgrade 
>>> === 
>>>
>>> For installation, please see the instructions at: 
>>>
>>>   Server:  http://www.katello.org/docs/3.1/installation/index.html 
>>>   Capsule:  http://www.katello.org/docs/3.1/installation/capsule.html 
>>>
>>> For those testing upgrades, please use the instructions below and file 
>>> any issues you encounter. Please note that there are separate upgrade 
>>> instructions for the Katello server and Capsules: 
>>>
>>>   Server:  http://www.katello.org/docs/3.1/upgrade/index.html 
>>>   Capsule:  http://www.katello.org/docs/3.1/upgrade/capsule.html 
>>>
>>>
>>>
>>> Bug reporting 
>>> = 
>>> If you come across a bug in your testing, please file it and note the 
>>> version of Katello that you're using in the report and set the release 
>>> to 3.1.0. 
>>>
>>>   http://projects.theforeman.org/projects/katello/issues/new 
>>>
>>> -- 
>> 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.
>>
>

-- 
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: Katello 3.1 RC1 Released

[Duncan Innes]

Hi,

Is Katello 3.1 not going to support the same OS platforms as Foreman 1.12 
is doing?

i.e. Fedora 24 for my purpose, but others may look to Debian & Ubuntu

Cheers

Duncan

On Monday, 11 July 2016 13:52:50 UTC+1, jsherril wrote:
>
>
> We are happy to announce the first release candidate for Katello 3.1 
> (California Common). 
>
> Your help is appreciated to ensure our GA release is solid, by either 
> installing a new instance or upgrading a test server. 
>
> A list of the changes in Katello 3.1 is in our release notes: 
> http://www.katello.org/docs/3.1/release_notes/release_notes.html 
>
>
> Installation or Upgrade 
> === 
>
> For installation, please see the instructions at: 
>
>   Server:  http://www.katello.org/docs/3.1/installation/index.html 
>   Capsule:  http://www.katello.org/docs/3.1/installation/capsule.html 
>
> For those testing upgrades, please use the instructions below and file 
> any issues you encounter. Please note that there are separate upgrade 
> instructions for the Katello server and Capsules: 
>
>   Server:  http://www.katello.org/docs/3.1/upgrade/index.html 
>   Capsule:  http://www.katello.org/docs/3.1/upgrade/capsule.html 
>
>
>
> Bug reporting 
> = 
> If you come across a bug in your testing, please file it and note the 
> version of Katello that you're using in the report and set the release 
> to 3.1.0. 
>
>   http://projects.theforeman.org/projects/katello/issues/new 
>
>

-- 
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: Katello 3.0 (Saison) Released

[Duncan Innes]

P.S. Surprised that this major announcement isn't in the, um, announcements 
list.

I know Katello is seen as "only" a plugin, but come on.  It's a REALLY big 
plugin!

-- 
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: Katello 3.0 (Saison) Released

[Duncan Innes]

Yay \o/ great news.

Congratulations for getting this over the finish line.  And thanks to all 
the devs for their hard work.

D

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