[Backport 2024.2] fix(nemesis): fix network block nemesis

[mergify]

Due required update of tc-config to version 0.28.1, network block nemesis broke.

Issue has been fixed in tcconfig 0.29.0 so updating it.

fixes: #8064

Testing

• - tested locally (could be reproduced easily by running tcset lo --loss 1% --tc-command

PR pre-checks (self review)

• I added the relevant backport labels
• I didn't leave commented-out/debugging code

Reminders

• Add New configuration option and document them (in sdcm/sct_config.py)
• Add unit tests to cover my changes (under unit-test/ folder)
• Update the Readme/doc folder relevant to this change (if needed)

(cherry picked from commit 1e2ab0e)

Parent PR: #8223

[mergify]

Cherry-pick of 1e2ab0e has failed:

On branch mergify/bp/branch-2024.2/pr-8223
Your branch is up to date with 'origin/branch-2024.2'.

You are currently cherry-picking commit 1e2ab0ec9.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   requirements.in

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docker/env/version
	both modified:   requirements.txt

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[fruch]

@soyacz one more reason to update the docker images on those.

lets backport the needed changes to the docker image to 6.0, 6.1, 2024.2, one by one, and let's try keep them in sync with master in that regards as much as possible

[soyacz]

@soyacz one more reason to update the docker images on those.

lets backport the needed changes to the docker image to 6.0, 6.1, 2024.2, one by one, and let's try keep them in sync with master in that regards as much as possible

I totally agree.
Is there a way to recreate backport with mergify? After backporting previous ones these would be mergable without conflicts resolution.

[fruch]

@soyacz one more reason to update the docker images on those.
lets backport the needed changes to the docker image to 6.0, 6.1, 2024.2, one by one, and let's try keep them in sync with master in that regards as much as possible

I totally agree. Is there a way to recreate backport with mergify? After backporting previous ones these would be mergable without conflicts resolution.

there isn't, one need to manually rebase and solved the issues
you can open an issue for them:
https://github.com/Mergifyio/mergify/issues

and ask them about it

[soyacz]

@soyacz one more reason to update the docker images on those.
lets backport the needed changes to the docker image to 6.0, 6.1, 2024.2, one by one, and let's try keep them in sync with master in that regards as much as possible

I totally agree. Is there a way to recreate backport with mergify? After backporting previous ones these would be mergable without conflicts resolution.

there isn't, one need to manually rebase and solved the issues you can open an issue for them: https://github.com/Mergifyio/mergify/issues

and ask them about it

Mergifyio/mergify#5121