Unable to ssh Fedora CoreOs Vm Created thorugh Vcloud Director

[Devops-Techstack]

Describe the bug Unable to ssh Fedora CoreOs Vm Created thorugh Vcloud Director.Below error i see in Web console .

Under the same VCD network i can connect to RHEL/Centos machine .

System details

• Bare Metal/QEMU/AWS/GCP/etc. : VMWARE
• Fedora CoreOS version : https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/35.20220116.3.0/x86_64/fedora-coreos-35.20220116.3.0-vmware.x86_64.ova

Ignition config { "ignition": { "version": "3.1.0" }, "networkd": {}, "passwd": { "users": [ { "name": "core", "sshAuthorizedKeys": [ "ssh-rsa ...." ] } ] }, "storage": {}, "systemd": {} }

Additional information Add any other information about the problem here.

[lucab]

Thanks for the report. Your node is booting into an emergency shell, so likely there is some provisioning problem. However your node console is not properly setup for your environment. You can try adjusting console settings as shown in https://docs.fedoraproject.org/en-US/fedora-coreos/emergency-shell/, and then further investigate the underlying provisioning issue.

[Devops-Techstack]

So do i need to set console parameter set from ignition data , as with minimal ignition data also i am getting same error .

[bgilbert]

The reason you're not seeing a proper error message on the console is that it's being sent to the (nonexistent) serial port. If you manually remove console=ttyS0,115200 from the kernel arguments before booting, you'll be able to see the underlying error.

[Devops-Techstack]

Hi, Thanks for the information . So for me Network manager service is failing after the first boot .I am trying to assign static IP to my fedora coreos machine using the below ignition data but it doesn't work . variant: fcos version: 1.4.0 storage: files:

• path: /etc/NetworkManager/system-connections/ens2.nmconnection mode: 0600 contents: inline: | [connection] id=ens2 type=ethernet interface-name=ens2 [ipv4] address1=* dhcp-hostname=** dns=9.9.9.9; dns-search= may-fail=false method=manual NM_CONTROLLED=no

[dustymabe]

I'm pretty sure NM_CONTROLLED=no isn't valid for NetworkManager keyfiles.

Here's our example configs for setting up a static IP: https://docs.fedoraproject.org/en-US/fedora-coreos/sysconfig-network-configuration/#_butane_config

[Devops-Techstack]

For me even if i try to assign static IP through above ignition data , i am not able to ping any of the public Ip or google.com. I see in ifconfig command the IP is getting assigned now .

[Devops-Techstack]

I am provisioning these Fedora core os machines from Vcloud director vmware .So instead of static Ip configuration is there any other set up we need to do for accessing public IP

[dustymabe]

Are you setting a default gateway (i.e. default route)?. In the template in the docs it looks like address1=${ip}/${prefix},${gateway}.