Foreman » Smart Proxy

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.

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.

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

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