Re: [foreman-users] Re: Foreman OpenSCAP problems

[Marek Hulan]

Hello, it seems that the parameters for the host were not set. The ENC 
output does not contain information about any policy. Did you configure at 
least one? Did you assign it to hostgroup that the host is assigned to? The 
puppet class is not meant to be assigned manually to the host, it should 
happen automatically if you do policy association.


Hope this helps

--
Marek

Sent with AquaMail for Android
http://www.aqua-mail.com


On August 23, 2017 21:54:17 Diggy  wrote:


Sorry, should have added this to my initial post.  Here's output from when
I try to do an OpenSCAP scan on a host from Foreman:

Failed to initialize: Dynflow::ExecutionPlan::Steps::Error - Failed
rendering template: error during rendering: ERF47-1439
[TemplateInput::ValueNotReady]: Input 'policies' is not ready for rendering


On Wednesday, August 23, 2017 at 3:31:48 PM UTC-4, Diggy wrote:


Hello, all.

I'm running the latest version of Foreman, and would like to extend its
capabilities by enabling OpenSCAP.  As per the Foreman OpenSCAP Manual,
I've installed foreman_openscap, smart_proxy_openscap, and
puppet-foreman_openscap_client, and can see OpenSCAP-related controls in my
Foreman instance.  However, when the foreman_scap_client class is added
to a host that I've added to an OpenScap policy, not only doesn't Foreman
OpenSCap not work on that host, but Puppet on that host stops working
altogether.  Here's the relevant output from running "puppet agent --test"
on the host:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
{"message":"Server Error: Evaluation Error: Error while evaluating a
Resource Statement, Evaluation Error: Error while evaluating a Function
Call, Failed to parse inline template: undefined local variable or method
`policies_array' for # at
/etc/puppetlabs/code/environments/production/modules/foreman_scap_client/manifests/init.pp:42:20
on node 
agrega2.netatlantic.com","issue_kind":"RUNTIME_ERROR","stacktrace":["Warning:

The 'stacktrace' property is deprecated and will be removed in a future
version of Puppet. For security reasons, stacktraces are not returned with
Puppet HTTP Error responses."]}
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Firstly, can anyone tell me why this error is occurring?  Secondly, can
anyone help me with (explicit) steps needed to make Foreman OpenSCAP work?

Your help would be greatly appreciated.

Diggy



--
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to foreman-users+unsubscr...@googlegroups.com.

To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.



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

[foreman-users] Re: Foreman OpenSCAP problems

[Diggy]

Sorry, should have added this to my initial post.  Here's output from when 
I try to do an OpenSCAP scan on a host from Foreman:

Failed to initialize: Dynflow::ExecutionPlan::Steps::Error - Failed 
rendering template: error during rendering: ERF47-1439 
[TemplateInput::ValueNotReady]: Input 'policies' is not ready for rendering


On Wednesday, August 23, 2017 at 3:31:48 PM UTC-4, Diggy wrote:
>
> Hello, all.
>
> I'm running the latest version of Foreman, and would like to extend its 
> capabilities by enabling OpenSCAP.  As per the Foreman OpenSCAP Manual, 
> I've installed foreman_openscap, smart_proxy_openscap, and 
> puppet-foreman_openscap_client, and can see OpenSCAP-related controls in my 
> Foreman instance.  However, when the foreman_scap_client class is added 
> to a host that I've added to an OpenScap policy, not only doesn't Foreman 
> OpenSCap not work on that host, but Puppet on that host stops working 
> altogether.  Here's the relevant output from running "puppet agent --test" 
> on the host:
>
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
> {"message":"Server Error: Evaluation Error: Error while evaluating a 
> Resource Statement, Evaluation Error: Error while evaluating a Function 
> Call, Failed to parse inline template: undefined local variable or method 
> `policies_array' for # at 
> /etc/puppetlabs/code/environments/production/modules/foreman_scap_client/manifests/init.pp:42:20
>  
> on node 
> agrega2.netatlantic.com","issue_kind":"RUNTIME_ERROR","stacktrace":["Warning: 
> The 'stacktrace' property is deprecated and will be removed in a future 
> version of Puppet. For security reasons, stacktraces are not returned with 
> Puppet HTTP Error responses."]}
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
> Firstly, can anyone tell me why this error is occurring?  Secondly, can 
> anyone help me with (explicit) steps needed to make Foreman OpenSCAP work?
>
> Your help would be greatly appreciated.
>
> Diggy
>

-- 
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 OpenSCAP problems

[Diggy]

Hello, all.

I'm running the latest version of Foreman, and would like to extend its 
capabilities by enabling OpenSCAP.  As per the Foreman OpenSCAP Manual, 
I've installed foreman_openscap, smart_proxy_openscap, and 
puppet-foreman_openscap_client, and can see OpenSCAP-related controls in my 
Foreman instance.  However, when the foreman_scap_client class is added to 
a host that I've added to an OpenScap policy, not only doesn't Foreman 
OpenSCap not work on that host, but Puppet on that host stops working 
altogether.  Here's the relevant output from running "puppet agent --test" 
on the host:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
{"message":"Server Error: Evaluation Error: Error while evaluating a 
Resource Statement, Evaluation Error: Error while evaluating a Function 
Call, Failed to parse inline template: undefined local variable or method 
`policies_array' for # at 
/etc/puppetlabs/code/environments/production/modules/foreman_scap_client/manifests/init.pp:42:20
 
on node 
agrega2.netatlantic.com","issue_kind":"RUNTIME_ERROR","stacktrace":["Warning: 
The 'stacktrace' property is deprecated and will be removed in a future 
version of Puppet. For security reasons, stacktraces are not returned with 
Puppet HTTP Error responses."]}
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Firstly, can anyone tell me why this error is occurring?  Secondly, can 
anyone help me with (explicit) steps needed to make Foreman OpenSCAP work?

Your help would be greatly appreciated.

Diggy

-- 
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] Getting error : "ERF42-7633 [Foreman::Exception]: No templates found" after host builds.

[Ashish Singh]

While creating a host, I can see few "Provisioning templates" but after the 
host builds, I see this error "ERF42-7633 [Foreman::Exception]: No 
templates found" and there is no information regarding it here : 
http://projects.theforeman.org/projects/foreman/wiki/ErrorCodes

-- 
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] Broken host creation API call after upgrading to 1.11

[Dmytro Korochkin]

Hi there, 

I've recently upgraded my Foreman 1.10 -> 1.11.4 . Since that time we 
cannot create hosts using API/hammer anymore with non-admin user.
My POST. Architecture, etc are inherited from the hostgroup
[ INFO 2017-08-23 13:39:11 API] POST /api/hosts
[DEBUG 2017-08-23 13:39:11 API] Params: {
"host" => {
  "name" => "testserver01",
   "location_id" => 6,
"ip" => "192.168.0.5",
   "mac" => "00:26:27:28:29:FF",
"operatingsystem_id" => 65,
 "subnet_id" => 1686,
  "hostgroup_id" => 2,
 "build" => false,
   "enabled" => true,
   "managed" => true,
"compute_attributes" => {
"volumes_attributes" => {}
},
 "overwrite" => true,
"host_parameters_attributes" => {},
 "interfaces_attributes" => {}
}
}

Response:
[DEBUG 2017-08-23 13:39:53 API] 422 Unprocessable Entity
{
"error" => {
   "id" => nil,
   "errors" => {
"base" => [
[0] "No PXELinux templates were found for this host, make 
sure you define at least one in your Redhat 6.9 settings"
],
   "interfaces.domain" => [
[0] "can't be blank"
],
"interfaces.domain_id" => [
[0] "can't find domain with this id"
],
 "interfaces.base" => [
[0] "No PXELinux templates were found for this host, make 
sure you define at least one in your Redhat 6.9 settings"
],
 "architecture_id" => [
[0] "can't be blank"
],
"conflict" => [],
 "interfaces.conflict" => []
},
"full_messages" => [
[0] "No PXELinux templates were found for this host, make sure 
you define at least one in your Redhat 6.9 settings",
[1] "Domain can't be blank",
[2] "Interfaces.domain can't find domain with this id",
[3] "Base No PXELinux templates were found for this host, make 
sure you define at least one in your Redhat 6.9 settings",
[4] "Architecture can't be blank"
]
}
}

Those parameters are available in a hostgroup.
At the same time it works okay with the admin user. Everything was okay in 
1.10 with non-admin.
No error messages in the foreman log.

I tried to change permissions in roles, but even after adding of all 
possible items it still doesn't work with the same error.
It can only be fixed by making API user as Admin, which is a unsecure.

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.

[foreman-users] Re: Single stack ipv6 build, Foreman 1.15+?

[Mike Wilson]

Additionally when manually setting up the subnets/etc I get the following 
error when submitting the new VM.

Unable to render PXELinux template 'Kickstart default PXELinux': bad URI(is 
not URI?): http://:XXX:XXX:X:XXX:XXff:XX84:XXbd

Where that long string is the ipv6 address of the foreman server/proxy.

-- 
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] Single stack ipv6 build, Foreman 1.15+?

[Mike Wilson]

I'm trying to configure Foreman to build a host, using ipv6 only. First 
off, is this possible? Secondly is there a walkthrough on a sample setup 
for it? I've been having nothing but bad luck trying to get it working. 
Biggest blocker seems to be with the "provisioning setup" it only lists the 
ipv4 "provisioning network" to select.

-- 
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] Help with Foreman's external authentication with FreeIPA. (Kerberos)

[VladF]

Hi, 
I am trying  to make external authentication via kerberos SSO on foreman 
server.  I use this tutorial 
- https://theforeman.org/manuals/1.6/#5.7ExternalAuthentication
Foreman server is freeipa enrolled. I've make a service 
HTTP/foreman.test.com on freeipa and do that on foreman server:

kinit admin ipa-getkeytab -s MY IPA SERVER fqdn -k /etc/http.keytab -p HTTP/
foreman.test.com
chown apache /etc/http.keytab 
chmod 600 /etc/http.keytab 



but when I try to access foreman.test.com I see the error Kerberos 
authentication did not pass.

klist on my foreman server:

[root@foreman ~]# klist
Ticket cache: KEYRING:persistent:0:krb_ccache_Sab2PVh
Default principal: HTTPS/foreman.test@centos-25.test.com


Valid starting   Expires  Service principal
08/23/2017 08:50:29  08/24/2017 08:50:29  krbtgt/CENTOS-25.TEST.COM@CENTOS-
25.TEST.COM

I've installed modules mod_auth_kerb mod_authnz_pam and edit my 
/etc/httpd/conf.d/auth_kerb.conf.

# add to /etc/httpd/conf.d/auth_kerb.conf LoadModule auth_kerb_module 
modules/mod_auth_kerb.so LoadModule authnz_pam_module 
modules/mod_authnz_pam.so  AuthType Kerberos 
AuthName "Kerberos Login" KrbMethodNegotiate On KrbMethodK5Passwd Off 
KrbAuthRealms EXAMPLE.COM Krb5KeyTab /etc/http.keytab KrbLocalUserMapping 
On # require valid-user require pam-account foreman-prod ErrorDocument 401 
'Kerberos authentication did not 
pass.' # The following is needed as a workaround for 
https://bugzilla.redhat.com/show_bug.cgi?id=1020087 ErrorDocument 500 
'Kerberos authentication did not 
pass.' 

What am I doing wrong? How can I debug this problem?

-- 
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 ansible callback plugin foreman_callback.py generate duplicate hosts in foreman

[Michael Klug]

Just experimented a little more, I think it's your callback version. Will 
write more information in the next few days.

On Wednesday, August 23, 2017 at 1:05:43 PM UTC+2, Michael Klug wrote:
>
> I think this happens when you don't use the fqdn in ansible hosts file. 
>
> As soon as I started using the the correct fqdn I only got one host and no 
> duplicates.
>
> On Wednesday, August 23, 2017 at 11:45:31 AM UTC+2, mobios wrote:
>>
>> Hello,
>>
>> I have a problem with duplicate hosts in Foreman.
>>
>>
>> Info: My setup
>> Foreman = 1.15.2
>> Foreman_ansible = 1.4.5
>> ansible = 2.0.0.2
>>
>>
>>
>> I use the callback plugin foreman_callback.py
>>  as described here -> 
>> https://theforeman.org/plugins/foreman_ansible/0.x/index.html.
>>
>> I have configured my foreman and ansible.
>>
>> Foreman-Settings:
>> Create new host when Facts are uploaded = Yes
>> Create new host when reports is uploaded = Yes
>>
>>
>> If i run on my ansible server:
>>
>> ansible all  -m setup
>>
>> all is fine the hosts were created correctly in Foreman.
>> But if i run the ansible command again the host were duplicated.
>>
>> Please see attachment how is look like.
>>
>>
>>
>> Has anyone a idea why the foreman_callback.py duplicated the Hosts in 
>> Foreman?
>>
>> Regards
>> mobios
>>  
>>
>>

-- 
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 3.4 fixed with new Bastion release

[Eric D Helms]

All,

Some have reported a broken issue with a new version of tfm-rubygem-bastion
breaking Katello installs and upgrades. I have pushed out an updated
version of the plugin (5.0.10) that is now available in the plugins. Please
upgrade to it and re-run your workflows.

My sincerest apologies for breaking everyone.


-- 
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: Foreman ansible callback plugin foreman_callback.py generate duplicate hosts in foreman

[Michael Klug]

I think this happens when you don't use the fqdn in ansible hosts file. 

As soon as I started using the the correct fqdn I only got one host and no 
duplicates.

On Wednesday, August 23, 2017 at 11:45:31 AM UTC+2, mobios wrote:
>
> Hello,
>
> I have a problem with duplicate hosts in Foreman.
>
>
> Info: My setup
> Foreman = 1.15.2
> Foreman_ansible = 1.4.5
> ansible = 2.0.0.2
>
>
>
> I use the callback plugin foreman_callback.py
>  as described here -> 
> https://theforeman.org/plugins/foreman_ansible/0.x/index.html.
>
> I have configured my foreman and ansible.
>
> Foreman-Settings:
> Create new host when Facts are uploaded = Yes
> Create new host when reports is uploaded = Yes
>
>
> If i run on my ansible server:
>
> ansible all  -m setup
>
> all is fine the hosts were created correctly in Foreman.
> But if i run the ansible command again the host were duplicated.
>
> Please see attachment how is look like.
>
>
>
> Has anyone a idea why the foreman_callback.py duplicated the Hosts in 
> Foreman?
>
> Regards
> mobios
>  
>
>

-- 
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 ansible callback plugin foreman_callback.py generate duplicate hosts in foreman

[mobios]

Sorry i forgot the attachment. Now i added.
>

-- 
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: bastion plugin requires Foreman >= 1.16 but current is 1.15.3

[Jorick Astrego]

For anyone with the same problem, doing

yum downgrade tfm-rubygem-bastion tfm-rubygem-angular-rails-templates

tfm-rubygem-bastion-5.0.6-1.fm1_15.el7.noarch

tfm-rubygem-angular-rails-templates-0.1.2-5.el7.noarch

Gets things working again.

Regards, Jorick Astrego



On 08/23/2017 11:25 AM, Jorick Astrego wrote:
>
> Sorry, just saw this from this morning:
>
> Re: [foreman-users] UPG from 2.4.4 to 3.x (also to 3.4.4 failing)
>
> So same problem here :-&
>
>
> On 08/23/2017 11:23 AM, Jorick Astrego wrote:
>>
>> Hi,
>>
>> Upgraded to Katello 3.4, but I get the following error:
>>
>> Foreman::PluginRequirementError: ERF72-1622
>> [Foreman::PluginRequirementError]: bastion plugin requires
>> Foreman >= 1.16 but current is 1.15.3
>>
>> Katello 3.4 has as dependency 1.15, so why does the plugin require 1.16?
>>
>> tfm-rubygem-bastion-5.0.9-1.fm1_15.el7.noarch
>> foreman-1.15.3-1.el7.noarch
>> katello-3.4.4-2.el7.noarch
>>
>>
>





Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts 



Tel: 053 20 30 270  i...@netbulae.euStaalsteden 4-3A
KvK 08198180
Fax: 053 20 30 271  www.netbulae.eu 7547 TA Enschede
BTW NL821234584B01



-- 
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: bastion plugin requires Foreman >= 1.16 but current is 1.15.3

[Jorick Astrego]

Sorry, just saw this from this morning:

Re: [foreman-users] UPG from 2.4.4 to 3.x (also to 3.4.4 failing)

So same problem here :-&


On 08/23/2017 11:23 AM, Jorick Astrego wrote:
>
> Hi,
>
> Upgraded to Katello 3.4, but I get the following error:
>
> Foreman::PluginRequirementError: ERF72-1622
> [Foreman::PluginRequirementError]: bastion plugin requires Foreman
> >= 1.16 but current is 1.15.3
>
> Katello 3.4 has as dependency 1.15, so why does the plugin require 1.16?
>
> tfm-rubygem-bastion-5.0.9-1.fm1_15.el7.noarch
> foreman-1.15.3-1.el7.noarch
> katello-3.4.4-2.el7.noarch
>
>





Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts 



Tel: 053 20 30 270  i...@netbulae.euStaalsteden 4-3A
KvK 08198180
Fax: 053 20 30 271  www.netbulae.eu 7547 TA Enschede
BTW NL821234584B01



-- 
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 ans ansible playbook

[mobios]

Hello,

did you set under Foreman settings/ansible the right user?
I had the same issue till i set the right username.

Regards
Mobios








Am Dienstag, 1. August 2017 10:58:13 UTC+2 schrieb Arsène Gschwind:

> Hi,
>
> I'm trying to use ansible with foreman but when tying to execute an 
> ansible playbook I get the following error:
>
> fatal: [darla-hesley.vm.sapify.ch]: UNREACHABLE! => {"changed": false, "msg": 
> "Failed to connect to the host via ssh: write: Broken pipe\r\n", 
> "unreachable": true}
>   to retry, use: --limit 
> @/tmp/foreman-playbook-9bc23404-2d9b-4c65-ad58-04a799263dc1.retry
>
> When running the playbook directly with ansible from the shell  it works 
> even when doing a sudo -u foreman-proxy.
>
> I'm not sure which user foreman is using to run playbooks, I've tried to 
> set the user in the foreman settings->ansible tab or even using the 
> parameter ansible_user on the host, neither did help.
> I'm running the following version:
> foreman : Version 1.15.2
> katello: 3.4.2
> foreman-tasks: 0.9.4
> ansible 2.3.1.0
>
> Thanks for any help
> rgds,
> Arsène
>

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

[foreman-users] Katello 3.4: bastion plugin requires Foreman >= 1.16 but current is 1.15.3

[Jorick Astrego]

Hi,

Upgraded to Katello 3.4, but I get the following error:

Foreman::PluginRequirementError: ERF72-1622
[Foreman::PluginRequirementError]: bastion plugin requires Foreman
 >= 1.16 but current is 1.15.3

Katello 3.4 has as dependency 1.15, so why does the plugin require 1.16?

 tfm-rubygem-bastion-5.0.9-1.fm1_15.el7.noarch
 foreman-1.15.3-1.el7.noarch
 katello-3.4.4-2.el7.noarch






Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts 



Tel: 053 20 30 270  i...@netbulae.euStaalsteden 4-3A
KvK 08198180
Fax: 053 20 30 271  www.netbulae.eu 7547 TA Enschede
BTW NL821234584B01



-- 
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] UPG from 2.4.4 to 3.x (also to 3.4.4 failing)

[Klaas Demter]

Hi,
not sure about the other things but the bastion dependency issue is known, it 
should be fixed soon https://github.com/theforeman/foreman-packaging/pull/1771

Greetings
Klaas Demter

ATIX - The Linux & Open Source Company
www.atix.de

- Ursprüngliche Mail -
Von: ehart...@gmail.com
An: "Foreman users" 
Gesendet: Mittwoch, 23. August 2017 09:59:09
Betreff: [foreman-users] UPG from 2.4.4 to 3.x (also to 3.4.4 failing)

Dear all,

I´m trying to upgrade my Katello from 2.4.4 to any version of 3.x but 
everytime I´m failing with different errors, its a real nightmare, below is 
what I get now for the latest version of 3.4.4:

[DEBUG 2017-08-23 00:44:07 main] katello-service start --only 
tomcat,tomcat6 finished successfully!
[ INFO 2017-08-23 00:44:07 main] Upgrade Step: fix_katello_settings_file...
[ INFO 2017-08-23 00:44:07 main] Upgrade Step: migrate_foreman...
*[ERROR 2017-08-23 00:44:27 main] foreman-rake -- config -k use_pulp_oauth 
-v true >/dev/null failed! Check the output for error!*
*[DEBUG 2017-08-23 00:44:41 main] API controllers newer than Apipie cache! 
Run apipie:cache rake task to regenerate cache.*
[DEBUG 2017-08-23 00:44:47 main] rake aborted!
*[DEBUG 2017-08-23 00:44:47 main] Foreman::PluginRequirementError: 
ERF72-1622 [Foreman::PluginRequirementError]: bastion plugin requires 
Foreman >= 1.16 but current is 1.15.3*
[DEBUG 2017-08-23 00:44:47 main] 
/usr/share/foreman/app/services/foreman/plugin.rb:143:in `requires_foreman'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/theforeman/tfm/root/usr/share/gems/gems/bastion-5.0.9/lib/bastion/engine.rb:48:in
 
`block (2 levels) in '
[DEBUG 2017-08-23 00:44:47 main] 
/usr/share/foreman/app/services/foreman/plugin.rb:66:in `instance_eval'
[DEBUG 2017-08-23 00:44:47 main] 
/usr/share/foreman/app/services/foreman/plugin.rb:66:in `register'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/theforeman/tfm/root/usr/share/gems/gems/bastion-5.0.9/lib/bastion/engine.rb:47:in
 
`block in '
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
 
`instance_exec'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
 
`run'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in
 
`block in run_initializers'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in
 
`run_initializers'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in
 
`initialize!'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
 
`public_send'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
 
`method_missing'
[DEBUG 2017-08-23 00:44:47 main] 
/usr/share/foreman/config/environment.rb:5:in `'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/polyglot-0.3.4/lib/polyglot.rb:65:in
 
`require'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
 
`block in require'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:240:in
 
`load_dependency'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
 
`require'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:328:in
 
`require_environment!'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:457:in
 
`block in run_tasks_blocks'
[DEBUG 2017-08-23 00:44:47 main] Tasks: TOP => db:migrate => environment
[DEBUG 2017-08-23 00:44:47 main] (See full trace by running task with 
--trace)
[ERROR 2017-08-23 00:44:47 main] foreman-rake db:migrate failed! Check the 
output for error!
[ERROR 2017-08-23 00:45:05 main] foreman-rake -- config -k use_pulp_oauth 
-v false >/dev/null failed! Check the output for error!
[ERROR 2017-08-23 00:45:05 main] Upgrade step migrate_foreman failed. Check 
logs for more information.
[DEBUG 2017-08-23 00:45:05 main] Exit with status code: 1 (signal was 1)
[ERROR 2017-08-23 00:45:05 main] Errors encountered during run:
[ERROR 2017-08-23 00:45:05 main] foreman-rake -- config -k use_pulp_oauth 
-v true >/dev/null failed! Check the output for error!
[ERROR 2017-08-23 00:45:05 main] foreman-rake db:migrate failed! Check the 
output for error!
[ERROR 2017-08-23 00:45:05 main] foreman-rake -- config -k use_pulp_oauth 
-v false >/dev/null failed! Check the output for error!
[ERROR 2017-08-23 

[foreman-users] UPG from 2.4.4 to 3.x (also to 3.4.4 failing)

[ehartchr]

Dear all,

I´m trying to upgrade my Katello from 2.4.4 to any version of 3.x but 
everytime I´m failing with different errors, its a real nightmare, below is 
what I get now for the latest version of 3.4.4:

[DEBUG 2017-08-23 00:44:07 main] katello-service start --only 
tomcat,tomcat6 finished successfully!
[ INFO 2017-08-23 00:44:07 main] Upgrade Step: fix_katello_settings_file...
[ INFO 2017-08-23 00:44:07 main] Upgrade Step: migrate_foreman...
*[ERROR 2017-08-23 00:44:27 main] foreman-rake -- config -k use_pulp_oauth 
-v true >/dev/null failed! Check the output for error!*
*[DEBUG 2017-08-23 00:44:41 main] API controllers newer than Apipie cache! 
Run apipie:cache rake task to regenerate cache.*
[DEBUG 2017-08-23 00:44:47 main] rake aborted!
*[DEBUG 2017-08-23 00:44:47 main] Foreman::PluginRequirementError: 
ERF72-1622 [Foreman::PluginRequirementError]: bastion plugin requires 
Foreman >= 1.16 but current is 1.15.3*
[DEBUG 2017-08-23 00:44:47 main] 
/usr/share/foreman/app/services/foreman/plugin.rb:143:in `requires_foreman'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/theforeman/tfm/root/usr/share/gems/gems/bastion-5.0.9/lib/bastion/engine.rb:48:in
 
`block (2 levels) in '
[DEBUG 2017-08-23 00:44:47 main] 
/usr/share/foreman/app/services/foreman/plugin.rb:66:in `instance_eval'
[DEBUG 2017-08-23 00:44:47 main] 
/usr/share/foreman/app/services/foreman/plugin.rb:66:in `register'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/theforeman/tfm/root/usr/share/gems/gems/bastion-5.0.9/lib/bastion/engine.rb:47:in
 
`block in '
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
 
`instance_exec'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
 
`run'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in
 
`block in run_initializers'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in
 
`run_initializers'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in
 
`initialize!'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
 
`public_send'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
 
`method_missing'
[DEBUG 2017-08-23 00:44:47 main] 
/usr/share/foreman/config/environment.rb:5:in `'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/polyglot-0.3.4/lib/polyglot.rb:65:in
 
`require'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
 
`block in require'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:240:in
 
`load_dependency'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
 
`require'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:328:in
 
`require_environment!'
[DEBUG 2017-08-23 00:44:47 main] 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:457:in
 
`block in run_tasks_blocks'
[DEBUG 2017-08-23 00:44:47 main] Tasks: TOP => db:migrate => environment
[DEBUG 2017-08-23 00:44:47 main] (See full trace by running task with 
--trace)
[ERROR 2017-08-23 00:44:47 main] foreman-rake db:migrate failed! Check the 
output for error!
[ERROR 2017-08-23 00:45:05 main] foreman-rake -- config -k use_pulp_oauth 
-v false >/dev/null failed! Check the output for error!
[ERROR 2017-08-23 00:45:05 main] Upgrade step migrate_foreman failed. Check 
logs for more information.
[DEBUG 2017-08-23 00:45:05 main] Exit with status code: 1 (signal was 1)
[ERROR 2017-08-23 00:45:05 main] Errors encountered during run:
[ERROR 2017-08-23 00:45:05 main] foreman-rake -- config -k use_pulp_oauth 
-v true >/dev/null failed! Check the output for error!
[ERROR 2017-08-23 00:45:05 main] foreman-rake db:migrate failed! Check the 
output for error!
[ERROR 2017-08-23 00:45:05 main] foreman-rake -- config -k use_pulp_oauth 
-v false >/dev/null failed! Check the output for error!
[ERROR 2017-08-23 00:45:05 main] Upgrade step migrate_foreman failed. Check 
logs for more information.


*I tried to upgrade Foreman with Nighly Version to get 1.16 but then I´m 
getting failed dependencies*

Error: Package: tfm-rubygem-runcible-1.12.0-1.el7.noarch (@katello)
   Requires: tfm-rubygem(rest-client) < 2.0.0
   Removing: tfm-rubygem-rest-client-1.8.0-1.el7.noarch (@foreman)
   tfm-rubygem(rest-client) = 1.8.0
   Updated By: