Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S snf-ganeti
  • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • itmineduitminedu
  • snf-ganeti
  • Repository
Switch branch/tag
  • snf-ganeti
  • lib
  • objects.py
Find file BlameHistoryPermalink
  • Iustin Pop's avatar
    Fix upgrading the cluster ipolicy · 38a6e2e1
    Iustin Pop authored Jan 23, 2012
    
    
    When running from git HEAD, just initialising the ipolicy when
    non-existing is not good enough; we need to upgrade also missing keys,
    etc.
    
    This has downsides though, as it means we'll always 'rewrite' the
    ipolicy, which might create silent data loss for unhandled changes
    (e.g. key removal).
    
    Signed-off-by: default avatarIustin Pop <iustin@google.com>
    Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
    38a6e2e1