Elaad FURREEDAN
- Login: elaad.furreedan
- GitHub: ElaadF
- Registered on: 2019-03-29
- Last sign in: 2026-04-08
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 67 | 228 | 295 |
| Reported issues | 124 | 451 | 575 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Rudder | Developer | 2019-03-29 |
| Rudder plugins | Developer | 2019-04-03 |
| API authorizations | Developer, Release | 2019-04-03 |
| Authentication backends | Developer | 2019-04-03 |
| Branding | Developer | 2019-04-03 |
| Centreon | Developer | 2019-04-03 |
| Change validation | Developer, Release | 2019-04-03 |
| Consul | Developer | 2020-04-06 |
| Datasources | Developer | 2019-04-03 |
| GLPI | Developer | 2019-04-03 |
| Node external reports | Developer | 2019-04-03 |
| Notifications | Developer | 2019-04-03 |
| OpenSCAP | Developer | 2019-10-22 |
| Scale-out relay | Developer | 2019-04-03 |
| User management | Developer, Release | 2019-04-03 |
| Vault | Developer | 2019-04-03 |
| Zabbix | Developer | 2019-04-03 |
| Rudder tools | Developer | 2019-07-09 |
| Rudder websites | Developer | 2019-07-09 |
Activity
2026-04-01
-
15:27 Rudder Bug #28682 (Pending technical review): We should have consistant behaviour when creating group with empty criteria
- # When we create a group without criteria => he is empty --> OK
# refresh the page => still empty --> OK
# Click on save button => he is still empty --> OK
# refresh the page
# The group contains all nodes --> NOT OK
* There is a ... -
11:16 Rudder User story #28674 (New): Add hierarchy view on node list
- The list of nodes is totally flat. But it will be nice to see which nodes are under a relay without searching the ID of the relay.
2026-03-31
-
16:24 Rudder Bug #28651: Ignored node compliance are seens as no report
- !{width: 1716px}.clipboard-202603311623-7msn0.png!
!{width: 1685px}.clipboard-202603311624-oatgk.png!
-
16:19 Rudder Bug #28651 (Pending technical review): Ignored node compliance are seens as no report
- When a node status is changed to @Ignored@, after a run, the node is marked as grey node @No report@, resulting in a bad overall compliance, preventing to be 100% compliant.
Occurs at least on 9.0.4
!{width: 1025px}.clipboard-202603311...
2026-03-24
-
11:19 Rudder Bug #28588 (New): Missing Ubuntu 26.04 in supported OS
- According to https://github.com/Normation/rudder-tools/blob/master/release-data/rudder-9.1.cson we support Ubuntu 26.04, we should update the doc accordingly
2026-03-23
-
14:15 Change validation User story #28576 (New): Log when a user is validating or deploying his own change request
- This is a need from a user. He wants a log when someone validating and deploying his own change request.
Something like :
2026-03-04
-
11:51 Scale-out relay Enhancement #28475: Start of promoting and demoting should be info level log
- How to test it:
# install plugin scale-out-relay:
@rudder package install scale-out-relay@
# promote a node to a relay with his UUID:
@rudder server node-to-relay <node's UUID>@
# You should see 2 lines (start and end) in @/var/log/ru... -
11:42 Scale-out relay Enhancement #28475 (Pending technical review): Start of promoting and demoting should be info level log
- PR https://github.com/Normation/rudder-plugins/pull/925
-
11:42 Scale-out relay Enhancement #28475 (In progress): Start of promoting and demoting should be info level log
-
11:41 Scale-out relay Enhancement #28475: Start of promoting and demoting should be info level log
- To clarify (cannot edit the main description): We have error logs, when the promoting/demoting is started (debug level)