kubekey icon indicating copy to clipboard operation
kubekey copied to clipboard

local iso not being referenced

Open lbrigman124 opened this issue 1 year ago • 2 comments

What is version of KubeKey has the issue?

3.1.0-alpha.7

What is your os environment?

Rocky 9

KubeKey config file

Sub section of the config:
  arches:
  - amd64
  operatingSystems:
  - arch: amd64
    type: linux
    id: rocky
    version: "9"
    osImage: Rocky Linux release 9.2 (Blue Onyx)
    repository:
      iso:
        localPath: rockylinux-9-amd64-rpms.iso

A clear and concise description of what happend.

When the above section of the kubekey config file is set. The actual file that is being referenced is: ......./kubekey/repository/amd64/rocky/9.3/rocky-9.3-amd64.iso Path prefix is based on the directory where kk is being run from.

Relevant log output

failed: [sample.lab.local] [SyncRepositoryISOFile] exec failed after 2 retries: scp /home/XXXX/kubekey/repository/amd64/rocky/9.3/rocky-9.3-amd64.iso to /tmp/kubekey/rocky-9.3-amd64.iso failed: get file stat failed: stat /home/XXXX/kubekey/repository/amd64/rocky/9.3/rocky-9.3-amd64.iso: no such file or directory
+ exit 1

Additional information

If the directory referenced above is created and the iso is copied to that location. The process works.

Secondary issue: if the version is not a quoted string the ISO process is not used and no output about it is in the logs.

lbrigman124 avatar Feb 22 '24 19:02 lbrigman124

The location being referenced may be due to using kk init os with the -a artifact.tgz However, the artifact file didn't have any ISO images within it.

lbrigman124 avatar Feb 23 '24 17:02 lbrigman124

if you use kk init os with the -a artifact.tgz, which means expecting install os packages from iso file, and the artifact.tgz should have specific iso files in it.

In other words, config

repository:
  iso:
    localPath: rockylinux-9-amd64-rpms.iso

is used when running command kk artifact export, not for command kk init os

will4j avatar May 26 '24 01:05 will4j

For some reason, I had thought I had seen the details in the standard config file for installing. If that is not the case then this can be closed.

lbrigman124 avatar Jul 24 '24 16:07 lbrigman124

close issues. Works as documented.

lbrigman124 avatar Jul 24 '24 16:07 lbrigman124