You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
root@controller-0:~# puppet agent -t
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error:
Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error:
Error while evaluating a Resource Statement,
Cannot alias Package[kubernetes-kube-controller-manager] to [nil, "kubernetes-server", nil] at
(file: /etc/puppetlabs/code/environments/production/modules/k8s/manifests/binary.pp, line: 42);
resource ["Package", nil, "kubernetes-server", nil] already declared (file: /etc/puppetlabs/code/environments/production/modules/k8s/manifests/binary.pp, line: 42)
(file: /etc/puppetlabs/code/environments/production/modules/k8s/manifests/binary.pp, line: 42, column: 7)
(file: /etc/puppetlabs/code/environments/production/modules/k8s/manifests/server/controller_manager.pp, line: 20) on node controller-0.example.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
i think this might somehow connect to the k8s::binary define and with setting a different title and name for the package resource in it. but i don't know how to fix it, because i don't know why title and name are different in the first place.
switched to loose for native_packaging and then use packages only for etcd and cni_plugins. I mirrored the k8s binaries internally and changed the native_url_template
when i run this:
i get this:
i think this might somehow connect to the k8s::binary define and with setting a different title and name for the package resource in it. but i don't know how to fix it, because i don't know why title and name are different in the first place.
puppet-k8s/manifests/binary.pp
Lines 42 to 45 in a444fdf
used os:
The text was updated successfully, but these errors were encountered: