Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S slapos.core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slapos.core
  • Merge requests
  • !211

Merged
Created Apr 30, 2020 by Jérome Perrin@jeromeOwner

prune: tolerate all forms of broken slapos.cfg in instance

  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 2

When we recurse in instance to find nested slapos that might be using parts from ourselves, we check all files named slapos.cfg but we may encounter some slapos.cfg that are not actual slapos config files, for example in testnodes we have a working copy of slapos repository which contains a stack/slapos.cfg which is completly different.

This was breaking prune with an error like this:

2020-04-29 20:07:28 slapos[2097] DEBUG Reading config at /srv/slapgrid/slappart9/srv/testnode/czp/slapos-repository/stack/slapos.cfg
2020-04-29 20:07:28 slapos[2097] ERROR No section: 'slapos'
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix/prune_recursive_slapos_cfg
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7