Project

General

Profile

3.1.1

closed

2015-08-19

Maintenance release 1 for 3.1 version

100%

22 issues   (22 closed — 0 open)

Issues by
Bug

20/20
User story

1/1
Architecture

1/1
Related issues
Bug #6922: Curl SSL error on Ubuntu 10.04 Actions
Bug #7011: Do not sign inventory on windows Actions
Bug #7015: Some inventories have empty FQDN attribute, mandatory in 3.1 Actions
Bug #7019: Could not upload inventory when SELinux is enabled Actions
Bug #7020: Copy ncf only if it is updated Actions
Bug #7021: When SELinux is enabled, the ncf-api-venv home is owned by root Actions
Bug #7027: Fix compilation issue due to function removal in 6840 Actions
Bug #7041: Add httpd log context to /var/log/rudder/apache2 Actions
Bug #7051: rudder-webapp.fc is not copied in the builddir Actions
Bug #7053: With SELinux enabled, httpd cannot execute ncf scripts Actions
Bug #7059: In UI, directives in a rule are not sorted as their bundle order Actions
Bug #7063: Rudder specific information are not added anymore on the inventory when using FusionInventory < 2.3 Actions
Bug #7076: Broken SELinux packaging Actions
Bug #7083: Broken SELinux packaging in ncf-api-virtualenv Actions
Bug #7088: Unable to build ncf-api-virtualenv since rudderdir does not exists in spec Actions
Bug #7089: ncf-api-virtualenv package does not create its own 'share/selinux' directory Actions
Bug #7090: Wrong buidl directory when building selinux policy for ncf-api-virtualenv Actions
Bug #7095: Wrong permissions on /var/lib/ncf-api-venv/ Actions
Bug #7109: After an upgrade to 3.1.1-1, the nodes report error on "Could not retrieve the UUID of the policy server" Actions
Bug #7110: If I have a Rudder server in 3.1, but the relay in 3.0, all nodes behind the relay can't fetch the uuid of the relay Actions
User story #2881: Allow user to choose order of Directive application in a Rule Actions
Architecture #7043: Make Rudder code use BundleOrder where it's needed Actions

Also available in: TXT