Project

General

Profile

Actions

Feature #10860

open

Provide resources on / API index

Added by Xudong Li over 8 years ago. Updated over 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Core
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Foreman Proxy is running at https://foreman.beijing.com:8443, However, when open that url in firefox, it display "Sinatra doesn’t know this ditty."

Actions #1

Updated by Lukas Zapletal over 8 years ago

  • Tracker changed from Bug to Support
  • Category changed from SSL to Packaging

Can you run foreman-debug tool on the proxy host and when ask, upload the report to our secured site? Then paste the filename here.

Actions #2

Updated by Eelco Maljaars over 8 years ago

Hi,

I'm experiencing the same error when running the foreman in a custom docker image. As this report did not contain any feedback I uploaded debug info from my container :

[root@foreman ~]# foreman-debug

HOSTNAME: foreman.localdomain
OS: redhat
RELEASE: CentOS release 6.6 (Final)
FOREMAN: 1.8.2
RUBY: ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux]
PUPPET: 3.8.1

A debug file has been created: /tmp/foreman-debug-aLaTV.tar.bz2 (14 bytes)

You may want to upload the tarball to our public server via rsync. There is a
write only directory (readable only by Foreman core developers) for that. Note
the rsync transmission is UNENCRYPTED:

rsync /tmp/foreman-debug-aLaTV.tar.bz2 rsync://theforeman.org/debug-incoming

Do you want to do this now? [y/N] y
Uploading...
The tarball has been uploaded, please contact us on mailing list or IRC.

Actions #3

Updated by Eelco Maljaars over 8 years ago

The first file appears to be empty. Here is the second run :

[root@foreman tmp]# foreman-debug

HOSTNAME: foreman.localdomain
OS: redhat
RELEASE: CentOS release 6.6 (Final)
FOREMAN: 1.8.2
RUBY: ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux]
PUPPET: 3.8.1

A debug file has been created: /tmp/foreman-debug-hrB6g.tar.bz2 (104153 bytes)

You may want to upload the tarball to our public server via rsync. There is a
write only directory (readable only by Foreman core developers) for that. Note
the rsync transmission is UNENCRYPTED:

rsync /tmp/foreman-debug-hrB6g.tar.bz2 rsync://theforeman.org/debug-incoming

Do you want to do this now? [y/N] y
Uploading...
The tarball has been uploaded, please contact us on mailing list or IRC.

Actions #4

Updated by Eelco Maljaars over 8 years ago

The first run probably failed because there was no tar binary in the container. The debug should probably fail on that.

Actions #5

Updated by Pieter Hollants over 8 years ago

The question I'm asking myself: what would have been the expected behavior? API does not list anything for the / resource.

Actions #6

Updated by Dominic Cleal over 8 years ago

  • Tracker changed from Support to Feature
  • Subject changed from Foreman Proxy display "Sinatra doesn’t know this ditty." to Provide resources on / API index
  • Category changed from Packaging to Core
  • translation missing: en.field_release deleted (62)

Pieter Hollants wrote:

The question I'm asking myself: what would have been the expected behavior? API does not list anything for the / resource.

Indeed, this is expected right now. It could match Foreman core and list available REST endpoints.

Actions

Also available in: Atom PDF