Skip to content

hpilo_boot task with the option state: boot_once should not fail if the server is already on #9737

Closed
@christian-naenny

Description

@christian-naenny

Summary

In the idea of the idempotency of Ansible plays and tasks, I would like to suggest that the following task should not fail but rather just skip if the server is already on:

- name: Power on a server
  community.general.hpilo_boot:
    host: YOUR_ILO_HOST
    login: YOUR_ILO_LOGIN
    password: YOUR_ILO_PASSWORD
    state: boot_once

Of course, if the option force: true is set, the server should still be rebooted.

Issue Type

Feature Idea

Component Name

hpilo_boot

Additional Information

- name: Power on a server
  community.general.hpilo_boot:
    host: YOUR_ILO_HOST
    login: YOUR_ILO_LOGIN
    password: YOUR_ILO_PASSWORD
    state: boot_once

Code of Conduct

  • I agree to follow the Ansible Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureThis issue/PR relates to a feature requestmodulemodulepluginsplugin (any type)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions