Bug #3802
closedThe migration script rudder-upgrade does not take into account the new apache configuration of rudder-default
Description
AS the apache configuration file rudder-default is not updated during a migration, the configuration to get the User Manual page is not present and the button on the WebUI redirect to 404 error. This is the same for the restriction for API added into rudder-default.
Updated by Nicolas PERRON over 11 years ago
- Subject changed from The User Manual page redirect to a 404 page after a migration to The new Apache configurations from the rudder-default file are not present after a migration
- Description updated (diff)
Updated by Nicolas PERRON over 11 years ago
A migration file shoule be done but this is not as simple as the property file rudder-web.properties.
- For the documentation, we only have to add it into the tag <VirtualHost></VirtualHost>
- For the API restriction we have to:
- Remove the old API restriction
- Add another one into between <VirtualHost></VirtualHost>
But I don't see how I can do that for the moment
Updated by Nicolas PERRON over 11 years ago
- Status changed from New to In progress
- % Done changed from 0 to 20
How to remove the lines about old API restriction:
sed -i "/^[ \t]*# NO access to the API unless you are localhost/,/^[ \t]*<\/Location>/d" rudder-default
Updated by Nicolas PERRON over 11 years ago
- % Done changed from 20 to 90
- Pull Request set to https://github.com/Normation/rudder-packages/pull/92
Pull Request URL added: https://github.com/Normation/rudder-packages/pull/92
Updated by Nicolas PERRON over 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- % Done changed from 90 to 100
Pull Request Updated ! Jon, could you review it please ?
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:eafcb3af4d82f6ce8ec4ebac6b5d6aea45095c04.
Updated by Nicolas PERRON over 11 years ago
- Subject changed from The new Apache configurations from the rudder-default file are not present after a migration to The migration script rudder-upgrade does not take into account the new apache configuration of rudder-default
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending release to Released
Updated by Nicolas PERRON over 11 years ago
This bug has been fixed in Rudder 2.7.0, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000043.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog27
- Download information: http://www.rudder-project.org/foswiki/Download/
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 34 to Rudder
- Category set to Packaging