Salt 3008.0rc2 (Argon) LTS Release Candidate is available!

[Shane Lee]

Hi everyone,

We are excited to announce that the first release candidate for Argon, Salt 3008.0rc2, is now available for testing! This is a Long Term Support (LTS) release, and we would appreciate your help in testing it within your environments to ensure the best possible stable release.

https://saltproject.io/blog/salt-3008-rc2-available/

Where to find it:

• Release Tag: Salt 3008.0rc2 on GitHub

• Source  (PyPi): Salt-3008.0rc2 Tarball

• Release Notes: Salt 3008.0rc2 Release Notes

How you can help:

Please report any bugs or regressions you encounter on GitHub Issues. When reporting, please be sure to include the version number (3008.0rc2) so our team can triage them quickly.

We want to extend a huge thank you to the community. Your contributions, bug reports, and continued support are what make the Salt Project possible. We couldn’t do this without you!

Happy testing,

The Salt Project Team

[Anand Buddhdev]

Hi Shane,

This is a testing release, and the installation instructions even tell the user to install it using pip, or from a tarball. This implies that RPMs and DEBs should not be distributed to repositories yet.

However, the RPM repository contains release candidate RPMs. Anyone who is using the repository, and has not pinned the version of salt, will be surprised to see salt updated to this testing version when they run "dnf update". In my opinion, these testing versions should not be placed in the repository.

Regards,

Anand

[Shane Lee]

Hi Anand,

I understand the concern. In our current environment, we don't have the same level of granular control over repository segregation that we may have had in the past.

Because the RCs are currently served through these main repositories, we made it a point to announce the version pinning requirement ahead of the RC1 and RC2 releases. For those who want to remain on the stable path and avoid automatic updates to testing versions, pinning is the necessary step.

We’ll continue to highlight this requirement in our communications to ensure users are aware of how to manage their environments given the current repository structure.

[David Komanek]

Hi,

I have the same problem on Ubuntu, the RC version is propagated through the "stable" channel. I didn't notice until some strange behaviour and errors since our server is still on 3007. So I downgraded the minion and marked it for hold ...

# apt policy salt-minion
salt-minion:
  Installed: 3007.7
  Candidate: 3008.0~rc2
  Version table:
     3008.0~rc2 500
        500 https://packages.broadcom.com/artifactory/saltproject-deb stable/main amd64 Packages
     3008.0~rc1 500
        500 https://packages.broadcom.com/artifactory/saltproject-deb stable/main amd64 Packages
...

The errors when running 3008-minion against 3007-server, I have no idea what does it mean:

May 04 08:39:02 gpu-titan-03 salt-minion[11331]: [ERROR   ] Task was destroyed but it is pending!
May 04 08:39:02 gpu-titan-03 salt-minion[11331]: task: <Task pending name='Task-72' coro=<Queue.get() running at /opt/saltstack/salt/lib/python3.11/asyncio/queues.py:158> wait_for=<Future finished result=None> cb=>
May 04 08:39:02 gpu-titan-03 salt-minion[11331]: [ERROR   ] Task was destroyed but it is pending!
May 04 08:39:02 gpu-titan-03 salt-minion[11331]: task: <Task pending name='Task-57' coro=<Queue.get() running at /opt/saltstack/salt/lib/python3.11/asyncio/queues.py:158> wait_for=<Future finished result=None> cb=>
May 04 08:39:02 gpu-titan-03 salt-minion[11331]: [ERROR   ] Task was destroyed but it is pending!
May 04 08:39:02 gpu-titan-03 salt-minion[11331]: task: <Task pending name='Task-60' coro=<Queue.get() running at /opt/saltstack/salt/lib/python3.11/asyncio/queues.py:158> wait_for=<Future finished result=None> cb=>
May 04 08:39:02 gpu-titan-03 salt-minion[11331]: [ERROR   ] Task was destroyed but it is pending!
...

May 04 08:39:03 gpu-titan-03 salt-minion[3005]: [WARNING ] The minion function caused an exception
May 04 08:39:07 gpu-titan-03 salt-minion[11331]: [ERROR   ] Task was destroyed but it is pending!
May 04 08:39:07 gpu-titan-03 salt-minion[11331]: task: <Task pending name='Task-78' coro=<Queue.get() running at /opt/saltstack/salt/lib/python3.11/asyncio/queues.py:158> wait_for=<Future finished result=None> cb=>
May 04 08:39:08 gpu-titan-03 salt-minion[11331]: /opt/saltstack/salt/lib/python3.11/site-packages/salt/utils/pycrypto.py:27: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13
May 04 08:39:08 gpu-titan-03 salt-minion[11331]:   import crypt  # pylint: disable=deprecated-module
May 04 08:39:08 gpu-titan-03 salt-minion[11331]: /opt/saltstack/salt/lib/python3.11/site-packages/salt/modules/solaris_shadow.py:17: DeprecationWarning: 'spwd' is deprecated and slated for removal in Python 3.13
May 04 08:39:08 gpu-titan-03 salt-minion[11331]:   import spwd  # pylint: disable=deprecated-module
May 04 08:39:08 gpu-titan-03 salt-minion[11331]: [ERROR   ] Source file salt:///etc/postfix/main.cf not found in saltenv 'base'
May 04 08:39:08 gpu-titan-03 salt-minion[11331]: [ERROR   ] Source file salt:///etc/postfix/saslpass not found in saltenv 'base'
May 04 08:39:08 gpu-titan-03 salt-minion[11331]: [ERROR   ] Source file salt:///etc/systemd/timesyncd.conf not found in saltenv 'base'
...

--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/salt-users/b50ab60b-2057-410c-956e-85aa8385d2d3n%40googlegroups.com.