Fuel for OpenStack

There is no ability to execute particular task on the nodes without injecting them into default deployment graph

Bug #1470822 reported by Vladimir Kuklin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Dima Shulyak
Fuel for OpenStack 7.0
6.1.x
Won't Fix
High
MOS Maintenance
Fuel for OpenStack 6.1-updates
7.0.x
Fix Released
High
Dima Shulyak
Fuel for OpenStack 7.0

Bug Description

create a 'fire-and-forget' task, for example - https://review.openstack.org/#/c/190181/ which is an example of a bugfix. Add it onto the master node and sync tasks to nailgun

Expected behaviour:

user can run this task when he wants and not include it into default deployment graph

Actual result:

task gets injected into default deployment graph

Proposed solution:

introduce new field into tasks.yaml 'excldue:true|false' and new api handler parameter which allows you to include excluded-by-default tasks into deployment graph

This should allow use to ship bugfixes as puppet tasks

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-web (master)

Fix proposed to branch: master
Review: https://review.openstack.org/211052

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-fuelclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/211067

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (master)

Reviewed: https://review.openstack.org/211052
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=0fe7803400121f20fedd440a8cd1183a48860bdf
Submitter: Jenkins
Branch: master

commit 0fe7803400121f20fedd440a8cd1183a48860bdf
Author: Dmitry Shulyak <email address hidden>
Date: Mon Aug 10 11:45:32 2015 +0300

    Allow to include skipped tasks

    Including skipped by default tasks may be usefull for
    maintenance or patching procedure.

    All tasks received by uri:
      /clusters/(?P<cluster_id>\d+)/deploy_tasks/
    Will be included to execution, without exception for state.

    If user wants to use nailgun graph filtering logic and include
    some tasks into execution - additional input *include* with list of tasks
    must be provided to ClusterDeploymentTasksHandler.
    If include wont be provided - skipped=True will be preserved, and
    tasks wont be returned.

    *state=skipped* should be deprecated, and removed after notification
    in mailing list.

    Change-Id: I4d9621d77c09c8f0101e3eb0e8fa17372cf3f80e
    Closes-Bug: 1470822

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-fuelclient (master)

Reviewed: https://review.openstack.org/211067
Committed: https://git.openstack.org/cgit/stackforge/python-fuelclient/commit/?id=a649dfa6b06a596ad704bae87e6892df3b670ebc
Submitter: Jenkins
Branch: master

commit a649dfa6b06a596ad704bae87e6892df3b670ebc
Author: Dmitry Shulyak <email address hidden>
Date: Mon Aug 10 12:38:51 2015 +0300

    Add to execution tasks that are provided by user

    Tasks provided with flag *--tasks* will be always added to execution.
    This patch is necessary to support this behaviour with flags *--start/--end*.

    Change-Id: Ic5e95b5160a824fdca210717efa1a3b884d8e373
    Partial-Bug: 1470822

Aleksey Kasatkin (alekseyk-ru)
summary: - There is no ability to execute particular task pn the nodes without
+ There is no ability to execute particular task on the nodes without
injecting them into default deployment graph
Alexander Bochkarev (abochkarev)
tags: added: on-verification
Revision history for this message
Alexander Bochkarev (abochkarev) wrote :

Verified on 297 ISO.
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "7.0"
  openstack_version: "2015.1.0-7.0"
  api: "1.0"
  build_number: "297"
  build_id: "297"
  nailgun_sha: "28751b8cb0f2300cb3a036abc70f75c422f69fd7"
  python-fuelclient_sha: "2864459e27b0510a0f7aedac6cdf27901ef5c481"
  fuel-agent_sha: "082a47bf014002e515001be05f99040437281a2d"
  fuel-nailgun-agent_sha: "d7027952870a35db8dc52f185bb1158cdd3d1ebd"
  astute_sha: "6c5b73f93e24cc781c809db9159927655ced5012"
  fuel-library_sha: "0623b4daad438ceeb5dc41b10cdd3011795fff7e"
  fuel-ostf_sha: "1f08e6e71021179b9881a824d9c999957fcc7045"
  fuelmain_sha: "6b83d6a6a75bf7bca3177fcf63b2eebbf1ad0a85"

tags: removed: on-verification
Nastya Urlapova (aurlapova)
Changed in fuel:
status: Fix Committed → Fix Released
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

Not a critical/security issue, looks like not very important to customers (wasn't triaged since last year). Closing as Won't Fix for 6.1-updates as MOS 6.1 is on limited support.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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