Project

General

Profile

Actions

Bug #2693

closed

unattended installation without Puppet CA is failing

Added by Anonymous almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Unattended installations
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Unattended installations work very well in my environment... Today a collegue forgot to select the Puppet master and Puppet CA while provivisoning a new host.

While I could preview /unattended/provision?spoof=<ip> without problems, the client came across an internal server error:

Started GET "/unattended/provision?token=1771b184-6c0c-4789-8fc3-ee2b6f77495c" for 1.2.3.4 at Fri Jun 21 20:32:17 +0200 2013
Processing by UnattendedController#provision as HTML
  Parameters: {"token"=>"1771b184-6c0c-4789-8fc3-ee2b6f77495c"}
Found nasign.test.1234.de
  Rendered text template (0.0ms)
Filter chain halted as :handle_ca rendered or redirected
Completed 500 Internal Server Error in 8ms (Views: 0.5ms | ActiveRecord: 0.7ms)

Dominic said: "Sounds like an issue relating to when they were made optional"


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #3541: ec2 provisioning failure in setSSHProvision (when no CA available?)ClosedIvan Necas10/29/2013Actions
Actions

Also available in: Atom PDF