Bug #17468
Build PXE menu responds with success alert when no TFTP proxies exist
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assigned To: |  Amir Fefer | ||
| Category: | Templates | ||
| Target version: | - | ||
| Difficulty: | Bugzilla link: | ||
| Found in release: | Pull request: | https://github.com/theforeman/foreman/pull/4044 | |
| Story points | - | ||
| Velocity based estimate | - | ||
| Release | 1.14.0 | Release relationship | Auto |
Description
Steps to reproduce:
1. Disable smart proxy (Or just TFTP)
2. Go to Provision Template page
3. click the `Build PXE Default' button
4. UI render a success message
Associated revisions
Fixes #17468 - build PXE returns error with no TFTP proxies
Build PXE menu responds with no error when no TFTP
proxies are found, it renders an error message in the UI.
History
#1
Updated by Dominic Cleal over 1 year ago
Can you show logs? The UI shows a full concatenated list of error messages from different smart proxy failures and the logs should show:
2016-11-24T10:52:07 edd00426 [app] [W] Cannot deploy rendered template 'PXEGrub global default' to 'foreman.example.com'
[ stack trace ]The page should always render with a 200 response code, errors are shown via flashes.
#2
Updated by The Foreman Bot over 1 year ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4044 added
#3
Updated by Dominic Cleal over 1 year ago
- Subject changed from Build PXE menu responds with code 200 though the process has been failed to Build PXE menu responds with success alert when no TFTP proxies exist
- Release set to 1.14.0
#4
Updated by Amir Fefer over 1 year ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset af53af441c66565308afda382bda9c511cc3ce5b.