-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.12
-
-
-
Critical
-
No
-
ShiftStack Sprint 241, ShiftStack Sprint 242, ShiftStack Sprint 243, ShiftStack Sprint 244, ShiftStack Sprint 245
-
5
-
Rejected
-
False
-
Description of problem:
Not able to add new node in OpenShift cluster due to error message: {"badRequest": {"code": 400, "message": "Availability zone 'cloud-rtp-1-a' is invalid."}}
One thing would like to apprise is that as per our observations after upgrade OCP to 4.12 OCP is trying to create Volume in same zone as of VM, where as it should create volume in nova zone. Failed to create root volume; size=100 imageID=3fce74f1-4c79-497c-9aea-f75775e9e240 err=Bad request with: [POST https://cloud-xxxx.xxx.xxxx:8776/v3/fe4459eca8794f8d89a0a8d07724ecc2/volumes], error message: {"badRequest": {"code": 400, "message": "Availability zone 'cloud-rtp-1-b' is invalid."}} Failed to create root volume; size=100 imageID=3fce74f1-4c79-497c-9aea-f75775e9e240 err=Bad request with: [POST https://cloud-xxxx.xxxx.xxx:8776/v3/fe4459eca8794f8d89a0a8d07724ecc2/volumes], error message: {"badRequest": {"code": 400, "message": "Availability zone 'cloud-rtp-1-c' is invalid."}} This issue started coming only after upgrade to OCP 4.12, It looks like that in 4.10 we do not need to mention any Zone for storage and by default it takes "nova" as default zone if nothing is specified, but in 4.12 I think it is taking reference of availability zone for storage from the zone for VM(1a/1b/1c) itself.