Actions
Bug #3774
closedThe output of rudder-upgrade script contains some disappointing messages during upgrade
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
The script rudder-upgrade show some messages which should not appear:
On debian 6:
[...] INFO: Launching script to check if a migration is needed INFO: Checking LDAP service status... OK INFO: Checking PostgreSQL service status... OK [master 8360a50] Upgrade system Techniques - automatically done by rudder-upgrade script Committer: root <root@vagrant-debian-squeeze-64.vagrantup.com> Your name and email address were configured automatically based on your username and hostname. Please check that they are accurate. You can suppress this message by setting them explicitly: git config --global user.name "Your Name" git config --global user.email you@example.com If the identity used for this commit is wrong, you can fix it with: git commit --amend --author='Your Name <you@example.com>' 8 files changed, 73 insertions(+), 18 deletions(-) create mode 100644 techniques/system/common/1.0/rudder_parameters.st INFO: A Technique library reload is needed and has been scheduled. INFO: Modifying system group entries in LDAP if necessary... Done INFO: Adding default Global Parameter containing the header put in file managed by Rudder...adding new entry "parameterName=rudder_file_edit_header,ou=Parameters,ou=Rudder,cn=rudder-configuration" Done. INFO: End of migration script [...]
On SLES 11:
[...] INFO: Launching script to check if a migration is needed INFO: Checking LDAP service status... OK INFO: Checking PostgreSQL service status... OK Created commit fe4a6e2: Upgrade system Techniques - automatically done by rudder-upgrade script 8 files changed, 73 insertions(+), 18 deletions(-) create mode 100644 techniques/system/common/1.0/rudder_parameters.st INFO: A Technique library reload is needed and has been scheduled. INFO: Modifying system group entries in LDAP if necessary... Done INFO: The Rudder OpenLDAP schema is not up to date, adding Global Parameter ou...adding new entry "ou=Parameters,ou=Rudder,cn=rudder-configuration" Done. INFO: Adding default Global Parameter containing the header put in file managed by Rudder...ldap_add: Invalid DN syntax (34) additional info: invalid DN adding new entry "parameterName=rudder_file_edit_header,ou=Parameters,ou=Rudder,cn=rudder-configuration" INFO: End of migration script [...]
Could we consider this as a bug since it will not lead to a "blocking state" ?
Actions