Chandan Purushothama created CLOUDSTACK-273:
-----------------------------------------------
Summary: 2.2.14 to 4.0 Upgrade: XenServer Failed to connect to the
management server after Upgrade due to Null Pointer Exception
Key: CLOUDSTACK-273
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-273
Project: CloudStack
Issue Type: Bug
Components: Management Server
Affects Versions: pre-4.0.0
Environment: Build Used to Upgrade the RHEL 6.2 - 2.2.14 CloudStack
Management Server:
http://jenkins.cloudstack.org/job/build-4.0-rhel63/lastSuccessfulBuild/artifact/CloudStack-oss-4.0.0-426.tar.bz2
Reporter: Chandan Purushothama
Priority: Blocker
Fix For: pre-4.0.0
===========================
Steps to Reproduce:
===========================
1. Deployed a 2.2.14 Advanced Zone Setup using the 2.2.14 CS build for RHEL 6.2.
2. Added a XenServer 5.6 SP2 to the Advanced Zone Setup.
3. Deployed two VMs using the default CentOS Template on the Advanced Zone
Setup
4. Registered the 3.0.0 System VM Template on the CloudStack Setup that is
required as per the Upgrade Procedure
5. Stop the Usage Server
6. Stop management server.
7. Upgrade to 4.0.
8. Merge the additions in content to the old db.properties file.
9. Run cloud-setup-encryption
10. Start Management server
===========
Observations:
===========
================
NullPointerException:
================
2012-10-05 18:16:04,869 DEBUG [agent.manager.ClusteredAgentManagerImpl]
(ClusteredAgentManager Timer:null) Found 1 unmanaged direct hosts, processing
connect for them...
2012-10-05 18:16:04,869 DEBUG [agent.manager.ClusteredAgentManagerImpl]
(ClusteredAgentManager Timer:null) Loading directly connected host
2(Rack3Host18.lab.vmops.com)
2012-10-05 18:16:05,307 DEBUG [agent.manager.AgentManagerImpl]
(AgentTaskPool-1:null) Simulating start for resource
1a7520c4-d646-4199-a680-b00acb8072ea id 2
2012-10-05 18:16:05,350 DEBUG [xen.resource.XenServerConnectionPool]
(AgentTaskPool-1:null) Logging on as the slave to 10.223.59.3
2012-10-05 18:16:05,475 DEBUG [xen.resource.XenServerConnectionPool]
(AgentTaskPool-1:null) Add master connection through 10.223.59.3 for pool(null)
2012-10-05 18:16:05,549 DEBUG [xen.resource.CitrixResourceBase]
(AgentTaskPool-1:null) Management network is on
pif=f62b0330-2299-db0c-417d-bbfc05c21275
2012-10-05 18:16:05,568 WARN [xen.resource.CitrixResourceBase]
(AgentTaskPool-1:null) Unable to get host information for 10.223.59.3
java.lang.NullPointerException
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getHostInfo(CitrixResourceBase.java:4331)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.initialize(CitrixResourceBase.java:4460)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.initialize(XenServer56Resource.java:328)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1598)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1668)
at
com.cloud.agent.manager.AgentManagerImpl$SimulateStartTask.run(AgentManagerImpl.java:1195)
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)
2012-10-05 18:16:05,569 WARN [xen.resource.CitrixResourceBase]
(AgentTaskPool-1:null) Unable to get host information for 10.223.59.3
2012-10-05 18:16:05,569 INFO [cloud.resource.ResourceManagerImpl]
(AgentTaskPool-1:null) Unable to fully initialize the agent because no
StartupCommands are returned
2012-10-05 18:16:07,275 DEBUG [agent.transport.Request]
(AgentManager-Handler-13:null) Seq 4-1496252422: Processing: { Ans: , MgmtId:
7478611805898, via: 4, Ver: v1, Flags: 110,
[{"Answer":{"result":true,"wait":0}}] }
2012-10-05 18:16:07,276 DEBUG [agent.manager.AgentAttache]
(AgentManager-Handler-13:null) Seq 4-1496252422: Unable to find listener.
2012-10-05 18:16:07,276 DEBUG [agent.manager.AgentAttache]
(AgentManager-Handler-13:null) Seq 4-1496252423: Sending now. is current
sequence.
========================
Disconnected state of the Host:
========================
mysql> select * from host where id=2 \G
*************************** 1. row ***************************
id: 2
name: Rack3Host18.lab.vmops.com
status: Disconnected
type: Routing
private_ip_address: 10.223.59.3
private_netmask: 255.255.255.192
private_mac_address: bc:30:5b:d4:23:54
storage_ip_address: 10.223.59.3
storage_netmask: 255.255.255.192
storage_mac_address: bc:30:5b:d4:23:54
storage_ip_address_2: 10.223.59.3
storage_mac_address_2: bc:30:5b:d4:23:54
storage_netmask_2: 255.255.255.192
cluster_id: 1
public_ip_address: NULL
public_netmask: NULL
public_mac_address: NULL
proxy_port: NULL
data_center_id: 1
pod_id: 1
cpus: 4
speed: 2260
url: iqn.2012-10.com.example:402b1cc9
fs_type: NULL
hypervisor_type: XenServer
hypervisor_version: NULL
ram: 16190149248
resource: com.cloud.hypervisor.xen.resource.XenServer56SP2Resource
version: 2.2.14.20120210102939
parent: NULL
total_size: NULL
capabilities: xen-3.0-x86_64 , xen-3.0-x86_32p , hvm-3.0-x86_32 ,
hvm-3.0-x86_32p , hvm-3.0-x86_64
guid: 1a7520c4-d646-4199-a680-b00acb8072ea
available: 1
setup: 1
dom0_memory: 0
last_ping: 1317856577
mgmt_server_id: 7478611805898
disconnected: NULL
created: 2012-10-06 00:41:07
removed: NULL
uuid: NULL
update_count: 0
resource_state: Enabled
1 row in set (0.00 sec)
mysql> select * from version;
+----+-----------------------+---------------------+----------+
| id | version | updated | step |
+----+-----------------------+---------------------+----------+
| 1 | 2.2.14.20120210102939 | 2012-10-05 16:36:38 | Complete |
| 2 | 3.0.0 | 2012-10-06 01:15:48 | Complete |
| 3 | 3.0.1 | 2012-10-06 01:15:48 | Complete |
| 4 | 3.0.2 | 2012-10-06 01:15:49 | Complete |
| 5 | 4.0.0 | 2012-10-06 01:15:49 | Complete |
+----+-----------------------+---------------------+----------+
5 rows in set (0.00 sec)
=========
Git Info:
=========
Git Revision: 521b0f640197b3a875ce9d2ea0050234d501085b
Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
