cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-236) Network Offering IDs are being exposed to the Regular User Account in the UpdateNetworkCmd Error message
Date Mon, 01 Jul 2013 22:15:20 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alena Prokharchyk resolved CLOUDSTACK-236.
------------------------------------------

    Resolution: Fixed

Fixed with 37f12a31a353855d5e7bde2b4abca3d17b6a463e
                
> Network Offering IDs are being exposed to the Regular User Account in the UpdateNetworkCmd
Error message
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-236
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-236
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: pre-4.0.0
>            Reporter: Chandan Purushothama
>            Assignee: Alena Prokharchyk
>             Fix For: 4.2.0
>
>         Attachments: UIBug57.PNG
>
>
> The Corresponding UI Screenshot of the Error Message has been attached to the bug report.
> ===============
> Steps to Reproduce:
> ===============
> 1. Create Advanced zone with all supported traffic types (Management, Guest, Public,
Storage)
> i) PhyNet1
>         - Mgmt,public,Guest (Traffic label = NIC0)
>         - Tags =  Tag1
> ii) PhyNet2
>         - Guest (Traffic label = NIC1)
>         - Tags = Tag2
> 2. Create at least 2 n/w offerings each using one of the above physical networks
> 3. Create a Regular Account. Log in as the regular account user.
> 4. Deploy Guest VM using one of the above network offerings. Update/change the guest
network to a different offering that uses different physical n/w.
> ==========
> Observations:
> ==========
> ==================
> UpdateNetworkCmd Job:
> ==================
> 2012-09-28 15:04:15,388 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-20:null)
submit async job-117, details: AsyncJobVO {id:117, userId: 3, accountId: 3, sessionKey: null,
instanceType: None, instanceId: null, cmd: com.cloud.api.commands.UpdateNetworkCmd, cmdOriginator:
null, cmdInfo: {"response":"json","changecidr":"false","id":"f3db526b-7a50-4696-941f-e016dd181496","sessionkey":"QrlDUGRAUpoIcM3AnFXDnRggcK4\u003d","ctxUserId":"3","networkofferingid":"277b7b7a-8aeb-46f8-94e9-e83de34912a8","name":"TestNetwork-guest2-atoms","displaytext":"TestNetwork-guest2-atoms","_":"1348870146901","ctxAccountId":"3","ctxStartEventId":"432"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, processStatus: 0, resultCode:
0, result: null, initMsid: 7471666038533, completeMsid: null, lastUpdated: null, lastPolled:
null, created: null}
> 2012-09-28 15:04:15,393 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-12:job-117)
Executing com.cloud.api.commands.UpdateNetworkCmd for job-117
> 2012-09-28 15:04:15,417 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-12:job-117)
Access to Ntwk[205|Guest|14] granted to Acct[3-atoms] by DomainChecker
> 2012-09-28 15:04:15,434 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-12:job-117)
Network offerings 13 and 14 have different tags, can't upgrade
> 2012-09-28 15:04:15,443 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-12:job-117)
Complete async job-117, jobStatus: 2, resultCode: 530, result: Error Code: 431 Error text:
Can't upgrade from network offering 14 to 13; check logs for more information
> ======
> Git Info:
> ======
> Git Revision: 30b19887fd05c7694f8fdf45be9fe9b02d90b1d1
> Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git

--
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

Mime
View raw message