deploy_start task should not be bound to any real node

Bug #1587462 reported by Vladimir Kozhukalov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Toolbox

Bug Description

deploy_start task should only start on virtual_sync_node

Tags: area-python
Revision history for this message
Vladimir Kozhukalov (kozhukalov) wrote :
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Medium priority bugs should be targeted to Newton release because we passed SCF for Mitaka.

Changed in fuel:
milestone: 9.0 → 10.0
tags: added: area-library
Changed in fuel:
assignee: Fuel Library (Deprecated) (fuel-library) → Fuel Sustaining (fuel-sustaining-team)
tags: added: area-python
removed: area-library
summary: - [Fuel-library] deploy_start task should not be bound to any real node
+ deploy_start task should not be bound to any real node
Revision history for this message
Vladimir Kozhukalov (kozhukalov) wrote :

it is better to force virtual task to be bound to virtual hosts only

Roman Vyalov (r0mikiam)
tags: removed: area-build
Ilya Kutukov (ikutukov)
Changed in fuel:
status: New → Confirmed
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Fuel Toolbox (fuel-toolbox)
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.