Skip to content

Conversation

@bisgaard-itis
Copy link
Contributor

This reverts commit 1865d84.

What do these changes do?

Related issue/s

Related PR/s

Checklist

  • I tested and it works

@bisgaard-itis bisgaard-itis self-assigned this Jul 17, 2025
@bisgaard-itis bisgaard-itis added this to the Engage milestone Jul 17, 2025
Copy link
Collaborator

@YuryHrytsuk YuryHrytsuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks 🙏

For future viewers: deploy ops CI job got broken and make confgiure graylog makefile target would fail --> so we revert original PR

We need to define better procedure how to update graylog content packs and how to test it

@bisgaard-itis bisgaard-itis merged commit d782ba7 into main Jul 17, 2025
4 checks passed
@bisgaard-itis bisgaard-itis deleted the revert-content-pack-commit branch July 17, 2025 12:54
@YuryHrytsuk
Copy link
Collaborator

This revert was not enough to fix the problem. cd services/graylog && make configure kept failing.

error log

Caused by: com.mongodb.DuplicateKeyException: Write failed with error code 11000 and error message 'Write operation error on server mongo:27017. Write error: WriteError{code=11000, message='E11000 duplicate key error collection: graylog.pipeline_processor_pipelines index: title_1 dup key: { title: "osparc-simcore replace pipeline" }', details={}}.'

Manually removing this pipeline via Graylog GUI (System / Content Packs --> Pipelines --> Choose Pipeline & Delete it) fixed the issue.

It is also important to understand what happens to content pack versions. This revert a version to previous one (but both previous version and current version being reverted are already present in Graylog). TODO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants