cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9198) VR gets created in the disabled POD
Date Wed, 01 Mar 2017 07:50:45 GMT


ASF GitHub Bot commented on CLOUDSTACK-9198:

Github user anshul1886 commented on the issue:
    @abhinandanprateek, Yes they are using same deployment planner. But VR was getting created
in disabled Pod but not regular VM because for VR deployment system user context was getting
set. In planner checks are not done/skipped for system user. So if you observe here fix is
to use user from calling context instead of system user. Hope this clears your doubt.
    One such example:
    `if (!isRootAdmin(vmProfile)) {
                    List<Long> disabledPods = listDisabledPods(plan.getDataCenterId());
                    if (!disabledPods.isEmpty()) {
                        if (s_logger.isDebugEnabled()) {
                            s_logger.debug("Removing from the podId list these pods that are
disabled: " + disabledPods);

> VR gets created in the disabled POD
> -----------------------------------
>                 Key: CLOUDSTACK-9198
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
> VR gets created in the disabled POD

This message was sent by Atlassian JIRA

View raw message