[FUEL]Deployment has failed. Method granular_deploy. Deployment failed on nodes 1.

Bug #1565672 reported by Samer Machara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Fuel Sustaining

Bug Description

Detailed bug description:
    "Deployment has failed. Method granular_deploy. Deployment failed on nodes 1.
     Inspect Astute logs for the details."

Expected results:
 One controller node deployment in an empty environment.

Description of the environment:
 Operation system: ubuntu 14.04 LTS
 Memory: 7.7 Gb
 Processor: Intel® Core™2 Quad CPU Q9550 @ 2.83GHz × 4
 Hard Disk: 250 GB

Additional information:
  Last week I had a "time out error" , deploying only one controller node on one virtual machine (https://bugs.launchpad.net/fuel/+bug/1564312), searching for the error I found
  that my hard disk doesn't have enought space (110GB), So I mounted another HHD linked VBox folder to this new disk,
  then I re-started with a clean instalation of Fuel.
  Now, I found a diferent error "Deployment has failed. Method granular_deploy. Deployment failed on nodes 1.
  Inspect Astute logs for the details."

Revision history for this message
Samer Machara (samer-machara) wrote :
Changed in fuel:
milestone: none → 9.0
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Deployment has failed. Method granular_deploy. Deployment failed on nodes 1. Inspect Astute logs for the details.

But there is no astute log in snapshot.

Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
importance: Undecided → High
status: New → Confirmed
tags: added: area-python
Revision history for this message
Vladimir Kozhukalov (kozhukalov) wrote :

Astute.log is there 10.20.0.2/var/log/docker-logs/astute/astute.log.

The errors in puppet log are:
"2016-04-01T17:55:00.767861+00:00 err: Could not prefetch keystone_domain provider 'openstack': Command: 'openstack domain list --quiet --format csv ' has been running for more then 10 seconds!"
"Execution of '/usr/bin/openstack domain create --format shell heat --enable' returned 1: ERROR: openstack Unable to establish connection to http://192.168.0.2:5000/v3/auth/tokens"

haproxy is up and running, probably something went wrong while configuring keystone. I can not see 192.168.0.2:5000/v3 entry point to be configured.

Changed in fuel:
assignee: Fuel Python Team (fuel-python) → Fuel Library Team (fuel-library)
Revision history for this message
Vladimir Kozhukalov (kozhukalov) wrote :

The environment is Fuel 7.0

Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Maksim Malchuk (mmalchuk)
Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

Keystone fail because of MySQL:

2016-04-01T16:45:33.923712+00:00 err: 2016-04-01 16:45:33.151 11977 ERROR keystone.common.wsgi [-] (OperationalError) (2013, 'Lost connection to MySQL server during query') 'SELECT service.id AS service_id, service.type AS service_type, service.enabled AS service_enabled, service.extra AS service_extra, endpo
int_1.id AS endpoint_1_id, endpoint_1.legacy_endpoint_id AS endpoint_1_legacy_endpoint_id, endpoint_1.interface AS endpoint_1_interface, endpoint_1.region_id AS endpoint_1_region_id, endpoint_1.service_id AS endpoint_1_service_id, endpoint_1.url AS endpoint_1_url, endpoint_1.enabled AS endpoint_1_enabled, endp
oint_1.extra AS endpoint_1_extra \nFROM service LEFT OUTER JOIN endpoint AS endpoint_1 ON service.id = endpoint_1.service_id \nWHERE service.enabled = 1' ()
2016-04-01 16:45:33.151 11977 TRACE keystone.common.wsgi Traceback (most recent call last):

But the first fail was with nova-api:

2016-04-01T16:34:40.332244+00:00 debug: Executing '/usr/bin/nova-manage db sync'
2016-04-01T16:39:40.510837+00:00 err: (/Stage[main]/Nova::Api/Exec[nova-db-sync]) Failed to call refresh: Command exceeded timeout
2016-04-01T16:39:40.560403+00:00 err: (/Stage[main]/Nova::Api/Exec[nova-db-sync]) Command exceeded timeout

it failed because of MySQL too:

2016-04-01T16:41:07.537614+00:00 crit: 2016-04-01 16:41:07.171 24527 CRITICAL nova [-] DBConnectionError: (OperationalError) (2013, 'Lost connection to MySQL server during query') '\nALTER TABLE pci_devices CHANGE COLUMN product_id product_id VARCHAR(4) NOT NULL' ()
2016-04-01 16:41:07.171 24527 TRACE nova Traceback (most recent call last):
2016-04-01 16:41:07.171 24527 TRACE nova File "/usr/bin/nova-manage", line 10, in <module>
2016-04-01 16:41:07.171 24527 TRACE nova sys.exit(main())

As I can see You assigned both compute and controller roles on the one node which have only 1.5Gb memory - this is not enough.
As in the previous ticket we recommend You to change hardware configuration for Your lab.

Changed in fuel:
status: Confirmed → Incomplete
assignee: Maksim Malchuk (mmalchuk) → Fuel Library Team (fuel-library)
milestone: 9.0 → 7.0-updates
importance: High → Medium
Changed in fuel:
assignee: Fuel Library (Deprecated) (fuel-library) → Fuel Sustaining (fuel-sustaining-team)
Revision history for this message
Maciej Relewicz (rlu) wrote :

Due to inactivity, bug was closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.

Changed in fuel:
status: Incomplete → Invalid
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.