action #160080
open[security][15-SP6] test fails in git
Added by tjyrinki_suse about 2 months ago. Updated 16 days ago.
0%
Description
Always latest result in this scenario: latest
Zypper seems to claim ntp is not found, maybe the Legacy Module is not enabled on 15-SP6 where 'ntp' package resides?
Updated by amanzini about 2 months ago
- Status changed from Workable to In Progress
Updated by amanzini about 2 months ago
- Status changed from In Progress to Feedback
Updated by openqa_review about 1 month ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_env_mode_tests_crypt_tool
https://openqa.suse.de/tests/14367744#step/git/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by amanzini about 1 month ago
- Subject changed from [security][15-SP6] test fails in ntpd due to ntp not found (legacy module missing) to [security][15-SP6] test fails in git
- Assignee deleted (
amanzini)
updating ticket and insert in the backlog due to a different failure in git+ssh:
Cloning into 'qa2'...
/etc/crypto-policies/back-ends/openssh.config line 1: Bad SSH2 cipher spec 'aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes128-gcm@openssh.com,aes128-ctr'.
/etc/crypto-policies/back-ends/openssh.config line 2: Bad SSH2 MAC spec 'hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512'.
/etc/crypto-policies/back-ends/openssh.config line 4: Bad SSH2 KexAlgorithms 'curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512'.
/etc/crypto-policies/back-ends/openssh.config: terminating, 3 bad configuration options
Updated by amanzini about 1 month ago
- Status changed from Workable to In Progress
- Assignee set to amanzini
Updated by amanzini about 1 month ago
- Copied to action #161312: [security][15-SP6] test fails in git added
Updated by amanzini about 1 month ago
- Status changed from In Progress to Resolved
closing this to avoid confusion and creating another ticket for the different issue
Updated by openqa_review 16 days ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_env_mode_tests_crypt_tool
https://openqa.suse.de/tests/14609745#step/git/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.