[jira] [Commented] (CLOUDSTACK-5440) Missing GuestOS types for CentOS6.5, Windows 8.1 and Windows Server 2012 R2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887678#comment-13887678 ] Donal Lafferty commented on CLOUDSTACK-5440: Could you also add "Windows Server 2012 R2"? > Missing GuestOS types for CentOS6.5, Windows 8.1 and Windows Server 2012 R2 > --- > > Key: CLOUDSTACK-5440 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5440 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Donal Lafferty >Assignee: Alex Hitchins >Priority: Minor > > These operating systems were released in the last month or two, but they do > not appear as new os_guest types in > https://github.com/apache/cloudstack/blob/master/setup/db/db/schema-421to430.sql -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5440) Missing GuestOS types for CentOS6.5, Windows 8.1 and Windows Server 2012 R2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878745#comment-13878745 ] Donal Lafferty commented on CLOUDSTACK-5440: To fix the problem, you need to add new values to the GuestOS type enumeration. IIRC, the enumeration is a database table. To fix the problem, you need to add new rows to the table. You would do this in the setup *.sql file like the one linked to in the description. > Missing GuestOS types for CentOS6.5, Windows 8.1 and Windows Server 2012 R2 > --- > > Key: CLOUDSTACK-5440 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5440 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Donal Lafferty >Assignee: Alexander Hitchins >Priority: Minor > > These operating systems were released in the last month or two, but they do > not appear as new os_guest types in > https://github.com/apache/cloudstack/blob/master/setup/db/db/schema-421to430.sql -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-999) Plugin to provide Hyper-V 2012 support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty resolved CLOUDSTACK-999. --- Resolution: Fixed Hyper-V plugin is available in the code base. > Plugin to provide Hyper-V 2012 support > -- > > Key: CLOUDSTACK-999 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-999 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template, UI >Affects Versions: Future > Environment: Hyper-V 2012 is available on releases of Windows > operating system from 2012 onwards. E.g. Windows Server 2012, and Hyper-V > Server 2012. > The plugin will execute at least in part on the CloudStack management server. >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Labels: Hyper-V, newbie > Fix For: 4.3.0 > > Attachments: Jessica_UI_change_1.PNG, Jessica_UI_change_2.PNG, > jessica_UI_change_3.jpg, jessica_hyperv_edit_traffic_type_of_guest.PNG, > jessica_hyperv_edit_traffic_type_of_management.PNG, > jessica_hyperv_edit_traffic_type_of_public.PNG > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hyper-V+2012+%283.0%29+Support > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Original+Feature+Spec > https://cwiki.apache.org/confluence/display/CLOUDSTACK/BootArgs+Support+for+Hyper-V+with+KVP+Data+Exchange > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CIFS+Support > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Progress -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5463) Hyper-V does not report stopped VMs
Donal Lafferty created CLOUDSTACK-5463:
--
Summary: Hyper-V does not report stopped VMs
Key: CLOUDSTACK-5463
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5463
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.3.0
Reporter: Donal Lafferty
Priority: Blocker
The Hyper-V agent is never asked whether a VM is running. E.g. it is only
asked the VmStats:
2013-12-11 06:28:08,544 [32] INFO HypervResource.HypervResourceController
[7bbebc6a-400a-4d9f-832a-06924b823ba4] - com.cloud.agent.api.GetVmStatsCommand{
"vmNames": [
"i-2-3-VM"
],
"hostGuid": "700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource",
"hostName": "10.70.176.29",
"contextMap": {},
"wait": 0
}
2013-12-11 06:28:08,716 [32] DEBUG HypervResource.WmiCallsV2
[7bbebc6a-400a-4d9f-832a-06924b823ba4] - VM
20E0665F-4EE0-42A5-AC94-03DC9D3B5E8C(elementName i-2-3-VM) has 1 CPUs, and load
of 0
2013-12-11 06:28:08,717 [32] INFO HypervResource.HypervResourceController
[7bbebc6a-400a-4d9f-832a-06924b823ba4] - {
"com.cloud.agent.api.GetVmStatsAnswer": {
"vmStatsMap": {
"i-2-3-VM": {
"cpuUtilization": 0.0,
"networkReadKBs": 1.0,
"networkWriteKBs": 1.0,
"numCPUs": 1,
"entityType": "vm"
}
},
"result": true,
"contextMap": {}
}
}
Therefore, if the VM shut itself down, the management server thinks it is still
running.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5462) Hyper-V Agent confused by existing volume of different image type
Donal Lafferty created CLOUDSTACK-5462: -- Summary: Hyper-V Agent confused by existing volume of different image type Key: CLOUDSTACK-5462 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5462 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Reporter: Donal Lafferty VolumeObjectTO objects do not specify the image format. Hyper-V infers the format from files with the same name as that specified in the VolumeObjectTO.name field. This fails when a name is reused for a different image type. E.g. if the agent finds a ROOT2-1.vhd, it will assume that the VolumeObjectTO is a VHD. However, if the VolumeObjectTO is actually a VHDX, then the disk will appear to be corrupt to the hypervisor. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5462) Hyper-V Agent confused by existing volume of different image type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-5462: --- Affects Version/s: 4.3.0 > Hyper-V Agent confused by existing volume of different image type > - > > Key: CLOUDSTACK-5462 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5462 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.3.0 >Reporter: Donal Lafferty > Labels: hyper-v > > VolumeObjectTO objects do not specify the image format. > Hyper-V infers the format from files with the same name as that specified in > the VolumeObjectTO.name field. This fails when a name is reused for a > different image type. > E.g. if the agent finds a ROOT2-1.vhd, it will assume that the VolumeObjectTO > is a VHD. However, if the VolumeObjectTO is actually a VHDX, then the disk > will appear to be corrupt to the hypervisor. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5442) Virtual Router does not start properly on Hyper-V for DefaultSharedNetworkOffering network
Donal Lafferty created CLOUDSTACK-5442:
--
Summary: Virtual Router does not start properly on Hyper-V for
DefaultSharedNetworkOffering network
Key: CLOUDSTACK-5442
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5442
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Donal Lafferty
Priority: Blocker
Create DefaultSharedNetworkOffering using the following settings:
echo listNetworkOfferings name="DefaultSharedNetworkOffering"
apiresult=`cloudmonkey api listNetworkOfferings
name='"DefaultSharedNetworkOffering"' `
echo
echo listNetworkOfferings returned
echo $apiresult
echo
qcNetOffId=`echo $apiresult | sed -e 's/^.*"id": //; s/,.*$//'`
echo cluster is
echo $qcNetOffId
echo
# provides network but no ip ranges, those are populated on a pod by pod basis
echo createNetwork zoneid=$zone networkofferingid=$qcNetOffId
physicalnetworkid=$physnetid name="CorporateNet" displaytext="Limited Access"
apiresult=`cloudmonkey api createNetwork zoneid=$zone
networkofferingid=$qcNetOffId name="CorporateNet" displaytext="Limited Access" `
echo
echo createNetwork returned
echo $apiresult
echo
netId=`echo $apiresult | sed -e 's/^.*"id": //; s/,.*$//'`
echo network id is
echo $netId
echo
...
echo createVlanIpRange networkid=$netId podid=$pod gateway='"10.70.176.1"'
netmask='"255.255.240.0"' startip='"10.70.176.124"' endip='"10.70.176.144"'
forvirtualnetwork='"false"'
apiresult=`cloudmonkey api createVlanIpRange networkid=$netId podid=$pod
gateway='"10.70.176.1"' netmask='"255.255.240.0"' startip='"10.70.176.124"'
endip='"10.70.176.144"' forvirtualnetwork='"false"' `
echo
echo createVlanIpRange returned
echo $apiresult
echo
When virtual router starts, it returns an invalid IP address as shown in this
log entry:
2013-12-10 15:33:23,964 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-34:ctx-02a1939d) executeRequest received response
[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":4,"name":"r-4-VM","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"i686","os":"Debian
GNU/Linux 5.0 (32-bit)","bootArgs":" template\u003ddomP name\u003dr-4-VM
eth0ip\u003d10.70.176.127 eth0mask\u003d255.255.240.0 gateway\u003d10.70.176.1
domain\u003dcs1cloud.internal dhcprange\u003d10.70.176.1 eth1ip\u003d0.0.0.0
eth1mask\u003d0.0.0.0 type\u003ddhcpsrvr disable_rp_filter\u003dtrue
dns1\u003d4.4.4.4","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"2d49f38670916c19","params":{},"uuid":"fea15e5a-49ae-463c-a5b7-b30d2a9aae4f","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"9244f17c-e15e-4ffe-a0c5-af2c589ba84d","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource","id":1,"poolType":"Filesystem","host":"10.70.176.29","path":"E:\\CSHV3\\VHDXs\\","port":0,"url":"Filesystem://10.70.176.29/E:\\CSHV3\\VHDXs\\/?ROLE\u003dPrimary\u0026STOREUUID\u003d700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource"}},"name":"ROOT-4","size":2101252608,"volumeId":4,"vmName":"r-4-VM","accountId":1,"id":4,"deviceId":0,"hypervisorType":"Hyperv"}},"diskSeq":0,"type":"ROOT","_details":{"managed":"false","storagePort":"0","storageHost":"10.70.176.29","volumeSize":"2101252608"}}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"b099ba13-6f48-4e5c-8a2f-26db548766f3","ip":"10.70.176.127","netmask":"255.255.240.0","gateway":"10.70.176.1","mac":"06:3e:a2:00:00:0d","dns1":"4.4.4.4","broadcastType":"Native","type":"Guest","broadcastUri":"vlan://untagged","isolationUri":"ec2://untagged","isSecurityGroupEnabled":false},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"uuid":"817d22a5-3c0a-403b-a5da-16ffa441e2b4","ip":"0.0.0.0","netmask":"0.0.0.0","gateway":"0.0.0.0","mac":"02:00:20:bb:00:01","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false}]},"result":true,"contextMap":{},"wait":0}}]
2013-12-10 15:33:23,964 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-34:ctx-02a1939d) Ping command port, 0.0.0.0:3922
2013-12-10 15:33:23,964 INFO [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-34:ctx-02a1939d) Trying to connect to 0.0.0.0
2013-12-10 15:33:23,965 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-34:ctx-02a1939d) Ping command port succeeded for vm r-4-VM
2013-12-10 15:33:23,965 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-34:ctx-02a1939d) Execute network usage setup command on r-4-VM
2013-12-10 15:33:24,163 ERROR [c.c.h.h.r.HypervDirectConnectResource]
(DirectAgent-34:ctx-02a1939d) Unable to execute NetworkUsage command on DomR
(0.0.0.0), domR may not be ready yet. failure due to java.io.IOException: There
was a problem w
[jira] [Created] (CLOUDSTACK-5440) Missing GuestOS types for CentOS6.5, Windows 8.1 and Windows Server 2012 R2
Donal Lafferty created CLOUDSTACK-5440: -- Summary: Missing GuestOS types for CentOS6.5, Windows 8.1 and Windows Server 2012 R2 Key: CLOUDSTACK-5440 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5440 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Donal Lafferty Priority: Minor These operating systems were released in the last month or two, but they do not appear as new os_guest types in https://github.com/apache/cloudstack/blob/master/setup/db/db/schema-421to430.sql -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5439) CloudStack does not deal with existing Hyper-V System VMs
Donal Lafferty created CLOUDSTACK-5439:
--
Summary: CloudStack does not deal with existing Hyper-V System VMs
Key: CLOUDSTACK-5439
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5439
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Reporter: Donal Lafferty
I started a Hyper-V zone, which deployed a secondary storage VM to my Hyper-V
host.
Later, I stopped the management server, deleted the database, and restarted the
database server. I applied the same configuration script.
This time, the management server seemed to get stuck trying to connect to the
agent on the existing secondary storage. I saw the following message appear
multiple times in vmops.log:
2013-12-10 13:15:26,997 DEBUG [c.c.s.StatsCollector]
(StatsCollector-1:ctx-c483bea4) HostStatsCollector is running...
2013-12-10 13:15:26,999 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-a2557e88) VmStatsCollector is running...
2013-12-10 13:15:27,005 DEBUG [c.c.s.StatsCollector]
(StatsCollector-3:ctx-6520624e) StorageCollector is running...
2013-12-10 13:15:31,243 WARN [c.c.u.n.Link] (AgentManager-Selector:null) SSL:
Fail to find the generated keystore. Loading fail-safe one to continue.
2013-12-10 13:15:32,129 DEBUG [c.c.a.t.Request] (AgentManager-Handler-7:null)
Seq 0-0: Scheduling the first command { Cmd , MgmtId: -1, via: 0, Ver: v1,
Flags: 101,
[{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
}
2013-12-10 13:15:32,137 DEBUG [c.c.a.t.Request]
(AgentConnectTaskPool-2:ctx-10fb889d) Seq 0-0: Processing the first command {
Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 101,
[{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
}
2013-12-10 13:15:32,144 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentConnectTaskPool-2:ctx-10fb889d) Failed to handle host connection:
java.lang.IllegalArgumentException: Host 10.70.176.93 sent incorrect data
center: 1
2013-12-10 13:15:32,149 WARN [c.c.a.m.AgentManagerImpl]
(AgentConnectTaskPool-2:ctx-10fb889d) Unable to create attache for agent: Seq
0-0: { Cmd , MgmtId: -1, via: 0, Ver: v1, Flags: 101,
[{"com.cloud.agent.api.StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","id":0,"version":"4.3.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.70.176.132","publicNetmask":"255.255.240.0","publicMacAddress":"06:56:a4:00:00:12","privateIpAddress":"10.70.176.93","privateMacAddress":"06:de:9a:00:00:04","privateNetmask":"255.255.240.0","storageIpAddress":"10.70.176.93","storageNetmask":"255.255.240.0","storageMacAddress":"06:de:9a:00:00:04","resourceName":"NfsSecondaryStorageResource","wait":0}}]
}
2013-12-10 13:15:32,240 WARN [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-8:null) Throwing away a request because it came through
as the first command on a connect: Seq 0--1: { Cmd , MgmtId: -1, via: 0, Ver:
v1, Flags: 111,
[{"com.cloud.agent.api.ShutdownCommand":{"reason":"sig.kill","wait":0}}] }
2013-12-10 13:15:32,247 WARN [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-9:null) Throwing away a request because it came through
as the first command on a connect: Seq 0-1: { Cmd , MgmtId: -1, via: 0, Ver:
v1, Flags: 11,
[{"com.cloud.agent.api.PingStorageCommand":{"changes":{},"hostType":"Storage","hostId":0,"wait":0}}]
}
2013-12-10 13:15:33,190 INFO [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-10:null) Connection from /10.70.176.93 closed but no
cleanup was done.
2013-12-10 13:15:40,875 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-fe8996d6) Skip capacity scan due to there is no Primary
Storage UPintenance mode
2013-12-10 13:15:42,022 DEBUG [c.c.a.AlertMana
[jira] [Closed] (CLOUDSTACK-3281) StartCommand carries VolumeObjectTO with format field of NULL
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Lafferty closed CLOUDSTACK-3281.
--
Verified correct operation with integration test that involved creating a
Hyper-V zone.
> StartCommand carries VolumeObjectTO with format field of NULL
> -
>
> Key: CLOUDSTACK-3281
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3281
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
>Affects Versions: Future
> Environment: Hyper-V cluster
>Reporter: Donal Lafferty
>Assignee: Devdeep Singh
> Labels: hyper-V,
> Fix For: 4.3.0
>
>
> Disk image format is missing from VolumeObjectTO in StartCommand. Not clear
> whether Hypervisor needs to set this in the CopyCmdAnswer returned when the
> volume is created, if the hypervisor is never to use the format when looking
> up an image or if there is a bug in the system.
> Sample command:
> {
> "vm": {
> "id": 2,
> "name": "v-2-VM",
> "type": "ConsoleProxy",
> "cpus": 1,
> "minSpeed": 500,
> "maxSpeed": 500,
> "minRam": 1073741824,
> "maxRam": 1073741824,
> "arch": "i686",
> "os": "Debian GNU/Linux 5.0 (32-bit)",
> "bootArgs": " template=domP type=consoleproxy host=10.80.3.83 port=8250
> name=v-2-VM premium=true zone=1 pod=1 guid=Proxy.2 proxy_vm=2
> disable_rp_filter=true eth2ip=10.70.176.125 eth2mask=255.255.240.0
> gateway=10.70.176.1 eth0ip=169.254.1.121 eth0mask=255.255.0.0
> eth1ip=10.70.176.96 eth1mask=255.255.240.0 mgmtcidr=10.80.2.0/23
> localgw=10.70.176.1 internaldns1=10.70.176.118 internaldns2=10.70.160.66
> dns1=4.4.4.4",
> "rebootOnCrash": false,
> "enableHA": false,
> "limitCpuUse": false,
> "enableDynamicallyScaleVm": false,
> "vncPassword": "ce12c56d3290de94",
> "params": {},
> "uuid": "89384857-b45d-47c0-8c7e-b011b0fcb118",
> "disks": [
> {
> "data": {
> "org.apache.cloudstack.storage.to.VolumeObjectTO": {
> "uuid": "35a079e4-7767-47d1-8629-72d32c866a08",
> "volumeType": "ROOT",
> "dataStore": {
> "org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
> "uuid": "700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource",
> "id": 1,
> "poolType": "Filesystem",
> "host": "10.70.176.29",
> "path": "E:\\Disks\\",
> "port": 0
> }
> },
> "name": "ROOT-2",
> "size": 140616708,
> "volumeId": 2,
> "vmName": "v-2-VM",
> "accountId": 1,
> "id": 2
> }
> },
> "diskSeq": 0,
> "type": "ROOT"
> }
> ],
> "nics": [
> {
> "deviceId": 2,
> "networkRateMbps": -1,
> "defaultNic": true,
> "uuid": "022f8487-aba2-441b-85dd-3a68c3614fec",
> "ip": "10.70.176.125",
> "netmask": "255.255.240.0",
> "gateway": "10.70.176.1",
> "mac": "06:9d:26:00:00:0c",
> "dns1": "4.4.4.4",
> "broadcastType": "Vlan",
> "type": "Public",
> "broadcastUri": "vlan://untagged",
> "isolationUri": "vlan://untagged",
> "isSecurityGroupEnabled": false
> },
> {
> "deviceId": 0,
> "networkRateMbps": -1,
> "defaultNic": false,
> "uuid": "4fbb6713-de1e-4930-a944-6b5685c4ac62",
> "ip": "169.254.1.121",
> "netmask": "255.255.0.0",
> "gateway": "169.254.0.1",
> "mac": "0e:00:a9:fe:01:79",
> "broadcastType": "LinkLocal",
> "type": "Control",
> "isSecurityGroupEnabled": false
> },
> {
> "deviceId": 1,
> "networkRateMbps": -1,
> "defaultNic": false,
> "uuid": "2eeefa17-429e-47a5-bf41-bfa4742b712c",
> "ip": "10.70.176.96",
> "netmask": "255.255.240.0",
> "gateway": "10.70.176.1",
> "mac": "06:26:ae:00:00:07",
> "broadcastType": "Native",
> "type": "Management",
> "isSecurityGroupEnabled": false
> }
> ]
> },
> "hostIp": "10.70.176.29",
> "executeInSequence": false,
> "contextMap": {},
> "wait": 0
> }
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5420) Hyper-V host does not transition to maintenance mode
Donal Lafferty created CLOUDSTACK-5420:
--
Summary: Hyper-V host does not transition to maintenance mode
Key: CLOUDSTACK-5420
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5420
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Hypervisor Controller
Affects Versions: 4.3.0
Reporter: Donal Lafferty
I'm trying to remove a zone, because the networking API calls did not work
properly.
The first step to removing the Hyper-V cluster is to remove its hosts. This
requires they be put into maintenance mode. However, the transition to
maintenance mode never completes.
Can't see any exceptions in the vmops.log file, and the MaintainCommand on the
agent does not complain. E.g.
2013-12-09 05:00:54,200 [25] INFO HypervResource.HypervResourceController
[3fba50e8-fcc5-4e80-88b8-105521336c9e] - com.cloud.agent.api.MaintainCommand{
"contextMap": {},
"wait": 0
}
2013-12-09 05:00:54,201 [25] INFO HypervResource.HypervResourceController
[3fba50e8-fcc5-4e80-88b8-105521336c9e] - {
"com.cloud.agent.api.MaintainAnswer": {
"result": true,
"details": "success - NOP for MaintainCommand",
"_reconnect": false,
"contextMap": {}
}
}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5418) createtmplt.sh@207 complains about isCifs parameter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-5418: --- Assignee: (was: Rajesh Battala) > createtmplt.sh@207 complains about isCifs parameter > --- > > Key: CLOUDSTACK-5418 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5418 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.3.0 >Reporter: Donal Lafferty > > use createtmplt.sh to preseed the system VM template for Hyper-V. > When command runs, it complains about the isCifs parameter > E.g. > # Pre-seed the system VM template, because it is not enough to insert it into > the database > ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/cloud-install-sys-tmplt > -m /mnt/qc_secondary -u > http://10.70.176.4/pub/systemvmtemplate-hyper-v-20131205.vhd -h hyperv -F -o > localhost > ... runs, but generates following text: > File > ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/999d9e4b-27b8-472c-a2b2-220e719c39f0.vhd > does not appear to be compressed > ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh: > line 207: [: isCifs: integer expression expected -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5418) createtmplt.sh@207 complains about isCifs parameter
Donal Lafferty created CLOUDSTACK-5418: -- Summary: createtmplt.sh@207 complains about isCifs parameter Key: CLOUDSTACK-5418 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5418 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Donal Lafferty Assignee: Rajesh Battala use createtmplt.sh to preseed the system VM template for Hyper-V. When command runs, it complains about the isCifs parameter E.g. # Pre-seed the system VM template, because it is not enough to insert it into the database ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/qc_secondary -u http://10.70.176.4/pub/systemvmtemplate-hyper-v-20131205.vhd -h hyperv -F -o localhost ... runs, but generates following text: File ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/999d9e4b-27b8-472c-a2b2-220e719c39f0.vhd does not appear to be compressed ./client/target/generated-webapp/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh: line 207: [: isCifs: integer expression expected -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5415) SMB/cifs path should tell user to start with slash
Donal Lafferty created CLOUDSTACK-5415:
--
Summary: SMB/cifs path should tell user to start with slash
Key: CLOUDSTACK-5415
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5415
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Website
Reporter: Donal Lafferty
Assignee: Devdeep Singh
Priority: Minor
Using client to add secondary storage.
Use the SMB/cifs option.
This asks for server name and path; however, it should tell user that ath must
start with slash ('/').
Why? If you don't lead with '/', the command files with not feedback. You
have to inspect the log file, which is a pain.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Created] (CLOUDSTACK-5412) Zone Creation Wizard mislabels CIFS Server
Donal Lafferty created CLOUDSTACK-5412: -- Summary: Zone Creation Wizard mislabels CIFS Server Key: CLOUDSTACK-5412 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5412 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Website Affects Versions: 4.3.0 Reporter: Donal Lafferty Assignee: Devdeep Singh Priority: Minor Under secondary storage tab, if you select SMB/cifs, it asks you for the "NFS Server". This should say "SMB/cifs" server. Also, cifs should be capitalised, e.g. CIFS. See http://en.wikipedia.org/wiki/Server_Message_Block -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Assigned] (CLOUDSTACK-5339) VHDX file type not recognised by CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty reassigned CLOUDSTACK-5339: -- Assignee: Donal Lafferty > VHDX file type not recognised by CloudStack > --- > > Key: CLOUDSTACK-5339 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5339 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, Volumes >Affects Versions: 4.3.0, 4.4.0 >Reporter: Donal Lafferty >Assignee: Donal Lafferty >Priority: Blocker > Labels: hyper-V, > Original Estimate: 24h > Remaining Estimate: 24h > > Code that looks at the file extension of a template URL or volume does not > recognise vhd. E.g. > grep -R -A 2 -B 10 'Please specify a valid "' * --include=*.java > When checking the fix, add a test for vhdx.gz decompression in the Hyper-V > hypervisor. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5339) VHDX file type not recognised by CloudStack
Donal Lafferty created CLOUDSTACK-5339: -- Summary: VHDX file type not recognised by CloudStack Key: CLOUDSTACK-5339 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5339 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template, Volumes Affects Versions: 4.3.0, 4.4.0 Reporter: Donal Lafferty Priority: Blocker Code that looks at the file extension of a template URL or volume does not recognise vhd. E.g. grep -R -A 2 -B 10 'Please specify a valid "' * --include=*.java When checking the fix, add a test for vhdx.gz decompression in the Hyper-V hypervisor. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5339) VHDX file type not recognised by CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-5339: --- Assignee: Devdeep Singh (was: Donal Lafferty) > VHDX file type not recognised by CloudStack > --- > > Key: CLOUDSTACK-5339 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5339 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Template, Volumes >Affects Versions: 4.3.0, 4.4.0 >Reporter: Donal Lafferty >Assignee: Devdeep Singh >Priority: Blocker > Labels: hyper-V, > Original Estimate: 24h > Remaining Estimate: 24h > > Code that looks at the file extension of a template URL or volume does not > recognise vhd. E.g. > grep -R -A 2 -B 10 'Please specify a valid "' * --include=*.java > When checking the fix, add a test for vhdx.gz decompression in the Hyper-V > hypervisor. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5335) Review Request #15314 marked Ship, but not commited
Donal Lafferty created CLOUDSTACK-5335: -- Summary: Review Request #15314 marked Ship, but not commited Key: CLOUDSTACK-5335 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5335 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: Future Reporter: Donal Lafferty Assignee: Devdeep Singh Priority: Minor https://reviews.apache.org/r/15314/ marked 'Ship it!', but the code has not found its way into Master or 4.3 I checked the commit listed in the review, and it does not contain the files to be committed. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5004) Hyper-V VMs in wrong state after Mgmt Server Restart
Donal Lafferty created CLOUDSTACK-5004: -- Summary: Hyper-V VMs in wrong state after Mgmt Server Restart Key: CLOUDSTACK-5004 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5004 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.3.0 Reporter: Donal Lafferty Assignee: Donal Lafferty When mgmt server is restarted, the CloudStack kernel will synchronise VM states in its database with the values on the hypervisor. With Hyper-V hypervisors, this process fails. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-4839) Install Guide, section 3.5, provides wrong list of .deb packages
Donal Lafferty created CLOUDSTACK-4839: -- Summary: Install Guide, section 3.5, provides wrong list of .deb packages Key: CLOUDSTACK-4839 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4839 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Donal Lafferty See http://stackoverflow.com/questions/19240323/cloudstack-created-7-debian-package-instead-of-16-why -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4082) vhd-utils download used by developers is stale
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742034#comment-13742034 ] Donal Lafferty commented on CLOUDSTACK-4082: Sorry for the delay, 'watch' was not working as expected. The vhd-util affects XenAPI calls. XenAPI uses vhd-util during vdi_create, and it expects the -S to be available. On my 6.0.2, CloudStack replaced the orginal vhd-util, and made a /opt/xensource/bin/vhd-util a symlink. E.g. [root@camctxlabs-svr05 ~]# ls -al /opt/xensource/bin/vhd-util lrwxrwxrwx 1 root root 18 Nov 23 2012 /opt/xensource/bin/vhd-util -> /usr/sbin/vhd-util I was running with Master, but I don't know where the symlink came from. For this reason, I could not rule out problems with 4.2 SMlog attached. > vhd-utils download used by developers is stale > -- > > Key: CLOUDSTACK-4082 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4082 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: XenServer >Affects Versions: 4.1.1, 4.2.0 > Environment: XenServer 6.0.2 (and possibly later versions) >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Attachments: info_SMlog > > > vhd-utils is downloaded separately to the Apache CloudStack source code base. > See > https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingCloudStack > This version of vhd-utils lacks the '-S' option used by XenServer 6.0.2 (and > possibly above). As a consequence, it will not create VDIs -- 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
[jira] [Updated] (CLOUDSTACK-4082) vhd-utils download used by developers is stale
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-4082: --- Attachment: info_SMlog > vhd-utils download used by developers is stale > -- > > Key: CLOUDSTACK-4082 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4082 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: XenServer >Affects Versions: 4.1.1, 4.2.0 > Environment: XenServer 6.0.2 (and possibly later versions) >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Attachments: info_SMlog > > > vhd-utils is downloaded separately to the Apache CloudStack source code base. > See > https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingCloudStack > This version of vhd-utils lacks the '-S' option used by XenServer 6.0.2 (and > possibly above). As a consequence, it will not create VDIs -- 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
[jira] [Commented] (CLOUDSTACK-3893) Remove Hyperv option from Zone and Cluster configuration screen hypervisors dropdown list
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736453#comment-13736453 ] Donal Lafferty commented on CLOUDSTACK-3893: Remove HypervisorType.Hyperv from HypervisorList in server/src/com/cloud/configuration/Config.java (@205?) Explanation: http://markmail.org/message/suw6p2m72g77oytm Need to get a committer to make this tweak :( > Remove Hyperv option from Zone and Cluster configuration screen hypervisors > dropdown list > - > > Key: CLOUDSTACK-3893 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3893 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Management Server >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Priority: Critical > Fix For: 4.2.0 > > Attachments: hyper.png, hypervUI.png > > > Observations: > Hyperv is not supported in 4.2 release . But its listed as hyper visor while > Adding Zone and Cluster. > Expected behavior: > This should not be listed. -- 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
[jira] [Updated] (CLOUDSTACK-1031) Hypervisor Plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-1031: --- Fix Version/s: (was: 4.2.0) Future > Hypervisor Plugin > - > > Key: CLOUDSTACK-1031 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1031 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller > Environment: Windows O/S running Hyper-V 2012 >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Fix For: Future > > > Plugin responsible for receiving message from management server and > dispatching to agent that will use WMI and file system to implement the > hypervisor commands and backing storage. -- 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
[jira] [Updated] (CLOUDSTACK-1034) Merge to Master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-1034: --- Affects Version/s: (was: 4.2.0) Future > Merge to Master > --- > > Key: CLOUDSTACK-1034 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1034 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template, UI >Affects Versions: Future >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Fix For: 4.2.0 > > > Synchronise the development branch with master, and determine what source > needs to be merged. -- 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
[jira] [Commented] (CLOUDSTACK-999) Plugin to provide Hyper-V 2012 support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736437#comment-13736437 ] Donal Lafferty commented on CLOUDSTACK-999: --- Updated to 'Future' release > Plugin to provide Hyper-V 2012 support > -- > > Key: CLOUDSTACK-999 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-999 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template, UI >Affects Versions: Future > Environment: Hyper-V 2012 is available on releases of Windows > operating system from 2012 onwards. E.g. Windows Server 2012, and Hyper-V > Server 2012. > The plugin will execute at least in part on the CloudStack management server. >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Labels: Hyper-V, newbie > Fix For: 4.2.0 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hyper-V+2012+%283.0%29+Support -- 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
[jira] [Updated] (CLOUDSTACK-1032) Management Server updates for VHDX templates, and Hyper-V clusters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-1032: --- Affects Version/s: (was: 4.2.0) Future > Management Server updates for VHDX templates, and Hyper-V clusters > -- > > Key: CLOUDSTACK-1032 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1032 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Template, UI >Affects Versions: Future >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Fix For: 4.2.0 > > > UI exposed by management server must allow templates with the VHDX image type > used by Hyper-V 2012, and it must allow Hyper-V clusters to be configured. > SystemVMs are not available in this phase, so management server should be > stopped from attempting to create them on this kind of cluster. -- 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
[jira] [Updated] (CLOUDSTACK-1033) Deployment Guides
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-1033: --- Affects Version/s: (was: 4.2.0) Future > Deployment Guides > - > > Key: CLOUDSTACK-1033 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1033 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, Hypervisor Controller, Management Server >Affects Versions: Future >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Fix For: 4.2.0 > > > Provide description of how to deploy the plugin with a management server, and > how to get the remote agent running on the hypervisor. -- 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
[jira] [Updated] (CLOUDSTACK-999) Plugin to provide Hyper-V 2012 support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-999: -- Affects Version/s: (was: 4.2.0) Future > Plugin to provide Hyper-V 2012 support > -- > > Key: CLOUDSTACK-999 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-999 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template, UI >Affects Versions: Future > Environment: Hyper-V 2012 is available on releases of Windows > operating system from 2012 onwards. E.g. Windows Server 2012, and Hyper-V > Server 2012. > The plugin will execute at least in part on the CloudStack management server. >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Labels: Hyper-V, newbie > Fix For: 4.2.0 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hyper-V+2012+%283.0%29+Support -- 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
[jira] [Updated] (CLOUDSTACK-4082) vhd-utils download used by developers is stale
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-4082: --- Assignee: Prasanna Santhanam > vhd-utils download used by developers is stale > -- > > Key: CLOUDSTACK-4082 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4082 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: XenServer >Affects Versions: 4.1.1, 4.2.0 > Environment: XenServer 6.0.2 (and possibly later versions) >Reporter: Donal Lafferty >Assignee: Prasanna Santhanam > > vhd-utils is downloaded separately to the Apache CloudStack source code base. > See > https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingCloudStack > This version of vhd-utils lacks the '-S' option used by XenServer 6.0.2 (and > possibly above). As a consequence, it will not create VDIs -- 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
[jira] [Created] (CLOUDSTACK-4156) Changes to VLAN encoding break XenServer 6.0.2 support
Donal Lafferty created CLOUDSTACK-4156: -- Summary: Changes to VLAN encoding break XenServer 6.0.2 support Key: CLOUDSTACK-4156 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4156 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: Future Reporter: Donal Lafferty CloudStack used to encode the network BroadCast URI in with a '//', e.g. "broadcastUri":"vlan//:366" Now that the '//' is dropped, e.g. "broadcastUri":"vlan:366" As a result, the following code: com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetwork(CitrixResourceBase.java:1043): long vlan = Long.parseLong(broadcastUri.getHost()); Throws an exception: 2013-08-07 16:01:37,635 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-28:null) Catch Exception: class java.lang.NumberFormatException due to java.lang.NumberFormatException: null java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:404) at java.lang.Long.parseLong(Long.java:483) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetwork(CitrixResourceBase.java:1043) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVif(CitrixResourceBase.java:1094) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1633) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:561) -- 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
[jira] [Commented] (CLOUDSTACK-4156) Changes to VLAN encoding break XenServer 6.0.2 support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732190#comment-13732190 ] Donal Lafferty commented on CLOUDSTACK-4156: Could be that https://reviews.apache.org/r/12849/ will fix this problem. > Changes to VLAN encoding break XenServer 6.0.2 support > -- > > Key: CLOUDSTACK-4156 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4156 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: Future >Reporter: Donal Lafferty > > CloudStack used to encode the network BroadCast URI in with a '//', e.g. > "broadcastUri":"vlan//:366" > Now that the '//' is dropped, e.g. "broadcastUri":"vlan:366" > As a result, the following code: > com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetwork(CitrixResourceBase.java:1043): > long vlan = Long.parseLong(broadcastUri.getHost()); > Throws an exception: > 2013-08-07 16:01:37,635 WARN [c.c.h.x.r.CitrixResourceBase] > (DirectAgent-28:null) Catch Exception: class java.lang.NumberFormatException > due to java.lang.NumberFormatException: null > java.lang.NumberFormatException: null > at java.lang.Long.parseLong(Long.java:404) > at java.lang.Long.parseLong(Long.java:483) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetwork(CitrixResourceBase.java:1043) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVif(CitrixResourceBase.java:1094) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1633) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:561) -- 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
[jira] [Closed] (CLOUDSTACK-3650) CloudStack scripts fail when running on Jetty
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty closed CLOUDSTACK-3650. -- Resolution: Fixed Fix Version/s: Future Assignee: Donal Lafferty See review request https://reviews.apache.org/r/12747/ > CloudStack scripts fail when running on Jetty > - > > Key: CLOUDSTACK-3650 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3650 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Projects >Affects Versions: Future > Environment: XenServer deployment >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Labels: maven > Fix For: Future > > > 1. Run CloudStack in jetty using mvn :cloud-client-ui project. E.g. command > line: mvn -pl :cloud-client-ui jetty:run > 2. Deploy a XenServer zone > 3. Register a template > CloudStack fails: it is unable to start scripts, because they are not set to > executable. > Sample log file warning: > WARN [storage.resource.NfsSecondaryStorageResource] (consoleproxy-1:) > Exception: > /root/github/cshv3/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh > -s 2 -n 0061d74e-67e0-4504-8a2a-e795eb72c241.vhd -t > /mnt/secStorage/fa894f55-dd09-39b8-adf9-aa7e238aa29c/template/tmpl/1/1 -f > /mnt/secStorage/fa894f55-dd09-39b8-adf9-aa7e238aa29c/template/tmpl/1/1/acton-systemvm-02062012.vhd.bz2 > java.io.IOException: Cannot run program > "/root/github/cshv3/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh": > error=13, Permission denied > Confirmation script is missing executable permissions: > root@mgmtserver:~/github/cshv3# ls -al > /root/github/cshv3/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh > -rw-r--r-- 1 root root 4779 Jul 16 23:24 > /root/github/cshv3/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh > Similar to, but not the same as > https://issues.apache.org/jira/browse/CLOUDSTACK-1304, because there was a > fix already in place for that bug. -- 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
[jira] [Created] (CLOUDSTACK-4082) vhd-utils download used by developers is stale
Donal Lafferty created CLOUDSTACK-4082: -- Summary: vhd-utils download used by developers is stale Key: CLOUDSTACK-4082 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4082 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.1.1, 4.2.0 Environment: XenServer 6.0.2 (and possibly later versions) Reporter: Donal Lafferty vhd-utils is downloaded separately to the Apache CloudStack source code base. See https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingCloudStack This version of vhd-utils lacks the '-S' option used by XenServer 6.0.2 (and possibly above). As a consequence, it will not create VDIs -- 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
[jira] [Closed] (CLOUDSTACK-3919) Unknown column 'vm_instance.dynamically_scalable' in 'field list'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty closed CLOUDSTACK-3919. -- Resolution: Cannot Reproduce Pulled latest master, and the problem no longer exists. Not sure what changed. Could be recent updates to the list of components loaded in applicationContext.xml Alternatively, the issue was dealt with by a multi-push fix, and I got a bad intermediate state for the master branch. > Unknown column 'vm_instance.dynamically_scalable' in 'field list' > - > > Key: CLOUDSTACK-3919 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3919 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Environment: Running in jetty environment >Reporter: Donal Lafferty >Assignee: Nitin Mehta > > ERROR [AgentManagerImpl] (AgentTaskPool-1:ctx-d50085a9) Monitor > ClusteredVirtualMachineManagerImpl_EnhancerByCloudStack_c2fe87fe says there > is an error in the connect process for 1 due to DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@4ae33037: SELECT vm_instance.id, > vm_instance.name, vm_instance.vnc_password, vm_instance.proxy_id, > vm_instance.proxy_assign_time, vm_instance.state, > vm_instance.private_ip_address, vm_instance.instance_name, > vm_instance.vm_template_id, vm_instance.guest_os_id, vm_instance.host_id, > vm_instance.last_host_id, vm_instance.pod_id, > vm_instance.private_mac_address, vm_instance.data_center_id, > vm_instance.vm_type, vm_instance.ha_enabled, vm_instance.display_vm, > vm_instance.limit_cpu_use, vm_instance.update_count, vm_instance.created, > vm_instance.removed, vm_instance.update_time, vm_instance.domain_id, > vm_instance.account_id, vm_instance.service_offering_id, > vm_instance.reservation_id, vm_instance.hypervisor_type, > vm_instance.dynamically_scalable, vm_instance.uuid, > vm_instance.disk_offering_id FROM vm_instance INNER JOIN host ON > vm_instance.host_id=host.id WHERE vm_instance.removed IS NULL AND > (host.cluster_id = 1 ) > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@4ae33037: SELECT vm_instance.id, > vm_instance.name, vm_instance.vnc_password, vm_instance.proxy_id, > vm_instance.proxy_assign_time, vm_instance.state, > vm_instance.private_ip_address, vm_instance.instance_name, > vm_instance.vm_template_id, vm_instance.guest_os_id, vm_instance.host_id, > vm_instance.last_host_id, vm_instance.pod_id, > vm_instance.private_mac_address, vm_instance.data_center_id, > vm_instance.vm_type, vm_instance.ha_enabled, vm_instance.display_vm, > vm_instance.limit_cpu_use, vm_instance.update_count, vm_instance.created, > vm_instance.removed, vm_instance.update_time, vm_instance.domain_id, > vm_instance.account_id, vm_instance.service_offering_id, > vm_instance.reservation_id, vm_instance.hypervisor_type, > vm_instance.dynamically_scalable, vm_instance.uuid, > vm_instance.disk_offering_id FROM vm_instance INNER JOIN host ON > vm_instance.host_id=host.id WHERE vm_instance.removed IS NULL AND > (host.cluster_id = 1 ) > at > com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:415) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:350) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:905) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:882) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:895) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.vm.dao.VMInstanceDaoImpl.listByClusterId(VMInstanceDaoImpl.java:274) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.vm.VirtualMachineManagerImpl.fullSync(VirtualMachineManagerImpl.java:2100) > at > com.cloud.vm.VirtualMa
[jira] [Reopened] (CLOUDSTACK-3919) Unknown column 'vm_instance.dynamically_scalable' in 'field list'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty reopened CLOUDSTACK-3919: Assignee: Nitin Mehta (was: Alena Prokharchyk) Hi Nitin, Alena had a look at this issue yesterday. Unfortunately, the fix she mentioned has already been tried. I have provided verification in my most recent comment. I think you are in the best position to understand what is going on with the upgrade script. I looked at the repository, and you signed off on on the updates to the upgrade script. This puts you in a very good position to understand why the dynamically_scalable column is not being added to the table, but it is being referenced by VMInstanceDaoImpl.listByClusterId DL > Unknown column 'vm_instance.dynamically_scalable' in 'field list' > - > > Key: CLOUDSTACK-3919 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3919 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Environment: Running in jetty environment >Reporter: Donal Lafferty >Assignee: Nitin Mehta > > ERROR [AgentManagerImpl] (AgentTaskPool-1:ctx-d50085a9) Monitor > ClusteredVirtualMachineManagerImpl_EnhancerByCloudStack_c2fe87fe says there > is an error in the connect process for 1 due to DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@4ae33037: SELECT vm_instance.id, > vm_instance.name, vm_instance.vnc_password, vm_instance.proxy_id, > vm_instance.proxy_assign_time, vm_instance.state, > vm_instance.private_ip_address, vm_instance.instance_name, > vm_instance.vm_template_id, vm_instance.guest_os_id, vm_instance.host_id, > vm_instance.last_host_id, vm_instance.pod_id, > vm_instance.private_mac_address, vm_instance.data_center_id, > vm_instance.vm_type, vm_instance.ha_enabled, vm_instance.display_vm, > vm_instance.limit_cpu_use, vm_instance.update_count, vm_instance.created, > vm_instance.removed, vm_instance.update_time, vm_instance.domain_id, > vm_instance.account_id, vm_instance.service_offering_id, > vm_instance.reservation_id, vm_instance.hypervisor_type, > vm_instance.dynamically_scalable, vm_instance.uuid, > vm_instance.disk_offering_id FROM vm_instance INNER JOIN host ON > vm_instance.host_id=host.id WHERE vm_instance.removed IS NULL AND > (host.cluster_id = 1 ) > com.cloud.utils.exception.CloudRuntimeException: DB Exception on: > com.mysql.jdbc.JDBC4PreparedStatement@4ae33037: SELECT vm_instance.id, > vm_instance.name, vm_instance.vnc_password, vm_instance.proxy_id, > vm_instance.proxy_assign_time, vm_instance.state, > vm_instance.private_ip_address, vm_instance.instance_name, > vm_instance.vm_template_id, vm_instance.guest_os_id, vm_instance.host_id, > vm_instance.last_host_id, vm_instance.pod_id, > vm_instance.private_mac_address, vm_instance.data_center_id, > vm_instance.vm_type, vm_instance.ha_enabled, vm_instance.display_vm, > vm_instance.limit_cpu_use, vm_instance.update_count, vm_instance.created, > vm_instance.removed, vm_instance.update_time, vm_instance.domain_id, > vm_instance.account_id, vm_instance.service_offering_id, > vm_instance.reservation_id, vm_instance.hypervisor_type, > vm_instance.dynamically_scalable, vm_instance.uuid, > vm_instance.disk_offering_id FROM vm_instance INNER JOIN host ON > vm_instance.host_id=host.id WHERE vm_instance.removed IS NULL AND > (host.cluster_id = 1 ) > at > com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:415) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:350) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:905) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:882) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:895) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.vm.dao.VMInstanceDaoImpl.listByClusterId(VMInstanceDaoImpl.java:274) >
[jira] [Commented] (CLOUDSTACK-3919) Unknown column 'vm_instance.dynamically_scalable' in 'field list'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723597#comment-13723597 ] Donal Lafferty commented on CLOUDSTACK-3919: Okay, but I am using latest db upgrade script. E.g. root@mgmtserver:~/github/cshv3# grep -n -R "dynamically_scalable" * --include=*.sql client/target/utilities/scripts/db/db/schema-410to420.sql:45:ALTER TABLE `cloud`.`vm_template` ADD COLUMN `dynamically_scalable` tinyint(1) unsigned NOT NULL DEFAULT 0 COMMENT 'true if template contains XS/VMWare tools inorder to support dynamic scaling of VM cpu/memory'; client/target/utilities/scripts/db/db/schema-410to420.sql:46:ALTER TABLE `cloud`.`vm_instance` ADD COLUMN `dynamically_scalable` tinyint(1) unsigned NOT NULL DEFAULT 0 COMMENT 'true if VM contains XS/VMWare tools inorder to support dynamic scaling of VM cpu/memory'; client/target/utilities/scripts/db/db/schema-410to420.sql:47:UPDATE `cloud`.`vm_template` SET dynamically_scalable = 1 WHERE name = "CentOS 5.6(64-bit) no GUI (XenServer)" AND type = "BUILTIN"; client/target/utilities/scripts/db/db/schema-410to420.sql:48:UPDATE `cloud`.`vm_template` SET dynamically_scalable = 1 WHERE name = "SystemVM Template (vSphere)" AND type = "SYSTEM"; client/target/utilities/scripts/db/db/schema-410to420.sql:1625: vm_instance.dynamically_scalable dynamically_scalable client/target/utilities/scripts/db/db/schema-410to420.sql:1824: vm_template.dynamically_scalable, developer/target/db/db/schema-410to420.sql:45:ALTER TABLE `cloud`.`vm_template` ADD COLUMN `dynamically_scalable` tinyint(1) unsigned NOT NULL DEFAULT 0 COMMENT 'true if template contains XS/VMWare tools inorder to support dynamic scaling of VM cpu/memory'; developer/target/db/db/schema-410to420.sql:46:ALTER TABLE `cloud`.`vm_instance` ADD COLUMN `dynamically_scalable` tinyint(1) unsigned NOT NULL DEFAULT 0 COMMENT 'true if VM contains XS/VMWare tools inorder to support dynamic scaling of VM cpu/memory'; developer/target/db/db/schema-410to420.sql:47:UPDATE `cloud`.`vm_template` SET dynamically_scalable = 1 WHERE name = "CentOS 5.6(64-bit) no GUI (XenServer)" AND type = "BUILTIN"; developer/target/db/db/schema-410to420.sql:48:UPDATE `cloud`.`vm_template` SET dynamically_scalable = 1 WHERE name = "SystemVM Template (vSphere)" AND type = "SYSTEM"; developer/target/db/db/schema-410to420.sql:1625: vm_instance.dynamically_scalable dynamically_scalable developer/target/db/db/schema-410to420.sql:1824: vm_template.dynamically_scalable, setup/db/db/schema-410to420.sql:45:ALTER TABLE `cloud`.`vm_template` ADD COLUMN `dynamically_scalable` tinyint(1) unsigned NOT NULL DEFAULT 0 COMMENT 'true if template contains XS/VMWare tools inorder to support dynamic scaling of VM cpu/memory'; setup/db/db/schema-410to420.sql:46:ALTER TABLE `cloud`.`vm_instance` ADD COLUMN `dynamically_scalable` tinyint(1) unsigned NOT NULL DEFAULT 0 COMMENT 'true if VM contains XS/VMWare tools inorder to support dynamic scaling of VM cpu/memory'; setup/db/db/schema-410to420.sql:47:UPDATE `cloud`.`vm_template` SET dynamically_scalable = 1 WHERE name = "CentOS 5.6(64-bit) no GUI (XenServer)" AND type = "BUILTIN"; setup/db/db/schema-410to420.sql:48:UPDATE `cloud`.`vm_template` SET dynamically_scalable = 1 WHERE name = "SystemVM Template (vSphere)" AND type = "SYSTEM"; setup/db/db/schema-410to420.sql:1625:vm_instance.dynamically_scalable dynamically_scalable setup/db/db/schema-410to420.sql:1824:vm_template.dynamically_scalable, This script is not adding the column properly. E.g. root@mgmtserver:~/github/cshv3# mysql --user=root --password="" cloud -e "show columns from vm_instance;" +-+-+--+-+-+---+ | Field | Type| Null | Key | Default | Extra | +-+-+--+-+-+---+ | id | bigint(20) unsigned | NO | PRI | NULL| | | name| varchar(255)| NO | | NULL| | | uuid| varchar(40) | YES | UNI | NULL| | | instance_name | varchar(255)| NO | | NULL| | | state | varchar(32) | NO | MUL | NULL| | | vm_template_id | bigint(20) unsigned | YES | MUL | NULL| | | guest_os_id | bigint(20) unsigned | NO | | NULL| | | private_mac_address | varchar(17) | YES | | NULL| | | private_ip_address | char(40)| YES | | NULL| | | pod_id | bigint(20) unsigned | YES | MUL | NULL| | | data_center_id | bigint(20) unsigned | NO | MUL | NULL| | | host_id | bigint(20) unsigned | YES | MUL | NULL| | | last_host_id| bigint(20
[jira] [Created] (CLOUDSTACK-3919) Unknown column 'vm_instance.dynamically_scalable' in 'field list'
Donal Lafferty created CLOUDSTACK-3919: -- Summary: Unknown column 'vm_instance.dynamically_scalable' in 'field list' Key: CLOUDSTACK-3919 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3919 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Environment: Running in jetty environment Reporter: Donal Lafferty ERROR [AgentManagerImpl] (AgentTaskPool-1:ctx-d50085a9) Monitor ClusteredVirtualMachineManagerImpl_EnhancerByCloudStack_c2fe87fe says there is an error in the connect process for 1 due to DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@4ae33037: SELECT vm_instance.id, vm_instance.name, vm_instance.vnc_password, vm_instance.proxy_id, vm_instance.proxy_assign_time, vm_instance.state, vm_instance.private_ip_address, vm_instance.instance_name, vm_instance.vm_template_id, vm_instance.guest_os_id, vm_instance.host_id, vm_instance.last_host_id, vm_instance.pod_id, vm_instance.private_mac_address, vm_instance.data_center_id, vm_instance.vm_type, vm_instance.ha_enabled, vm_instance.display_vm, vm_instance.limit_cpu_use, vm_instance.update_count, vm_instance.created, vm_instance.removed, vm_instance.update_time, vm_instance.domain_id, vm_instance.account_id, vm_instance.service_offering_id, vm_instance.reservation_id, vm_instance.hypervisor_type, vm_instance.dynamically_scalable, vm_instance.uuid, vm_instance.disk_offering_id FROM vm_instance INNER JOIN host ON vm_instance.host_id=host.id WHERE vm_instance.removed IS NULL AND (host.cluster_id = 1 ) com.cloud.utils.exception.CloudRuntimeException: DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@4ae33037: SELECT vm_instance.id, vm_instance.name, vm_instance.vnc_password, vm_instance.proxy_id, vm_instance.proxy_assign_time, vm_instance.state, vm_instance.private_ip_address, vm_instance.instance_name, vm_instance.vm_template_id, vm_instance.guest_os_id, vm_instance.host_id, vm_instance.last_host_id, vm_instance.pod_id, vm_instance.private_mac_address, vm_instance.data_center_id, vm_instance.vm_type, vm_instance.ha_enabled, vm_instance.display_vm, vm_instance.limit_cpu_use, vm_instance.update_count, vm_instance.created, vm_instance.removed, vm_instance.update_time, vm_instance.domain_id, vm_instance.account_id, vm_instance.service_offering_id, vm_instance.reservation_id, vm_instance.hypervisor_type, vm_instance.dynamically_scalable, vm_instance.uuid, vm_instance.disk_offering_id FROM vm_instance INNER JOIN host ON vm_instance.host_id=host.id WHERE vm_instance.removed IS NULL AND (host.cluster_id = 1 ) at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:415) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:350) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:905) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:882) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:895) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.vm.dao.VMInstanceDaoImpl.listByClusterId(VMInstanceDaoImpl.java:274) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.vm.VirtualMachineManagerImpl.fullSync(VirtualMachineManagerImpl.java:2100) at com.cloud.vm.VirtualMachineManagerImpl.processConnect(VirtualMachineManagerImpl.java:2616) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:589) at com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1485) at com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1749) at com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1911) at com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.run(AgentManagerImpl.java:1133) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[jira] [Created] (CLOUDSTACK-3918) com.cloud.ucs.manager.UcsManagerImpl cannot parse default config
Donal Lafferty created CLOUDSTACK-3918: -- Summary: com.cloud.ucs.manager.UcsManagerImpl cannot parse default config Key: CLOUDSTACK-3918 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3918 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Environment: Run using jetty environment Reporter: Donal Lafferty Assignee: frank zhang INFO [ComponentContext] (Timer-2:) Starting com.cloud.ucs.manager.UcsManagerImpl ERROR [ComponentContext] (Timer-2:) Unhandled exception java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:454) at java.lang.Integer.valueOf(Integer.java:582) at com.cloud.ucs.manager.UcsManagerImpl.start(UcsManagerImpl.java:178) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:135) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) -- 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
[jira] [Commented] (CLOUDSTACK-3723) System VM Template for XenServer has wrong guest OS type Information on the Database
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720723#comment-13720723 ] Donal Lafferty commented on CLOUDSTACK-3723: Ignore my edits (I believe I've reverted them). After submitting https://issues.apache.org/jira/browse/CLOUDSTACK-3853, I did not realise I'd been returned to this bug. > System VM Template for XenServer has wrong guest OS type Information on the > Database > > > Key: CLOUDSTACK-3723 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3723 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.0 > > > Observe that the guest_os id of the System VM Template for XenServer is 133 > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=1 \G > *** 1. row *** > id: 1 >name: SystemVM Template (XenServer) >type: SYSTEM > format: VHD >display_text: SystemVM Template (XenServer) > guest_os_id: 133 > hypervisor_type: XenServer > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=8 \G > *** 1. row *** > id: 8 >name: SystemVM Template (vSphere) >type: SYSTEM > format: OVA >display_text: SystemVM Template (vSphere) > guest_os_id: 15 > hypervisor_type: VMware > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=3 \G > *** 1. row *** > id: 3 >name: SystemVM Template (KVM) >type: SYSTEM > format: QCOW2 >display_text: SystemVM Template (KVM) > guest_os_id: 15 > hypervisor_type: KVM > 1 row in set (0.00 sec) > mysql> > mysql> select * from guest_os where id=133; > +-+-+--+--++ > | id | category_id | name | uuid | > display_name | > +-+-+--+--++ > | 133 | 2 | NULL | 0099b9c8-f320-11e2-b49d-06cba2000705 | Debian > GNU/Linux 6(64-bit) | > +-+-+--+--++ > 1 row in set (0.00 sec) > The System VM deployed from the XenServer System VM Template is not a 64 bit > machine. > The above correction is crucial for Upgrades -- 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
[jira] [Updated] (CLOUDSTACK-3723) System VM Template for XenServer has wrong guest OS type Information on the Database
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-3723: --- Fix Version/s: (was: Future) 4.2.0 > System VM Template for XenServer has wrong guest OS type Information on the > Database > > > Key: CLOUDSTACK-3723 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3723 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.0 > > > Observe that the guest_os id of the System VM Template for XenServer is 133 > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=1 \G > *** 1. row *** > id: 1 >name: SystemVM Template (XenServer) >type: SYSTEM > format: VHD >display_text: SystemVM Template (XenServer) > guest_os_id: 133 > hypervisor_type: XenServer > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=8 \G > *** 1. row *** > id: 8 >name: SystemVM Template (vSphere) >type: SYSTEM > format: OVA >display_text: SystemVM Template (vSphere) > guest_os_id: 15 > hypervisor_type: VMware > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=3 \G > *** 1. row *** > id: 3 >name: SystemVM Template (KVM) >type: SYSTEM > format: QCOW2 >display_text: SystemVM Template (KVM) > guest_os_id: 15 > hypervisor_type: KVM > 1 row in set (0.00 sec) > mysql> > mysql> select * from guest_os where id=133; > +-+-+--+--++ > | id | category_id | name | uuid | > display_name | > +-+-+--+--++ > | 133 | 2 | NULL | 0099b9c8-f320-11e2-b49d-06cba2000705 | Debian > GNU/Linux 6(64-bit) | > +-+-+--+--++ > 1 row in set (0.00 sec) > The System VM deployed from the XenServer System VM Template is not a 64 bit > machine. > The above correction is crucial for Upgrades -- 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
[jira] [Updated] (CLOUDSTACK-3723) System VM Template for XenServer has wrong guest OS type Information on the Database
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-3723: --- Component/s: Upgrade > System VM Template for XenServer has wrong guest OS type Information on the > Database > > > Key: CLOUDSTACK-3723 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3723 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.2.0 > > > Observe that the guest_os id of the System VM Template for XenServer is 133 > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=1 \G > *** 1. row *** > id: 1 >name: SystemVM Template (XenServer) >type: SYSTEM > format: VHD >display_text: SystemVM Template (XenServer) > guest_os_id: 133 > hypervisor_type: XenServer > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=8 \G > *** 1. row *** > id: 8 >name: SystemVM Template (vSphere) >type: SYSTEM > format: OVA >display_text: SystemVM Template (vSphere) > guest_os_id: 15 > hypervisor_type: VMware > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=3 \G > *** 1. row *** > id: 3 >name: SystemVM Template (KVM) >type: SYSTEM > format: QCOW2 >display_text: SystemVM Template (KVM) > guest_os_id: 15 > hypervisor_type: KVM > 1 row in set (0.00 sec) > mysql> > mysql> select * from guest_os where id=133; > +-+-+--+--++ > | id | category_id | name | uuid | > display_name | > +-+-+--+--++ > | 133 | 2 | NULL | 0099b9c8-f320-11e2-b49d-06cba2000705 | Debian > GNU/Linux 6(64-bit) | > +-+-+--+--++ > 1 row in set (0.00 sec) > The System VM deployed from the XenServer System VM Template is not a 64 bit > machine. > The above correction is crucial for Upgrades -- 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
[jira] [Updated] (CLOUDSTACK-3723) System VM Template for XenServer has wrong guest OS type Information on the Database
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty updated CLOUDSTACK-3723: --- Component/s: (was: Upgrade) Fix Version/s: (was: 4.2.0) Future > System VM Template for XenServer has wrong guest OS type Information on the > Database > > > Key: CLOUDSTACK-3723 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3723 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Chandan Purushothama >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: Future > > > Observe that the guest_os id of the System VM Template for XenServer is 133 > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=1 \G > *** 1. row *** > id: 1 >name: SystemVM Template (XenServer) >type: SYSTEM > format: VHD >display_text: SystemVM Template (XenServer) > guest_os_id: 133 > hypervisor_type: XenServer > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=8 \G > *** 1. row *** > id: 8 >name: SystemVM Template (vSphere) >type: SYSTEM > format: OVA >display_text: SystemVM Template (vSphere) > guest_os_id: 15 > hypervisor_type: VMware > 1 row in set (0.00 sec) > mysql> select id,name,type,format,display_text,guest_os_id,hypervisor_type > from vm_template where id=3 \G > *** 1. row *** > id: 3 >name: SystemVM Template (KVM) >type: SYSTEM > format: QCOW2 >display_text: SystemVM Template (KVM) > guest_os_id: 15 > hypervisor_type: KVM > 1 row in set (0.00 sec) > mysql> > mysql> select * from guest_os where id=133; > +-+-+--+--++ > | id | category_id | name | uuid | > display_name | > +-+-+--+--++ > | 133 | 2 | NULL | 0099b9c8-f320-11e2-b49d-06cba2000705 | Debian > GNU/Linux 6(64-bit) | > +-+-+--+--++ > 1 row in set (0.00 sec) > The System VM deployed from the XenServer System VM Template is not a 64 bit > machine. > The above correction is crucial for Upgrades -- 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
[jira] [Created] (CLOUDSTACK-3853) System VM Template for Hyper-V has wrong guest OS type Information on the Database
Donal Lafferty created CLOUDSTACK-3853: -- Summary: System VM Template for Hyper-V has wrong guest OS type Information on the Database Key: CLOUDSTACK-3853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3853 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Environment: Default template database, e.g. mysql> select URL from template_view where hypervisor_type='Hyperv'; +---+ | url | +---+ | http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 | +---+ 1 row in set (0.00 sec) Reporter: Donal Lafferty Assignee: Sanjay Tripathi Image recorded as Hyper-V system VM is not a valid Hyper-V image. It will not boot :( Fortunately, the more recent builds of the Hyper-V system VM do boot. This image has been examined, and it has the correct drivers for Hyper-V. See http://dlafferty.blogspot.co.uk/2013/07/installing-hyper-v-pv-drivers-for-linux.html for details of the required drivers. -- 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
[jira] [Commented] (CLOUDSTACK-3714) 4.2 KVM agent sends wrong StartupRoutingCommand to 4.1 management server
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717712#comment-13717712
]
Donal Lafferty commented on CLOUDSTACK-3714:
This issue is due to JSON serialisation changes that were not made backwards
compatible. Look to http://markmail.org/message/5blyteot6nxnju3d for a brief
explanation.
This issue also affects SystemVMs. The default download URL is for system VMs
built with v4.1 serialisation. These are incompatible with the current
managment server code. The issue for this probelm is
https://issues.apache.org/jira/browse/CLOUDSTACK-3377
> 4.2 KVM agent sends wrong StartupRoutingCommand to 4.1 management server
>
>
> Key: CLOUDSTACK-3714
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3714
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
>Affects Versions: 4.2.0
> Environment: 4.2 agent with 4.1 management server
>Reporter: Wido den Hollander
> Fix For: 4.2.0
>
>
> When the Agent starts it sends a StartupRoutingCommand to the management
> server, but this has changed it seems:
> In 4.1 the Agent sends this JSON:
> Sending Startup: Seq 4-0: { Cmd , MgmtId: -1, via: 4, Ver: v1, Flags: 1,
> [{"StartupRoutingCommand":{
> In 4.2 however the JSON data starts with:
> Sending Startup: Seq 1-6: { Cmd , MgmtId: -1, via: 1, Ver: v1, Flags: 1,
> [{"com.cloud.agent.api.StartupRoutingCommand":{
> So the Agent sends the full name of the class and this confuses the
> Management server, it throws an Exception:
> Caused by: com.cloud.utils.exception.CloudRuntimeException: can't find
> com.cloud.agent.api.com.cloud.agent.api.StartupRoutingCommand
> at
> com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:79)
> at
> com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:37)
> at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
> ... 15 more
> So it's searching for
> "com.cloud.agent.api.com.cloud.agent.api.StartupRoutingCommand" which
> obviously fails.
--
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
[jira] [Commented] (CLOUDSTACK-3377) Error seen when system vms are started and due to which template download is not initiated : com.google.gson.JsonParseException: The JsonDeserializer com.cloud.age
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713542#comment-13713542
]
Donal Lafferty commented on CLOUDSTACK-3377:
Problem due to incorrect serialization in system VM being used. Previously,
the JSON serializer encoded object types using the type's simple name. Now it
is using the type's fully qualified name. Thus, the system VM should be
returning "com.cloud.agent.api.StartupProxyCommand" and not
"StartupProxyCommand". Therefore, the system VM in use needs to be updated.
> Error seen when system vms are started and due to which template download is
> not initiated : com.google.gson.JsonParseException: The JsonDeserializer
> com.cloud.agent.transport.ArrayTypeAdaptor@697537aa failed to deserialize
> json object
>
>
> Key: CLOUDSTACK-3377
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3377
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
>Reporter: Abhinav Roy
> Fix For: 4.2.0
>
>
> Steps :
>
> 1. Deploy an advanced zone setup with XenServer as host.
> Expected behaviour :
> ===
> 1. Deployment should be successful and the system vms should be created and
> started without any issue.
> Observed behaviour :
> ==
> Though the system vms get started and are in running state, during the start
> process the following error is thrown due to which the templates don't get
> downloaded
> 013-07-05 11:52:03,688 ERROR [agent.transport.Request]
> (AgentManager-Handler-8:null) Caught problem with
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.102.195.11","publicNetmask":"255.255.252.0","publicMacAddress":"06:7a:80:00:00:15","privateIpAddress":"10.102.195.42","privateMacAddress":"06:2c:6e:00:00:0c","privateNetmask":"255.255.252.0","storageIpAddress":"10.102.195.42","storageNetmask":"255.255.252.0","storageMacAddress":"06:2c:6e:00:00:0c","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
> com.google.gson.JsonParseException: The JsonDeserializer
> com.cloud.agent.transport.ArrayTypeAdaptor@697537aa failed to deserialize
> json object
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.102.195.11","publicNetmask":"255.255.252.0","publicMacAddress":"06:7a:80:00:00:15","privateIpAddress":"10.102.195.42","privateMacAddress":"06:2c:6e:00:00:0c","privateNetmask":"255.255.252.0","storageIpAddress":"10.102.195.42","storageNetmask":"255.255.252.0","storageMacAddress":"06:2c:6e:00:00:0c","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
> given the type class [Lcom.cloud.agent.api.Command;
> at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
> at
> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
> at
> com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
> at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
> at
> com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
> at
> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
> at com.google.gson.Gson.fromJson(Gson.java:551)
> at com.google.gson.Gson.fromJson(Gson.java:498)
> at com.cloud.agent.transport.Request.getCommands(Request.java:235)
> at
> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(AgentManagerImpl.java:1196)
> at
> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerImpl.java:1349)
> at
> com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.doTask(ClusteredAgentManagerImpl.java:659)
> at com.cloud.utils.nio.Task.run(Task.java:83)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.ru
[jira] [Commented] (CLOUDSTACK-3377) Error seen when system vms are started and due to which template download is not initiated : com.google.gson.JsonParseException: The JsonDeserializer com.cloud.age
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713512#comment-13713512
]
Donal Lafferty commented on CLOUDSTACK-3377:
Confirmed. I see the identical problem. Using master code from July 12th.
Unable to duplicate work around. Rebooted Xen without first removing from
management server or disabling it. On restart, failed to run system Vms on
machine, because I ran out of management IPs,
> Error seen when system vms are started and due to which template download is
> not initiated : com.google.gson.JsonParseException: The JsonDeserializer
> com.cloud.agent.transport.ArrayTypeAdaptor@697537aa failed to deserialize
> json object
>
>
> Key: CLOUDSTACK-3377
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3377
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
>Reporter: Abhinav Roy
> Fix For: 4.2.0
>
>
> Steps :
>
> 1. Deploy an advanced zone setup with XenServer as host.
> Expected behaviour :
> ===
> 1. Deployment should be successful and the system vms should be created and
> started without any issue.
> Observed behaviour :
> ==
> Though the system vms get started and are in running state, during the start
> process the following error is thrown due to which the templates don't get
> downloaded
> 013-07-05 11:52:03,688 ERROR [agent.transport.Request]
> (AgentManager-Handler-8:null) Caught problem with
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.102.195.11","publicNetmask":"255.255.252.0","publicMacAddress":"06:7a:80:00:00:15","privateIpAddress":"10.102.195.42","privateMacAddress":"06:2c:6e:00:00:0c","privateNetmask":"255.255.252.0","storageIpAddress":"10.102.195.42","storageNetmask":"255.255.252.0","storageMacAddress":"06:2c:6e:00:00:0c","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
> com.google.gson.JsonParseException: The JsonDeserializer
> com.cloud.agent.transport.ArrayTypeAdaptor@697537aa failed to deserialize
> json object
> [{"StartupSecondaryStorageCommand":{"type":"SecondaryStorage","dataCenter":"1","pod":"1","guid":"s-1-VM-NfsSecondaryStorageResource","name":"s-1-VM","version":"4.2.0-SNAPSHOT","iqn":"NoIqn","publicIpAddress":"10.102.195.11","publicNetmask":"255.255.252.0","publicMacAddress":"06:7a:80:00:00:15","privateIpAddress":"10.102.195.42","privateMacAddress":"06:2c:6e:00:00:0c","privateNetmask":"255.255.252.0","storageIpAddress":"10.102.195.42","storageNetmask":"255.255.252.0","storageMacAddress":"06:2c:6e:00:00:0c","resourceName":"NfsSecondaryStorageResource","contextMap":{},"wait":0}}]
> given the type class [Lcom.cloud.agent.api.Command;
> at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:64)
> at
> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
> at
> com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:80)
> at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:101)
> at
> com.google.gson.JsonDeserializationContextDefault.fromJsonArray(JsonDeserializationContextDefault.java:67)
> at
> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:52)
> at com.google.gson.Gson.fromJson(Gson.java:551)
> at com.google.gson.Gson.fromJson(Gson.java:498)
> at com.cloud.agent.transport.Request.getCommands(Request.java:235)
> at
> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(AgentManagerImpl.java:1196)
> at
> com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerImpl.java:1349)
> at
> com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.doTask(ClusteredAgentManagerImpl.java:659)
> at com.cloud.utils.nio.Task.run(Task.java:83)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: com.cloud.utils.exception.CloudRuntimeException: can't find
[jira] [Created] (CLOUDSTACK-3650) CloudStack scripts fail when running on Jetty
Donal Lafferty created CLOUDSTACK-3650: -- Summary: CloudStack scripts fail when running on Jetty Key: CLOUDSTACK-3650 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3650 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Projects Affects Versions: Future Environment: XenServer deployment Reporter: Donal Lafferty 1. Run CloudStack in jetty using mvn :cloud-client-ui project. E.g. command line: mvn -pl :cloud-client-ui jetty:run 2. Deploy a XenServer zone 3. Register a template CloudStack fails: it is unable to start scripts, because they are not set to executable. Sample log file warning: WARN [storage.resource.NfsSecondaryStorageResource] (consoleproxy-1:) Exception: /root/github/cshv3/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh -s 2 -n 0061d74e-67e0-4504-8a2a-e795eb72c241.vhd -t /mnt/secStorage/fa894f55-dd09-39b8-adf9-aa7e238aa29c/template/tmpl/1/1 -f /mnt/secStorage/fa894f55-dd09-39b8-adf9-aa7e238aa29c/template/tmpl/1/1/acton-systemvm-02062012.vhd.bz2 java.io.IOException: Cannot run program "/root/github/cshv3/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh": error=13, Permission denied Confirmation script is missing executable permissions: root@mgmtserver:~/github/cshv3# ls -al /root/github/cshv3/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh -rw-r--r-- 1 root root 4779 Jul 16 23:24 /root/github/cshv3/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/storage/secondary/createtmplt.sh Similar to, but not the same as https://issues.apache.org/jira/browse/CLOUDSTACK-1304, because there was a fix already in place for that bug. -- 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
[jira] [Created] (CLOUDSTACK-3449) Configuration of Hyper-V System VMs Missing
Donal Lafferty created CLOUDSTACK-3449: -- Summary: Configuration of Hyper-V System VMs Missing Key: CLOUDSTACK-3449 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3449 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: Future Environment: Hyper-V hypervisors Reporter: Donal Lafferty Background: System VMs are passed their configuration details in the 'bootArgs' field of the StartCommand used to create and start them. For instance, with XenServer, the vm.set_PV_args command is used. When the SystemVM is launched, the cloud-early-config script reads this information and sets up the system VM accordingly. Problem: The current SystemVM does not process its configuration when running on a Hyper-V hypervisor. -- 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
[jira] [Closed] (CLOUDSTACK-3283) System VM does not start on Hyper-V Server 2012
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty closed CLOUDSTACK-3283. -- Duplicate of CLOUDSTACK-3283 > System VM does not start on Hyper-V Server 2012 > --- > > Key: CLOUDSTACK-3283 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3283 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: Future > Environment: Hyper-V hypervisor >Reporter: Donal Lafferty > > The SystemVM is supposed to have Hyper-V drivers installed. > A VM was created with the SystemVM image attached and started. > Although CPU was stuck at 12%, the console displayed no text. It was > impossible to login from the console. -- 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
[jira] [Resolved] (CLOUDSTACK-3283) System VM does not start on Hyper-V Server 2012
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty resolved CLOUDSTACK-3283. Resolution: Duplicate Duplicate of CLOUDSTACK-3283 > System VM does not start on Hyper-V Server 2012 > --- > > Key: CLOUDSTACK-3283 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3283 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: Future > Environment: Hyper-V hypervisor >Reporter: Donal Lafferty > > The SystemVM is supposed to have Hyper-V drivers installed. > A VM was created with the SystemVM image attached and started. > Although CPU was stuck at 12%, the console displayed no text. It was > impossible to login from the console. -- 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
[jira] [Created] (CLOUDSTACK-3385) Wrong Image for Hyper-V System VM
Donal Lafferty created CLOUDSTACK-3385: -- Summary: Wrong Image for Hyper-V System VM Key: CLOUDSTACK-3385 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3385 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: Future Reporter: Donal Lafferty The System VM registered on downloads.cloud.com for Hyper-V is not a Hyper-V image. It should be updated with a more recent version from http://jenkins.cloudstack.org/job/build-systemvm-master/? -- 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
[jira] [Closed] (CLOUDSTACK-186) Setting Up instructions do not appear to work
[ https://issues.apache.org/jira/browse/CLOUDSTACK-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Lafferty closed CLOUDSTACK-186. - Problem was due to doc / build mismatch when the build moved from ant to maven. When build docs were updated, this issue disappeared. > Setting Up instructions do not appear to work > - > > Key: CLOUDSTACK-186 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-186 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Affects Versions: 4.0.0 > Environment: Cygwin environment on Windows >Reporter: Donal Lafferty >Assignee: Prasanna Santhanam >Priority: Minor > Fix For: pre-4.0.0 > > > After following the Windows setup instructions and cloning the ASF repo, I > run "ant clean-all build-all". The build is unable to find the .jar files > for Axis2, and I get the error message below: > BUILD FAILED > C:\cygwin\home\donall\incubator\incubator-cloudstack\build.xml:48: The > following error occurred while executing this line: > C:\cygwin\home\donall\incubator\incubator-cloudstack\build\build-aws-api.xml:34: > taskdef class org.apache.axis2.tool.ant.AntCodegenTask cannot be found > using the classloader AntClassLoader[] -- 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
[jira] [Created] (CLOUDSTACK-3283) System VM does not start on Hyper-V Server 2012
Donal Lafferty created CLOUDSTACK-3283: -- Summary: System VM does not start on Hyper-V Server 2012 Key: CLOUDSTACK-3283 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3283 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: Future Environment: Hyper-V hypervisor Reporter: Donal Lafferty The SystemVM is supposed to have Hyper-V drivers installed. A VM was created with the SystemVM image attached and started. Although CPU was stuck at 12%, the console displayed no text. It was impossible to login from the console. -- 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
[jira] [Created] (CLOUDSTACK-3281) StartCommand carries VolumeObjectTO with format field of NULL
Donal Lafferty created CLOUDSTACK-3281:
--
Summary: StartCommand carries VolumeObjectTO with format field of
NULL
Key: CLOUDSTACK-3281
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3281
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller
Affects Versions: Future
Environment: Hyper-V cluster
Reporter: Donal Lafferty
Disk image format is missing from VolumeObjectTO in StartCommand. Not clear
whether Hypervisor needs to set this in the CopyCmdAnswer returned when the
volume is created, if the hypervisor is never to use the format when looking up
an image or if there is a bug in the system.
Sample command:
{
"vm": {
"id": 2,
"name": "v-2-VM",
"type": "ConsoleProxy",
"cpus": 1,
"minSpeed": 500,
"maxSpeed": 500,
"minRam": 1073741824,
"maxRam": 1073741824,
"arch": "i686",
"os": "Debian GNU/Linux 5.0 (32-bit)",
"bootArgs": " template=domP type=consoleproxy host=10.80.3.83 port=8250
name=v-2-VM premium=true zone=1 pod=1 guid=Proxy.2 proxy_vm=2
disable_rp_filter=true eth2ip=10.70.176.125 eth2mask=255.255.240.0
gateway=10.70.176.1 eth0ip=169.254.1.121 eth0mask=255.255.0.0
eth1ip=10.70.176.96 eth1mask=255.255.240.0 mgmtcidr=10.80.2.0/23
localgw=10.70.176.1 internaldns1=10.70.176.118 internaldns2=10.70.160.66
dns1=4.4.4.4",
"rebootOnCrash": false,
"enableHA": false,
"limitCpuUse": false,
"enableDynamicallyScaleVm": false,
"vncPassword": "ce12c56d3290de94",
"params": {},
"uuid": "89384857-b45d-47c0-8c7e-b011b0fcb118",
"disks": [
{
"data": {
"org.apache.cloudstack.storage.to.VolumeObjectTO": {
"uuid": "35a079e4-7767-47d1-8629-72d32c866a08",
"volumeType": "ROOT",
"dataStore": {
"org.apache.cloudstack.storage.to.PrimaryDataStoreTO": {
"uuid": "700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource",
"id": 1,
"poolType": "Filesystem",
"host": "10.70.176.29",
"path": "E:\\Disks\\",
"port": 0
}
},
"name": "ROOT-2",
"size": 140616708,
"volumeId": 2,
"vmName": "v-2-VM",
"accountId": 1,
"id": 2
}
},
"diskSeq": 0,
"type": "ROOT"
}
],
"nics": [
{
"deviceId": 2,
"networkRateMbps": -1,
"defaultNic": true,
"uuid": "022f8487-aba2-441b-85dd-3a68c3614fec",
"ip": "10.70.176.125",
"netmask": "255.255.240.0",
"gateway": "10.70.176.1",
"mac": "06:9d:26:00:00:0c",
"dns1": "4.4.4.4",
"broadcastType": "Vlan",
"type": "Public",
"broadcastUri": "vlan://untagged",
"isolationUri": "vlan://untagged",
"isSecurityGroupEnabled": false
},
{
"deviceId": 0,
"networkRateMbps": -1,
"defaultNic": false,
"uuid": "4fbb6713-de1e-4930-a944-6b5685c4ac62",
"ip": "169.254.1.121",
"netmask": "255.255.0.0",
"gateway": "169.254.0.1",
"mac": "0e:00:a9:fe:01:79",
"broadcastType": "LinkLocal",
"type": "Control",
"isSecurityGroupEnabled": false
},
{
"deviceId": 1,
"networkRateMbps": -1,
"defaultNic": false,
"uuid": "2eeefa17-429e-47a5-bf41-bfa4742b712c",
"ip": "10.70.176.96",
"netmask": "255.255.240.0",
"gateway": "10.70.176.1",
"mac": "06:26:ae:00:00:07",
"broadcastType": "Native",
"type": "Management",
"isSecurityGroupEnabled": false
}
]
},
"hostIp": "10.70.176.29",
"executeInSequence": false,
"contextMap": {},
"wait": 0
}
--
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
[jira] [Created] (CLOUDSTACK-3215) Cannot Deploy VM when using S3 object store without NFS Cache
Donal Lafferty created CLOUDSTACK-3215: -- Summary: Cannot Deploy VM when using S3 object store without NFS Cache Key: CLOUDSTACK-3215 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3215 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0, Future Environment: Tested with Windows development environment, Hyper-V hypervisor. However, the problem appears to be more general. Reporter: Donal Lafferty This scenario arises when S3 is used for secondary storage, but no NFS cache is added. Tested on Master. May affect 4.2.0 as well. Cause: AncientDataMotionStrategy.needCacheStorage does not allow for CloudStack to deployed without NFS and without an image cache. -- 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
