Error 404: manifest for so-curator:2.4.50 not found

[DoughnutPeach]

Version

2.4.50

Installation Method

Security Onion ISO image

Description

upgrading

Installation Type

Distributed

Location

cloud

Hardware Specs

Exceeds minimum requirements

CPU

32

RAM

16

Storage for /

500

Storage for /nsm

1TB

Network Traffic Collection

tap

Network Traffic Speeds

1Gbps to 10Gbps

Status

No, one or more services are failed (please provide detail below)

Salt Status

Yes, there are salt failures (please provide detail below)

Logs

Yes, there are additional clues in /opt/so/log/ (please provide detail below)

Detail

Since upgrading Security Onion from v2.4.30 -> v2.4.50, my so-curator has been missing.

Ran so-docker-refresh, so-docker-prune, then salt-call state.highstate and so-curator-start. And I'm still getting the following error

.
.
----------
          ID: so-curator
    Function: docker_container.running
      Result: False
     Comment: Failed to pull master:5000/security-onion-solutions/so-curator:2.4.50: Error 404: manifest for master:5000/security-onion-solutions/so-curator:2.4.50 not found: manifest unknown: manifest unknown
     Started: 11:40:35.665166
    Duration: 73.521 ms
     Changes:   
.
.
Summary for local
-------------
Succeeded: 12 (changed=1)
Failed:     1
-------------
Total states run:     13

From the docs here (https://docs.securityonion.net/en/2.4/curator.html) it says

Starting in Security Onion 2.4.40, Curator is no longer included in Security Onion. To learn more about index maintenance, please see the [Elasticsearch](https://docs.securityonion.net/en/2.4/elasticsearch.html#elasticsearch) section.

Can I confirm if I can safely stop and remove so-curator? If so, how do i do it?

Thanks!

Guidelines

• I have read the discussion guidelines at Read before posting! #1720 and assert that I have followed the guidelines.

[DoughnutPeach]

This appears to be an issue with my salt configuration. so-curator should be disabled from 2.4.40 onward, thus the issue.

Troubleshooting steps

If you are facing similar issues, there is likely an issue with your salt configuration. so-curator should be disabled.

My issue was that I accidentally ran so-saltstack-update without defining the correct version (it defaults to 2.3 branch). Eventually I re-ran so-saltstack-update 2.4/main and it resolved the salt issues.