efansoftware opened a new issue #4680: URL: https://github.com/apache/cloudstack/issues/4680
<!-- Similar to but not exactly: https://github.com/apache/cloudstack/issues/4578 --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report May also: * Improvement Request * Documentation Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ UI - the official new UI as announced big feature ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.15.0.0 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> N/A ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> CentOS-7 in my trial ##### SUMMARY <!-- Explain the problem/feature briefly --> Built packages from 4.15.0.0 source successfully, then use the generated rpms to upgrade an working 4.13.1.0 environment. [cd packaging; ./package.sh -d centos7] But no new UI load. Legacy UI works with nice warning though. In the upgraded management server folder, I can see that old UI code is indeed put under "legacy" folder, left "index.html" and "error.html" two files only in the webapp. Similar to but not exactly: https://github.com/apache/cloudstack/issues/4578 ##### STEPS TO REPRODUCE <!-- 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. --> <!-- Paste example playbooks or commands between quotes below --> ~~~ [cd packaging; ./package.sh -d centos7] ~~~ <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ ~~~ ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
