Re: [foreman-users] Adding new OSes: ESXi, Windows, Solaris11

2017-12-11 Thread Tomer Brisker
Hello,

The files you mentioned are database migrations that are only needed if you
need to change some aspects of the database, from what you describe it
doesn't sound like it's required.

​In fact, adding ESXi support is a long-open feature request [1], we would
appreciate it if you would open a pull request with your changes against
the Foreman project on github[2]. This will also help ensure that any
changes you make do not break in future Foreman versions.
There was some attempt done in the past[3] for this but it looks like the
contribution got stale and eventually was not included, you could take a
look into that for some more insights into what is needed for this.

[1] http://projects.theforeman.org/issues/5176
[2] https://github.com/theforeman/foreman
[3] https://github.com/theforeman/foreman/pull/3998

On Tue, Dec 12, 2017 at 12:43 AM, Trisha Hoang 
wrote:

> Our R labs do a lot of testing on a variety of Operating Systems. We
> have gotten the Linuxes working and would like to add ESXi, Windows and
> Solaris 11 as well. The steps we have taken so far are as described below.
>
>
>
> 1.  Edit file ~foreman/app/models/operatingsystem.rb and add the new
> OS
>
> FAMILIES = { 'Debian'=> %r{Debian|Ubuntu}i,
>
>'Redhat'=> %r{RedHat|Centos|Fedora|
> Scientific|SLC|OracleLinux}i,
>
>'Suse'  => %r{OpenSuSE|SLES|SLED}i,
>
>'Windows'   => %r{Windows}i,
>
>'Altlinux'  => %r{Altlinux}i,
>
>'Archlinux' => %r{Archlinux}i,
>
>'Coreos'=> %r{CoreOS}i,
>
>'Gentoo'=> %r{Gentoo}i,
>
>'Solaris'   => %r{Solaris}i,
>
>'Freebsd'   => %r{FreeBSD}i,
>
>'AIX'   => %r{AIX}i,
>
>'Junos' => %r{Junos}i,
>
>'NXOS'  => %r{NX-OS}i,
>
>'Xenserver' => %r{XenServer}i,
>
>   'ESXi'  => %r{ESXi}i, }
>
> 2.   Add file ~foreman/app/models/operatingsystems/esxi.rb with
> relevant information
>
> 3.   Add relevant Provisioning Templates using the Foreman web
> interface
>
>
>
> The question we have is do we need to make changes to the Database? The
> following files under ~foreman/migrate/ seem to indicate some kind of
> database updates? Sorry, I’m not familiar with Ruby Rails architecture.
>
>
>
> 20100310080727_add_family_to_os.rb:os.family_id =
> Operatingsystem::FAMILIES.index :Solaris
>
> 20100616114400_change_family_in_os.rb:families = ["Debian", "Redhat",
> "Solaris", "Suse", "Windows"]
> 20120127141602_add_windows_templates.rb:class AddWindowsTemplates <
> ActiveRecord::Migration
>
> Thanks for your input.
> Trisha Hoang
>
> --
> 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.
>



-- 
Have a nice day,
Tomer Brisker
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 + katello install issues

2017-12-11 Thread Ivan Necas
On Mon, 11 Dec 2017 at 21:07, Joe Auerbach  wrote:

> So I'm very new to foreman, but I'm investigating it as a solution for
> some work issues.  it was recomended as an alternative to Spacewalk and it
> looks promising, however ...
>
> I installed on a centos 7 server built in Google Cloud Platform.  Right
> away, I got a server configuration error when i started Foreman (which
> installed without error).  This is, i think, because foreman thinks that my
> server can be accessed via the placeholder hostname assigned by google, but
> that's not a  huge issue.  Using the assigned IP i can access the system
> fine.
>
> However, when i try to install Katello, no luck. I followed the
> instructions found on the foreman site (
> https://theforeman.org/plugins/katello/3.2/installation/index.html) but
> upon trying to run "yum -y install katello" I'm getting dependency errors.
> Specifically about the only available version of rubygem (tfm  stuff) being
> too recent (for example version 0.9.1 when the install wants < 0.9.0
>

Have you tried katello 3.5 version?

-- Ivan


> I'm not really sure what to do with it at this point, but an assist would
> be appreciated.   Here's a pastebin of the error I get when following the
> website instructions. https://pastebin.com/NqsbkHJN
>
> --
> 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: Unable to add an EC2 compute resource : Error 500. How to setup an http proxy in Foreman ?

2017-12-11 Thread mldmld1968
Hi,
Finally, I found myself, 
in  /etc/sysconfig/httpd
http_proxy=http://proxyuser:proxypassw...@myproxy.company.com:1234
https_proxy=https://proxyuser:proxypassw...@myproxy.company.com:1234
+ systemctl restart httpd
But still have an issue, the proxy refuse the outbound connection. I will 
ask to the security team why. 
MLD

Le lundi 11 décembre 2017 21:07:49 UTC+1, mldml...@gmail.com a écrit :
>
> Hi,
> I'm a newbie on Foreman and relatively new on Linux. I installed it today 
> on CentOS 7. I play with the interface and I would like to add an EC2 
> compute resource
> For this, I created an account whitch if FullEC2Admin. So I have an access 
> key and a secret key.
> When I fill the form, and click on Load regions, I get a message : An 
> error occurred while testing the connection: Internal Server Error and the 
> production_log show an error 500.
>
> The first line shows getaddrinfo: Name or service not known (SocketError)
>
> As My foreman server is behind a firewall with authentication I tried 
> without success to add : 
>
>- In Configure>Global Parameters:
>
> http-password 
> http-port
> http-proxy
> http-user
>
>- Then I tried to add theses lines in  /etc/sysconfig/httpd
>
> export http_proxy=http://proxyuser:proxypassw...@myproxy.company.com:1234/
> export https_proxy=
> https://proxyuser:proxypassw...@myproxy.company.com:1234/
> + systemctl restart httpd
>
> Do foreman support an http or https proxy to connect to AWS ? And how to 
> setup it ?
>
> Thank you
> MLD
>
>
> 2017-12-11 18:36:22 951ba80a [app] [I] Processing by 
> ComputeResourcesController#test_connection as */*
> 2017-12-11 18:36:22 951ba80a [app] [I]   Parameters: {"utf8"=>"✓", 
> "authenticity_token"=>"lPBbTF/U3pcOVTRE6W2PZszvyO7GPmd32hzlH0kgMJo/FflA204r2u1JGvlgytKaYKsSRs9OazEwhXpGC88kgA==",
>  
> "compute_resource"=>{"name"=>"AWS Sandbox", "provider"=>"EC2", 
> "description"=>"", "user"=>"xxx", 
> "password"=>"[FILTERED]"}, "fakepassword"=>"[FILTERED]", "cr_id"=>""}
> 2017-12-11 18:36:22 951ba80a [app] [I] Current user: a067085 
> (administrator)
> 2017-12-11 18:36:22 951ba80a [app] [W] Action failed
>  | Excon::Error::Socket: getaddrinfo: Name or service not known 
> (SocketError)
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/socket.rb:101:in
>  
> `getaddrinfo'
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/socket.rb:101:in
>  
> `connect'
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/ssl_socket.rb:154:in
>  
> `connect'
> <...>
>  | 
> /usr/share/passenger/phusion_passenger/request_handler/thread_handler.rb:109:in
>  
> `main_loop'
>  | /usr/share/passenger/phusion_passenger/request_handler.rb:455:in `block 
> (3 levels) in start_threads'
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in
>  
> `call'
>  | 
> /opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in
>  
> `block in create_with_logging_context'
> 2017-12-11 18:36:22 951ba80a [app] [I]   Rendered common/500.html.erb 
> (12.3ms)
> 2017-12-11 18:36:22 951ba80a [app] [I] Completed 500 Internal Server Error 
> in 48ms (Views: 13.7ms | ActiveRecord: 1.2ms)
>

-- 
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: No available repos in 1.16.0

2017-12-11 Thread James Shewey
Doing some additional debugging, if I navigate to:

https://simulator.jdshewey.com/rhsm/consumers/b0ece1e3-2996-4bbe-a4cd-c2cd75640ac3/owner

I get back content:

{"parentOwner":null,"id":"ff808081603d3ab101603d3ba2950001","key":"foobar","displayName":"foobar","contentPrefix":"/foobar/$env","defaultServiceLevel":null,"upstreamConsumer":null,"logLevel":null,"autobindDisabled":null,"contentAccessMode":"entitlement","contentAccessModeList":"entitlement","href":"/owners/foobar","created":"2017-12-09T21:43:26+","updated":"2017-12-09T21:43:26+"}

But if I navigate to: 


https://simulator.jdshewey.com/rhsm/consumers/b0ece1e3-2996-4bbe-a4cd-c2cd75640ac3/enabled_repos


I get back "The page you were looking for doesn't exist. You may have mistyped 
the address or the page may have moved."

Should I be getting back a list of repos 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.


[foreman-users] No available repos in 1.16.0

2017-12-11 Thread James Shewey
I'm having trouble adding hosts with an Activation key. I am pretty sure I 
have it all set up right, and I can see that the activation key is 
associated with the correct environment and that subscriptions are properly 
attached, but I can't list any repos:

-

[root@slik01 ~]# hammer -u admin -p Password#1 subscription list 
--organization="foobar"
---|--|--|--|--|-|-|-|---|-
ID | UUID | NAME | TYPE | CONTRACT | 
ACCOUNT | SUPPORT | END DATE| QUANTITY  | CONSUMED
---|--|--|--|--|-|-|-|---|-
1  | ff808081603d3ab101603d468cd30006 | EPEL | Physical |  |
 | | 2047/12/02 21:55:19 | Unlimited | 1
2  | ff808081603d3ab101603d4730ee0011 | Katello  | Physical |  |
 | | 2047/12/02 21:56:03 | Unlimited | 1
3  | ff808081603d3ab101603d48ba8b00b5 | CentOS 7 | Physical |  |
 | | 2047/12/02 21:57:44 | Unlimited | 1
---|--|--|--|--|-|-|-|---|-
[root@slik01 ~]# hammer -u admin -p Password#1 activation-key list 
--organization="foobar"
---|--||---|
ID | NAME | HOST LIMIT | LIFECYCLE ENVIRONMENT | CONTENT VIEW
---|--||---|
1  | CentOS 7 | 0 of Unlimited |   | CentOS 7 - EPEL
2  | SLIK | 1 of Unlimited | Prod  | SLIK
---|--||---|
[root@slik01 ~]# hammer -u admin -p Password#1 activation-key subscriptions 
--organization="foobar" --id 2
---|--|--|--|-|-|-|--|
ID | NAME | ATTACHED | QUANTITY | START DATE  | END DATE
| SUPPORT | CONTRACT | ACCOUNT
---|--|--|--|-|-|-|--|
1  | EPEL |  |  | 2017/12/09 21:55:19 | 2047/12/02 
21:55:19 | |  |
2  | Katello  |  |  | 2017/12/09 21:56:03 | 2047/12/02 
21:56:03 | |  |
3  | CentOS 7 |  |  | 2017/12/09 21:57:44 | 2047/12/02 
21:57:44 | |  |
---|--|--|--|-|-|-|--|
[root@slik01 katello]# hammer -u admin -p Password#1 lifecycle-environment 
list --organization-label foobar
---|-|
ID | NAME| PRIOR
---|-|
2  | Dev | Library
1  | Library |
4  | Prod| Test
3  | Test| Dev
---|-|
[root@slik01 ~]# subscription-manager list --all --available
No available subscription pools to list
[root@slik01 katello]# subscription-manager repos
This system has no repositories available through subscriptions.
[root@slik01 ~]# sudo subscription-manager list --consumed
+---+
   Consumed Subscriptions
+---+
Subscription Name:   CentOS 7
Provides:CentOS 7
SKU: 122637583339
Contract:
Account:
Serial:  6681120976201556648
Pool ID: ff808081603d3ab101603d48ba8b00b5
Provides Management: No
Active:  True
Quantity Used:   1
Service Level:
Service Type:
Status Details:  Subscription is current
Subscription Type:   Standard
Starts:  12/09/2017
Ends:12/02/2047
System Type: Physical

Subscription Name:   EPEL
Provides:EPEL
SKU: 396060552743
Contract:
Account:
Serial:  7772339727441143075
Pool ID: ff808081603d3ab101603d468cd30006
Provides Management: No
Active:  True
Quantity Used:   1
Service Level:
Service Type:
Status Details:  Subscription is current
Subscription Type:   Standard
Starts:  12/09/2017
Ends:12/02/2047
System Type: Physical

Subscription Name:   Katello
Provides:Katello
SKU: 801967583872
Contract:
Account:
Serial:  1311031984624637998
Pool ID: ff808081603d3ab101603d4730ee0011
Provides Management: No
Active:  True
Quantity Used:   1
Service Level:
Service Type:
Status Details:  Subscription is current
Subscription Type:   Standard
Starts:  12/09/2017
Ends:12/02/2047
System Type: Physical

-

Interestingly, if I try to attach without an activation key, Katello can't 
seem to find the environment, even though I can see with hammer it exists

[root@slik01 

[foreman-users] Adding new OSes: ESXi, Windows, Solaris11

2017-12-11 Thread Trisha Hoang


Our R labs do a lot of testing on a variety of Operating Systems. We have 
gotten the Linuxes working and would like to add ESXi, Windows and Solaris 
11 as well. The steps we have taken so far are as described below.

 

1.  Edit file ~foreman/app/models/operatingsystem.rb and add the new OS

FAMILIES = { 'Debian'=> %r{Debian|Ubuntu}i,

   'Redhat'=> 
%r{RedHat|Centos|Fedora|Scientific|SLC|OracleLinux}i,

   'Suse'  => %r{OpenSuSE|SLES|SLED}i,

   'Windows'   => %r{Windows}i,

   'Altlinux'  => %r{Altlinux}i,

   'Archlinux' => %r{Archlinux}i,

   'Coreos'=> %r{CoreOS}i,

   'Gentoo'=> %r{Gentoo}i,

   'Solaris'   => %r{Solaris}i,

   'Freebsd'   => %r{FreeBSD}i,

   'AIX'   => %r{AIX}i,

   'Junos' => %r{Junos}i,

   'NXOS'  => %r{NX-OS}i,

   'Xenserver' => %r{XenServer}i,

  'ESXi'  => %r{ESXi}i, }

2.   Add file ~foreman/app/models/operatingsystems/esxi.rb with 
relevant information

3.   Add relevant Provisioning Templates using the Foreman web interface

 

The question we have is do we need to make changes to the Database? The 
following files under ~foreman/migrate/ seem to indicate some kind of 
database updates? Sorry, I’m not familiar with Ruby Rails architecture. 

 

20100310080727_add_family_to_os.rb:os.family_id = 
Operatingsystem::FAMILIES.index :Solaris

20100616114400_change_family_in_os.rb:families = ["Debian", "Redhat", 
"Solaris", "Suse", "Windows"]
20120127141602_add_windows_templates.rb:class AddWindowsTemplates < 
ActiveRecord::Migration

Thanks for your input.
Trisha Hoang

-- 
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/Katello upgrade to 1.16/3.5 fails on db:seed

2017-12-11 Thread Sven Jansen
Done.


On Monday, December 11, 2017 at 2:16:43 PM UTC+1, Andrew Kofink wrote:
>
> This looks like a valid bug. Would you mind opening an issue for it? 
> http://projects.theforeman.org/projects/katello/issues/new
>
> On first look, it seems like an issue with `Setting.foreman_url` here (
> https://github.com/theforeman/foreman_chef/blob/v0.5.0/db/seeds.rb#L19). 
> It should be `Setting[:foreman_url]`. I'm not sure when this changed in 
> Foreman, but foreman_chef needs to be updated.
>
> On Sun, Dec 10, 2017 at 9:49 AM, Sven Jansen  > wrote:
>
>> Hi,
>>
>> i have trouble running "foreman-installer --scenario katello --upgrade" 
>> after updating katello packages from 3.5rc1 to 3.5.
>>
>> I created this new server with following software, katello was 3.5rc1 and 
>> updated to 3.5 today.
>>
>> CentOS 7
>> Puppet 5
>> Foreman 1.16
>> Katello 3.5
>>
>> The upgrader complaints about "foreman_url". In settings the foreman_url 
>> is correctly configured.
>>
>> Success!
>> katello-service restart finished successfully!
>> Upgrade Step: db_seed...
>> /usr/share/foreman/lib/foreman.rb:8: warning: already initialized 
>> constant Foreman::UUID_REGEXP
>> /usr/share/foreman/lib/foreman.rb:8: warning: previous definition of 
>> UUID_REGEXP was here
>> rake aborted!
>> NoMethodError: undefined method `foreman_url' for 
>> #
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-
>> 4.2.5.1/lib/active_record/dynamic_matchers.rb:26:in `method_missing'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_chef-0.5.0/db/seeds.rb:19:in
>>  
>> `'
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
>> 4.2.5.1/lib/active_support/dependencies.rb:268:in `load'
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
>> 4.2.5.1/lib/active_support/dependencies.rb:268:in `block in load'
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
>> 4.2.5.1/lib/active_support/dependencies.rb:240:in `load_dependency'
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
>> 4.2.5.1/lib/active_support/dependencies.rb:268:in `load'
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:547:in
>>  
>> `load_seed'
>> /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'
>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_chef-0.5.0/lib/foreman_chef/engine.rb:12:in
>>  
>> `block (2 levels) in '
>> Tasks: TOP => db:seed
>> (See full trace by running task with --trace)
>> Seeding /usr/share/foreman/db/seeds.d/02-partition_tables_list.rb
>> Seeding /usr/share/foreman/db/seeds.d/02-permissions_list.rb
>> Seeding /usr/share/foreman/db/seeds.d/02-provisioning_templates_list.rb
>> Seeding /usr/share/foreman/db/seeds.d/02-roles_list.rb
>> Seeding /usr/share/foreman/db/seeds.d/03-auth_sources.rb
>> Seeding /usr/share/foreman/db/seeds.d/03-permissions.rb
>> Seeding /usr/share/foreman/db/seeds.d/03-roles.rb
>> Seeding /usr/share/foreman/db/seeds.d/04-admin.rb
>> Seeding /usr/share/foreman/db/seeds.d/05-taxonomies.rb
>> Seeding /usr/share/foreman/db/seeds.d/06-architectures.rb
>> Seeding /usr/share/foreman/db/seeds.d/07-provisioning_templates.rb
>> Seeding /usr/share/foreman/db/seeds.d/08-partition_tables.rb
>> Seeding /usr/share/foreman/db/seeds.d/10-installation_media.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/db/seeds.d/101-locations.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/db/seeds.d/102-organizations.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/db/seeds.d/103-provisioning_templates.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/db/seeds.d/104-proxy.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/db/seeds.d/106-mail_notifications.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/db/seeds.d/107-enable_dynflow.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/db/seeds.d/108-subcription-bookmarks.rb
>> Seeding /usr/share/foreman/db/seeds.d/11-smart_proxy_features.rb
>> Seeding /usr/share/foreman/db/seeds.d/13-compute_profiles.rb
>> Seeding /usr/share/foreman/db/seeds.d/15-bookmarks.rb
>> Seeding /usr/share/foreman/db/seeds.d/16-mail_notifications.rb
>> Seeding /usr/share/foreman/db/seeds.d/17-notification_blueprints.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.10.0/db/seeds.d/20-foreman_tasks_permissions.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_bootdisk-9.0.0/db/seeds.d/50-bootdisk_templates.rb
>> Seeding 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.10.0/db/seeds.d/60-dynflow_proxy_feature.rb
>> Seeding 
>> 

[foreman-users] Foreman yum dependency after a Katello 3.4 -> 3.5 upgrade

2017-12-11 Thread Tony Coffman
I did an update from Katello 3.4 -> 3.5 yesterday and ran into what looks 
like it might be a packaging issue.

The original symptom was that remote execution was broken. It took me a 
little while but then I realized that I still had the 1.15 remote execution 
packages installed instead of the 1.16 equivalents.

[root@rich-form-01-pv yum.repos.d]# rpm -qa | grep fm1_15
tfm-rubygem-dynflow-0.8.30-1.fm1_15.el7.noarch
tfm-rubygem-foreman_remote_execution-1.3.7-1.fm1_15.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.0.6-1.fm1_15.el7.noarch
tfm-rubygem-concurrent-ruby-edge-0.2.3-1.fm1_15.el7.noarch


I check and I did have the correct 1.16 repos defined but yum update showed 
everything as up to date.  When I tried to manually install the 1.16 
version, I got this

[root@rich-form-01-pv ~]# yum install 
https://yum.theforeman.org/plugins/1.16/el7/x86_64/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm
Loaded plugins: fastestmirror
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm  
  | 434 kB  00:00:00
Examining 
/var/tmp/yum-root-5i1ybr/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm:
 
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch
/var/tmp/yum-root-5i1ybr/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm:
 
does not update installed package.
Error: Nothing to do


So I ended up removing my remote 1.15 remote execution package and 
installing the 1.16 equivalents.  That got remote execution working but 
then I ran an orphan check as a sanity check and found some additional 
packages that don't seem to be right.

[root@rich-form-01-pv yum.repos.d]# package-cleanup --orphans
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.riverfrontnetworks.com
 * epel: mirror.steadfast.net
 * extras: mirror.beyondhosting.net
 * updates: mirror.rackspace.com
java-client-1.0-1.noarch
katello-client-bootstrap-1.4.0-2.el7.noarch
katello-default-ca-1.0-1.noarch
katello-server-ca-1.0-1.noarch
kernel-3.10.0-514.el7.x86_64
kernel-3.10.0-514.16.1.el7.x86_64
kernel-3.10.0-514.21.1.el7.x86_64
kernel-3.10.0-514.26.2.el7.x86_64
pulp-client-1.0-1.noarch
python-nectar-1.5.4-1.el7.noarch
rich-form-01-pv.ipa.snapbs.com-apache-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-foreman-client-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-foreman-proxy-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-foreman-proxy-client-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-puppet-client-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-qpid-broker-1.0-2.noarch
rich-form-01-pv.ipa.snapbs.com-qpid-client-cert-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-qpid-router-client-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-qpid-router-server-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-tomcat-1.0-1.noarch
tfm-rubygem-concurrent-ruby-edge-0.2.3-1.fm1_15.el7.noarch
tfm-rubygem-dynflow-0.8.30-1.fm1_15.el7.noarch
tfm-rubygem-net-ssh-4.0.1-2.el7.noarch
tfm-rubygem-safemode-1.3.2-1.el7.noarch
tfm-rubygem-scoped_search-4.1.2-1.el7.noarch

I don't understand the last 5 packages in this list.  Some of these 
definitely have 1.16 equivalents but it seems like some kind of dependency 
isn't right as I can't upgrade or remove and reinstall without blowing up a 
lot of packages.  I'm pretty sure when I did the 3.3 -> 3.4 upgrade the 
orphans list didn't have any Foreman or Katello packages (except certs).

Any ideas what may be going on with those packages during an upgrade?

Regards,
--Tony



-- 
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] Unable to add an EC2 compute resource : Error 500. How to setup an http proxy in Foreman ?

2017-12-11 Thread mldmld1968
Hi,
I'm a newbie on Foreman and relatively new on Linux. I installed it today 
on CentOS 7. I play with the interface and I would like to add an EC2 
compute resource
For this, I created an account whitch if FullEC2Admin. So I have an access 
key and a secret key.
When I fill the form, and click on Load regions, I get a message : An error 
occurred while testing the connection: Internal Server Error and the 
production_log show an error 500.

The first line shows getaddrinfo: Name or service not known (SocketError)

As My foreman server is behind a firewall with authentication I tried 
without success to add : 

   - In Configure>Global Parameters:

http-password 
http-port
http-proxy
http-user

   - Then I tried to add theses lines in  /etc/sysconfig/httpd

export http_proxy=http://proxyuser:proxypassw...@myproxy.company.com:1234/
export https_proxy=https://proxyuser:proxypassw...@myproxy.company.com:1234/
+ systemctl restart httpd

Do foreman support an http or https proxy to connect to AWS ? And how to 
setup it ?

Thank you
MLD


2017-12-11 18:36:22 951ba80a [app] [I] Processing by 
ComputeResourcesController#test_connection as */*
2017-12-11 18:36:22 951ba80a [app] [I]   Parameters: {"utf8"=>"✓", 
"authenticity_token"=>"lPBbTF/U3pcOVTRE6W2PZszvyO7GPmd32hzlH0kgMJo/FflA204r2u1JGvlgytKaYKsSRs9OazEwhXpGC88kgA==",
 
"compute_resource"=>{"name"=>"AWS Sandbox", "provider"=>"EC2", 
"description"=>"", "user"=>"xxx", 
"password"=>"[FILTERED]"}, "fakepassword"=>"[FILTERED]", "cr_id"=>""}
2017-12-11 18:36:22 951ba80a [app] [I] Current user: a067085 (administrator)
2017-12-11 18:36:22 951ba80a [app] [W] Action failed
 | Excon::Error::Socket: getaddrinfo: Name or service not known 
(SocketError)
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/socket.rb:101:in
 
`getaddrinfo'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/socket.rb:101:in
 
`connect'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/ssl_socket.rb:154:in
 
`connect'
<...>
 | 
/usr/share/passenger/phusion_passenger/request_handler/thread_handler.rb:109:in 
`main_loop'
 | /usr/share/passenger/phusion_passenger/request_handler.rb:455:in `block 
(3 levels) in start_threads'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in
 
`call'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in
 
`block in create_with_logging_context'
2017-12-11 18:36:22 951ba80a [app] [I]   Rendered common/500.html.erb 
(12.3ms)
2017-12-11 18:36:22 951ba80a [app] [I] Completed 500 Internal Server Error 
in 48ms (Views: 13.7ms | ActiveRecord: 1.2ms)

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


[foreman-users] Foreman + katello install issues

2017-12-11 Thread Joe Auerbach
So I'm very new to foreman, but I'm investigating it as a solution for some 
work issues.  it was recomended as an alternative to Spacewalk and it looks 
promising, however ...

I installed on a centos 7 server built in Google Cloud Platform.  Right 
away, I got a server configuration error when i started Foreman (which 
installed without error).  This is, i think, because foreman thinks that my 
server can be accessed via the placeholder hostname assigned by google, but 
that's not a  huge issue.  Using the assigned IP i can access the system 
fine. 

However, when i try to install Katello, no luck. I followed the 
instructions found on the foreman site 
(https://theforeman.org/plugins/katello/3.2/installation/index.html) but 
upon trying to run "yum -y install katello" I'm getting dependency errors.  
Specifically about the only available version of rubygem (tfm  stuff) being 
too recent (for example version 0.9.1 when the install wants < 0.9.0

I'm not really sure what to do with it at this point, but an assist would 
be appreciated.   Here's a pastebin of the error I get when following the 
website instructions. https://pastebin.com/NqsbkHJN

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


[foreman-users] katello proxy ssl error

2017-12-11 Thread Ondřej Levý
Hi,
i trying add first katello capsule. But with no luck. I always stuck with 
this error bellow. I use katello 3.4.

- Unable to communicate with the proxy: ERF12-2530 
[ProxyAPI::ProxyException]: Unable to detect features 
([OpenSSL::SSL::SSLError]: SSL_connect returned=1 errno=0 state=SSLv3 read 
server session ticket A: tlsv1 alert un...) for proxy 
https://XX:9090/features
- Please check the proxy is configured and running on the host.

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


[foreman-users] Foreman host provisioning on the different subnet with external DHCP

2017-12-11 Thread mt
Hello everyone,

So far I was playing with Foreman provisioning within only one network in 
which Foreman was configured as the DHCP server. Everything is working 
fine, IP addresses are assigned and the network (PXE boot) provisioning 
works just great.

Now comes the question, if I want to play with it seriously, I need to have 
the possibility of provisioning hosts to many networks, not only the one 
the Foreman is installed in. In particular, I'm interested in the scenario 
where I am able to provision the hosts in the network, where there is 
another DHCP server running. Is this possible? Of course, routing is in 
place and the Foreman is capable of reaching the other network.

If so, can someone provide me with the quick how to or link to the proper 
article?

Thanks in advance!

-- 
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/Katello upgrade to 1.16/3.5 fails on db:seed

2017-12-11 Thread Andrew Kofink
This looks like a valid bug. Would you mind opening an issue for it?
http://projects.theforeman.org/projects/katello/issues/new

On first look, it seems like an issue with `Setting.foreman_url` here (
https://github.com/theforeman/foreman_chef/blob/v0.5.0/db/seeds.rb#L19). It
should be `Setting[:foreman_url]`. I'm not sure when this changed in
Foreman, but foreman_chef needs to be updated.

On Sun, Dec 10, 2017 at 9:49 AM, Sven Jansen 
wrote:

> Hi,
>
> i have trouble running "foreman-installer --scenario katello --upgrade"
> after updating katello packages from 3.5rc1 to 3.5.
>
> I created this new server with following software, katello was 3.5rc1 and
> updated to 3.5 today.
>
> CentOS 7
> Puppet 5
> Foreman 1.16
> Katello 3.5
>
> The upgrader complaints about "foreman_url". In settings the foreman_url
> is correctly configured.
>
> Success!
> katello-service restart finished successfully!
> Upgrade Step: db_seed...
> /usr/share/foreman/lib/foreman.rb:8: warning: already initialized
> constant Foreman::UUID_REGEXP
> /usr/share/foreman/lib/foreman.rb:8: warning: previous definition of
> UUID_REGEXP was here
> rake aborted!
> NoMethodError: undefined method `foreman_url' for #
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-
> 4.2.5.1/lib/active_record/dynamic_matchers.rb:26:in `method_missing'
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_chef-0.5.0/db/seeds.rb:19:in
> `'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/dependencies.rb:268:in `load'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/dependencies.rb:268:in `block in load'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/dependencies.rb:240:in `load_dependency'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/dependencies.rb:268:in `load'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:547:in
> `load_seed'
> /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'
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_chef-
> 0.5.0/lib/foreman_chef/engine.rb:12:in `block (2 levels) in
> '
> Tasks: TOP => db:seed
> (See full trace by running task with --trace)
> Seeding /usr/share/foreman/db/seeds.d/02-partition_tables_list.rb
> Seeding /usr/share/foreman/db/seeds.d/02-permissions_list.rb
> Seeding /usr/share/foreman/db/seeds.d/02-provisioning_templates_list.rb
> Seeding /usr/share/foreman/db/seeds.d/02-roles_list.rb
> Seeding /usr/share/foreman/db/seeds.d/03-auth_sources.rb
> Seeding /usr/share/foreman/db/seeds.d/03-permissions.rb
> Seeding /usr/share/foreman/db/seeds.d/03-roles.rb
> Seeding /usr/share/foreman/db/seeds.d/04-admin.rb
> Seeding /usr/share/foreman/db/seeds.d/05-taxonomies.rb
> Seeding /usr/share/foreman/db/seeds.d/06-architectures.rb
> Seeding /usr/share/foreman/db/seeds.d/07-provisioning_templates.rb
> Seeding /usr/share/foreman/db/seeds.d/08-partition_tables.rb
> Seeding /usr/share/foreman/db/seeds.d/10-installation_media.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.
> 1/db/seeds.d/101-locations.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.
> 1/db/seeds.d/102-organizations.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.
> 1/db/seeds.d/103-provisioning_templates.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.
> 1/db/seeds.d/104-proxy.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.
> 1/db/seeds.d/106-mail_notifications.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.
> 1/db/seeds.d/107-enable_dynflow.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.
> 1/db/seeds.d/108-subcription-bookmarks.rb
> Seeding /usr/share/foreman/db/seeds.d/11-smart_proxy_features.rb
> Seeding /usr/share/foreman/db/seeds.d/13-compute_profiles.rb
> Seeding /usr/share/foreman/db/seeds.d/15-bookmarks.rb
> Seeding /usr/share/foreman/db/seeds.d/16-mail_notifications.rb
> Seeding /usr/share/foreman/db/seeds.d/17-notification_blueprints.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-
> 0.10.0/db/seeds.d/20-foreman_tasks_permissions.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_
> bootdisk-9.0.0/db/seeds.d/50-bootdisk_templates.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-
> 0.10.0/db/seeds.d/60-dynflow_proxy_feature.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_
> remote_execution-1.3.3/db/seeds.d/60-ssh_proxy_feature.rb
> Seeding /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-
> 0.10.0/db/seeds.d/61-foreman_tasks_bookmarks.rb
> Seeding 

Re: [foreman-users] Can Foreman support Deploying Windows images into Bare Metal?

2017-12-11 Thread Lukas Zapletal
We have several users doing that, check demos from this year, we had
one or two demos around this topic.

LZ

On Mon, Dec 11, 2017 at 8:04 AM, shrek maxi  wrote:
> If it does. How?
>
> --
> 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: celery and pulp_streamer not working in fresh install Katello 3.5 and Foreman 1.16

2017-12-11 Thread Mike Hulsman
I found the solution for this.

When installing with:  foreman-installer --scenario katello the 
rpm python-django16-1.6.11.6-6.el7.noarch is installed.
That is given the error exceptions.ImportError: No module named 
django.core.urlresolvers

When you manually install the rpm  python-django-1.6.11.6-1.el7.noarch all 
the pulp workers are starting and no 500 Internal Server Errors appear.

Regard.
Mike Hulsman

On Sunday, December 10, 2017 at 10:15:23 AM UTC+1, Mike Hulsman wrote:
>
> In a fresh install on CentOS 7.4 pulp is not working.
> The webui is working , but when I try to add a yum repository to a product 
> the following message is displayed:
> "There was an issue with the backend service pulp: 500 Internal Server 
> Error"
>
> The smartproxy is running on the same server as foreman , iptables and 
> selinux disabled
>
>
> Running the foreman-service status  I see the following errors.
>
> /usr/sbin/service-wait pulp_resource_manager status
> ● pulp_resource_manager.service - Pulp Resource Manager
>Loaded: loaded (/usr/lib/systemd/system/pulp_resource_manager.service; 
> enabled; vendor preset: disabled)
>Active: failed (Result: exit-code) since Sat 2017-12-09 22:29:35 CET; 
> 1h 26min ago
>   Process: 1186 ExecStart=/usr/bin/celery worker -A pulp.server.async.app 
> -n resource_manager@%%h -Q resource_manager -c 1 --events --umask 18 
> --pidfile=/var/run/pulp/resource_manager.pid (code=exited, st
> atus=1/FAILURE)
>  Main PID: 1186 (code=exited, status=1/FAILURE)
>
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl celery[1186]: File 
> "/usr/lib/python2.7/site-packages/pulp/plugins/loader/manager.py", line 9, 
> in 
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl celery[1186]: from 
> pulp.server.db.model import ContentUnit
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl celery[1186]: File 
> "/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py", line 
> 33, in 
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl celery[1186]: from 
> pulp.server.webservices.views import serializers
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl celery[1186]: File 
> "/usr/lib/python2.7/site-packages/pulp/server/webservices/views/serializers/__init__.py",
>  
> line 4, in 
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl celery[1186]: from 
> django.core.urlresolvers import reverse
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl celery[1186]: ImportError: No module 
> named django.core.urlresolvers
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl systemd[1]: 
> pulp_resource_manager.service: main process exited, code=exited, 
> status=1/FAILURE
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl systemd[1]: Unit 
> pulp_resource_manager.service entered failed state.
> Dec 09 22:29:35 v1c2c02.mst.proxy.nl systemd[1]: 
> pulp_resource_manager.service failed.
> /usr/sbin/service-wait pulp_streamer status
> ● pulp_streamer.service - The Pulp lazy content loading streamer
>Loaded: loaded (/usr/lib/systemd/system/pulp_streamer.service; enabled; 
> vendor preset: disabled)
>Active: failed (Result: exit-code) since Sat 2017-12-09 22:29:36 CET; 
> 1h 26min ago
>   Process: 1193 ExecStart=/usr/bin/pulp_streamer --nodaemon --syslog 
> --prefix=pulp_streamer --pidfile= --python 
> /usr/share/pulp/wsgi/streamer.tac (code=exited, status=1/FAILURE)
>  Main PID: 1193 (code=exited, status=1/FAILURE)
>
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl pulp_streamer[1193]: from 
> pulp.server.db.model import Worker, ReservedResource, TaskStatus, \
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl pulp_streamer[1193]: File 
> "/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py", line 
> 33, in 
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl pulp_streamer[1193]: from 
> pulp.server.webservices.views import serializers
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl pulp_streamer[1193]: File 
> "/usr/lib/python2.7/site-packages/pulp/server/webservices/views/serializers/__init__.py",
>  
> line 4, in 
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl pulp_streamer[1193]: from 
> django.core.urlresolvers import reverse
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl pulp_streamer[1193]: 
> exceptions.ImportError: No module named django.core.urlresolvers
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl pulp_streamer[1193]: Failed to load 
> application: No module named django.core.urlresolvers
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl systemd[1]: pulp_streamer.service: 
> main process exited, code=exited, status=1/FAILURE
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl systemd[1]: Unit 
> pulp_streamer.service entered failed state.
> Dec 09 22:29:36 v1c2c02.mst.proxy.nl systemd[1]: pulp_streamer.service 
> failed.
>
> Systemctl for the pulp services:
> ● pulp_celerybeat.service 
>loadedfailed   failedPulp's 
> Celerybeat
> ● pulp_resource_manager.service   
>loadedfailed   failedPulp 
> Resource Manager
> ● pulp_streamer.service   
>