Vsphere UPI doesn't inject network static files

[chechuironman]

hey guys,

I'm running the vsphere scripts, and works fine, but network files for static IPs are not injected into the CoreOS 4.2

Version

[root@terraform ocp4.2]# ./openshift-install version
./openshift-install v4.2.0
built from commit 90ccb37ac1f85ae811c50a29f9bb7e779c5045fb
release image quay.io/openshift-release-dev/ocp-release@sha256:c5337afd85b94c93ec513f21c8545e3f9e36a227f55d41bc1dfb8fcc3f2be129

Platform:

What happened?

Network static files are not injected into de OS CoreOS4.2

What you expected to happen?

static IPs

How to reproduce it (as minimally and precisely as possible)?

Run the tf scripts with the nodes IPs defined on the variables file

[vishnoisuresh]

yea, I have got the same issue.

[ooOOJavaOOoo]

we are seeing this issue as well.. only available workaround is to create an iso per static ip..

[fherbert]

We had this problem with RHCOS RHCOS_42.80.20190801, updating to RHCOS_42.80.20190828.2 or RHCOS_42.80.20191002.0 fixed static ip config using ignition for us.

[crissonpl]

I have the same issue both with RHCOS latest 4.1 and 4.2 images.

Some weeks ago with the same images it was working fine and now after I cloned the repo again it doesn't assign static IPs.

In the VM Options of the VMs I don't see the fields - guestinfo.ignition.config.data neither guestinfo.ignition.config.data.encoding. Should the terraform scrip create them?

[bortek]

Same here. Static IPs renot being ssigned and guestinfo.ignition.config.dataand enconding are not set on the VM guests. Are these the right parameters, jhave they changed their name inthe VM ?

It is this block in the machine/main.tf that should do the magic

vapp {
properties {
"guestinfo.ignition.config.data" = "${base64encode(data.ignition_config.ign.*.rendered[count.index])}"
"guestinfo.ignition.config.data.encoding" = "base64"
}
}

[David-Igou]

Can we get some clarity on if true static IPs are possible via ignition files? I suspect the vSphere UPI terraform requires a DHCP server to be available, but doesn't clearly document it. The download of the remote ignition file is done at the initram level, which requires networking, but ifgcfg-ens192 is written to after this. takes place.

[crissonpl]

My experience is that you still need DHCP as you wrote. The static IPs config is done after ignition download so the VMs without DHCP and with static IPs configured via ignition were still making a DHCP request

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.