Hi guys,
happy to see some other SaltStack + SmartOS users out there. Recently
salt became a bit more unstable for me and I was hoping to dig a bit
deeper and check whether the issue is on my side, my salt-master side
or in the compatibility of salt-minion and SmartOS zone. Here's the
deal:
1. I'm using 15.4.1 LTS on all of my zones.
2. Not long ago I decided to "bump up" my SaltStack minions to version 2016.3.1.
a) In order to achieve both points mentioned above, I had to use
some "creativity" when it comes to SaltStack installation.
b) I have a deploy script that I run after every
provisioning/reprovisioning of the zone which is also handling Salt
installation, like this:
# Installing Salt dependencies:
pkgin -y in zeromq py27-m2crypto py27-crypto py27-msgpack
py27-yaml py27-jinja2 py27-zmq py27-requests py27-pip py27-tornado
py27-six
# This one ought to be installed via pip for some reason I
can't recall now:
pip install futures
# The de facto installation:
curl -L https://bootstrap.saltstack.com -o install_salt.sh
sudo sh install_salt.sh -A ${master_ip} -i
"${1:-${minion_name}}" -P git v2016.3.1
3. This is generally working fine -- while I'm running silly stuff
like test.version, test.ping or cmd.run <any_given_cmd> all is good.
But whenever I hit some more demanding stuff, like state.highstate
that's going through couple of formulas, I very often get information
in red saying: "didn't get response from the minion" (or something
along these lines).
My question is -- are you guys also experiencing such behavior? I have
some formulas that are supposed to run bash script in order to get
some stuff done on the zone, but they rarely succeed when triggered
through Salt. Sometimes they are succeeding, but I still get the same
"didn't get response from the minion" on the master.
Guess I will need to dig a bit deeper into debugging this, but I was
hoping that maybe some of you already experienced such behavior and
have some tips & tricks to share (like for example: "dude, don't
upgrade to anything above 2015.8.x on LTS zones...").
All the best
--
Filip
On Sat, Aug 22, 2015 at 11:38 AM, Jorge Schrauwen <[email protected]> wrote:
> I've decided the old smartos_vmadm (virt) module to smartos_legacy and added
> a deprecation message.
>
> A new smartos_vmadm will be implemented, leaving the old behavior unchanged
> for now.
>
> Regards
>
> Jorge
>
>
>
> On 2015-08-20 08:53, Jasper Siepkes wrote:
>>
>> Hi Jorge,
>>
>> I'm a SaltStack user on SDC / SmartOS! I've also made a modest
>> contribution to
>> the pkgsrc SaltStack package by contributing an SMF manifests for it. My
>> idea is
>> to provision SDC Base64 images with Saltstack. That way I can also easily
>> upgrade to newer base64 images.
>>
>> I'm not (yet) really into the internals of SaltStack so I can't really say
>> anything about the refactoring your proposing.
>>
>> Thanks for all your work on SaltStack so far! I'm also on #smartos BTW as
>> KermitTheFragger (yeah cheesy, I know ;-).
>>
>> Kind regards,
>>
>> Jasper
>>
>>> Op 20 augustus 2015 om 8:22 schreef Jorge Schrauwen
>>> <[email protected]>:
>>>
>>> Hey All,
>>>
>>> Anyone around here use SaltStack on SmartOS?
>>> I've been fixing up the 2015.8 release to work again. All that is left
>>> is the smartos_vmadm module which needs a lot of love.
>>>
>>> I'm a bit worried about breaking things as the changes I want to do are
>>> rather big: https://github.com/saltstack/salt/issues/26507
>>>
>>> So if you use SaltStack, speak up before I start tackling this :)
>>>
>>> Regards
>>>
>>> Jorge
>>>
>>
>>>
>>
>>
>
>
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
