Deployment failed as one node get offline, after 82% deployment

Bug #1718398 reported by manju
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Undecided
Unassigned

Bug Description

Problem Description:
I was trying to create test environment using 2 slave nodes(VMs)
Fuel Master node:(2 GB RAM and 68 GB HDD; 2 Host only and 1 NAT interface)
Roles assigned to Slave1: controller and base OS(Configuration:1GB RAM and 68 GB HDD, 3 Host only network interface)
Roles assigned to Slave2: compute,cinder and base OS (Configuration:2GB RAM and 68 GB HDD, 3 Host only network interface)
Do fuel installation on master node as per following link:
https://docs.mirantis.com/openstack/fuel/fuel-7.0/quickstart-guide.html#quickstart-guide

Now after environment creation i do successful network verification and then proceed for deployment, deployment proceed successfully upto 82%.

And then deployment gets failed and in fuel Dashboard following error msg was shown:

Failed tasks: Task[swift-proxy_storage/2] Stopping the deployment process!
one node become offline.

In Node Tab: Slave1 was in offline state.

Now after some time it become in offline state and in dashboard Your deployment was unsuccessful msg is displayed.
-----------------------------------------
It will be great if someone resolve following queries:
1.>Please suggest what are the setting which i might miss while configuration.As i go with default setting and also verify the network setting.

2.>Can i re-execute deployment on same setup/environment or i need to create new slave nodes for next trial.

3.>Could you suggest clear steps to reset/clean the environment.

4.>I want to create dummy FIWARE Lab, only for this i was trying to create open stack environment using fuel.Does Somebody can guide or give instruction how one can setup..fiware local Lab where one can use generic enables.

manju (mnj13)
summary: - Deployment failed on one node get offline after 82% deployment
+ Deployment failed as one node get offline, after 82% deployment
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

It seems you had some kind of connectivity problems, you can just do redeploy.

Changed in fuel:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.