cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8745) After a volume is migrated; the usage table still shows the old volume id
Date Wed, 19 Aug 2015 04:53:45 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702446#comment-14702446
] 

ASF GitHub Bot commented on CLOUDSTACK-8745:
--------------------------------------------

Github user ksowmya commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/713#discussion_r37379847
  
    --- Diff: test/integration/component/maint/test_ha_pool_maintenance.py ---
    @@ -0,0 +1,229 @@
    +#!/usr/bin/env python
    +# Licensed to the Apache Software Foundation (ASF) under one
    +# or more contributor license agreements.  See the NOTICE file
    +# distributed with this work for additional information
    +# regarding copyright ownership.  The ASF licenses this file
    +# to you under the Apache License, Version 2.0 (the
    +# "License"); you may not use this file except in compliance
    +# with the License.  You may obtain a copy of the License at
    +#
    +#   http://www.apache.org/licenses/LICENSE-2.0
    +#
    +# Unless required by applicable law or agreed to in writing,
    +# software distributed under the License is distributed on an
    +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    +# KIND, either express or implied.  See the License for the
    +# specific language governing permissions and limitations
    +# under the License.
    +
    +from nose.plugins.attrib import attr
    +from marvin.cloudstackTestCase import cloudstackTestCase
    +from marvin.cloudstackAPI import (enableStorageMaintenance,
    +                                  cancelStorageMaintenance
    +                                  )
    +from marvin.lib.utils import (cleanup_resources,
    +                              validateList)
    +from marvin.lib.base import (Account,
    +                             VirtualMachine,
    +                             ServiceOffering,
    +                             Cluster,
    +                             StoragePool,
    +                             Volume)
    +from marvin.lib.common import (get_zone,
    +                               get_domain,
    +                               get_template,
    +                               list_hosts
    +                               )
    +from marvin.codes import PASS
    +
    +
    +def maintenance(self, storageid):
    +    """enables maintenance mode of a Storage pool"""
    +
    +    cmd = enableStorageMaintenance.enableStorageMaintenanceCmd()
    +    cmd.id = storageid
    +    return self.api_client.enableStorageMaintenance(cmd)
    +
    --- End diff --
    
    hmm... I thought something like this should work: StoragePool.enableMaintenance(self.api_client,
id=storageself.storageid[0][0]) since it is a classmethod
    I am just trying to confirm you're using the latest base.py since couple of these enhancements
went in recently into base.py...
    If it still doesn't fit in, it's ok. You can continue the way you've done


> After a volume is migrated; the usage table still shows the old volume id
> -------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8745
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8745
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: marvin, Usage
>    Affects Versions: 4.5.0
>            Reporter: prashant kumar mishra
>            Assignee: prashant kumar mishra
>
> After a volume is migrated; the usage table still shows the old volume id
> steps to verify:
> ==========
> 1-Created a HA VM with both root and data disk
> 2. Add one more primary storage to this cluster
> 3. Put the original /old Primary storage into maintenance which has the root and data
disk of VM created in step 1
> 4. Start the VM which was stopped as a part of step 3
> 5. Check for VOLUME.DELETE & VOLUME.CREATE events for root disk and data disk in
usage_event table



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message