[
https://issues.apache.org/jira/browse/CLOUDSTACK-8484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613156#comment-14613156
]
ASF GitHub Bot commented on CLOUDSTACK-8484:
--------------------------------------------
Github user sudhansu7 commented on the pull request:
https://github.com/apache/cloudstack/pull/335#issuecomment-118331438
@remibergsma @karuturi
I have added marvin test for this issue.
Test result from local setup:
Sudhansus-MAC:cloudstack sudhansu$ nosetests --with-marvin
--marvin-config=setup/dev/advanced.cfg
./test/integration/smoke/find_hosts_for_migration.py
==== Marvin Init Started ====
=== Marvin Parse Config Successful ===
=== Marvin Setting TestData Successful===
==== Log Folder Path: /tmp//MarvinLogs//Jul_03_2015_17_38_01_JVMT7H. All
logs will be available here ====
=== Marvin Init Logging Successful===
==== Marvin Init Successful ====
===final results are now copied to:
/tmp//MarvinLogs/find_hosts_for_migration_FKMWAR===
Sudhansus-MAC:cloudstack sudhansu$ cat
/tmp//MarvinLogs/find_hosts_for_migration_FKMWAR/results.txt
Test find suitable and not-suitable list of hosts for migration ... ===
TestName: test_01_find_hosts_for_migration | Status : SUCCESS ===
ok
----------------------------------------------------------------------
Ran 1 test in 27.003s
OK
Sudhansus-MAC:cloudstack sudhansu$ cat
/tmp//MarvinLogs/find_hosts_for_migration_FKMWAR/failed_plus_exceptions.txt
Sudhansus-MAC:cloudstack sudhansu$ cat
/tmp//MarvinLogs/find_hosts_for_migration_FKMWAR/runinfo.txt | grep -i
'Suitable Hosts'
2015-07-03 17:38:18,171 - DEBUG - Suitable Hosts: set([])
2015-07-03 17:38:18,171 - DEBUG - Not suitable Hosts:
set([{cpuwithoverprovisioning : u'32000.0', version : u'4.5.2-SNAPSHOT',
memorytotal : 8589934592, jobstatus : 0, zoneid :
u'7a83176c-4ae7-49cc-88ff-a794716e74f9', cpunumber : 4, managementserverid :
4278190080, cpuallocated : u'0%', memoryused : 0, id :
u'b1b25f17-18f7-4b4d-a8e1-a353ebf33660', cpuused : u'0%', suitableformigration
: False, clusterid : u'c138587b-c149-4819-9d30-d4fa9d6d5da4', capabilities :
u'hvm', state : u'Up', memoryallocated : 1879048192, networkkbswrite : 16384,
cpuspeed : 8000, type : u'Routing', events : u'Ping; StartAgentRebalance;
ShutdownRequested; ManagementServerDown; HostDown; AgentDisconnected;
PingTimeout; Remove; AgentConnected', zonename : u'Sandbox-simulator', podid :
u'b0b72cfb-db0a-4e9c-a9da-84854d8c4a1f', clustertype : u'CloudManaged', hahost
: False, lastpinged : u'1970-01-17T11:01:01+0530', ipaddress : u'172.16.15.21',
disconnected : u'2015-07-03T14:32:16+0530', name :
u'SimulatedAgent.3481871b-7626-450a-b2c1-ab4e6a2e5965', networkkbsread : 32768,
created : u'2015-07-03T13:39:27+0530', clustername : u'C0', hypervisor :
u'Simulator', islocalstorageactive : False, resourcestate : u'Enabled',
requiresStorageMotion : False, podname : u'POD0'}])
> Hosts without tag are not listed while listing the hosts for migration for
> instance with tag
> --------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8484
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8484
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.5.0
> Reporter: Sudhansu Sahu
> Assignee: Sudhansu Sahu
>
> Hosts without tag are not listed while listing the hosts for migration for
> instance with tag.
> Ideally system should list all available hosts with "not suitable" suffix.
> Steps to reproduce:
> 1) Create a compute offering with a host tag eg: 'tag-1'
> 2) Tag a host in your cluster as 'tag-1'
> 3) Deploy an instance using this offering.
> 4) Instance will get deployed to the tagged host
> 5) Try listing the hosts for migration,it would return no host is available
> for migration.
> 6) Tag other hosts with 'tag-1' and they would start appearing in the list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
