Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C ceph-ansible
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tang liyu
  • ceph-ansible
  • Repository

Switch branch/tag
  • ceph-ansible
  • infrastructure-playbooks
  • rolling_update.yml
Find file BlameHistoryPermalink
  • Guillaume Abrioux's avatar
    rolling_update: unmask monitor service after a failure · 82b934cf
    Guillaume Abrioux authored Mar 18, 2021
    if for some reason the playbook fails after the service was
    stopped, disabled and masked and before it got restarted, enabled and
    unmasked, the playbook leaves the service masked and which can make users
    confused and forces them to unmask the unit manually.
    
    Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1917680
    
    Signed-off-by: default avatarGuillaume Abrioux <gabrioux@redhat.com>
    (cherry picked from commit 07029e1b)
    82b934cf

Replace rolling_update.yml

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.