Skip to content
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

chore(deps): update ci dependencies #250

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore(deps): update ci dependencies #250

wants to merge 2 commits into from

Conversation

akocbek
Copy link
Contributor

@akocbek akocbek commented Mar 7, 2025

Description

includes solutions from:

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content
fix(deps): sysdig-deploy version updated to `1.76.2`<br>- `cluster_shield` image updated to `1.8.2`<br>- `kspm_collector` image updated to `1.39.8`<br>- `agent_slim` image updated to `13.8.0`<br>- `vuln_host_scanner` image updated to `0.13.0`<br>- `agent_kmodule` image updated to `13.8.0`<br>- `kspm_analyzer` image updated to `1.44.33`<br><br>DA updates:<br>- kubernetes provider version updated to `2.36.0`<br>- IBM provider version updated to `1.75.2`

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@akocbek
Copy link
Contributor Author

akocbek commented Mar 7, 2025

/run pipeline

@akocbek
Copy link
Contributor Author

akocbek commented Mar 7, 2025

upgrade test failed

Error Trace:	/go/pkg/mod/github.com/terraform-ibm-modules/[email protected]/testhelper/terraform.go:243
        	            				/go/pkg/mod/github.com/terraform-ibm-modules/[email protected]/testhelper/tests.go:620
        	            				/__w/terraform-ibm-scc-workload-protection-agent/terraform-ibm-scc-workload-protection-agent/tests/pr_test.go:78
        	Error:      	Should be false
        	Test:       	TestRunBasicUpgradeExample
        	Messages:   	Resource(s) identified to be updated 
        	            	Name: pool
        	            	Address: module.ocp_base[0].ibm_container_vpc_worker_pool.pool["default"]
        	            	Actions: [update]
        	            	DIFF:
        	            	  Before: 
        	            		{"orphan_on_delete":null}
        	            	  After: 
        	            		{"orphan_on_delete":true}

this is expected, because the change was introduced in terraform-ibm-modules/terraform-ibm-base-ocp-vpc@ef733dd#diff-dc46acf24afd63ef8c556b77c126ccc6e578bc87e3aa09a931f33d9bf2532fbbR370

it is a part of examples and we are safe to skip the upgrade test

@akocbek
Copy link
Contributor Author

akocbek commented Mar 7, 2025

/run pipeline

@akocbek
Copy link
Contributor Author

akocbek commented Mar 7, 2025

TestSecureExampleInSchematic test failed.

=== NAME  TestSecureExampleInSchematic
    schematics.go:513: [SCHEMATICS] ... still waiting for job DESTROY to complete: 3 minutes
    schematics.go:513: [SCHEMATICS] ... still waiting for job DESTROY to complete: 4 minutes
    schematics.go:513: [SCHEMATICS] ... still waiting for job DESTROY to complete: 5 minutes
    schematics.go:513: [SCHEMATICS] ... still waiting for job DESTROY to complete: 6 minutes
    schematics.go:513: [SCHEMATICS] ... still waiting for job DESTROY to complete: 7 minutes
    schematics.go:513: [SCHEMATICS] ... still waiting for job DESTROY to complete: 8 minutes
    schematics.go:513: [SCHEMATICS] ... still waiting for job DESTROY to complete: 9 minutes
    schematics.go:513: [SCHEMATICS] ... still waiting for job DESTROY to complete: 10 minutes
    schematics.go:522: [SCHEMATICS] The status of job DESTROY is: COMPLETED
--- FAIL: TestSecureExampleInSchematic (6329.12s)

schematics UI shows that all resources has been destroyed successfully.
image

@ocofaigh
Copy link
Member

ocofaigh commented Mar 9, 2025

/run pipeline

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