Project

General

Profile

Bug #1498

unattended provisioning with foreman login enabled

Added by Peter Velas over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

When using unattended provisioning and foreman login enabled foreman always try to redirect to login page.
Thats the reason why new server cant be kickstarted if the login is enabled.

curl http://foreman/unattended/provision?spoof=192.168.1.14
<html><body>You are being <a href="http://foreman/users/login">redirected</a>.</body></html

It works if I disable login in settings.yaml ( ":login: false") . (both method curl the kickstart and install new server )

History

#1 Updated by Ohad Levy over 10 years ago

  • Status changed from New to Feedback
  • Assignee deleted (Ohad Levy)

normally, when a server request the kickstart (not using the spoof option) this should work.
your servers should not be using spoof, as using spoof avoiding activating some options (such as puppet certificate cleanup and generation).

#2 Updated by Peter Velas over 10 years ago

So I checked source codes and its now clear. Its just bad misinterpretation from my side.
But at least documentation should be more descriptive, because not everyone can consult foreman source...

You should close this ticket.
Thanks a lot for your time.

#3 Updated by Benjamin Papillon over 9 years ago

  • Status changed from Feedback to Closed
  • Target version set to Bug scrub

Closing the ticket as opener request.

What exactly do you want to see in the documentation?

Also available in: Atom PDF