Closed webvictim closed 2 weeks ago
i have same problem.
i have same problem.
same problem here. Any update?
for context, i want to deploy this on docker swarm and using traefik
This also happens on 16.2.0 when changing teleport.nodename
(with proxy_service.https_keypairs
set):
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z INFO [PROC:1] Initiating new sync rotation state cycle after backoff. pid:2156.1 backoff_time:17.094732199s service/connect.go:719
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z INFO [PROC:1] Rotation in progress, updating SSH principals. pid:2156.1 identity:Admin additional_principals:[ip-172-31-4-69] current_principals:[3bf51591-a1c8-4871-8dcc-be6fdad8c5da ip-172-31-4-118] service/connect.go:905
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z INFO [PROC:1] Service has updated principals and DNS Names, going to request new principals and update. pid:2156.1 identity:Admin principals:[ip-172-31-4-69] dns_names:[*.teleport.cluster.local teleport.cluster.local] service/connect.go:1000
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z DEBU Generated SSH host certificate for role Admin with principals: [3bf51591-a1c8-4871-8dcc-be6fdad8c5da ip-172-31-4-69]. keygen/keygen.go:128
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z DEBU [CA] Generating TLS certificate common_name:3bf51591-a1c8-4871-8dcc-be6fdad8c5da.leaf1.gus.devteleport.com dns_names:[ip-172-31-4-69 *.teleport.cluster.local teleport.cluster.local] key_usage:5 not_after:2034-08-28 19:05:25.655616833 +0000 UTC tlsca/ca.go:1229
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z INFO [PROC:1] Rotation in progress, updating SSH principals. pid:2156.1 identity:Instance additional_principals:[ip-172-31-4-69] current_principals:[3bf51591-a1c8-4871-8dcc-be6fdad8c5da.leaf1.gus.devteleport.com 3bf51591-a1c8-4871-8dcc-be6fdad8c5da ip-172-31-4-118.leaf1.gus.devteleport.com ip-172-31-4-118 localhost 127.0.0.1 ::1] service/connect.go:905
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z INFO [PROC:1] Service has updated principals and DNS Names, going to request new principals and update. pid:2156.1 identity:Instance principals:[ip-172-31-4-69] dns_names:[] service/connect.go:1000
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z DEBU [PROC:1] Generating new key pair. pid:2156.1 identity:Instance reason:re-register service/connect.go:346
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z DEBU Generated SSH host certificate for role Instance with principals: [3bf51591-a1c8-4871-8dcc-be6fdad8c5da.leaf1.gus.devteleport.com 3bf51591-a1c8-4871-8dcc-be6fdad8c5da ip-172-31-4-69.leaf1.gus.devteleport.com ip-172-31-4-69 localhost 127.0.0.1 ::1]. keygen/keygen.go:128
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z DEBU [CA] Generating TLS certificate common_name:3bf51591-a1c8-4871-8dcc-be6fdad8c5da.leaf1.gus.devteleport.com dns_names:[ip-172-31-4-69] key_usage:5 not_after:2034-08-28 19:05:25.686153637 +0000 UTC tlsca/ca.go:1229
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z DEBU [PROC:1] Deleted generated key pair. pid:2156.1 identity:Instance reason:re-register service/connect.go:332
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z INFO [PROC:1] Rotation in progress, updating SSH principals. pid:2156.1 identity:Proxy additional_principals:[ip-172-31-4-69 leaf1.gus.devteleport.com 0.0.0.0 localhost 127.0.0.1 ::1 remote.kube.proxy.teleport.cluster.local] current_principals:[3bf51591-a1c8-4871-8dcc-be6fdad8c5da.leaf1.gus.devteleport.com 3bf51591-a1c8-4871-8dcc-be6fdad8c5da ip-172-31-4-118.leaf1.gus.devteleport.com ip-172-31-4-118 localhost 127.0.0.1 ::1 leaf1.gus.devteleport.com remote.kube.proxy.teleport.cluster.local] service/connect.go:905
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z INFO [PROC:1] Service has updated principals and DNS Names, going to request new principals and update. pid:2156.1 identity:Proxy principals:[ip-172-31-4-69 leaf1.gus.devteleport.com 0.0.0.0 localhost 127.0.0.1 ::1 remote.kube.proxy.teleport.cluster.local] dns_names:[*.teleport.cluster.local teleport.cluster.local *.leaf1.gus.devteleport.com] service/connect.go:1000
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z DEBU [PROC:1] Returning existing key pair for. pid:2156.1 identity:Proxy reason:re-register service/connect.go:343
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z WARN [PROC:1] Failed to sync rotation state. pid:2156.1 error:[
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: ERROR REPORT:
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: Original Error: *trace.BadParameterError missing parameter hostname
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: Stack Trace:
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/utils/utils.go:286 github.com/gravitational/teleport/lib/utils.Host
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/auth/auth.go:4291 github.com/gravitational/teleport/lib/auth.(*Server).GenerateHostCerts
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/auth/register.go:122 github.com/gravitational/teleport/lib/auth.ReRegister
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/connect.go:414 github.com/gravitational/teleport/lib/service.(*TeleportProcess).reRegister
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/connect.go:1001 github.com/gravitational/teleport/lib/service.(*TeleportProcess).rotate
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/connect.go:871 github.com/gravitational/teleport/lib/service.(*TeleportProcess).syncServiceRotationState
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/connect.go:850 github.com/gravitational/teleport/lib/service.(*TeleportProcess).syncRotationState
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/connect.go:813 github.com/gravitational/teleport/lib/service.(*TeleportProcess).syncRotationStateAndBroadcast
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/connect.go:745 github.com/gravitational/teleport/lib/service.(*TeleportProcess).syncRotationStateCycle
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/connect.go:709 github.com/gravitational/teleport/lib/service.(*TeleportProcess).periodicSyncRotationState
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/supervisor.go:588 github.com/gravitational/teleport/lib/service.(*LocalService).Serve
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: github.com/gravitational/teleport/lib/service/supervisor.go:313 github.com/gravitational/teleport/lib/service.(*LocalSupervisor).serve.func1
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: runtime/asm_amd64.s:1695 runtime.goexit
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: User Message: missing parameter hostname] service/connect.go:818
Aug 30 19:05:25 ip-172-31-4-69 teleport[2156]: 2024-08-30T19:05:25Z WARN [PROC:1] Sync rotation state cycle failed. pid:2156.1 retry_interval:10s service/connect.go:714
This just repeats on a loop forever and the old nodename continues to be used.
Config change:
version: v3
teleport:
- nodename: ip-172-31-4-118
+ nodename: ip-172-31-4-69
data_dir: /var/lib/teleport
log:
output: stderr
severity: INFO
format:
output: text
ca_pin: ""
diag_addr: ""
auth_service:
enabled: "yes"
listen_addr: 0.0.0.0:3025
cluster_name: root.teleport.example.com
proxy_listener_mode: multiplex
authentication:
second_factor: on
webauthn:
rp_id: root.teleport.example.com
ssh_service:
enabled: "yes"
proxy_service:
enabled: "yes"
web_listen_addr: 0.0.0.0:3080
public_addr: root.teleport.example.com:443
https_keypairs:
- key_file: /etc/letsencrypt/live/root.teleport.example.com/privkey.pem
cert_file: /etc/letsencrypt/live/root.teleport.example.com/fullchain.pem
https_keypairs_reload_interval: 12h
acme: {}
proxy_protocol: on
This issue should be fixed once https://github.com/gravitational/teleport/pull/46087 gets in. In the meantime, specifying advertise_ip
or explicitly binding a specific network interface rather than 0.0.0.0
will circumvent the bug.
Expected behavior
Changing the
public_addr
of a cluster'sproxy_service
should result in new self-signed certificates being generated for theProxy
without error.Current behavior:
Changing
proxy_service.public_addr
causes a rotation state error to repeat ad infinitum:Config change was as shown here:
Changing
teleport.nodename
also has a similar effect.Bug details: