Activity
From 08/21/2017 to 09/19/2017
09/18/2017
- 07:35 PM Support #19261 (Closed): unexpected token JSON parse error when reading Puppet environment
- This appears to be an issue with one of the puppet classes, not puppet or smart-proxy themselves. I'm closing the iss...
- 07:23 PM Bug #19625 (Rejected): Smart proxy starts up successfully when module fails due to file permissions
- Closing the issue, described behaviour is by design.
- 06:58 PM Support #20372: dns_route53 not working.
- I don't see any dns-related calls to smart-proxy in the log. Did you associate the correct smart-proxy with the domai...
- 06:47 PM Bug #20977: With wrong IPMI password, calling /bmc/X.X.X.X/lan/ip endpoint causes smart-proxy to stuck in infinite loop
- The upstream change has been merged and will be available as soon as a new version of the gem is released. I don't th...
- 06:14 AM Bug #20977 (New): With wrong IPMI password, calling /bmc/X.X.X.X/lan/ip endpoint causes smart-proxy to stuck in infinite loop
- There is an upstream bug in @rubyipmi@ gem, which is causing this infinite loop, however all errors printed by this g...
09/13/2017
- 04:38 PM Bug #20474 (Ready For Testing): Multiple free IPs returned after record deletion
- 02:46 PM Support #20208: Failed puppet run: Dependency 'puppet_runner_impl' is undefined
- I suspect that mcollective-specific puppet agent is missing. Puppetlabs changed how agents are installed in Puppet ve...
- 02:13 PM Support #20208: Failed puppet run: Dependency 'puppet_runner_impl' is undefined
- Hello all.
Same problem here. Any help?
09/08/2017
- 11:51 AM Revision 9576bf84: Refs #20843 - Put public_suffix only in test
- public_suffix is only a dependency for webmock
- 12:56 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- Dmitri Dolguikh wrote:
> I released smart_proxy_dhcp_infoblox gem version 0.0.7, which includes all latest changes, ...
09/07/2017
- 05:58 PM Bug #20474 (Assigned): Multiple free IPs returned after record deletion
- 03:43 PM Bug #20823: Make -c (continue) wget flag optional when downloading kernel/initram
- I don't think we can safely remove "-c" option. Tftp orchestration (of which downloading kernel and initrd files is p...
- 01:58 PM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- I released smart_proxy_dhcp_infoblox gem version 0.0.7, which includes all latest changes, today. New RPM packages sh...
- 04:46 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- Klaas D wrote:
> there is one more bugfix after the 0.0.6 release: https://github.com/theforeman/smart_proxy_dhcp_in... - 04:43 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- Klaas D wrote:
> in general I'd say the 0.0.6 version of the infoblox proxy should work -- did you also update to th... - 04:41 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- Lukas Zapletal wrote:
> One more thing, can you increase foreman-proxy verbosity to DEBUG, restart it and perform on... - 04:22 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- there is one more bugfix after the 0.0.6 release: https://github.com/theforeman/smart_proxy_dhcp_infoblox/commit/80ab...
- 04:09 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- in general I'd say the 0.0.6 version of the infoblox proxy should work -- did you also update to the new infoblox 2.0...
- 04:05 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- One more thing, can you increase foreman-proxy verbosity to DEBUG, restart it and perform one another try. You can us...
- 04:04 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- Sorry I was informed that downgrade will not help, it's all broken in 1.15 series.
We don't test this provider tha... - 03:56 AM Support #20866 (New): Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- Thanks, there were no changes in smart-proxy in 1.15.3 release at all:
https://github.com/theforeman/smart-proxy/c... - 03:40 AM Support #20866: Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- Lukas Zapletal wrote:
> Hello,
>
> please provide foreman-debug -u and tell us what DHCP provider is in use?
... - 03:35 AM Support #20866 (Need more information): Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- Hello,
please provide foreman-debug -u and tell us what DHCP provider is in use? Shall I assume Infoblox as well? - 03:26 AM Support #20866 (Resolved): Unable to delete DHCP entry for 00:50:56:8f:c3:c5 ([RestClient::BadRequest]: 400 Bad Request)
- After update foreman und foreman-proxy to 1.15.3 we can't remove hosts.
in production.log (attached) you can find ...
09/06/2017
09/05/2017
- 06:03 PM Bug #20826 (Assigned): ISC DHCP new parser is unable to parse DUID
- 03:01 PM Refactor #20843 (Closed): Pin public_suffix on Ruby 2.0
- Applied in changeset commit:9607c50d128b69a6dea365d2fed260d6bdc35b04.
- 02:59 PM Revision 9607c50d: Fixes #20843 - Pin public_suffix on RUBY_VERSION 2.0
- 02:23 PM Refactor #19112 (Closed): Starting Foreman Proxy service on Windows as domain user
09/04/2017
- 01:42 PM Refactor #20843 (Ready For Testing): Pin public_suffix on Ruby 2.0
- 01:41 PM Refactor #20843 (Closed): Pin public_suffix on Ruby 2.0
- The newest version requires Ruby 2.1 so we need to pin.
09/01/2017
- 05:42 AM Bug #20474: Multiple free IPs returned after record deletion
- BZ set, customer facing.
- 05:42 AM Bug #20474: Multiple free IPs returned after record deletion
- Foreman core now contains randomized IPAM DB implementation, we need similar for Smart Proxy. Ideally this would be a...
- 05:01 AM Bug #20826 (Closed): ISC DHCP new parser is unable to parse DUID
- Hi there,
the new parser fails to parse this line on my system:
server-duid "\000\001\000\001!:}\221RT\000^... - 03:53 AM Bug #20823 (Rejected): Make -c (continue) wget flag optional when downloading kernel/initram
- Wget does not detect changed files correctly and -c option corrupts downloaded files. This is expected behavior and d...
08/31/2017
- 01:01 PM Bug #20700 (Closed): Hostgroup provisioning templating API does not work with spaces
- Applied in changeset commit:52e65523df4d1b091ee517abbce058bd9deb6373.
- 12:10 PM Revision 52e65523: Fixes #20700 - templates are passed with spaces in kind
08/29/2017
- 03:40 AM Feature #2595: Expose more existing rubyipmi features as BMC smart-proxy APIs
- Konstantin Orekhov wrote:
> Nick Liu wrote:
> > Applied in changeset commit:a9332b68542b3a4473cd1ce84c8740c093e21f3... - 01:20 AM Feature #2595: Expose more existing rubyipmi features as BMC smart-proxy APIs
- This added new API endpoints to Foreman proxy. Based on date, I think it is in 1.15. I don't see any change in Forema...
08/28/2017
- 08:13 PM Feature #2595: Expose more existing rubyipmi features as BMC smart-proxy APIs
- Nick Liu wrote:
> Applied in changeset commit:a9332b68542b3a4473cd1ce84c8740c093e21f3a.
Is this feature released?... - 06:18 AM Revision 03d1984b: Bump version to 1.17-develop
08/23/2017
- 07:05 AM Bug #20700: Hostgroup provisioning templating API does not work with spaces
- Requesting 1.15.
- 07:04 AM Bug #20700 (Ready For Testing): Hostgroup provisioning templating API does not work with spaces
- 07:01 AM Bug #20700 (Closed): Hostgroup provisioning templating API does not work with spaces
- When there are spaces, template proxy API does not proxy correctly:
curl -3 -H "Accept:application/json" -H "C...
Also available in: Atom