Bug 2162095
| Summary: | [vSphere on Nutanix] cannot change the value of "thin_provisioned" - (old: true newValue: false) | ||
|---|---|---|---|
| Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Tyler Bevan <tyler.bevan> |
| Component: | Cluster Lifecycle | Assignee: | Le Yang <leyan> |
| Status: | NEW --- | QA Contact: | Hui Chen <huichen> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhacm-2.6 | CC: | daliu, dhuynh, jcallen, padillon |
| Target Milestone: | --- | Flags: | padillon:
needinfo-
tyler.bevan: needinfo? (daliu) |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tyler Bevan
2023-01-18 18:57:02 UTC
Retagging to cluster-lifecycle as it relates to cluster provisioning @efried Could you help to take a look? This falls squarely in the installer's wheelhouse. @padillon could you find a pair of eyes for this please? @tyler.bevan I have create a discussion in openshift-installer channel about this issue. https://redhat-internal.slack.com/archives/CH06KMDRV/p1675213341255269 And Could you help to try the workaround. "Change install-config diskType to thin" "Making the assumption there is a storage policy that is forcing thin underneath terraform. Which it does not support well" Note: In ACM env, in order to update install-config, you need to update the secret named <Cluster Namespace>/<Cluster Namespace>-install-config An install attempt using "diskType: thin" on both machine pools did not resolve the issue. The error message was identical to the original log. I don't see any way to customize the bootstrap vm's specifications in the documentation for install-config, which seems to be where the failure is. As a side note, the documentation at https://github.com/openshift/installer/blob/master/docs/user/vsphere/customization.md#machine-pools is a bit unclear on if the key is disk_type or diskType. I did test it both ways to be sure. Tyler For context here is the sanitized install-config:
---
apiVersion: v1
metadata:
name: ocp-lab
baseDomain:xxxxxxxxxx
controlPlane:
name: master
architecture: amd64
hyperthreading: Enabled
replicas: 3
platform:
vsphere:
cpus: 8
coresPerSocket: 8
memoryMB: 16384
osDisk:
diskSizeGB: 120
disk_type: thin
compute:
- name: worker
hyperthreading: Enabled
architecture: amd64
replicas: 0
platform:
vsphere:
cpus: 4
coresPerSocket: 2
memoryMB: 16384
osDisk:
diskSizeGB: 120
disk_type: thin
platform:
vsphere:
vCenter: xxxxxxxxxxxx
username: xxxxxxxxxx
password: xxxxxxxxxxxxxxxxxxx
datacenter: xxxxxxxxxxxxxxx
defaultDatastore: xxxxxxxxxxxx
folder: /xxxxxxxx/vm/Openshift/ocp-lab
cluster: xxxxxxxx
apiVIP: 10.10.x.x
ingressVIP: 10.10.x.x
network: xxxxxxxxxxxxxxxxx
@jcallen Any more suggestion ? Sorry I didn't see the reporter was not RH employee, repeating what I already stated in a private comment... The install-config was incorrect, diskType is not at the machinepool, it is in the platform spec https://github.com/openshift/installer/blob/master/pkg/types/vsphere/platform.go#L92 e.g. platform: vsphere: vCenter: xxxxxxxxxxxx username: xxxxxxxxxx password: xxxxxxxxxxxxxxxxxxx datacenter: xxxxxxxxxxxxxxx defaultDatastore: xxxxxxxxxxxx folder: /xxxxxxxx/vm/Openshift/ocp-lab cluster: xxxxxxxx apiVIP: 10.10.x.x ingressVIP: 10.10.x.x network: xxxxxxxxxxxxxxxxx diskType: thin If this still fails we will need a bug created in Jira assigned to installer. Please link the bug here. We previously had issues with the vsphere terraform provider but I had thought those were resolved. This is also probably related to: https://kb.vmware.com/s/article/68107 Changing state of objects that terraform created is a good way of having a failure. @tyler.bevan Could you help to try again follow https://bugzilla.redhat.com/show_bug.cgi?id=2162095#c10 @daliu That change does appear to fix the problem, as the provision finished as expected. So, should we just presume that if you're on VMWare with a Nutanix storage backend that adding diskType: thin to the platform spec is mandatory? I can put a bug in to fix it (will be changed for 4.13 once the PR below is merged) Just a single line change for terraform to ignore disk type state issue. https://github.com/openshift/installer/pull/6770/files#diff-b4dbed356c5acdaefe0d1716089c2fa5efacfa5cb6ca4ad2000e1b5a5ddb7194R55 Not the owner of this BZ I believe it can be closed. I will work this one in jira: https://issues.redhat.com/browse/OCPBUGS-7551 |