Actions
Bug #6836
closed
Relay configuration should be defined on https
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When a node is looking to its server/relay uuid it makes a request to https://server/uuid
This is working on rudder server root but on a relay it does not works:
- The apache configuration is not ok (only define access on http)
It must be fixed in two places:
- documentation is wrong about that (and should state to use the package instead of doing it manually)
- rudder-server-relay package should be fixed
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from New to In progress
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Matthieu CERDA
- Pull Request set to https://github.com/Normation/rudder-packages/pull/699
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-packages|3088cbcc1ef678ab0a235bbb2b1e93d6b1aa48f2.
Updated by Matthieu CERDA over 9 years ago
Applied in changeset rudder-packages|8fbc6a8ef30c40cd3626f394209bb3beda0ca564.
Updated by Vincent MEMBRÉ over 9 years ago
- Category changed from System integration to Server components
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.0 which was released today.
- Announcement 3.1
- Changelog 3.1
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Jonathan CLARKE over 9 years ago
- Related to Bug #7097: Error starting apache on SLES11 relay added
Actions