ansible/awx

Add "nodes" to "Relaunch on" when relaunching jobs after failure - users think it relates to failed tasks and not nodes

Open

#12,438 opened on Jun 29, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (3,333 forks)batch import
Hacktoberfestcomponent:uigood first issuehelp wantedtype:enhancement

Repository metrics

Stars
 (13,071 stars)
PR merge metrics
 (Avg merge 24d 6h) (30 merged PRs in 30d)

Description

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX is open source software provided for free and that I might not receive a timely response.

Feature Summary

When a job has run and failed, you sometimes want to click the little rocket to relaunch your job. Having taught many, many classes on ansible and introduced the tool to many, many clients they always assume 'all' and 'failed' refers to failed tasks and not failed nodes.

It might be totally obvious to those of us who have used the tool that ansible works on the idempotence principle on each host the play applies to. In my experience, every new user I have shown this to assumes this refers to tasks!

It would be a quite a simple GUI change to have the drop down when you click the relaunch rocket say 'all nodes' and 'failed nodes' instead, I think, and quite helpful for newbies.

Select the relevant components

  • UI
  • API
  • Docs
  • Collection
  • CLI
  • Other

Contributor guide

Research direction
Locate the dropdown component for 'Relaunch on' in the UI codebase and update the labels from 'all' and 'failed' to 'all nodes' and 'failed nodes'.
Tech stack
pythonjavascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85