⚲
Project
General
Profile
Sign in
Register
Home
Projects
Help
Search
:
Rudder
All Projects
Rudder
Overview
Activity
Roadmap
Issues
Repository
3.0.16
closed
2016-06-02
Maintenance release 16 of 3.0 branch
100%
41 issues
(
41 closed
— 0 open)
Issues by
Tracker
Status
Priority
Author
Assignee
Category
Bug
37/37
User story
4/4
Related issues
Bug #7042
: Directive detail don't show the OS compatibility version
Actions
Bug #7336
: Node stuck in "Applying" status
Actions
Bug #7348
: rudder-jetty initialisation should not support Java 6
Actions
Bug #7735
: OOM in Rudder when there are too many repaired reports
Actions
Bug #7825
: Add a left margin to the Rudder search box
Actions
Bug #7976
: rudder doc can be misleading on the repo to use for Centos/RHEL
Actions
Bug #8045
: Using Rudder server 3.x + rudder agent 2.11.x, a node doesn't properly detect its change of relay server
Actions
Bug #8051
: Compliance is not correctly computed if we receive run agent right after generation
Actions
Bug #8136
: Fix display issues on IE11
Actions
Bug #8147
: Message about cron on windows are confusing
Actions
Bug #8162
: Document usage of line replacement in Enforce a file content technique
Actions
Bug #8189
: It is not possible to define value with " in generic variable definition (branch 3.0 and more)
Actions
Bug #8192
: Better document Node Api: include detail always returns "default"
Actions
Bug #8195
: Correct memory profile and efficiency of non-compliant-reports logger
Actions
Bug #8201
: Priority field in Directive form does not show it has a tooltip and has wrong description
Actions
Bug #8203
: permissions technique tries to set a group even when we do not ask for it - 3.0 branch / technique versions 2.0 and 2.1
Actions
Bug #8212
: The start at boot does not work in the openssh technique on systemd OSes - 3.0 branch
Actions
Bug #8213
: Change audit message is not checked in the "Clone Directive" popup
Actions
Bug #8254
: Double reporting for group creation - 3.0 branch
Actions
Bug #8262
: Prevent red color usage in inventory graphs
Actions
Bug #8265
: Clear package caches when repairing a package repository for apt - branch 3.0
Actions
Bug #8298
: rudder doc can be misleading on the repo to use for Centos/RHEL fix typo
Actions
Bug #8303
: Broken xml output after #8233
Actions
Bug #8317
: "rudder agent enable -s" doesn't return an error code if it can't start the agent
Actions
Bug #8336
: Error on windows: agent tries to check if /usr/bin/env supports the -0 option
Actions
Bug #8344
: Missing relevant information about why the compliance is what it is on node
Actions
Bug #8346
: rudder agent update doesn't always update policy
Actions
Bug #8364
: Only invalidate cache for node with new completed runs
Actions
Bug #8370
: Makefile missing in rudder-server-relay package
Actions
Bug #8373
: Remove duplicate java version check from init script
Actions
Bug #8382
: In case of error in logrotate check, there is no report
Actions
Bug #8387
: check-techniques script doesn't properly exit non-zero on errors
Actions
Bug #8388
: rudder-jetty build fails when applying a removed patch
Actions
Bug #8395
: applications/aptPackageManagerSettings/3.1 missing from list of maintained techniques
Actions
Bug #8396
: "repaired" are counted as "required attention" on node compliance details
Actions
Bug #8399
: Misleading message on node compliance detail when run's configID is unknown
Actions
Bug #8400
: "All the last execution reports for this server are ok" displayed when no report received
Actions
User story #7889
: Move Relay doc to the install section
Actions
User story #8107
: Augment default number of lines displayed and add more options
Actions
User story #8204
: Adapt "Troubleshooting" section for 3.0
Actions
User story #8332
: Move man pages into the reference section
Actions
Loading...