[Deepsea-users] adventures with wip-salt2018 / SLE 15 / python3
Joshua Schmid
jschmid at suse.de
Mon Apr 9 02:31:14 MDT 2018
Hey Tim,
Tim Serong <tserong at suse.com> wrote on Mon, 09. Apr 17:06:
> Hi All,
>
> I have a problem. I'm trying out the deepsea wip-salt2018 branch on the
> latest(?) SLE 15 (salt 2018.1.99, python 3.6.4), and various runners
> somewhat intermittently break. Here's an example:
>
> # salt-run state.orch ceph.stage.3
> firewall : disabled
> apparmor : disabled
> fsid : valid
> public_network : valid
> cluster_network : valid
> cluster_interface : valid
> monitors : valid
> mgrs : valid
> storage : valid
> ganesha : valid
> master_role : valid
> time_server : valid
> fqdn : valid
> (...snip...)
>
> Summary for admin.ceph_master
> -------------
> Succeeded: 50 (changed=32)
> Failed: 0
> -------------
> Total states run: 50
> Total run time: 220.284 s
>
>
> OK, that worked fine. Now I run it again:
>
> # salt-run state.orch ceph.stage.3
> firewall : disabled
> apparmor : disabled
> [ERROR ] Rendering exception occurred
> Traceback (most recent call last):
> (...snip...)
> KeyError: 'validate.pillar'
That's apparently a bug in salt.. I mentioned that in my PR (https://github.com/SUSE/DeepSea/pull/1051)
under 'Caveats'.
Bug for it is here: https://bugzilla.suse.com/show_bug.cgi?id=1087232
>
> Has anyone else seen this? What the hell is going on here?
What I know is that salt's loader.py has goes a different path for
python_version >= 3.3 and uses the 'importlib' isntead of 'imp'.
That shouldn't mess with cache files, though..
So, no idea what the hell is going on :)
>
> Thanks,
>
> Tim
> --
> Tim Serong
> Senior Clustering Engineer
> SUSE
> tserong at suse.com
> _______________________________________________
> Deepsea-users mailing list
> Deepsea-users at lists.suse.com
> http://lists.suse.com/mailman/listinfo/deepsea-users
--
Joshua Schmid
Software Engineer
SUSE Enterprise Storage
More information about the Deepsea-users
mailing list