-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.13.z, 4.12.z, 4.11.z, 4.10.z
-
+
-
Moderate
-
No
-
ShiftStack Sprint 258
-
1
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-22106. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-20195. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-13781. The following is the description of the original issue:
—
Description of problem:
While troubleshooting https://issues.redhat.com/browse/OCPBUGS-13300, it is observed that openstack-test "sig-installerSuite_openshift/openstack_The_OpenStack_platform_creates_Worker_nodes_in_a_server_group" fails on multiAZ installation with below reason:
fail [/home/stack/openstack-test/test/extended/openstack/servergroup.go:157]: two Worker Machines have different workerGroupName set Expected <string>: ostest-wzvhw-worker-AZ-1 to equal <string>: ostest-wzvhw-worker-AZ-2 Ginkgo exit error 1: exit with code 1
But as each worker is on one AZ, one server group is created per each.
On openshift side:
$ oc get machines -n openshift-machine-api -o json | jq .items[].spec.providerSpec.value.serverGroupName "ostest-wzvhw-master" "ostest-wzvhw-master" "ostest-wzvhw-master" "ostest-wzvhw-worker-AZ-0" "ostest-wzvhw-worker-AZ-2" "ostest-wzvhw-worker-AZ-1"
On Openstack side:
$ openstack server group list +--------------------------------------+--------------------------+--------------------+ | ID | Name | Policy | +--------------------------------------+--------------------------+--------------------+ | a1922c64-ad74-40a5-8881-bc5e2af7bf64 | ostest-wzvhw-worker-AZ-0 | soft-anti-affinity | | 804de49f-166a-459a-9d1a-aac7b8032218 | ostest-wzvhw-master | soft-anti-affinity | | 1fb4e886-019f-42ca-86cb-8fadceadee9b | ostest-wzvhw-worker-AZ-2 | soft-anti-affinity | | 07ce72c9-4963-4f8c-9959-b3e5d1727724 | ostest-wzvhw-worker-AZ-1 | soft-anti-affinity | +--------------------------------------+--------------------------+--------------------+
How reproducible: Always
Steps to Reproduce: D/S periodic availiabilityzones multijob
Actual results: Test case failing
Expected results: The test should consider the scenario where there are different machinesets with different availabilityZones or at least, should be skipped.
Additional info: on private comment.
- clones
-
OCPBUGS-22106 worker servergroup test failing on multiAZ deployments
- Closed
- is blocked by
-
OCPBUGS-22106 worker servergroup test failing on multiAZ deployments
- Closed
- links to