Project

General

Profile

Actions
Copy link

Bug #3802

closed

The migration script rudder-upgrade does not take into account the new apache configuration of rudder-default

Bug #3802: The migration script rudder-upgrade does not take into account the new apache configuration of rudder-default

Added by Nicolas PERRON over 12 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
2.7.0
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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 12 years ago Actions
Copy link
 #1

  • Target version set to 2.7.0

Updated by Nicolas PERRON over 12 years ago Actions
Copy link
 #2

  • 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 12 years ago Actions
Copy link
 #3

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 12 years ago Actions
Copy link
 #4

  • 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 12 years ago Actions
Copy link
 #5

  • % Done changed from 20 to 90
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/92

Updated by Nicolas PERRON over 12 years ago Actions
Copy link
 #6

  • 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 12 years ago Actions
Copy link
 #7

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:eafcb3af4d82f6ce8ec4ebac6b5d6aea45095c04.

Updated by Nicolas PERRON over 12 years ago Actions
Copy link
 #8

  • 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 12 years ago Actions
Copy link
 #9

  • Status changed from Pending release to Released

Updated by Nicolas PERRON over 12 years ago Actions
Copy link
 #10

This bug has been fixed in Rudder 2.7.0, which was released today.
Check out:

Updated by Benoît PECCATTE almost 11 years ago Actions
Copy link
 #11

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions
Copy link

Also available in: PDF Atom