Activity
From 03/19/2017 to 04/17/2017
04/13/2017
-
07:46 AM Bug #19070: "Could not locate Gemfile (Bundler::GemfileNotFound)" starting standalone Foreman service
- That's unrelated to this bug, please "file a bug against Foreman":http://projects.theforeman.org/projects/foreman/iss...
-
07:33 AM Bug #19070: "Could not locate Gemfile (Bundler::GemfileNotFound)" starting standalone Foreman service
- Dominic Cleal wrote:
> Release is set for 1.14.4, see [[Foreman_114_Schedule]] for the approximate date.
>
> Dele... -
- Release is set for 1.14.4, see "Foreman_114_Schedule":http://projects.theforeman.org/projects/foreman/wiki/Foreman_11...
-
- Dominic Cleal wrote:
> Applied in changeset commit:foreman-packaging|8c9db2470c7203aee39535eba088be8c47736123.
Th... -
- Applied in changeset commit:foreman-packaging|8c9db2470c7203aee39535eba088be8c47736123.
-
-
- Sandro Emma wrote:
> Same error in foreman-1.15.0-0.1.RC1.el7.noarch on RHEL7.3
-
- Please don't modify the release field.
-
- Same error in foreman-1.15.0-0.1.RC1.el7.noarch on Centos7
-
07:01 AM Bug #19245 (Closed): Smart-proxy logrotates all files in /var/log/foreman-proxy
- Applied in changeset commit:foreman-packaging|2f4d4b82c0007712a4f966ca4ecb98ebde6d9f9b.
-
- Reopening since the DEB PR is not yet merged.
-
06:01 AM
Bug #19245 (Closed): Smart-proxy logrotates all files in /var/log/foreman-proxy
- Applied in changeset commit:foreman-packaging|1d5c8f1eac7bfeb2bde7448dd63ae2f580e5748e.
04/11/2017
-
-
- Smart-proxy logrotates files matching the /var/log/foreman-proxy/*.log glob. This may cause issues for processes logg...
04/10/2017
-
- Applied in changeset commit:foreman-packaging|5735daf2af2469a886fb66ed24662f7273b2b087.
04/07/2017
-
- Thanks for confirming.
-
04:28 AM Bug #19193: WARNING: The following packages cannot be authenticated!
- Yep I did some apt-get update before installing...
This is strange I tried to reproduce it from a docker container a... -
- Have you run @apt-get update@ since importing the key? The archive seems to be signed correctly as far as I can tell....
04/06/2017
-
- `
vagrant@vagrant-base-xenial-amd64:~$ apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/437D05B... -
-
- Can you show exactly which key you _did_ import? (@apt-key list@ output would be helpful too)
-
- Hi everyone,
I noticed that some of the foreman dependencies for ubuntu Xenial were not signed by the same key you...
04/03/2017
-
09:19 AM Bug #19132 (Closed): Provide puppet-agent-oauth for Puppet PC1 packages on Fedora
- When using the Puppetlabs-PC1 repos there is no puppet-agent-oauth package available.
https://github.com/theforema...
03/29/2017
-
10:06 AM Bug #19070 (Closed): "Could not locate Gemfile (Bundler::GemfileNotFound)" starting standalone Foreman service
- It seems that a package-based installation (following 3.3.1 in the installation docs) do not currently work in either...
-
09:38 AM Bug #19069 (Resolved): DNS and DHCP providers for libvirt fail to start
- Dominic Cleal wrote:
> @yum install rubygem-ruby-libvirt@ for the (optional) dependency. These providers are not int... -
- @yum install rubygem-ruby-libvirt@ for the (optional) dependency. These providers are not intended for use in product...
-
- After running:...
03/28/2017
-
04:01 AM
Bug #19041 (Closed): foreman-prepare-realm not packaged in DEBs
- Applied in changeset commit:foreman-packaging|141f5df616a3e7ce928bedb423309cc3b1d8790c.
03/27/2017
-
04:07 PM
Bug #19041 (Ready For Testing): foreman-prepare-realm not packaged in DEBs
-
03:38 PM Bug #19041 (Closed): foreman-prepare-realm not packaged in DEBs
- Hi all,
foreman-prepare-realm is not installed with the foreman-proxy package when installing on ubuntu 16.04, it ...
Also available in: Atom