cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] ernjvr opened a new issue #2537: Fix configuration file copying bugs during Upgrade from 4.x to 4.11
Date Thu, 05 Apr 2018 15:00:25 GMT
ernjvr opened a new issue #2537: Fix configuration file copying bugs during Upgrade from 4.x
to 4.11
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   New line separated list of affected versions, commit ID for issues on master branch.
   Information about the configuration if relevant, e.g. basic network, advanced networking,
etc.  N/A otherwise
   Information about the environment if relevant, N/A otherwise
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   The packaging/centos7/cloud.spec file line 400 moves the %{_sysconfdir}/sysconfig/%{name}-management
file to %{_sysconfdir}/default/%{name}-management.This is unnecessary because  the file contains
the deprecated tomcat configurations. Moving it prevents the 4.11 upgrade from overwriting
the old file with the new jetty configurations file. Also systemctl daemon-reload command
needs to be added to the end of the %post management step in order to refresh daemon services
so that management server can start up seamlessly after the upgrade.
   For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots
if accurate.
   For new features, show how the feature would be used.
   To Reproduce: install version 4.6 of cloudstack. 
   Update Systemvm templates.
   Stop management server and usage server.
   Do database backup.
   Change the /etc/yum.repos.d/cloudstack.repo file to upgrade to 4.11.
   Do sudo yum upgrade cloudstack-management.
   After upgrade it fails to start the management server because:
   1) the less /etc/default/cloudstack-management file still contains the old tomcat configurations
and not the new 4.11 Jetty server configurations.
   2) the systemctl daemon-reload needs to be executed to relaod the daemon services
   <!-- Paste example playbooks or commands between quotes below -->
   systemctl stop cloudstack-management
   systemctl stop cloudstack-usage
   mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
   mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
   vi /etc/yum.repos.d/cloudstack.repo
   sudo yum upgrade cloudstack-management
   sudo yum upgrade cloudstack-usage
   systemctl start cloudstack-management
   systemctl start cloudstack-usage
   <!-- You can also paste links for larger files -->
   <!-- What did you expect to happen when running the steps above? -->
   after upgrade:
   less /etc/default/cloudstack-management should show the new jetty server environment variables
   management server should start up successfully without manually executing systemctl daemon-reload
   able to log in to the UI  
   <!-- What actually happened? -->
   management server failed to start and returned an error message "Job for cloudstack-management.service
failed because the control process exited with error code. ..."
   <!-- Paste verbatim command output between quotes below -->
   systemctl start cloudstack-management produced the above error output

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message