[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 07 Dec 3pm [BST]

[Ori Rabin]

In case you missed it, this was recorded last week.
In this community demo, we covered Discourse updates, fact importing
improvements and more.

Sections in this demo:
* Intro (orabin): https://youtu.be/g8XnAKfG9xY?t=1
* Discourse updates (gwmngilfen): https://youtu.be/g8XnAKfG9xY?t=99
* Latest improvements in fact importing - performance and filtering
(shimshtein): https://youtu.be/g8XnAKfG9xY?t=447
* Subscription-manager in Debian (mdellweg):
https://youtu.be/g8XnAKfG9xY?t=776
* Ignoring global proxy on sync & Faster content view publish (jsherrill):
https://youtu.be/g8XnAKfG9xY?t=1030

As always you can ask questions here in the comments, or on the mailing
list,
or in our IRC channel - presenter IRC names are in the notes above!

Website: http://theforeman.org
IRC: Freenode/#theforeman
Matrix: #theforeman:matrix.org
Twitter: @ForemanProject
Mailing List: https://groups.google.com/forum/#!forum/foreman-users

On Thu, Nov 30, 2017 at 11:50 AM, Ori Rabin  wrote:

> Hi all,
>
> It's time for the next Foreman Community Demo! Join us at 3pm on Thu 07
> Dec
> for the usual roundup of all the new & interesting developments from
> around our community.
>
> More information is available on the event page [1] and the show
> agenda is being compiled at the Foreman wiki [2]. If you have anything new,
> cool tips, etc, that you'd like to share with the community, please let me
> know and I can arrange for you to be on the demo, or (if you can't make
> it) I
> can demo for you.
>
> As ever, we encourage live participation via the YouTube live chat, or in
> IRC
> (#theforeman on Freenode). For those that can't attend, the video will be
> posted to YouTube afterwards.
>
> If you'd like to know when other Foreman events are happening, check out
> our
> Events page on the Foreman website [3].
>
> [1] https://www.youtube.com/watch?v=g8XnAKfG9xY
> [2] http://projects.theforeman.org/projects/foreman/wiki/
> Current_Sprint_Information
> [3] http://theforeman.org/events
>
> --
> Ori
> IRC: orabin
>

-- 
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: Web interface SSL Cert

[Matt Cahill]

correction

cat intermediate.pem > foreman_ssl_ca.pem
cat digicert_root_ca.crt >> foreman_ssl_ca.pem

On 14 December 2017 at 17:22, Matt Cahill  wrote:

> Hi David,
>
> for us it's just simply a plain text PEM encoded certificate file like so:
>
> -BEGIN CERTIFICATE-
> encoded...
> ...cert...
> ...data
> -END CERTIFICATE-
> -BEGIN CERTIFICATE-
> encoded...
> ...cert...
> ...data
> -END CERTIFICATE-
>
> I just did the following
>
> cat intermediate.pem > foreman_ssl_ca.pem
> cat digicert_root_ca.crt > foreman_ssl_ca.pem
>
> cheers
>
> Matt
>
> On 14 December 2017 at 07:39, David Childs 
> wrote:
>
>> Hi Matt
>>
>> Concatenating their intermediate and the root CA into one pem and
>>> referencing that in /etc/puppetlabs/puppet/foreman.yaml for :ssl_ca: fixed
>>> the problem.
>>>
>>
>> Can you explain how you did this? It should be obvious, but I'm not
>> having any luck making it work.
>>
>>
>>
>> On Tuesday, July 11, 2017 at 6:27:16 AM UTC-4, Matt Cahill wrote:
>>>
>>> I did eventually get this working.
>>>
>>> https://theforeman.org/2015/11/foreman-ssl.html
>>> https://alexshepherd.me/articles/changing-foremans-ssl-certificate
>>> 
>>>
>>> The specific problem I had all along was that I was supplied an
>>> intermediate cert chain without the root CA (as mentioned by alex shepherd).
>>> Concatenating their intermediate and the root CA into one pem and
>>> referencing that in /etc/puppetlabs/puppet/foreman.yaml for :ssl_ca:
>>> fixed the problem.
>>>
>>> Installing via puppet:
>>>
>>> foreman::ssl: true
>>> puppet::server_foreman_ssl_ca: '/etc/pki/tls/certs/cachain_wi
>>> th_root.pem'
>>> puppet::server_foreman_url: 'https://puppet.example.com'
>>> foreman::server_ssl_key: '/etc/pki/tls/private/puppet.example.com.key'
>>> foreman::server_ssl_cert: '/etc/pki/tls/certs/puppet.example.com.crt'
>>> foreman::server_ssl_chain: '/etc/pki/tls/certs/cachain_with_root.pem'
>>> foreman::servername: 'puppet.example.com'
>>> foreman::foreman_url: 'https://puppet.example.com'
>>> foreman::websockets_ssl_key: '/etc/pki/tls/private/puppet.example.key'
>>> foreman::websockets_ssl_cert: '/etc/pki/tls/certs/puppet.example.crt'
>>>
>>> or with foreman-installer options
>>>
>>> foreman-installer --foreman-ssl \
>>> --puppet-server-foreman-ssl-ca '/etc/pki/tls/certs/cachain_wi
>>> th_root.pem' \
>>> --puppet-server-foreman-url 'https://puppet.example.com' \
>>> --foreman-server-ssl-key '/etc/pki/tls/private/puppet.example.com.key' \
>>> --foreman-server-ssl-cert '/etc/pki/tls/certs/puppet.example.com.crt' \
>>> --foreman-server-ssl-chain '/etc/pki/tls/certs/cachain_with_root.pem' \
>>> --foreman-servername 'puppet.example.com' \
>>> --foreman-foreman-url 'https://puppet.example.com' \
>>> --foreman-websockets-ssl-key '/etc/pki/tls/private/puppet.example.key' \
>>> --foreman-websockets-ssl-cert '/etc/pki/tls/certs/puppet.example.crt'
>>>
>>> cheers
>>>
>>> Matt
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Foreman users" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/foreman-users/MMug-F4hNHg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> foreman-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: [foreman-users] Re: Web interface SSL Cert

[Matt Cahill]

Hi David,

for us it's just simply a plain text PEM encoded certificate file like so:

-BEGIN CERTIFICATE-
encoded...
...cert...
...data
-END CERTIFICATE-
-BEGIN CERTIFICATE-
encoded...
...cert...
...data
-END CERTIFICATE-

I just did the following

cat intermediate.pem > foreman_ssl_ca.pem
cat digicert_root_ca.crt > foreman_ssl_ca.pem

cheers

Matt

On 14 December 2017 at 07:39, David Childs 
wrote:

> Hi Matt
>
> Concatenating their intermediate and the root CA into one pem and
>> referencing that in /etc/puppetlabs/puppet/foreman.yaml for :ssl_ca: fixed
>> the problem.
>>
>
> Can you explain how you did this? It should be obvious, but I'm not having
> any luck making it work.
>
>
>
> On Tuesday, July 11, 2017 at 6:27:16 AM UTC-4, Matt Cahill wrote:
>>
>> I did eventually get this working.
>>
>> https://theforeman.org/2015/11/foreman-ssl.html
>> https://alexshepherd.me/articles/changing-foremans-ssl-certificate
>> 
>>
>> The specific problem I had all along was that I was supplied an
>> intermediate cert chain without the root CA (as mentioned by alex shepherd).
>> Concatenating their intermediate and the root CA into one pem and
>> referencing that in /etc/puppetlabs/puppet/foreman.yaml for :ssl_ca:
>> fixed the problem.
>>
>> Installing via puppet:
>>
>> foreman::ssl: true
>> puppet::server_foreman_ssl_ca: '/etc/pki/tls/certs/cachain_with_root.pem'
>> puppet::server_foreman_url: 'https://puppet.example.com'
>> foreman::server_ssl_key: '/etc/pki/tls/private/puppet.example.com.key'
>> foreman::server_ssl_cert: '/etc/pki/tls/certs/puppet.example.com.crt'
>> foreman::server_ssl_chain: '/etc/pki/tls/certs/cachain_with_root.pem'
>> foreman::servername: 'puppet.example.com'
>> foreman::foreman_url: 'https://puppet.example.com'
>> foreman::websockets_ssl_key: '/etc/pki/tls/private/puppet.example.key'
>> foreman::websockets_ssl_cert: '/etc/pki/tls/certs/puppet.example.crt'
>>
>> or with foreman-installer options
>>
>> foreman-installer --foreman-ssl \
>> --puppet-server-foreman-ssl-ca '/etc/pki/tls/certs/cachain_with_root.pem'
>> \
>> --puppet-server-foreman-url 'https://puppet.example.com' \
>> --foreman-server-ssl-key '/etc/pki/tls/private/puppet.example.com.key' \
>> --foreman-server-ssl-cert '/etc/pki/tls/certs/puppet.example.com.crt' \
>> --foreman-server-ssl-chain '/etc/pki/tls/certs/cachain_with_root.pem' \
>> --foreman-servername 'puppet.example.com' \
>> --foreman-foreman-url 'https://puppet.example.com' \
>> --foreman-websockets-ssl-key '/etc/pki/tls/private/puppet.example.key' \
>> --foreman-websockets-ssl-cert '/etc/pki/tls/certs/puppet.example.crt'
>>
>> cheers
>>
>> Matt
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/foreman-users/MMug-F4hNHg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

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

[foreman-users] Known katello 3.5 pulp issue

[John Mitsch]

Katello users,

There is a known issue in our latest 3.5 release where python-django is not
being installed. This is being fixed, and our install docs have been
updated to install python-django.

For already installed systems just run:

 $ sudo yum install python-django
 $ sudo systemctl restart httpd pulp_workers pulp_resource_manager
pulp_celerybeat pulp_streamer

Let me know if you have any questions.

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

Re: [foreman-users] Re: Foreman + katello install issues

[John Mitsch]

Just an update on the pulp error, we updated the installation docs to
install python-django, which avoids these errors.

For already installed systems just run:

 $ sudo yum install python-django
 $ sudo systemctl restart httpd pulp_workers pulp_resource_manager
pulp_celerybeat pulp_streamer

Let me know if you have any questions.

Thanks,
John

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

On Wed, Dec 13, 2017 at 9:01 AM, Joe Auerbach 
wrote:

> thanks.  that worked like a charm here. Up and running.  Now to try to
> find an AWS APL that will work as well (they gave me grief on my spacewalk
> install and I have a feeling they will not be a LOT easier with foreman,
> but we'll see) .
>
> On Wed, Dec 13, 2017 at 8:19 AM, Patrick Creech 
> wrote:
>
>> On Tue, 2017-12-12 at 18:32 -0500, Joe Auerbach wrote:
>> > Thanks!  That's a big help.  If we use that manual fix I presume we
>> will have a second manual fix
>> > when the package comes out live?
>> >
>>
>> There will not.  The issue here is python-django16 is erroneously
>> installed due to a packaging error
>> in an upstream repo (epel).  The manual fix here is to get the system
>> into the correct state,
>> therefore there will be no need to 'fix' it later after the upstream repo
>> is fixed.  It will just
>> continue to work as it did prior to this past weekend for new installs.
>>
>> --
>> 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.
>

-- 
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: Web interface SSL Cert

[David Childs]

Hi Matt

Concatenating their intermediate and the root CA into one pem and 
> referencing that in /etc/puppetlabs/puppet/foreman.yaml for :ssl_ca: fixed 
> the problem.
>

Can you explain how you did this? It should be obvious, but I'm not having 
any luck making it work.

 

On Tuesday, July 11, 2017 at 6:27:16 AM UTC-4, Matt Cahill wrote:
>
> I did eventually get this working.
>
> https://theforeman.org/2015/11/foreman-ssl.html
> https://alexshepherd.me/articles/changing-foremans-ssl-certificate 
> 
>
> The specific problem I had all along was that I was supplied an 
> intermediate cert chain without the root CA (as mentioned by alex shepherd).
> Concatenating their intermediate and the root CA into one pem and 
> referencing that in /etc/puppetlabs/puppet/foreman.yaml for :ssl_ca: 
> fixed the problem.
>
> Installing via puppet:
>
> foreman::ssl: true
> puppet::server_foreman_ssl_ca: '/etc/pki/tls/certs/cachain_with_root.pem'
> puppet::server_foreman_url: 'https://puppet.example.com'
> foreman::server_ssl_key: '/etc/pki/tls/private/puppet.example.com.key'
> foreman::server_ssl_cert: '/etc/pki/tls/certs/puppet.example.com.crt'
> foreman::server_ssl_chain: '/etc/pki/tls/certs/cachain_with_root.pem'
> foreman::servername: 'puppet.example.com'
> foreman::foreman_url: 'https://puppet.example.com'
> foreman::websockets_ssl_key: '/etc/pki/tls/private/puppet.example.key'
> foreman::websockets_ssl_cert: '/etc/pki/tls/certs/puppet.example.crt'
>
> or with foreman-installer options
>
> foreman-installer --foreman-ssl \
> --puppet-server-foreman-ssl-ca '/etc/pki/tls/certs/cachain_with_root.pem' 
> \
> --puppet-server-foreman-url 'https://puppet.example.com' \
> --foreman-server-ssl-key '/etc/pki/tls/private/puppet.example.com.key' \
> --foreman-server-ssl-cert '/etc/pki/tls/certs/puppet.example.com.crt' \
> --foreman-server-ssl-chain '/etc/pki/tls/certs/cachain_with_root.pem' \
> --foreman-servername 'puppet.example.com' \
> --foreman-foreman-url 'https://puppet.example.com' \
> --foreman-websockets-ssl-key '/etc/pki/tls/private/puppet.example.key' \
> --foreman-websockets-ssl-cert '/etc/pki/tls/certs/puppet.example.crt'
>
> cheers
>
> Matt
>

-- 
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] tasks hanging

[Joe Auerbach]

last night I ran a sync of my centos repos and that was great . This
morning I tried to sync them again as a demonstration and of course that
failed . they're just hanging there.

So I checked my dashboard and saw some hanging tasks.  two paused and
errored, one paused and pending, and 11 stopped and errored.

I can see these tasks and look at them, but I have no way to cancel them,
it seems.  the button isn't live.  I went into the dynflow console for a
few to try to skip the hanging bits and it seemed to have no impact . I
can't even fathom how these were hung as the server was down overnight and
just came back up this morning.  These tasks are largely from last night.
Is there a way to clear them above and beyond rebooting the server?

-- 
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] Upgrading 1.15.6 -> 1.16.0 causes 'no such middleware error'

[Tyler Gregory]

No, reinstalling the memcached plugin seems to result in this error.

On Tuesday, December 12, 2017 at 7:59:06 AM UTC-6, Iain Walmsley wrote:
>
> I've encountered the same problem with the default hostgroup, but even 
> when removing this and still using memcached I see the same issue;
>
> rake aborted!
> No such middleware to insert after: 
> ActionDispatch::Session::ActiveRecordStore
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/stack.rb:125:in
>  
> `assert_index'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/stack.rb:96:in
>  
> `insert_after'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/configuration.rb:68:in
>  
> `block in merge_into'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/configuration.rb:67:in
>  
> `each'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/configuration.rb:67:in
>  
> `merge_into'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:501:in
>  
> `app'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:34:in
>  
> `block in '
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>  
> `instance_exec'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>  
> `run'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in
>  
> `block in run_initializers'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in
>  
> `run_initializers'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in
>  
> `initialize!'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>  
> `public_send'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>  
> `method_missing'
> /usr/share/foreman/config/environment.rb:5:in `'
>
> [root@localhost foreman]# rpm -qa  | grep -i foreman
> foreman-cli-1.16.0-1.el7.noarch
> tfm-rubygem-foreman_memcache-0.0.6-1.fm1_15.el7.noarch
> foreman-installer-1.16.0-1.el7.noarch
> foreman-1.16.0-1.el7.noarch
> tfm-rubygem-hammer_cli_foreman-0.11.0-1.el7.noarch
> tfm-rubygem-foreman_setup-5.0.0-1.fm1_13.el7.noarch
> foreman-selinux-1.16.0-1.el7.noarch
> foreman-debug-1.16.0-1.el7.noarch
> foreman-postgresql-1.16.0-1.el7.noarch
>
> Removing memcached seems to resolve the issue, are you installing 
> memcached successfully with 1.16?
>
> On Thursday, December 7, 2017 at 11:25:02 PM UTC, Jeff Stasko wrote:
>>
>> But I had to remove tfm-rubygem-foreman_default_hostgroup
>>
>>
>> My fix is in this post
>>
>> https://groups.google.com/forum/m/?source=mog=us#!topic/foreman-users/bWfJJ-xyzGE
>>
>

-- 
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 + katello install issues

[Joe Auerbach]

thanks.  that worked like a charm here. Up and running.  Now to try to find
an AWS APL that will work as well (they gave me grief on my spacewalk
install and I have a feeling they will not be a LOT easier with foreman,
but we'll see) .

On Wed, Dec 13, 2017 at 8:19 AM, Patrick Creech  wrote:

> On Tue, 2017-12-12 at 18:32 -0500, Joe Auerbach wrote:
> > Thanks!  That's a big help.  If we use that manual fix I presume we will
> have a second manual fix
> > when the package comes out live?
> >
>
> There will not.  The issue here is python-django16 is erroneously
> installed due to a packaging error
> in an upstream repo (epel).  The manual fix here is to get the system into
> the correct state,
> therefore there will be no need to 'fix' it later after the upstream repo
> is fixed.  It will just
> continue to work as it did prior to this past weekend for new installs.
>
> --
> 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: Foreman-docker publish port

[Marcin Bojko]

Also interested - Couldn't find any docs regarding publishing. Exposing 
works only on docker interface.

W dniu środa, 21 grudnia 2016 14:21:26 UTC+1 użytkownik Luiz Vasconcelos 
napisał:
>
> Is os possível to publish a porta using foreman-docker plugin? I need to 
> use -p or --publish and I'm not finding If it's possível. 
>
> Thanks

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

Re: [foreman-users] Re: Foreman + katello install issues

[Patrick Creech]

On Tue, 2017-12-12 at 18:32 -0500, Joe Auerbach wrote:
> Thanks!  That's a big help.  If we use that manual fix I presume we will have 
> a second manual fix
> when the package comes out live? 
> 

There will not.  The issue here is python-django16 is erroneously installed due 
to a packaging error
in an upstream repo (epel).  The manual fix here is to get the system into the 
correct state,
therefore there will be no need to 'fix' it later after the upstream repo is 
fixed.  It will just
continue to work as it did prior to this past weekend for new installs.

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


signature.asc
Description: This is a digitally signed message part

Re: [foreman-users] Remote Execution plugin issue

[Daniel Lobato Garcia]

On 12/12, jci...@fit.edu wrote:
> Hello,
>
> I am having an issue with the Remote Execution plugin that has me
> scratching my head. I was running commands yesterday throughout the day and
> had no problems. Today the SSH remote command execution is missing and when
> I click on a completed job (both successful and failed), I receive "Oops,
> we're sorry but something went wrong undefined method `name' for
> nil:NilClass." When I select a host and "Run job," I only see the Katello
> category and "Restart Services - Katello SSH Default." No changes or
> updates had been made to the server between yesterday and this morning.

>From what I see, that template is:

<%= input(:helper).split(",").map {|split| "#{split}" }.join("\n") %>

katello-tracer-upload


Did you make any changes or is that the tample we're speaking about?

>
> Attempted fixes: rebooting the server
> reinstalling the packages and restarting the services manually per the
> plugin documentation
> re-running "foreman-installer --enable-foreman-plugin-remote-execution
> --enable-foreman-proxy-plugin-remote-execution-ssh"
>
> I did not remove the packages specified in the documentation for the manual
> install because it wants to also remove the katello package(s) as well.
>
> I am currently running the following:
> CentOS 7.3
> Foreman 1.14.3
> w/ Plugins:
> Katello 3.3.2
> Remote Execution 1.2.2
>
>
> Has anyone had this issue or any ideas on how to fix it?

The error, "undefined method name" makes me think that there is some
problem with the Host Operating System or the Host itself. Could you
enable the debug log_level
(https://theforeman.org/manuals/1.16/#Foremandebugging) and share what
you see on /var/log/foreman/production.log when you try to run the job?

Probably you see the same issue when previewing the template, e.g:

https://imgur.com/a/rOk7F

Could you share the logs of that too? Does it work?

>
>
>
> Thanks,
>
>
> James
>
>
>
> James Cicak
> Systems Programmer | Information Technology/Enterprise Systems
>
> --
> 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.


--
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato

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


signature.asc
Description: PGP signature