Activity
From 05/27/2018 to 06/25/2018
06/25/2018
06/22/2018
- 07:26 AM Feature #9278: Copy required files for iPXE booting
- We added required templates into Foreman 1.11 and the document mentions this as "recent version". So everything is re...
06/20/2018
- 11:02 AM Feature #23477 (Ready For Testing): PuppetCA: Token Based Autosigning
- 08:55 AM Feature #24012 (Closed): Foreman-Proxy: Add settings for new PuppetCA providers
- As we are adding new providers to the PuppetCa SmartProxy module, we need to add its settings-file to the puppet modu...
06/19/2018
- 06:43 PM Bug #12646: Isolated Reverse proxy exposes all of Katello/Foreman
- If #17367 were fixed in the proposed way (only proxy /rhsm on 443), it would also solve this and I think #17367 has h...
06/16/2018
- 01:01 PM Bug #23905 (Closed): Default ansible_dir should be ~foreman-proxy
- Applied in changeset commit:puppet-foreman_proxy|4acf2d6a073e43c1501bf78f986fee6dea917c68.
06/13/2018
- 08:43 PM Bug #23919: installer breaks if TMPDIR and/or TMP is set.
- I suspect this is actually an issue in foreman-rake which is a bash script. I suspect that it exits with code 0 so th...
- 01:29 PM Bug #23919: installer breaks if TMPDIR and/or TMP is set.
- I'd also like to mention that the installer should have stopped when the db setup failed. It simply continued and mad...
- 01:17 PM Bug #23919 (New): installer breaks if TMPDIR and/or TMP is set.
- With help from tbrisker@irc.freenode.net I found out the installer fails if TMP and/or TMPDIR is set to a directory n...
06/12/2018
- 05:44 PM Bug #23905: Default ansible_dir should be ~foreman-proxy
- I think the suggested change is valid and already an improvement to current state. Even though config should not live...
- 02:06 PM Bug #23905: Default ansible_dir should be ~foreman-proxy
- It's configurable already, both in the installer or manually changing /etc/foreman-proxy/settings.d/ansible.yml. The ...
- 01:53 PM Bug #23905 (Ready For Testing): Default ansible_dir should be ~foreman-proxy
- 01:44 PM Bug #23905: Default ansible_dir should be ~foreman-proxy
- IMHO it should be configurable. Ideally we can change it to /etc/foreman-proxy/ansible in production for configs and ...
- 01:35 PM Bug #23905 (Closed): Default ansible_dir should be ~foreman-proxy
- Otherwise, ~foreman-proxy/.ansible.cfg settings are ignored when running Ansible jobs.
06/09/2018
- 02:00 PM Bug #23871 (Ready For Testing): dns checker returns empty string for fqdn resolting in wrong error message
- 01:56 PM Bug #23871 (Rejected): dns checker returns empty string for fqdn resolting in wrong error message
- I had an issue with a machine that the FQDN was not resolved by Ruby (but other programs did).
But instead of empty ...
06/07/2018
- 10:01 AM Bug #23844 (Closed): Disable SSL 64-bit Block Size Cipher Suites in Apache (SWEET32)
- Applied in changeset commit:e89c65e602243134aa533e82bc9c16134d5e44db.
- 07:43 AM Bug #23844 (Ready For Testing): Disable SSL 64-bit Block Size Cipher Suites in Apache (SWEET32)
- 07:37 AM Bug #23844 (Closed): Disable SSL 64-bit Block Size Cipher Suites in Apache (SWEET32)
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1586271
*Description of problem:*
Latest release at this...
06/06/2018
- 10:19 AM Bug #23754 (Feedback): Foreman 1.17 auto-installation fails with "Forward DNS 10.3.1.11 did not reverse resolve to any hostname."
- If that IP doesn't resolve correctly the check IMHO indeed did its job and the message is correct.
That check got ...
06/05/2018
- 01:45 PM Bug #16949 (Resolved): foreman proxy module generates invalid dhcpd.conf for non local networks
- 06:35 AM Bug #23754: Foreman 1.17 auto-installation fails with "Forward DNS 10.3.1.11 did not reverse resolve to any hostname."
- Moving to installer
06/04/2018
- 04:37 PM Bug #23754: Foreman 1.17 auto-installation fails with "Forward DNS 10.3.1.11 did not reverse resolve to any hostname."
- And adding server name and ip to /etc/hosts worked as a bypass.
06/01/2018
- 01:52 PM Bug #23754: Foreman 1.17 auto-installation fails with "Forward DNS 10.3.1.11 did not reverse resolve to any hostname."
- Noticed, when I tried to install version 1.17:
@
Forward DNS 10.3.1.11 did not reverse resolve to any hostname.
Yo...
05/31/2018
- 09:29 AM Bug #23753 (Rejected): DNS zone configuration files are not updated automatically
- Named has journal files it writes to. It's only flushed to disk on restart, rndc freeze. Note that no changes are all...
- 07:41 AM Bug #23753 (Rejected): DNS zone configuration files are not updated automatically
- Hi All,
Please be informed that, the DNS zone configuration files /var/named/dynamic/db.98.10.10.in-addr.arpa, and... - 07:53 AM Bug #23754 (Feedback): Foreman 1.17 auto-installation fails with "Forward DNS 10.3.1.11 did not reverse resolve to any hostname."
- Noticed, when I tried to install version 1.17:
@
Forward DNS 10.3.1.11 did not reverse resolve to any hostname.
Yo... - 07:42 AM Bug #23751: PXE configuration file is not created when selecting the Host Group
- Mostafa Yasin wrote:
> Foreman, DNS, DHCP, TFTP, Smart Proxy services are in the same server.
- 07:42 AM Bug #23751: PXE configuration file is not created when selecting the Host Group
- Foreman, DNS, DHCP, TFTP, services are in the same server.
- 07:35 AM Bug #23751 (New): PXE configuration file is not created when selecting the Host Group
- Hi All,
I have used "Provisioning Setup" wizard to create the provisioning configuration environment and I run
#...
05/30/2018
- 11:12 AM Bug #21664: Error during Foreman installation.
- I changed the Smart Proxy name to be the same as Smart Proxy URL. And this solved my issue. Thanks
05/29/2018
- 11:29 AM Refactor #23728 (Closed): Remove mark_qpid_cert_for_update from the installer upgrade hook
- mark_qpid_cert_for_update can probably be removed with https://github.com/theforeman/puppet-certs/pull/173
- 11:28 AM Refactor #23727 (Closed): Let puppet handle migrate_pulp
- migrate_pulp can be replaced by rm -f /var/lib/pulp/init.flag and then the installer will take care of it. Both start...
- 11:27 AM Refactor #23726 (Closed): Remove migrate_foreman from the upgrade hook
- I think migrate_foreman shouldn't be needed since theforeman/puppet-foreman@a32b663. There might be some weird stuff ...
Also available in: Atom