Arend Lapere
- Login: xabre
- Registered on: 04/11/2018
- Last sign in: 04/13/2021
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 1 | 14 | 15 |
Reported issues | 6 | 23 | 29 |
Projects
Project | Roles | Registered on |
---|---|---|
Foreman | Developer | 07/19/2018 |
Installer | Developer | 07/19/2018 |
Packaging | Developer | 07/19/2018 |
SELinux | Developer | 07/19/2018 |
Smart Proxy | Developer | 07/19/2018 |
Activity
08/24/2021
- 01:01 PM Foreman Remote Execution Bug #29384 (Closed): Connect By IP: IPv6 should be preferred over IPv4
- Applied in changeset commit:foreman_plugin|a49fa1980c15aeda2aa8a625fb537e059fa4be40.
- 12:52 PM Foreman Remote Execution Revision a49fa198 (foreman_plugin): Fixes #29384 - Connect by IP: Make IPv6 preference configurable
03/20/2020
- 08:55 AM Foreman Remote Execution Bug #29384 (Closed): Connect By IP: IPv6 should be preferred over IPv4
- Currently only ipv4 addresses are considerd when enableing "Connect By IP"; however, if we follow the OS level prefer...
01/23/2020
- 08:11 AM Foreman Bug #28843 (Duplicate): Audits page doesn't load the UI but the raw JSON output instead
- When on the host page, clicking on the "Audits" button in the top-left corner used to provide us with a clean page wh...
01/06/2020
10/30/2019
- 12:14 PM Foreman Feature #28147: Notify when a new version of foreman is available
- Marek Hulán wrote:
> Does the RSS check in notification drawer suffice? Whenever there's a blog post, people should ...
10/29/2019
- 09:57 PM Foreman Revision 7390618d (community-templates): Generic Windows Templates
- 04:27 PM Foreman Feature #28147 (New): Notify when a new version of foreman is available
- In the last poll it was clear that not everybody was using the latest greatest versions of foreman. For this reason, ...
09/13/2019
- 12:01 PM Foreman Bug #27153 (Closed): [API] Create Dual-NIC Host without IPv6 address results in duplicate IPv6 address
- 11:55 AM Foreman Bug #27153 (Resolved): [API] Create Dual-NIC Host without IPv6 address results in duplicate IPv6 address
- Good news; identified the issue... a classic PEBCAK.
The API was called using twice the same IPv6 address. No wonder...
Also available in: Atom