Illegal Base64 Data at Input Byte 0 during OKD Bootstrap

Jess4Tech commented 1 year ago

Describe the bug When trying to install okd 4.13.0-0.okd-2023-05-22-052007, the bootstrap node repeatedly fails with "illegal base64 data at input byte 0".

It's UPI. I made all the DNS mappings and such.

How reproducible It's happened whenever I try it, but I'm not sure if that's reproducible.

A whole loop of the issue https://pastebin.com/xJQ1XPdh

My install-config.yaml

apiVersion: v1
baseDomain: jessnuko.lan
metadata:
  name: okd

compute:
- hyperthreading: Enabled
  name: worker
  replicas: 0

controlPlane:
  hyperthreading: Enabled
  name: master
  replicas: 3

networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16

platform:
  none: {}

fips: false

pullSecret: '{"auths":{"fake":{"auth": "bar"}}}'
sshKey: 'ssh-ed25519 AAAA....'

Jess4Tech commented 1 year ago

To thicken the plot some more, I tried instead to use the pullSecret on the page of the okd project (pullSecret: '{"auths":{"fake":{"auth":"aWQ6cGFzcwo="}}}') instead of what the guide I was following said (pullSecret: '{"auths":{"fake":{"auth": "bar"}}}'), and instead of dying on invalid base64 data, the bootkube service kept failing on F0604 17:11:38.699336 1 render.go:53] problem with featuregate manifests: cannot return FeatureGate without rendered manifests. The full log from a loop is at https://pastebin.com/uQyaR9Ez.

Jess4Tech commented 1 year ago

This was apparently caused by an intermittent transmission/connection failure between the nodes. After fixing those issues, it worked perfectly. My apologies for any caused inconvenience.

okd-project / okd-scos

Illegal Base64 Data at Input Byte 0 during OKD Bootstrap #12