Bug #2863
closed
bad base href after upgrade
Description
My upgrade is finish but my web interface is not really beautiful (as promise), if I check in the source page I can find this line :
<base href="http://localhost:8080/rudder/" />
I suppose is not good no ?
Files
| Screenshot.png (43.6 KB) Screenshot.png | |||
| Screenshot-2.png (130 KB) Screenshot-2.png |
Updated by Jonathan CLARKE over 12 years ago
- Status changed from New to Discussion
- Assignee set to Francois BAYART
- Priority changed from N/A to 1 (highest)
That URL is set by the "base.url" property in /opt/rudder/etc/rudder-web.properties. Can you check if this has the right value for your server name?
If it doesn't (which I can only assume is the case, given the error), did you maybe ask apt-get/aptitude to overwrite this config file during upgrade?
Updated by Francois BAYART over 12 years ago
- File Screenshot-2.png Screenshot-2.png added
Yes I say YES for each new file to be sure to have new format + option + comments in configuration file.
My base.url is empty now and was base.url=http://cmdb.xxx.xxx/rudder
I have change this but + jetty restart.
Now the page is little bit more beautiful but I have a strange message in bottom (see attachment) : "Success Your changes have been saved" with a close button which make nothing. And the loading icone (which is ugly but ok) stay always between menu and the Welcome Rudder message.
Updated by Matthieu CERDA over 12 years ago
Can you please empty your browser cache and refresh the page ?
Updated by Francois BAYART over 12 years ago
I just make a logout + login without empty cache and the page is good now.
I suppose this message appear just one time.
Updated by Matthieu CERDA over 12 years ago
- Consider this as a bug to be fixed ?
- Just add a note to the documentation to warn the user about this ?
- Do nothing ?
- The "D" answer.
Updated by Jonathan CLARKE over 12 years ago
- Status changed from Discussion to 2
- Assignee changed from Francois BAYART to Nicolas PERRON
I don't think that there is any code or packaging changes we can do to improve this. However, it is clear that the documentation is lacking, since François followed it and did not reach a satisfactory state after upgrading.
The documentation needs clarifying, at least to say:- During upgrade, don't accept replacing the /opt/rudder/etc/rudder-web.properties configuration file when apt-get / aptitude asks, as this will delete your settings, and the postinst script will update it automatically.
- After upgrade if the web interface has display problems, empty cache or logout/login etc
Nicolas, can you update the upgrade doc please?
Updated by Nicolas PERRON over 12 years ago
- Status changed from 2 to In progress
Jonathan CLARKE wrote:
I don't think that there is any code or packaging changes we can do to improve this. However, it is clear that the documentation is lacking, since François followed it and did not reach a satisfactory state after upgrading.
The documentation needs clarifying, at least to say:
- During upgrade, don't accept replacing the /opt/rudder/etc/rudder-web.properties configuration file when apt-get / aptitude asks, as this will delete your settings, and the postinst script will update it automatically.
- After upgrade if the web interface has display problems, empty cache or logout/login etc
Nicolas, can you update the upgrade doc please?
Ok, I'm on it.
Updated by Nicolas PERRON over 12 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Additionnel informations has been added.
Updated by Jonathan CLARKE over 12 years ago
- Status changed from Pending technical review to Released
Updated by Nicolas PERRON over 12 years ago
- Target version changed from 2.4.0~rc1 to 2.4.0~beta5