SUSE Manager 3 - custom salt pillar invisible after upgrade

After upgrading SUSE Manager 3.0 with the patch ‘SUSE-SUSE-Manager-Server-3.0-2016-1539’ a call to ‘salt <minion(s)> pillar.items’ lacks the custom pillar data defined below ‘/srv/pillar’ addressed by ‘/srv/pillar/top.sls’. With the patch the path ‘/usr/share/susemanager/pillar’ becomes available and now contains the top file ‘top.sls’, which hides any pillar data from the environment ‘base’ previously addressed by the top file ‘/srv/pillar/top.sls’. From users point the file ‘/usr/share/susemanager/pillar/top.sls’ shall be considered ‘non-editable’.

What would be the recommended way to get back my custom pillar data without defining a new environment or setting another default top file name?

hwirths,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot…

Good luck!

Your SUSE Forums Team
http://forums.suse.com

For what it is worth, I heard that this is being worked on internally
right now; I’m not sure if you opened a Service Request (SR) or anything,
but either way engineering knows about it and is working on it.


Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…

Thanks for this information!

I have not opened a Service Request, yet.

Actually, I have configured a work around to integrate my custom pillar with the SUSE Manager 3 pillar.

Perhaps somebody else did, then, and cited your thread (thanks for
starting it). Either way, it sounds like a fix is in the works, and to
find out more you should open a Service Request (SR) with SUSE;
historically SRs for known, unresolved, issues are credited back to you
when closed.


Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…

Hi ab,

we’re in the loop (Harald is a colleague of me) and we’ve already had a chance to test.

Regards,
J