Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vSphere UPI: Update icon on status "Provisioned as node" for new machines not going away #245

Closed
jomeier opened this issue Jul 5, 2020 · 6 comments

Comments

@jomeier
Copy link
Contributor

jomeier commented Jul 5, 2020

Hi,

today I managed to get automatic worker creation on vSphere UPI working. Even with automatic creation of their hostnames because we don't get them from our DHCP server.

The Machines are reported as "Provisioned as node" and have a refresh/update icon left of them:

machineset

What does that mean? Is OKD doing something or has it successfully finished creating this machines?

If the latter than the icon should be different in my opinion.

Verision: 4.5.0-0.okd-2020-07-02-103539

Greetings,

Josef

@jomeier jomeier changed the title vSphere UPI: Update icon on status "Provisioned as nodes" for new machines not going away vSphere UPI: Update icon on status "Provisioned as node" for new machines not going away Jul 5, 2020
@vrutkovs
Copy link
Member

vrutkovs commented Jul 6, 2020

"Provisioned as node" is the final state - machine has been created, booted and registered itself as node.
Agree, checkmark on UI would fit better than a refresh-like icon - mind filing a bugzilla for console about that?

@jomeier
Copy link
Contributor Author

jomeier commented Jul 6, 2020

@vrutkovs
Copy link
Member

vrutkovs commented Jul 7, 2020

Thanks! Lets track this in the bugzilla

@vrutkovs vrutkovs closed this as completed Jul 7, 2020
@jomeier
Copy link
Contributor Author

jomeier commented Jul 7, 2020

openshift/console#5901

Nice !

@kai-uwe-rommel
Copy link

@jomeier Could you please describe what you needed to do to get automatic worker creation on vSphere UPI? Thanks!

@jomeier
Copy link
Contributor Author

jomeier commented Jul 14, 2020

Hi Kai Uwe,

we filled out the ProviderSpec for vSphere. You can use the MachineSet resources that are contained in OKD after the installation as an example. I remember that one field was missing there that is important.

You also must use a FCOS image that supports Ignition 2.3.0 (Spec 3.0.0) as a template for your workers.

I can post a sample tomorrow.

The most important thing was to get RBAC working on vSphere, because that’s a ... challenge 😁

binnes added a commit to binnes/okd that referenced this issue Jul 11, 2023
* Add docker/podman instructions for site update and fix broken links after switch to MkDocs site (okd-project#238) (okd-project#2)

* move from master to main branch

* remove blog entry re creating blog on old site

* Add site README

* add CNAME in docs so gets published

* Delete CNAME

* fix CNAME for production site

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

* fixed links re MkDocs going live + container tooling instructions

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

* added Windows support for docker based tooling

Signed-off-by: Brian Innes <brian@binnes.me.uk>

* added podman instructions

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

* tidy up commands

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

Co-authored-by: Brian Innes <brian@binnes.me.uk>

Co-authored-by: Brian Innes <brian@binnes.me.uk>

* added primary working group information

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

* add missing links

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

* fix branch name

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

* convert pdf links to relative links

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

* update working group overview

Signed-off-by: Brian Innes <binnes@uk.ibm.com>

Co-authored-by: Brian Innes <brian@binnes.me.uk>
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

No branches or pull requests

3 participants