unsupported protocol error raised calling init

[frobware]

Since PR #280 I get:

$ tectonic init --config ~/tectonic.libvirt.yaml 
FATA[0000] Get : unsupported protocol scheme ""

Debugging a little I see the following:

  DEBU[0034] nexting                                       layer=debugger
> github.com/openshift/installer/pkg/types/config/libvirt.(*Libvirt).UseCachedImage() /home/aim/go-projects/openshift-installer/src/github.com/openshift/installer/pkg/types/config/libvirt/cache.go:48 (PC: 0xb611fc)
    43:	
    44:		cache := diskcache.New(cacheDir)
    45:		transport := httpcache.NewTransport(cache)
    46:		resp, err := transport.Client().Get(libvirt.Image)
    47:		if err != nil {
=>  48:			return err
    49:		}
    50:		if resp.StatusCode != 200 {
    51:			return fmt.Errorf("%s while getting %s", resp.Status, libvirt.Image)
    52:		}
    53:		defer resp.Body.Close()
(dlv) p err
error(*net/url.Error) *{
	Op: "Get",
	URL: "",
	Err: error(*net/http.badStringError) *{
		what: "unsupported protocol scheme",
		str: "",},}
(dlv) p cacheDir
"/home/aim/.cache/openshift-install/libvirt"

[frobware]

/cc @wking

[steveej]

/assign

[wking]

What URI are you passing in? Maybe you are missing a file:// prefix.

[frobware]

What URI are you passing in? Maybe you are missing a file:// prefix.

admin:
  email: a@b.c
  password: redacted
  sshKey: "ssh-rsa ..."

# The base DNS domain of the cluster. It must NOT contain a trailing period. Some
# DNS providers will automatically add this if necessary.
#
# Example: `openshift.example.com`.
#
# Note: This field MUST be set manually prior to creating the cluster.
baseDomain: tt.testing

libvirt:
  # You must specify an IP address here that libvirtd is listening on,
  # and that the cluster-api controller pod will be able to connect
  # to.  Often 192.168.122.1 is the default for the virbr0 interface.
  uri: qemu+tcp://192.168.122.1/system
  network:
    name: tectonic
    ifName: tt0
    ipRange: 192.168.124.0/24
  image: /home/aim/rhcos-qemu.qcow2

ca:
  # (optional) The content of the PEM-encoded CA certificate, used to generate Tectonic Console's server certificate.
  # If left blank, a CA certificate will be automatically generated.
  # cert:

  # (optional) The content of the PEM-encoded CA key, used to generate Tectonic Console's server certificate.
  # This field is mandatory if `ca_cert` is set.
  # key:

  # (optional) The algorithm used to generate ca_key.
  # The default value is currently recommended.
  # This field is mandatory if `ca_cert` is set.
  # keyAlg: RSA

iscsi:
  # (optional) Start iscsid.service to enable iscsi volume attachment.
  # enabled: false

master:
  nodePools:
    - master

# The name of the cluster.
# If used in a cloud-environment, this will be prepended to `baseDomain` resulting in the URL to the Tectonic console.
#
# Note: This field MUST be set manually prior to creating the cluster.
# Warning: Special characters in the name like '.' may cause errors on OpenStack platforms due to resource name constraints.
name: gfs1

networking:
  # (optional) This declares the MTU used by Calico.
  # mtu:

  # (optional) This declares the IP range to assign Kubernetes pod IPs in CIDR notation.
  podCIDR: 10.2.0.0/16

  # (optional) This declares the IP range to assign Kubernetes service cluster IPs in CIDR notation.
  # The maximum size of this IP range is /12
  serviceCIDR: 10.3.0.0/16

  # (optional) Configures the network to be used in Tectonic. One of the following values can be used:
  #
  # - "flannel": enables overlay networking only. This is implemented by flannel using VXLAN.
  #
  # - "canal": enables overlay networking including network policy. Overlay is implemented by flannel using VXLAN. Network policy is implemented by Calico.
  #
  # - "calico-ipip": [ALPHA] enables BGP based networking. Routing and network policy is implemented by Calico. Note this has been tested on baremetal installations only.
  #
  # - "none": disables the installation of any Pod level networking layer provided by Tectonic. By setting this value, users are expected to deploy their own solution to enable network connectivity for Pods and Services.
  # type: flannel

nodePools:
    # The number of master nodes to be created.
    # This applies only to cloud platforms.
  - count: 1
    name: master

    # The number of worker nodes to be created.
    # This applies only to cloud platforms.
  - count: 1
    name: worker

# The platform used for deploying.
platform: libvirt

# The pull secret in JSON format.
# This is known to be a "Docker pull secret" as produced by the docker login [1] command.
# A sample JSON content is shown in [2].
# You can download the pull secret from your Account overview page at [3].
#
# [1] https://docs.docker.com/engine/reference/commandline/login/
#
# [2] https://coreos.com/os/docs/latest/registry-authentication.html#manual-registry-auth-setup
#
# [3] https://account.coreos.com/overview
pullSecretPath: /path/to/config.json
worker:
  nodePools:
    - worker

[wking]

image: /home/aim/rhcos-qemu.qcow2

This should be image: file:///home/aim/rhcos-qemu.qcow2 since #271 (see also #282).

[frobware]

This should be image: file:///home/aim/rhcos-qemu.qcow2 since #271 (see also #282).

Oh! OK, thanks. Apologies.

[steveej]

Oh! OK, thanks. Apologies.

No need for apologies ;-) I've added it to the troubleshooting docs so it's documented somewhere.

[wking]

I've added it to the troubleshooting docs so it's documented somewhere.

Probably not worth doing this, with the knob going away soon (#310, here).