Activity
From 08/12/2014 to 09/10/2014
09/10/2014
- 07:31 AM Feature #7398 (Duplicate): Add support for "providers" in smart-proxy plugins
- 07:26 AM Feature #7398 (Duplicate): Add support for "providers" in smart-proxy plugins
- 07:31 AM Feature #7008 (Assigned): Add providers to existing proxy modules from a plugin/module
09/09/2014
09/08/2014
- 08:20 AM Bug #7375 (Duplicate): Smart proxy return 400 when DNS entry not found
- 08:18 AM Bug #7375 (Duplicate): Smart proxy return 400 when DNS entry not found
- On Virsh, when the DNS is not found - smart proxy returns 400.
Expected 404.
09/05/2014
- 11:02 AM Bug #7351 (Closed): Plugins with missing http/https rackup file path crash smart-proxy
- Applied in changeset commit:b3402693323824dafb50838120073049d3d5a65e.
- 10:03 AM Revision b3402693: fixes #7351: plugins no longer crash smart-proxy if they are missing either of rackup paths
09/04/2014
- 07:16 AM Bug #7352 (Closed): Missing DNS record should return 404 not 400 for DELETE
- $ curl -X DELETE http://localhost:8443/dns/wheezy506.sapphire.elysium.emeraldreverie.org
DNS virsh provider error:... - 06:51 AM Bug #7351 (Ready For Testing): Plugins with missing http/https rackup file path crash smart-proxy
- 06:49 AM Bug #7351 (Closed): Plugins with missing http/https rackup file path crash smart-proxy
08/29/2014
- 06:33 AM Refactor #7298 (Closed): Remove Proxy::Virsh dependencies on dns and dhcp modules
- 06:18 AM Bug #7297 (Ready For Testing): Virsh error handlers throw "uninitialized constant Proxy::DNS" error
- 06:14 AM Bug #7297 (Closed): Virsh error handlers throw "uninitialized constant Proxy::DNS" error
- When a virsh update fails, the error handlers in lib/proxy/virsh.rb throw an uninitialized constant error themselves:...
- 05:03 AM Bug #7235 (Closed): Smart-proxy DHCP tests depend on a particular order of execution
- Applied in changeset commit:63f9e261e7c75be2042cbf0f74d04e591a72e22c.
- 04:51 AM Revision 63f9e261: fixes #7235: dhcp tests are now order-independent
08/27/2014
- 07:39 PM Bug #6916: MS DHCP Timeout
- Bump. The same issue.
It seems like the proxy readds all subnets upon addition of single server to Foreman, causin... - 07:27 PM Bug #6916: MS DHCP Timeout
- Oliver Weinmann wrote:
> Hi,
>
> just updated to Foreman 1.5.2 today as I already had issues with 1.5.1 deploying... - 12:01 PM Bug #7225 (Closed): Smart proxy does not correctly initialize logger
- Applied in changeset commit:915c16dd59e52b51456527ba93eeea380a619c28.
- 11:23 AM Revision 915c16dd: fixes #7225: logger is now being correctly initialized during launch
- 09:01 AM Bug #7274 (Closed): DHCP tests failing due to date mismatch
- Applied in changeset commit:ce9a075cd9c40353a91834ef765211b14495215f.
- 06:27 AM Bug #7274 (Ready For Testing): DHCP tests failing due to date mismatch
- 06:26 AM Bug #7274 (Assigned): DHCP tests failing due to date mismatch
- 06:09 AM Bug #7274 (Closed): DHCP tests failing due to date mismatch
- ...
- 07:01 AM Bug #7240 (Closed): When loading using bundler smart-proxy fails to load puppetca module if puppet module is disabled
- Applied in changeset commit:dae892ae9b3a7a3a7c925b661f6ee2475f595c0a.
- 05:34 AM Bug #7240: When loading using bundler smart-proxy fails to load puppetca module if puppet module is disabled
- To reproduce:
- ensure that puppet gem is not being loaded in :default bundler gem group
- enable puppetca module... - 06:26 AM Revision ce9a075c: fixes #7274 - generate date format expectation in tests to handle Ruby/JSON differences
- 05:58 AM Revision dae892ae: fixes #7240: puppetca now loads correctly if puppet module is disabled
- 03:04 AM Feature #7008: Add providers to existing proxy modules from a plugin/module
- Having a bit of a discussion about a PoC implementation I made: https://github.com/domcleal/smart-proxy/commit/d66f80...
08/22/2014
- 12:02 PM Bug #7240 (Ready For Testing): When loading using bundler smart-proxy fails to load puppetca module if puppet module is disabled
- 11:59 AM Bug #7240 (Closed): When loading using bundler smart-proxy fails to load puppetca module if puppet module is disabled
- 10:58 AM Bug #7225 (Ready For Testing): Smart proxy does not correctly initialize logger
- 08:15 AM Bug #7225 (Assigned): Smart proxy does not correctly initialize logger
- 05:07 AM Bug #7225 (Closed): Smart proxy does not correctly initialize logger
- During the boot (creating of pid dir, spawning daemons) proxy does make use of the logger class but it was not appare...
- 08:13 AM Bug #7235 (Ready For Testing): Smart-proxy DHCP tests depend on a particular order of execution
- 07:59 AM Bug #7235 (Closed): Smart-proxy DHCP tests depend on a particular order of execution
08/21/2014
- 09:21 AM Feature #7197 (Closed): Add man page for foreman-prepare-realm
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1132507
All scripts and binaries should have man pages. - 07:13 AM Feature #7181 (Ready For Testing): Add rubocop to smart-proxy code
- 07:08 AM Feature #7181 (Assigned): Add rubocop to smart-proxy code
- 07:00 AM Feature #7195: Deeper inspection of puppet classes to parse values from params.pp pattern
- We wanted to migrate smart proxy to use "kafo_parsers":https://github.com/theforeman/kafo_parsers gem which should gi...
- 06:47 AM Feature #7195: Deeper inspection of puppet classes to parse values from params.pp pattern
- Yea, I realize it's a bit difficult. It might not be really possible to do this well, but I can understand why a user...
- 06:41 AM Feature #7195: Deeper inspection of puppet classes to parse values from params.pp pattern
- This would only be possible at a very basic level, if the value was outside of any conditionals, didn't use a selecto...
- 06:39 AM Feature #7195 (Rejected): Deeper inspection of puppet classes to parse values from params.pp pattern
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1132421
Description of problem:
The 'params.pp' pattern i...
08/20/2014
- 11:27 AM Feature #7181 (Closed): Add rubocop to smart-proxy code
- 07:03 AM Feature #4332 (Resolved): Integrate Smart-Proxy with ABRT client and server
- This is being addressed via the https://github.com/theforeman/foreman_abrt and https://github.com/theforeman/smart_pr...
08/15/2014
- 11:01 AM Bug #7080 (Closed): Couldn't enable plugin puppet: undefined method `<=>' for :puppet_provider:Symbol
- Applied in changeset commit:7124635869b5eecea3f359e2f020aa6f6d9d1bba.
- 10:37 AM Revision 71246358: fixes #7080: symbols are no longer being sorted
- 07:56 AM Bug #7099 (Resolved): Import from Foreman-Proxy failed
- I'm glad to hear it!
- 07:55 AM Bug #7099: Import from Foreman-Proxy failed
- Thanks :-)
Import from Environment works again :-) - 06:50 AM Bug #7099: Import from Foreman-Proxy failed
- Check permissions on the file, and its parent directories. Also check that foreman-proxy is in the 'puppet' group (r...
- 06:45 AM Bug #7099: Import from Foreman-Proxy failed
- lease find also my auth.conf attached.
- 06:43 AM Bug #7099: Import from Foreman-Proxy failed
- After adding this parameter, a new error occurred (see Attachment)
In /var/log/foreman-proxy/foreman-proxy.log I f... - 06:33 AM Bug #7099: Import from Foreman-Proxy failed
- Looks fine, assuming the puppet.conf you pasted was from /etc/puppet/puppet.conf. I can't tell why it's not seeing e...
- 05:26 AM Bug #7099: Import from Foreman-Proxy failed
- Please find the "etc/foreman-proxy/settings.yml file attached:...
- 05:23 AM Bug #7099: Import from Foreman-Proxy failed
- Could you add your /etc/foreman-proxy/settings.yml file? Maybe it's not reading puppet.conf correctly at all.
- 05:21 AM Bug #7099: Import from Foreman-Proxy failed
- Thanks for your feedback.
I have still the same problem:... - 04:29 AM Bug #7099: Import from Foreman-Proxy failed
- Puzzling, it looks like the proxy isn't picking up the "modulepath" setting from puppet.conf (note, it's also missing...
- 04:04 AM Bug #7099 (Resolved): Import from Foreman-Proxy failed
- Import from Foreman-Proxy failed.
I have installed the following software packages on a Ubuntu 12.04 LTS 64bit:
...
08/14/2014
- 11:29 AM Bug #7090 (Rejected): Move the execution helpers in puppet proxy to Proxy::Util
- Puppet proxy provides a number of helpers related to command execution and shell escaping that should go to Proxy::Ut...
- 08:40 AM Bug #7060: puppet gem is required even when puppetca module is disabled
- I tested this only on RHEL7 which has Ruby 2.0...
- 06:59 AM Bug #7080: Couldn't enable plugin puppet: undefined method `<=>' for :puppet_provider:Symbol
- So we are safe in Satellite 6 snap5! Cool.
- 06:53 AM Bug #7080 (Ready For Testing): Couldn't enable plugin puppet: undefined method `<=>' for :puppet_provider:Symbol
- 04:35 AM Bug #7080 (Assigned): Couldn't enable plugin puppet: undefined method `<=>' for :puppet_provider:Symbol
- 04:23 AM Bug #7080: Couldn't enable plugin puppet: undefined method `<=>' for :puppet_provider:Symbol
- Lukas Zapletal wrote:
> So Foreman Proxy does not start in nightly? Damn.
On 1.8 platforms, correct. - 04:17 AM Bug #7080: Couldn't enable plugin puppet: undefined method `<=>' for :puppet_provider:Symbol
- So Foreman Proxy does not start in nightly? Damn.
- 03:41 AM Bug #7080 (Closed): Couldn't enable plugin puppet: undefined method `<=>' for :puppet_provider:Symbol
- Nightly tests are currently failing with the following error in /var/log/foreman-proxy/proxy.log:...
08/13/2014
- 05:33 PM Bug #7060: puppet gem is required even when puppetca module is disabled
- This seems to be breaking foreman-proxy on RHEL6 unless :puppet_provider: puppetrun is explicitly set in /etc/foreman...
- 12:01 PM Bug #7060 (Closed): puppet gem is required even when puppetca module is disabled
- Applied in changeset commit:ed3332ae5d731382a768c0329ae0ce9e990730e6.
- 06:34 AM Bug #7060 (Ready For Testing): puppet gem is required even when puppetca module is disabled
- 06:31 AM Bug #7060 (Closed): puppet gem is required even when puppetca module is disabled
- 12:01 PM Bug #7062 (Closed): Wrong requires in smart-proxy's 'facts' module
- Applied in changeset commit:4bfe725402cbe462ce2cd730132e91774010f596.
- 08:30 AM Bug #7062 (Ready For Testing): Wrong requires in smart-proxy's 'facts' module
- 08:26 AM Bug #7062 (Closed): Wrong requires in smart-proxy's 'facts' module
- 11:19 AM Revision ed3332ae: fixes #7060: puppet gem is no longer required if puppetca is disabled.
- 11:18 AM Revision 4bfe7254: fixes #7062: facts module uses correct path for 'requires'
Also available in: Atom