Project

General

Profile

Actions

Bug #35809

closed

smart_proxy_ansible needs smart_proxy_rex, but installer doesn't set it up automatically

Added by Evgeni Golov over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

if one tries to use --enable-foreman-proxy-plugin-ansible without --enable-foreman-proxy-plugin-remote-execution, installer fails with:

2022-11-30 15:35:52 [ERROR ] [configure] Error making POST request to Foreman at https://foreman.internal.pcfe.net/api/v2/smart_proxies: Response: 500 Internal Server Error: Check /var/log/foreman/production.log on foreman.internal.pcfe.net for detailed information
2022-11-30 15:35:52 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.internal.pcfe.net]/ensure: change from 'absent' to 'present' failed: Error making POST request to Foreman at https://foreman.internal.pcfe.net/api/v2/smart_proxies: Response: 500 Internal Server Error: Check /var/log/foreman/production.log on foreman.internal.pcfe.net for detailed information
2022-11-30 15:35:52 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.internal.pcfe.net]: Failed to call refresh: Error making GET request to Foreman at https://foreman.internal.pcfe.net/api/v2/smart_proxies: Response: 500 Internal Server Error: Check /var/log/foreman/production.log on foreman.internal.pcfe.net for detailed information
2022-11-30 15:35:52 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.internal.pcfe.net]: Error making GET request to Foreman at https://foreman.internal.pcfe.net/api/v2/smart_proxies: Response: 500 Internal Server Error: Check /var/log/foreman/production.log on foreman.internal.pcfe.net for detailed information
2022-11-30 15:35:56 [NOTICE] [configure] System configuration has finished.

because the SSH key is not deployed

Actions #1

Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/791 added
Actions #2

Updated by The Foreman Bot over 1 year ago

  • Fixed in Releases 3.6.0 added
Actions #3

Updated by Evgeni Golov over 1 year ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by Evgeni Golov over 1 year ago

  • Category deleted (Foreman modules)
  • Assignee deleted (Evgeni Golov)
  • Target version set to 3.5.0
  • Fixed in Releases deleted (3.6.0)
Actions #5

Updated by Evgeni Golov over 1 year ago

  • Category set to Foreman modules
  • Assignee set to Evgeni Golov
  • Fixed in Releases 3.6.0 added
Actions #6

Updated by Ewoud Kohl van Wijngaarden over 1 year ago

  • Triaged changed from No to Yes
  • Fixed in Releases 3.5.0 added
  • Fixed in Releases deleted (3.6.0)
Actions #7

Updated by WoodrowFaf WoodrowFaf about 1 year ago

  • Tracker changed from Bug to Support
  • Category changed from Foreman modules to foreman-installer script
  • Assignee changed from Evgeni Golov to Imri Zvik
  • Priority changed from Normal to Immediate
  • Difficulty deleted (easy)
  • Pull request deleted (https://github.com/theforeman/puppet-foreman_proxy/pull/791)
  • Found in Releases 1.10.0 added
Actions #8

Updated by WoodrowFaf WoodrowFaf about 1 year ago

  • Tracker changed from Support to Refactor
  • Category changed from foreman-installer script to Foreman modules
  • Assignee changed from Imri Zvik to Adam Ruzicka
  • Priority changed from Immediate to High
Actions #9

Updated by Ewoud Kohl van Wijngaarden about 1 year ago

  • Tracker changed from Refactor to Bug
  • Assignee changed from Adam Ruzicka to Evgeni Golov
  • Priority changed from High to Normal
  • Found in Releases deleted (1.10.0)
Actions

Also available in: Atom PDF