Skip to content

Conversation

@shwstppr
Copy link
Contributor

@shwstppr shwstppr commented Sep 9, 2020

For CoreOS VM to work properly on VMware, specific root disk controller and NIC adapater type must be specified while registering the template.

Without this combination, resizing root disk fails.

Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
@shwstppr
Copy link
Contributor Author

shwstppr commented Sep 9, 2020

requesting docbuild

@ACSGitBot
Copy link

Your request had been received, i'll go and build the documentation and check the output log for errors.

This shouldn't take long.

@ACSGitBot
Copy link

Build finished. You can review it at: https://acs-www.shapeblue.com/docs/WIP-PROOFING/pr151

Build Log Output:

No log errors found to report.

@yadvr
Copy link
Member

yadvr commented Sep 14, 2020

cc @Pearl1594 @PaulAngus

@PaulAngus
Copy link
Member

The new vSphere integration should use the controller that is specified in the OVF in the first place (to avoid exactly this problem)

@yadvr
Copy link
Member

yadvr commented Sep 23, 2020

cc @andrijapanicsb @nvazquez @Pearl1594 - can you check

@shwstppr
Copy link
Contributor Author

Was facing issue with root disk resize with other disk controller and nic controller combinations.

@yadvr yadvr added this to the 4.15 milestone Sep 24, 2020
@yadvr yadvr merged commit 846c1c1 into apache:master Sep 24, 2020
@shwstppr
Copy link
Contributor Author

With root disk resize I meant when createKubernetesCluster API is used with a value for its noderootdisksize

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants