prune: tolerate all forms of broken slapos.cfg in instance
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'
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#76762
external
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
01:17:30
|
||||||
canceled |
#76778
external
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
00:31:14
|
||||||
passed |
#76727
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python2 |
01:33:57
|
||||||
passed |
#76726
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
01:54:34
|
||||||
passed |
#76763
external
retried
|
SlapOS.Eggs.UnitTest-Jerome.Python3 |
01:44:24
|
||||||