date:20170815

Re: [foreman-users] Katello 3.4 (Oud Bruin) Released!

2017-08-15 Thread Lachlan Musicman

On 30 May 2017 at 16:31, Evgeni Golov  wrote:

> On Tue, May 30, 2017 at 11:50:40AM +1000, Lachlan Musicman wrote:
> > On 30 May 2017 at 11:40, Lachlan Musicman  wrote:
> >
> > > Great, thanks.
> > >
> > > I am seeing another issue:
> > >
> > >  - yum clean all, all good
> > >  - yum upgrade doesn't recognise new repos. If I look into
> > > /etc/yum.repos.d/redhat.repo and the new products aren't listed in that
> > > file.
> > >
> > > In order to get it to work, traditionally I've then performed:
> > >
> > > subscription-manager identity
> > > subscription-manager unsubscribe
> > > subscription-manager register --org="ACMI" --activationkey="Utility
> > > Server"
> >
> > I have discovered that my traditional method was finally deprecated and
> it
> > didn't work.
> >
> > But I also found that the slightly easier work around works:
> >
> > subscription-manager repos
> >
> > For whatever reason, that refreshes the redhat.repo.
>
> So would "subscription-manager refresh".
> When you change repos, your subscription changes, but it is not pulled
> in on every yum invocation.
>
> You can set full_refresh_on_yum = 1 in rhsm.conf, but even then not
> every aspect is properly updated [1].
>
> Also, I would suggest against using sub-man unregister && sub-man
> register as a cluebat workaround. The subscription certificate is also
> used for katello-agent, and if you don't restart it after doing the
> sub-man dance, you end up without the ability to apply errata via
> katello-agent.
>



Can I ask - since the unregister, reregister workaround is cluebat, what
are we to do when the subscription-manager refresh doesn't work as you
state it does?

We have systems - that I've just updated - but are not finding the new
redhat.repo or the updates therein.

Whereas the unregister, reregister workaround is shown to work,
consistently.

cheers
L.

--
"The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "

*Greg Bloom* @greggish
https://twitter.com/greggish/status/873177525903609857

-- 
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-proxy and dhcpd next-server

2017-08-15 Thread Bill Sirinek

Is there any update to this issue? I'm working on upgrading to 1.15.3 and 
this problem still exists. I have about 20 DHCP servers with smart proxies 
and many of them are multi-homed because we do a lot of building on 
non-routable admin networks.

I see Bug #1221 http://projects.theforeman.org/issues/1221 that was "Ready 
For Testing" but got moved back to "New" (!)

There is also http://projects.theforeman.org/issues/9169 that appears 
related.

In 1.15.3 I just commented out line 120 of 
/usr/share/foreman/app/models/concerns/orchestration/dhcp.rb to do the same 
workaround I did way back in 1.3, but this is obviously not ideal.

Thanks

Bill


On Monday, February 24, 2014 at 5:49:26 AM UTC-5, Александр Костырев wrote:
>
> Hello!
>
> I've got two subnet definitions in my /etc/dhcp/dhcpd.conf
>
> #
> # example.org
> #
> subnet 10.0.1.0 netmask 255.255.255.0 {
>
>   range 10.0.1.93 10.0.1.131;
>   option subnet-mask 255.255.255.0;
>   option routers 10.0.1.254;
>   option domain-name "example.org";
>   next-server 10.0.1.92;
>   option domain-name-servers 10.0.1.1, 10.0.1.2;
> }
> #
> # anothernet.com
> #
>
> subnet 192.168.5.0 netmask 255.255.255.0 {
>
>   range 192.168.5.162 192.168.5.199;
>   option subnet-mask 255.255.255.0;
>   option routers 192.168.5.4;
>   option domain-name "anothernet.com";
>   next-server 192.168.5.45;
>   option domain-name-servers 192.168.5.14, 192.168.5.15;
> }
>
> and this in /etc/foreman-proxy/settings.yml
>
> # Enable TFTP management
> :tftp: true
> :tftproot: /var/lib/tftpboot/
> # Defines the TFTP Servername to use, overrides the name in the subnet 
> declaration
> #:tftp_servername: tftp.domain.com
>
>
> BUT
> when I create new host in domain anothernet.com Foreman puts this in 
> dhcpd.leases
>
> host test1.anothernet.com {
>   dynamic;
>   hardware ethernet 00:0c:29:1b:50:5e;
>   fixed-address 192.168.5.162;
> supersede server.filename = "pxelinux.0";
> supersede server.next-server = *0a:00:01:5c*;
> supersede host-name = "test1.anothernet.com";
> }
>
>
> 0x0A:00:01:5C 10.0.1.92 
> 0xC0:A8:05:2D 192.168.5.45 
>
> so it says that next-server for this host is one from subnet 10.0.1.0 and 
> it is quite a big problem for my installation.
>
> How can I achieve what I want?
>
> Thanks in advance
>
>
>
>   RELEASE: CentOS release 6.5 (Final)
>   FOREMAN: 1.4.0
>  RUBY: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
>PUPPET: 3.4.3
>
>
>

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

2017-08-15 Thread Louis Bohm

I commented out the Listen 443 line from /etc/httpd/conf.d/ports.conf.

Louis
> On Aug 15, 2017, at 12:23 PM, Eric D Helms  wrote:
> 
> Which one did you remove? The one from sleeping.conf?
> 
> 
> On Aug 15, 2017 12:12 PM, "Louis Bohm"  > wrote:
> OK.  I see what you are saying and that is what I ran:  foreman-installer 
> --scenario katello —upgrade
> 
> When I run foreman-installer --scenario katello —upgrade apache fails to 
> start up.  When I fist look at the logs I see this:
> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock: 
> could not bind to address 0.0.0.0:443 
> 
> If I remove one of the Listen 443 in the configurations and manually start 
> apache with katello-services —only httpd I then get these errors:
> 
> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such 
> file or directory: AH01515: mod_mime_magic: can't read magic file 
> /etc/httpd/NEVER_EVER_USE
> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init: 
> Name-based SSL virtual hosts only work for clients with TLS server name 
> indication support (RFC 4366)
> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232: suEXEC 
> mechanism enabled (wrapper: /usr/sbin/suexec)
> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538 ]: 
> Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 
> 'default_python' => 'python', 'default_ruby' => 'ruby', 'default_user' => 
> 'nobody', 'log_level' => '0', 'max_pool_size' => '12', 'passenger_root' => 
> '/usr/share/passenger//phusion_passenger/locations.ini', 'passenger_version' 
> => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls' => 
> 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=',
>  'temp_dir' => '/tmp', 'union_station_gateway_address' => 
> 'gateway.unionstationapp.com ', 
> 'union_station_gateway_port' => '443', 'user_switching' => 'true', 
> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600', 
> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48', 
> 'web_server_worker_uid' => '48' }
> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650 
> ]: PassengerHelperAgent online, listening at 
> unix:/tmp/passenger.1.0.2600/generation-0/request
> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321 
> ]: PassengerLoggingAgent online, listening at 
> unix:/tmp/passenger.1.0.2600/generation-0/logging
> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728 ]: 
> All Phusion Passenger agents started!
> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module 
> access_compat_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module 
> actions_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module 
> alias_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module 
> auth_basic_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module 
> auth_digest_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module 
> authn_anon_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module 
> authn_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module 
> authn_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module 
> authn_file_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module 
> authz_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module 
> authz_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module 
> authz_groupfile_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module 
> authz_host_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module 
> authz_owner_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module 
> authz_user_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module 
> autoindex_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module 
> cache_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module 
> deflate_module is already loaded, skipping
> [Tue Aug 15 09:25:32.750009 2017] [so:warn]

Re: [foreman-users] Katello 3.4.4 Released

2017-08-15 Thread Eric D Helms

Which one did you remove? The one from sleeping.conf?


On Aug 15, 2017 12:12 PM, "Louis Bohm"  wrote:

> OK.  I see what you are saying and that is what I ran:  foreman-installer
> --scenario katello —upgrade
>
> When I run foreman-installer --scenario katello —upgrade apache fails to
> start up.  When I fist look at the logs I see this:
>
> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock:
> could not bind to address 0.0.0.0:443
>
>
> If I remove one of the Listen 443 in the configurations and manually start
> apache with katello-services —only httpd I then get these errors:
>
> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such
> file or directory: AH01515: mod_mime_magic: can't read magic file
> /etc/httpd/NEVER_EVER_USE
> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
> Name-based SSL virtual hosts only work for clients with TLS server name
> indication support (RFC 4366)
> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538
> ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' =>
> 'nobody', 'default_python' => 'python', 'default_ruby' => 'ruby',
> 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '12',
> 'passenger_root' => '/usr/share/passenger//phusion_passenger/locations.ini',
> 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls'
> => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29t
> OjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp',
> 'union_station_gateway_address' => 'gateway.unionstationapp.com',
> 'union_station_gateway_port' => '443', 'user_switching' => 'true',
> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600',
> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48',
> 'web_server_worker_uid' => '48' }
> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650
> ]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.2600/
> generation-0/request
> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321
> ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.2600/
> generation-0/logging
> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728
> ]: All Phusion Passenger agents started!
> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
> access_compat_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
> actions_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
> alias_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
> auth_basic_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
> auth_digest_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
> authn_anon_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
> authn_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
> authn_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
> authn_file_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
> authz_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
> authz_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module
> authz_groupfile_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module
> authz_host_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module
> authz_owner_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module
> authz_user_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module
> autoindex_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module
> cache_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module
> deflate_module is already loaded, skipping
> [Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module
> dir_module is already loaded, skipping
> [Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module
> env_module is already loaded, skipping
> [Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module
> expires_module is already loaded,

Re: [foreman-users] Katello 3.4.4 Released

2017-08-15 Thread Louis Bohm

OK.  I see what you are saying and that is what I ran:  foreman-installer 
--scenario katello —upgrade

When I run foreman-installer --scenario katello —upgrade apache fails to start 
up.  When I fist look at the logs I see this:
Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock: could 
not bind to address 0.0.0.0:443

If I remove one of the Listen 443 in the configurations and manually start 
apache with katello-services —only httpd I then get these errors:

[Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such file 
or directory: AH01515: mod_mime_magic: can't read magic file 
/etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init: 
Name-based SSL virtual hosts only work for clients with TLS server name 
indication support (RFC 4366)
[Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232: suEXEC 
mechanism enabled (wrapper: /usr/sbin/suexec)
[ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538 ]: 
Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 
'default_python' => 'python', 'default_ruby' => 'ruby', 'default_user' => 
'nobody', 'log_level' => '0', 'max_pool_size' => '12', 'passenger_root' => 
'/usr/share/passenger//phusion_passenger/locations.ini', 'passenger_version' => 
'4.0.53', 'pool_idle_time' => '300', 'prestart_urls' => 
'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=',
 'temp_dir' => '/tmp', 'union_station_gateway_address' => 
'gateway.unionstationapp.com', 'union_station_gateway_port' => '443', 
'user_switching' => 'true', 'web_server_passenger_version' => '4.0.53', 
'web_server_pid' => '2600', 'web_server_type' => 'apache', 
'web_server_worker_gid' => '48', 'web_server_worker_uid' => '48' }
[ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650 ]: 
PassengerHelperAgent online, listening at 
unix:/tmp/passenger.1.0.2600/generation-0/request
[ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321 
]: PassengerLoggingAgent online, listening at 
unix:/tmp/passenger.1.0.2600/generation-0/logging
[ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728 ]: 
All Phusion Passenger agents started!
[Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module 
access_compat_module is already loaded, skipping
[Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module 
actions_module is already loaded, skipping
[Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module 
alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module 
auth_basic_module is already loaded, skipping
[Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module 
auth_digest_module is already loaded, skipping
[Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module 
authn_anon_module is already loaded, skipping
[Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module 
authn_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module 
authn_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module 
authn_file_module is already loaded, skipping
[Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module 
authz_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module 
authz_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module 
authz_groupfile_module is already loaded, skipping
[Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module 
authz_host_module is already loaded, skipping
[Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module 
authz_owner_module is already loaded, skipping
[Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module 
authz_user_module is already loaded, skipping
[Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module 
autoindex_module is already loaded, skipping
[Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module 
cache_module is already loaded, skipping
[Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module 
deflate_module is already loaded, skipping
[Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module 
dir_module is already loaded, skipping
[Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module 
env_module is already loaded, skipping
[Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module 
expires_module is already loaded, skipping
[Tue Aug 15 09:25:32.750398 2017] [so:warn] [pid 2600] AH01574: module 
ext_filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750420 2017] [so:warn] [pid 2600] AH01574: module 
filter_module is already loaded, skipping
[Tue Aug 15

Re: [foreman-users] Katello 3.4.4 Released

2017-08-15 Thread Eric D Helms

I did not see anything included. But every upgrade both minor and patch,
since before 2.4 has required using the installer with --upgrade.

Per -- https://theforeman.org/plugins/katello/3.4/upgrade/index.html

Check Step 5

On Aug 15, 2017 12:03 PM, "Louis Bohm"  wrote:

> Here is the documentation and it does not show it.  I also do not remember
> it when I went from 3.2 to 3.3.  But I will run it.
>
> Louis
>
> On Aug 15, 2017, at 11:59 AM, Eric D Helms  wrote:
>
> Absolutely, every time. Can you double check? Or show a screenshot of what
> you looked at that didn't have it?
>
>
> On Aug 15, 2017 11:48 AM, "Louis Bohm"  wrote:
>
>> No.  Its not on the Katello upgrade page.  Am I supposed to?
>>
>> Louis
>>
>> On Aug 15, 2017, at 10:59 AM, Eric D Helms  wrote:
>>
>> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>>
>> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm  wrote:
>>
>>> I re-ran the foreman-installer —scenario katello —upgrade and it got as
>>> far as apache.  The apache upgrade failed.  The foreman log says this:
>>>
>>> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072:
>>> make_sock: could not bind to address 0.0.0.0:443
>>> Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down
>>>
>>>
>>> So I took a look and noticed that Listen 443 was listed twice.  Once in
>>> /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not
>>> good.  So I commented out the one in ports.conf and restarted it.
>>>
>>> Now when it fails I get a log more information.  From
>>> /var/log/httpd/error_log I see:
>>>
>>> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No
>>> such file or directory: AH01515: mod_mime_magic: can't read magic file
>>> /etc/httpd/NEVER_EVER_USE
>>> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
>>> Name-based SSL virtual hosts only work for clients with TLS server name
>>> indication support (RFC 4366)
>>> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
>>> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
>>> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780
>>> agents/Watchdog/Main.cpp:538 ]: Options: { 'analytics_log_user' =>
>>> 'nobody', 'default_group' => 'nobody', 'default_python' => 'python',
>>> 'default_ruby' => 'ruby', 'default_user' => 'nobody', 'log_level' => '0',
>>> 'max_pool_size' => '12', 'passenger_root' => 
>>> '/usr/share/passenger//phusion_passenger/locations.ini',
>>> 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls'
>>> => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29
>>> tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp',
>>> 'union_station_gateway_address' => 'gateway.unionstationapp.com',
>>> 'union_station_gateway_port' => '443', 'user_switching' => 'true',
>>> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600',
>>> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48',
>>> 'web_server_worker_uid' => '48' }
>>> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780
>>> agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online,
>>> listening at unix:/tmp/passenger.1.0.2600/generation-0/request
>>> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880
>>> agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online,
>>> listening at unix:/tmp/passenger.1.0.2600/generation-0/logging
>>> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780
>>> agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started!
>>> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
>>> access_compat_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
>>> actions_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
>>> alias_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
>>> auth_basic_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
>>> auth_digest_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
>>> authn_anon_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
>>> authn_core_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
>>> authn_dbm_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
>>> authn_file_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
>>> authz_core_module is already loaded, skipping
>>> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
>>> authz_dbm_module is already loaded, skipping
>>> [Tue Aug 15

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

2017-08-15 Thread Greg Sutcliffe

Sorry for the delay in updating this (vacation!), but here's the show
notes for the demo just over a week ago. In this demo we covered Remote
Execution (REX) updates, new developer tooling in Hammer, the new
scheduing support for ActiveJob, and a new community-made plugin for
ActiveDirectiry. Enjoy!

Sections in today's demo:

* Intro (gwmngilfen) - https://youtu.be/rZY6dE0HVyM?t=0
* Granular Permissions (mhulan) - https://youtu.be/rZY6dE0HVyM?t=156
* REX: Async SSH (aruzicka) - https://youtu.be/rZY6dE0HVyM?t=470
* REX: Abort/poll tasks (inecas) - https://youtu.be/rZY6dE0HVyM?t=630
* Hammer: New debug (tstrachota) - https://youtu.be/rZY6dE0HVyM?t=839
* ActiveJob backend (dlobatog) - https://youtu.be/rZY6dE0HVyM?t=1261
* AD Realm integration (mcassel) - https://youtu.be/rZY6dE0HVyM?t=2300

You can find the presenter IRC nicknames in the links above - feel free
to ask questions here or in IRC.

Cheers
Greg

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

2017-08-15 Thread Louis Bohm

Here is the documentation and it does not show it.  I also do not remember it 
when I went from 3.2 to 3.3.  But I will run it.

Louis
> On Aug 15, 2017, at 11:59 AM, Eric D Helms  wrote:
> 
> Absolutely, every time. Can you double check? Or show a screenshot of what 
> you looked at that didn't have it? 
> 
> 
> On Aug 15, 2017 11:48 AM, "Louis Bohm"  > wrote:
> No.  Its not on the Katello upgrade page.  Am I supposed to?
> 
> Louis
>> On Aug 15, 2017, at 10:59 AM, Eric D Helms > > wrote:
>> 
>> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>> 
>> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm > > wrote:
>> I re-ran the foreman-installer —scenario katello —upgrade and it got as far 
>> as apache.  The apache upgrade failed.  The foreman log says this:
>> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock: 
>> could not bind to address 0.0.0.0:443 
>> Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down
>> 
>> So I took a look and noticed that Listen 443 was listed twice.  Once in 
>> /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not good.  
>> So I commented out the one in ports.conf and restarted it.
>> 
>> Now when it fails I get a log more information.  From 
>> /var/log/httpd/error_log I see:
>> 
>> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such 
>> file or directory: AH01515: mod_mime_magic: can't read magic file 
>> /etc/httpd/NEVER_EVER_USE
>> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init: 
>> Name-based SSL virtual hosts only work for clients with TLS server name 
>> indication support (RFC 4366)
>> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232: suEXEC 
>> mechanism enabled (wrapper: /usr/sbin/suexec)
>> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538 ]: 
>> Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 
>> 'default_python' => 'python', 'default_ruby' => 'ruby', 'default_user' => 
>> 'nobody', 'log_level' => '0', 'max_pool_size' => '12', 'passenger_root' => 
>> '/usr/share/passenger//phusion_passenger/locations.ini', 'passenger_version' 
>> => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls' => 
>> 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=',
>>  'temp_dir' => '/tmp', 'union_station_gateway_address' => 
>> 'gateway.unionstationapp.com ', 
>> 'union_station_gateway_port' => '443', 'user_switching' => 'true', 
>> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600', 
>> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48', 
>> 'web_server_worker_uid' => '48' }
>> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650 
>> ]: PassengerHelperAgent online, listening at 
>> unix:/tmp/passenger.1.0.2600/generation-0/request
>> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 
>> agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online, listening 
>> at unix:/tmp/passenger.1.0.2600/generation-0/logging
>> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728 ]: 
>> All Phusion Passenger agents started!
>> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module 
>> access_compat_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module 
>> actions_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module 
>> alias_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module 
>> auth_basic_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module 
>> auth_digest_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module 
>> authn_anon_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module 
>> authn_core_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module 
>> authn_dbm_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module 
>> authn_file_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module 
>> authz_core_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module 
>> authz_dbm_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module 
>> authz_groupfile_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module

Re: [foreman-users] Katello 3.4.4 Released

2017-08-15 Thread Eric D Helms

Absolutely, every time. Can you double check? Or show a screenshot of what
you looked at that didn't have it?


On Aug 15, 2017 11:48 AM, "Louis Bohm"  wrote:

> No.  Its not on the Katello upgrade page.  Am I supposed to?
>
> Louis
>
> On Aug 15, 2017, at 10:59 AM, Eric D Helms  wrote:
>
> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>
> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm  wrote:
>
>> I re-ran the foreman-installer —scenario katello —upgrade and it got as
>> far as apache.  The apache upgrade failed.  The foreman log says this:
>>
>> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock:
>> could not bind to address 0.0.0.0:443
>> Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down
>>
>>
>> So I took a look and noticed that Listen 443 was listed twice.  Once in
>> /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not
>> good.  So I commented out the one in ports.conf and restarted it.
>>
>> Now when it fails I get a log more information.  From
>> /var/log/httpd/error_log I see:
>>
>> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No
>> such file or directory: AH01515: mod_mime_magic: can't read magic file
>> /etc/httpd/NEVER_EVER_USE
>> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
>> Name-based SSL virtual hosts only work for clients with TLS server name
>> indication support (RFC 4366)
>> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
>> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
>> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538
>> ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' =>
>> 'nobody', 'default_python' => 'python', 'default_ruby' => 'ruby',
>> 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '12',
>> 'passenger_root' => '/usr/share/passenger//phusion_passenger/locations.ini',
>> 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls'
>> => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29
>> tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp',
>> 'union_station_gateway_address' => 'gateway.unionstationapp.com',
>> 'union_station_gateway_port' => '443', 'user_switching' => 'true',
>> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600',
>> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48',
>> 'web_server_worker_uid' => '48' }
>> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780
>> agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online,
>> listening at unix:/tmp/passenger.1.0.2600/generation-0/request
>> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880
>> agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online,
>> listening at unix:/tmp/passenger.1.0.2600/generation-0/logging
>> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728
>> ]: All Phusion Passenger agents started!
>> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
>> access_compat_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
>> actions_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
>> alias_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
>> auth_basic_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
>> auth_digest_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
>> authn_anon_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
>> authn_core_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
>> authn_dbm_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
>> authn_file_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
>> authz_core_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
>> authz_dbm_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module
>> authz_groupfile_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module
>> authz_host_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module
>> authz_owner_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module
>> authz_user_module is already loaded, skipping
>> [Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module
>> autoindex_module is already loaded, skipping
>>

Re: [foreman-users] Katello 3.4.4 Released

2017-08-15 Thread Louis Bohm

No.  Its not on the Katello upgrade page.  Am I supposed to?

Louis
> On Aug 15, 2017, at 10:59 AM, Eric D Helms  wrote:
> 
> You ran 'foreman-installer --upgrade' once you updated the RPMs?
> 
> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm  > wrote:
> I re-ran the foreman-installer —scenario katello —upgrade and it got as far 
> as apache.  The apache upgrade failed.  The foreman log says this:
> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock: 
> could not bind to address 0.0.0.0:443 
> Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down
> 
> So I took a look and noticed that Listen 443 was listed twice.  Once in 
> /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not good.  
> So I commented out the one in ports.conf and restarted it.
> 
> Now when it fails I get a log more information.  From 
> /var/log/httpd/error_log I see:
> 
> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such 
> file or directory: AH01515: mod_mime_magic: can't read magic file 
> /etc/httpd/NEVER_EVER_USE
> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init: 
> Name-based SSL virtual hosts only work for clients with TLS server name 
> indication support (RFC 4366)
> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232: suEXEC 
> mechanism enabled (wrapper: /usr/sbin/suexec)
> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538 ]: 
> Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 
> 'default_python' => 'python', 'default_ruby' => 'ruby', 'default_user' => 
> 'nobody', 'log_level' => '0', 'max_pool_size' => '12', 'passenger_root' => 
> '/usr/share/passenger//phusion_passenger/locations.ini', 'passenger_version' 
> => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls' => 
> 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=',
>  'temp_dir' => '/tmp', 'union_station_gateway_address' => 
> 'gateway.unionstationapp.com ', 
> 'union_station_gateway_port' => '443', 'user_switching' => 'true', 
> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600', 
> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48', 
> 'web_server_worker_uid' => '48' }
> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650 
> ]: PassengerHelperAgent online, listening at 
> unix:/tmp/passenger.1.0.2600/generation-0/request
> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321 
> ]: PassengerLoggingAgent online, listening at 
> unix:/tmp/passenger.1.0.2600/generation-0/logging
> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728 ]: 
> All Phusion Passenger agents started!
> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module 
> access_compat_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module 
> actions_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module 
> alias_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module 
> auth_basic_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module 
> auth_digest_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module 
> authn_anon_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module 
> authn_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module 
> authn_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module 
> authn_file_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module 
> authz_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module 
> authz_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module 
> authz_groupfile_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module 
> authz_host_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module 
> authz_owner_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module 
> authz_user_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module 
> autoindex_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module 
> cache_module is already loaded, skipping
> [Tue Aug 15

Re: [foreman-users] Re: Katello 3.4.4 Released

2017-08-15 Thread Eric D Helms

You ran 'foreman-installer --upgrade' once you updated the RPMs?

On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm  wrote:

> I re-ran the foreman-installer —scenario katello —upgrade and it got as
> far as apache.  The apache upgrade failed.  The foreman log says this:
>
> Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock:
> could not bind to address 0.0.0.0:443
> Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down
>
>
> So I took a look and noticed that Listen 443 was listed twice.  Once in
> /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not
> good.  So I commented out the one in ports.conf and restarted it.
>
> Now when it fails I get a log more information.  From
> /var/log/httpd/error_log I see:
>
> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such
> file or directory: AH01515: mod_mime_magic: can't read magic file
> /etc/httpd/NEVER_EVER_USE
> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
> Name-based SSL virtual hosts only work for clients with TLS server name
> indication support (RFC 4366)
> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
> suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538
> ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' =>
> 'nobody', 'default_python' => 'python', 'default_ruby' => 'ruby',
> 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '12',
> 'passenger_root' => '/usr/share/passenger//phusion_passenger/locations.ini',
> 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls'
> => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29t
> OjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp',
> 'union_station_gateway_address' => 'gateway.unionstationapp.com',
> 'union_station_gateway_port' => '443', 'user_switching' => 'true',
> 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600',
> 'web_server_type' => 'apache', 'web_server_worker_gid' => '48',
> 'web_server_worker_uid' => '48' }
> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650
> ]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.2600/
> generation-0/request
> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321
> ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.2600/
> generation-0/logging
> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728
> ]: All Phusion Passenger agents started!
> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
> access_compat_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
> actions_module is already loaded, skipping
> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
> alias_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
> auth_basic_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
> auth_digest_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
> authn_anon_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
> authn_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
> authn_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
> authn_file_module is already loaded, skipping
> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
> authz_core_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
> authz_dbm_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module
> authz_groupfile_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module
> authz_host_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module
> authz_owner_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module
> authz_user_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module
> autoindex_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module
> cache_module is already loaded, skipping
> [Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module
> deflate_module is already loaded, skipping
> [Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module
> dir_module is already loaded, skipping
> [Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574:

Re: [foreman-users] Re: Katello 3.4.4 Released

2017-08-15 Thread Louis Bohm

I re-ran the foreman-installer —scenario katello —upgrade and it got as far as 
apache.  The apache upgrade failed.  The foreman log says this:
Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock: could 
not bind to address 0.0.0.0:443
Aug 15 09:22:45 fm httpd: no listening sockets available, shutting down

So I took a look and noticed that Listen 443 was listed twice.  Once in 
/etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf.  Thats not good.  So 
I commented out the one in ports.conf and restarted it.

Now when it fails I get a log more information.  From /var/log/httpd/error_log 
I see:

[Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such file 
or directory: AH01515: mod_mime_magic: can't read magic file 
/etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init: 
Name-based SSL virtual hosts only work for clients with TLS server name 
indication support (RFC 4366)
[Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232: suEXEC 
mechanism enabled (wrapper: /usr/sbin/suexec)
[ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538 ]: 
Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 
'default_python' => 'python', 'default_ruby' => 'ruby', 'default_user' => 
'nobody', 'log_level' => '0', 'max_pool_size' => '12', 'passenger_root' => 
'/usr/share/passenger//phusion_passenger/locations.ini', 'passenger_version' => 
'4.0.53', 'pool_idle_time' => '300', 'prestart_urls' => 
'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=',
 'temp_dir' => '/tmp', 'union_station_gateway_address' => 
'gateway.unionstationapp.com', 'union_station_gateway_port' => '443', 
'user_switching' => 'true', 'web_server_passenger_version' => '4.0.53', 
'web_server_pid' => '2600', 'web_server_type' => 'apache', 
'web_server_worker_gid' => '48', 'web_server_worker_uid' => '48' }
[ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650 ]: 
PassengerHelperAgent online, listening at 
unix:/tmp/passenger.1.0.2600/generation-0/request
[ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321 
]: PassengerLoggingAgent online, listening at 
unix:/tmp/passenger.1.0.2600/generation-0/logging
[ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728 ]: 
All Phusion Passenger agents started!
[Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module 
access_compat_module is already loaded, skipping
[Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module 
actions_module is already loaded, skipping
[Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module 
alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module 
auth_basic_module is already loaded, skipping
[Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module 
auth_digest_module is already loaded, skipping
[Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module 
authn_anon_module is already loaded, skipping
[Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module 
authn_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module 
authn_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module 
authn_file_module is already loaded, skipping
[Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module 
authz_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module 
authz_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module 
authz_groupfile_module is already loaded, skipping
[Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module 
authz_host_module is already loaded, skipping
[Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module 
authz_owner_module is already loaded, skipping
[Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module 
authz_user_module is already loaded, skipping
[Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module 
autoindex_module is already loaded, skipping
[Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module 
cache_module is already loaded, skipping
[Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module 
deflate_module is already loaded, skipping
[Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module 
dir_module is already loaded, skipping
[Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module 
env_module is already loaded, skipping
[Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module 
expires_module is already loaded, skipping
[Tue Aug 15 09:25:32.750398 2017] [so:warn] [pid 2600] AH01574: module 
ext_filter_module is already

[foreman-users] Re: Katello 3.4.4 Released

2017-08-15 Thread Louis Bohm

As with mongodb postgresql was also complaining about its pid directory:

Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server...
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG:  could not bind 
IPv6 socket: Cannot assign requested address
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT:  Is another 
postmaster already running on port 5432? If not, wait a few seconds and 
retry.
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL:  could not create 
lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file or 
directory
Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server
Aug 15 09:02:36 fm pg_ctl: Examine the log output.

And again once i created the dir /var/run/postgresql and set its 
perms/owner/group postgresql starts up fine.

Louis

On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
>
> We are happy to announce the GA of Katello 3.4.4. This release contains a 
> large number of bug fixes for both small UI issues, user issues found while 
> using 3.4.4 and developer found issues that we felt would bring more 
> stability to users.
>
> The highlights are too numerous to outline here, so I would recommend to 
> please look at the changelog for a full list of changes:
>
> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md  
>
> Installation:
> https://theforeman.org/plugins/katello/3.4/installation/index.html
>
> Upgrade:
> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
>
> 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-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.4.4 Released

2017-08-15 Thread Louis Bohm

I did a repair on mongodb and that did not help.  Looked at the log and 
found that the reason it was not starting up was because /var/run/mongodb 
was no longer around.  From the log:
   2017-08-14T17:29:22.938-0400 ERROR: Cannot write pid file to 
/var/run/mongodb/mongod.pid: No such file or directory

   [root@fm run]# ls -l /var/run/mongodb
   ls: cannot access /var/run/mongodb: No such file or directory

Once I created that dir, set its owner/group to mongodb I could start the 
DB.  Now to figure out what happened to postgresql.

Louis
On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
>
> We are happy to announce the GA of Katello 3.4.4. This release contains a 
> large number of bug fixes for both small UI issues, user issues found while 
> using 3.4.4 and developer found issues that we felt would bring more 
> stability to users.
>
> The highlights are too numerous to outline here, so I would recommend to 
> please look at the changelog for a full list of changes:
>
> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md  
>
> Installation:
> https://theforeman.org/plugins/katello/3.4/installation/index.html
>
> Upgrade:
> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
>
> 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-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 Host provisioning

2017-08-15 Thread Lukas Zapletal

Hello,

Foreman can talk to various virtualizations like libvirt or oVirt, but
not to Oracle Virtual VM unfortunately.

What you need to do is to create new VM and write down the VM MAC
address of the interface that is connected to network with Foreman. Do
not start it.

Then Create host, configure it and set MAC address of the provisioning
inteface, Submit. Then turn on your VM and it should start PXE booting
there.

There is one important thing - the virtual network (assuming you are
using that) must have DHCP turned off and your Foreman DHCP and TFTP
server must be configured and enabled responding to DHCP/PXE requests
on that network. I suggest you to create "Isolated virtual network"
for that purpose, or it can be NAT but make sure there is no Oracle
DHCP running there.

LZ

On Sat, Aug 12, 2017 at 5:50 PM, Phani Kumar
 wrote:
> Hi Team
>
> I am new to Foreman
>
> Clearly understood the reporting and Configuration.
> But not clear on provisioning  and I need help or link to documentation.
>
> What I did is till now .. I installed foreman on Oracle Virtuval machine VM
> and trying to provisioning a new VM from the foreman VM using bare metal
>
> I did all steps to create a new VM from host section as per documentation
> but its showing always pending for installation   since two days. and I
> restarted the foreman machine also. But no luck.
>
> Can you redirect me to right direction.
>
> Some of other questions.. If I am going to  provisioning a new host/VM..
> will it automatically creates new VM .. how this will work.. or do i need to
> create a VM and give the mac address and ip details while creating.
>
> Can you please help me here?
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.



-- 
Later,
  Lukas @lzap Zapletal

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

Re: [foreman-users] Re: DHCP issues - UNABLE TO SAVE: Create DHCP Settings task failed

2017-08-15 Thread Lukas Zapletal

> [{"network":"192.168.196.0.0","netmask":"255.255.255.0","options":{"range":["192.168.0.201","192.168.0.254"]}}]

This means DHCP proxy module now sees your network but I do not
understand why it reads non-sense:

192.168.196.0.0

It should be:

192.168.0.0

Have you manually edited this line? Show me your "subnets" declaration
in dhcpd.conf again.

Also what is your Subnet definition in Foreman? Verify your address,
netmask and reservation match what you have in dhcpd.conf. The range
is recommended to be set outside of your DHCP pool.

LZ

On Tue, Aug 15, 2017 at 8:30 AM, Michal Hagara  wrote:
> Anyone?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.



-- 
Later,
  Lukas @lzap Zapletal

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

[foreman-users] Re: Updating puppet from 3.8.7 to 4.8.1 with Foreman 1.12.4 on EL6.8.

2017-08-15 Thread darsh

After Updating puppet server from 3.8.7 to 4.10 on Foreman 1.15.1.
I am getting the same error messages as you did on client machines, 'Error: 
Could not retrieve catalog from remote server: Error 500 on SERVER...'

I 
followed 
http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4

My puppet.conf has vardir = /opt/puppetlabs/puppet/cache

And I copied /var/lib/puppet/foreman_cache_data to 
/opt/puppetlabs/puppet/cache/foreman_cache_data

You said, 'I fixed this by setting the correct puppet cache directory for 
foreman'. Can you please let me know what exactly you did?

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: DHCP issues - UNABLE TO SAVE: Create DHCP Settings task failed

2017-08-15 Thread Michal Hagara

Anyone?

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

[foreman-users] Re: foreman-proxy and dhcpd next-server

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Katello 3.4.4 Released

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

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Re: Katello 3.4.4 Released

Re: [foreman-users] Re: Katello 3.4.4 Released

[foreman-users] Re: Katello 3.4.4 Released

[foreman-users] Re: Katello 3.4.4 Released

Re: [foreman-users] Foreman Host provisioning

Re: [foreman-users] Re: DHCP issues - UNABLE TO SAVE: Create DHCP Settings task failed

[foreman-users] Re: Updating puppet from 3.8.7 to 4.8.1 with Foreman 1.12.4 on EL6.8.

Re: [foreman-users] Re: DHCP issues - UNABLE TO SAVE: Create DHCP Settings task failed

18 matches

Site Navigation

Mail list logo

Footer information