You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
controller is RHEL8, agents are Ubuntu 22.04
Reproduction steps
Create two openstack cloud definitions, one that has valid credentials and another with invalid credentials (bad password)
Notice that no nodes will launch on the cloud with valid credentials until the cloud definition with invalid credentials is either removed or fixed (credential updated)
Expected Results
One failed openstack cloud should not affect another. So when a credential is bad/expired/whatever for one definition, all the other ones that are correctly provisioned should still work.
Actual Results
When one openstack cloud has a bad credential or is otherwise misconfigured such that nodes are unable to launch, no launches will occur on any of the other openstack clouds on the same jenkins node, even if those are provisioned correctly.
Anything else?
Problem should be easy to reproduce with the information above, but if you need any additional information, please let me know!
Are you interested in contributing a fix?
Happy to help anyway I can.
The text was updated successfully, but these errors were encountered:
dbilling
changed the title
An openstack cloud definition that is failing (bad credentials) should not affect other other working openstack clouds
An openstack cloud definition that is failing (e.g. bad credentials) should not affect other other working openstack clouds
Jul 15, 2024
dbilling
changed the title
An openstack cloud definition that is failing (e.g. bad credentials) should not affect other other working openstack clouds
An openstack cloud definition that is failing (e.g. bad credentials) should not affect other working openstack clouds
Jul 15, 2024
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
controller is RHEL8, agents are Ubuntu 22.04
Reproduction steps
Expected Results
One failed openstack cloud should not affect another. So when a credential is bad/expired/whatever for one definition, all the other ones that are correctly provisioned should still work.
Actual Results
When one openstack cloud has a bad credential or is otherwise misconfigured such that nodes are unable to launch, no launches will occur on any of the other openstack clouds on the same jenkins node, even if those are provisioned correctly.
Anything else?
Problem should be easy to reproduce with the information above, but if you need any additional information, please let me know!
Are you interested in contributing a fix?
Happy to help anyway I can.
The text was updated successfully, but these errors were encountered: