[
https://issues.apache.org/jira/browse/CLOUDSTACK-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577356#comment-13577356
]
Rohit Yadav commented on CLOUDSTACK-1249:
-----------------------------------------
I've to rant here, the packaging team should have greped, checked and renamed
in all places wherever they had renamed a script. This includes docs as well.
The rename from cloud -> cloudstack is welcome, but not at the cost of
regressions which could have been avoided, further it does not much time to
cherry-pick to 4.1 branch.
The packaging team would be in a better position to go over those commits,
backport them to 4.1 and fix the rename issues, please do that.
> CloudStack Service restart has inconsistent names
> -------------------------------------------------
>
> Key: CLOUDSTACK-1249
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1249
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: non oss build 15 rhea 6.3
> Reporter: Parth Jagirdar
> Priority: Minor
>
> Service stopped is Cloud-management and Service being started is Cloudstack
> Management.
>
> No adverse effect functionality is observed; So marking as Minor.
> ------------------------------------------------------------------------------------
> [root@localhost management]# service cloudstack-management restart
> Stopping cloud-management: [ OK ]
> Starting cloudstack-management: [ OK ]
> [root@localhost management]#
>
> -------------------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
