metal3-io/ip-address-manager

Unable to run example from README

fhaftmann opened this issue · 5 comments

fhaftmann commented

What steps did you take and what happened:

Tried to replay the example as given in

ip-address-manager/README.md

Line 35 in 2d8ba7f

## Deployment and examples
ff.

Used a fresh k3s 1.25 on a virtual Ubuntu 22.04. as base.

The git commit was 2d8ba7f from a recent state of branch main.

(I tried tags v1.4.0 and api/v1.4.0 but both broke apart even earlier than described here.)

Issues:

  • In

    ip-address-manager/README.md

    Line 50 in 2d8ba7f

    kubectl scale -n capm3-system deployment.v1.apps/metal3-ipam-controller-manager \
    the deployment’s name is given as metal3-ipam-controller-manager but must read ipam-controller-manager

  • Step make run at go run ./main.go fails with

    I0517 10:08:42.475992   21439 listener.go:44] "controller-runtime/metrics: Metrics server is starting to listen" addr="localhost:8080"
I0517 10:08:42.476725   21439 webhook.go:124] "controller-runtime/builder: Registering a mutating webhook" GVK="ipam.metal3.io/v1alpha1, Kind=IPPool" path="/mutate-ipam-metal3-io-v1alpha1-ippool"
I0517 10:08:42.476838   21439 server.go:149] "controller-runtime/webhook: Registering webhook" path="/mutate-ipam-metal3-io-v1alpha1-ippool"
I0517 10:08:42.476970   21439 webhook.go:153] "controller-runtime/builder: Registering a validating webhook" GVK="ipam.metal3.io/v1alpha1, Kind=IPPool" path="/validate-ipam-metal3-io-v1alpha1-ippool"
I0517 10:08:42.477018   21439 server.go:149] "controller-runtime/webhook: Registering webhook" path="/validate-ipam-metal3-io-v1alpha1-ippool"
I0517 10:08:42.477133   21439 webhook.go:124] "controller-runtime/builder: Registering a mutating webhook" GVK="ipam.metal3.io/v1alpha1, Kind=IPAddress" path="/mutate-ipam-metal3-io-v1alpha1-ipaddress"
I0517 10:08:42.477183   21439 server.go:149] "controller-runtime/webhook: Registering webhook" path="/mutate-ipam-metal3-io-v1alpha1-ipaddress"
I0517 10:08:42.477296   21439 webhook.go:153] "controller-runtime/builder: Registering a validating webhook" GVK="ipam.metal3.io/v1alpha1, Kind=IPAddress" path="/validate-ipam-metal3-io-v1alpha1-ipaddress"
I0517 10:08:42.477354   21439 server.go:149] "controller-runtime/webhook: Registering webhook" path="/validate-ipam-metal3-io-v1alpha1-ipaddress"
I0517 10:08:42.477467   21439 webhook.go:124] "controller-runtime/builder: Registering a mutating webhook" GVK="ipam.metal3.io/v1alpha1, Kind=IPClaim" path="/mutate-ipam-metal3-io-v1alpha1-ipclaim"
I0517 10:08:42.477544   21439 server.go:149] "controller-runtime/webhook: Registering webhook" path="/mutate-ipam-metal3-io-v1alpha1-ipclaim"
I0517 10:08:42.477682   21439 webhook.go:153] "controller-runtime/builder: Registering a validating webhook" GVK="ipam.metal3.io/v1alpha1, Kind=IPClaim" path="/validate-ipam-metal3-io-v1alpha1-ipclaim"
I0517 10:08:42.477735   21439 server.go:149] "controller-runtime/webhook: Registering webhook" path="/validate-ipam-metal3-io-v1alpha1-ipclaim"
I0517 10:08:42.477885   21439 main.go:137] "setup: starting manager"
I0517 10:08:42.477948   21439 server.go:217] "controller-runtime/webhook/webhooks: Starting webhook server"
I0517 10:08:42.478061   21439 internal.go:369] "Starting server" path="/metrics" kind="metrics" addr="127.0.0.1:8080"
I0517 10:08:42.478142   21439 internal.go:369] "Starting server" kind="health probe" addr="[::]:9440"
I0517 10:08:42.478223   21439 internal.go:581] "Stopping and waiting for non leader election runnables"
I0517 10:08:42.478247   21439 internal.go:585] "Stopping and waiting for leader election runnables"
I0517 10:08:42.478339   21439 controller.go:186] "Starting EventSource" controller="ippool" controllerGroup="ipam.metal3.io" controllerKind="IPPool" source="kind source: *v1alpha1.IPPool"
I0517 10:08:42.478361   21439 controller.go:186] "Starting EventSource" controller="ippool" controllerGroup="ipam.metal3.io" controllerKind="IPPool" source="kind source: *v1alpha1.IPClaim"
I0517 10:08:42.478374   21439 controller.go:194] "Starting Controller" controller="ippool" controllerGroup="ipam.metal3.io" controllerKind="IPPool"
E0517 10:08:42.479060   21439 source.go:148] "controller-runtime/source: failed to get informer from cache" err="Timeout: failed waiting for *v1alpha1.IPClaim Informer to sync"
I0517 10:08:42.479140   21439 controller.go:228] "Starting workers" controller="ippool" controllerGroup="ipam.metal3.io" controllerKind="IPPool" worker count=10
I0517 10:08:42.479162   21439 controller.go:248] "Shutdown signal received, waiting for all workers to finish" controller="ippool" controllerGroup="ipam.metal3.io" controllerKind="IPPool"
E0517 10:08:42.479429   21439 source.go:148] "controller-runtime/source: failed to get informer from cache" err="Timeout: failed waiting for *v1alpha1.IPPool Informer to sync"
I0517 10:08:42.479483   21439 controller.go:250] "All workers finished" controller="ippool" controllerGroup="ipam.metal3.io" controllerKind="IPPool"
I0517 10:08:42.479505   21439 internal.go:591] "Stopping and waiting for caches"
I0517 10:08:42.479728   21439 internal.go:595] "Stopping and waiting for webhooks"
I0517 10:08:42.479833   21439 internal.go:599] "Wait completed, proceeding to shutdown the manager"
E0517 10:08:42.479904   21439 main.go:139] "setup: problem running manager" err="open /tmp/k8s-webhook-server/serving-certs/tls.crt: no such file or directory"

What did you expect to happen:

The example from the README works, or the README is more explicit about the environment the example is supposed to work within.

Anything else you would like to add:

Environment:

  • Cluster-api version:
  • CAPM3 version:
  • IPAM version: git 2d8ba7f
  • Minikube version:
  • environment (metal3-dev-env or other):
  • Kubernetes version: (use kubectl version): v1.25.9+k3s1

/kind bug

metal3-io-bot commented

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

Rozzii commented

@fhaftmann Cluster API does not support K3s try the examples with K8s please.
Please let us know if running with K8s has helped!

Rozzii commented

/triage needs-information
/kind question

metal3-io-bot commented

@Rozzii: The label(s) kind/question cannot be applied, because the repository doesn't have them.

In response to this:

/triage needs-information
/kind question

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.

fhaftmann commented

@fhaftmann Cluster API does not support K3s try the examples with K8s please. Please let us know if running with K8s has helped!

In the meantime I checked it successfully with our own environment (a complexity I wanted to avoid in the first step).
Maybe the hint that Cluster API does not support K3s could be added to / linked to in the README.