OSPRH-16753: Create an independent vars for graphing's deployment#696
OSPRH-16753: Create an independent vars for graphing's deployment#696MiguelCarpio wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
|
@MiguelCarpio: This pull request references OSPRH-16753 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: MiguelCarpio The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @MiguelCarpio. Thanks for your PR. I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b8ed6640a289451491b99dd1c34d3c26 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 25m 48s |
|
/ok-to-test |
|
the autoscaling failure is unrelated to the change, but it's interesting. What we're trying to do in the test is to create a stack, which adds a VM anytime the average load for all VMs in the stack is above 50%. I can see the values of the CPU load for each minute in the log. We start with 1 VM, we create load, it gets to 100% CPU and a second VM appears. Ideally the first VM should stay on 100% CPU and a third VM should appear, but instead it fell to 0% or 1% (I can't distinguish which VM is which from the logs) even though the load on the first VM should still be the same. This is a little concerning and it's something we should keep an eye on going forwards. This is also the first failure like that I've seen. I'll keep an eye out for that as the CI Watcher this week. |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/da0485d5d75a4c1589c09d3e604691d5 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 13m 30s |
|
Another failure. And it looks basically the same. |
|
recheck let's give it another chance |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
The |
4 participants
What does this PR do?
Create an independent vars for graphing's deployment
Why do we need it?
For independent graphing's deployment that will allow us to run specific graphing tests on it.