rapid-flag-87720
03/03/2023, 7:40 PMharvester-management:/home/rancher # kubectl get vmwaresource.migration
NAME STATUS
vcsim clusterNotReady
careful-dusk-92915
03/06/2023, 4:32 AMcareful-dusk-92915
03/06/2023, 4:38 AMloud-apartment-45889
03/08/2023, 2:21 AMquaint-alarm-7893
03/08/2023, 2:54 AMloud-apartment-45889
03/08/2023, 11:00 AMloud-apartment-45889
03/08/2023, 11:12 AMbig-judge-33880
03/10/2023, 8:30 PM[ 76.204319] A link change request failed with some changes committed already. Interface vm-br may have been left with an inconsistent configuration, please check.
controller:
time="2023-03-10T20:03:15Z" level=error msg="error syncing 'har-04': handler harvester-network-vlanconfig-controller: set up VLAN failed, vlanconfig: har-04, node: har-04, error: ensure bridge vm-br failed, error: set vlan filtering failed, error: invalid argument, iface: &{0xc0006de140}, requeuing"
I0310 20:03:15.252249 1 controller.go:75] vlan config har-04 has been changed, spec: {Description: ClusterNetwork:vm NodeSelector:map[<http://kubernetes.io/hostname:har-04|kubernetes.io/hostname:har-04>] Uplink:{NICs:[eno1 eno2] LinkAttrs:0xc001c85e30 BondOptions:0xc00052ad50}}
The associated bond is brought up just fine, any ideas what could be causing such a scenario?quaint-alarm-7893
03/10/2023, 8:39 PMdry-animal-96145
03/14/2023, 1:41 AMquaint-alarm-7893
03/14/2023, 7:59 PMquaint-alarm-7893
03/14/2023, 7:59 PMlittle-dress-13576
03/15/2023, 11:41 PMubuntu
user password, and allow console login..hundreds-evening-84071
03/15/2023, 11:52 PMsalmon-rainbow-35065
03/16/2023, 2:15 PMkind-nest-23311
03/16/2023, 9:44 PMquaint-alarm-7893
03/17/2023, 4:55 PMlively-zoo-40381
03/20/2023, 9:30 AMlively-zoo-40381
03/20/2023, 11:46 AMlively-zoo-40381
03/20/2023, 11:49 AMlively-zoo-40381
03/20/2023, 11:51 AMlively-zoo-40381
03/20/2023, 11:52 AMlively-zoo-40381
03/20/2023, 11:54 AMlively-zoo-40381
03/20/2023, 12:59 PMNormal Pulling 39m (x2 over 40m) kubelet Pulling image "rancher/harvester-cluster-repo:v1.1.1"
Normal BackOff 39m (x3 over 40m) kubelet Back-off pulling image "rancher/harvester-cluster-repo:v1.1.1"
Warning Failed 39m (x3 over 40m) kubelet Error: ImagePullBackOff
Normal Pulling 37m (x4 over 39m) kubelet Pulling image "rancher/harvester-cluster-repo:v1.1.1"
Warning Failed 37m (x4 over 39m) kubelet Failed to pull image "rancher/harvester-cluster-repo:v1.1.1": rpc error: code = Unknown desc = failed to pull and unpack image "<http://docker.io/rancher/harvester-cluster-repo:v1.1.1|docker.io/rancher/harvester-cluster-repo:v1.1.1>": failed to resolve reference "<http://docker.io/rancher/harvester-cluster-repo:v1.1.1|docker.io/rancher/harvester-cluster-repo:v1.1.1>": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Warning Failed 37m (x4 over 39m) kubelet Error: ErrImagePull
Warning Failed 37m (x6 over 38m) kubelet Error: ImagePullBackOff
Normal BackOff 4m6s (x154 over 38m) kubelet Back-off pulling image "rancher/harvester-cluster-repo:v1.1.1"
lively-zoo-40381
03/21/2023, 9:33 AMlively-zoo-40381
03/21/2023, 10:48 AMlively-zoo-40381
03/21/2023, 11:06 AMrefined-analyst-8898
03/21/2023, 3:32 PMwaiting for viable init nodeConditions log:
[Disconnected] Cluster agent is not connected
little-dress-13576
03/21/2023, 3:59 PMrefined-analyst-8898
03/21/2023, 5:08 PMrefined-analyst-8898
03/21/2023, 5:08 PMfailed to force format device 3db9feafc2382c78d6a3a70815680a72: stderr: mke2fs 1.43.8 (1-Jan-2018) /dev/sdc is apparently in use by the system; will not make a filesystem here! , err: exit status 1