-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TEST] Test BSS within the HPE CSM pipeline to identify regressions #49
Comments
FYI - vulnerability of level "high" is found in
|
Looks like that's related to hms-hmetcd. I've created a PR for that package at Cray-HPE/hms-hmetcd#13 which unvendors and updates the library. All tests pass locally with the changes. |
Similar to SMD reconciliation test (OpenCHAMI/smd#42), I've deployed CSM based version from scratch and modified deployment to run OpenCHAMI version of BSS container. Container started without errors. However, unlike SMD test, there were some test failures. I'm attaching archived logs of pods and test outputs: vshasta-bss-logs.tar.gz Test definitions: |
We're going to need more than a bunch of logs and some json. We're not familiar with your testing framework. What tests failed and what were the messages associated with each failure? |
It's in a file named
First 4 API tests fail on HTTP code 405 returned, where HTTP code 200 is expected. The last test got 404 at http://cray-bss/boot/v1/service/etcd while test expects 200. |
Let's get your BSS SMEs involved here. In the case of the 405 errors, I think the tests are invalid. Why would we want to support POST,PUT, PATCH on status urls? Given what I understand of those endpoints, they exist solely for reading health information. The 404 on Good to see that so many of your integration tests pass correctly. That should indicate that our work on BSS hasn't disrupted BSS functinality within CSM and that you can switch upstream without issue. |
I looked into test descriptions - my bad, I misinterpreted test results. These are so called "negative tests", which expect 405 HTTP code on invalid request. So outcome should be treated as "returned HTTP code 200 where 405 is expected", not the other way around. I'll check with Curt to see who is our BSS expert these days. |
This is a placeholder for @mtupitsyn to add any errors he finds with running SMD at HPE.
The text was updated successfully, but these errors were encountered: