[BUG] azure rke1 node driver not working - websocket: close 1006 (abnormal closure): unexpected EOF
#45398
Labels
area/provisioning-rke1
Provisioning issues with RKE1
kind/bug
Issues that are defects reported by users or that we know have reached a real release
kind/bug-qa
Issues that have not yet hit a real release. Bugs introduced by a new feature or enhancement
status/release-blocker
team/hostbusters
The team that is responsible for provisioning/managing downstream clusters + K8s version support
team/rke1
Rancher Server Setup
Information about the Cluster
User Information
Tested with Admin and Standard user, cluster owner
Describe the bug
provisioning using azure node driver is not working as expected, hanging after the last node has registered with the cluster in a new cluster setup, stuck in a
waiting
stateTo Reproduce
provision a node driver cluster using rke1 with default settings for azure
Result
all nodes are active, but cluster stuck in a waiting state
Expected Result
cluster should come to an active state
Screenshots
Additional context
logs from local cluster that may be relevant:
currently tested using 1 node per role
not affecting linode node driver
The text was updated successfully, but these errors were encountered: