Bug #5323
closed
The rudder-plugin script uses the wrong context XML anchor to define the plugins to use
Added by Matthieu CERDA over 10 years ago.
Updated about 10 years ago.
Description
We should change the "<Set name="extraClasspath">" instead of "<extraClassPath>", that is invalid, when adding or removing plugins, or we risk breaking the Jetty context.
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Nicolas CHARLES
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/450
- Status changed from Pending technical review to Pending release
Applied in changeset commit:10e9ff7c0e4a39ac5f9aa71af53aaec450b0bf4e.
Applied in changeset commit:71ff5462ffa3c285f80fbe051d8e11dbd2514af9.
- Subject changed from The rudder-plugin script uses the wrong context XML anchor to define extraClassPath to The rudder-plugin script uses the wrong context XML anchor to define the plugins to use
- Description updated (diff)
Note: This bug means that if any plugin were to be installed while this script is still wrong, we would create a malformed context file that will prevent the Rudder webapp to run and would require manual fixing by removing the "<extraClassPath>" line from /opt/rudder/share/webapps/rudder.xml.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.2, which was released today.
Check out:
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by 
Updated by