Originally from the User Slack
@Cong_Guo: Hi community, does anyone know what below error mean?
E0425 13:02:59.325076 1 sidecar/controller.go:143] syncing key 'scylla/scylla-fstore-gen-1-com2-ldc1-b-15' failed: can't sync the HostID annotation: can't get token hash: can't get token ring: agent [HTTP 500] std::bad_alloc (std::bad_alloc)
E0425 13:02:59.332063 1 sidecar/controller.go:143] syncing key 'scylla/scylla-fstore-gen-1-com2-ldc1-b-15' failed: can't sync the HostID annotation: can't get token hash: can't get token ring: agent [HTTP 500] std::bad_alloc (std::bad_alloc)
also see below log in scylla-operator
E0424 09:43:15.926139 1 scyllacluster/controller.go:263] syncing key 'scylla/scylla-fstore-gen-1-com2' failed: <http://ScyllaCluster.scylla.scylladb.com|ScyllaCluster.scylla.scylladb.com> "scylla-fstore-gen-1-com2" is invalid: [status.conditions[15].reason: Too long: may not be longer than 1024, status.conditions[17].reason: Too long: may not be longer than 1024]
@Maciej_Zimnoch: it means operator sidecar cannot get host id from Scylla due to bad_alloc exception raised inside Scylla. Looks like you’re having memory issues.
status.conditions[15].reason: Too long: may not be longer than 1024, these kind of errors will be fixed in next Operator release. It cannot update ScyllaCluster status due to this validation error.
@Cong_Guo: > It cannot update ScyllaCluster status due to this validation error.
Does that mean it won’t impact the functionality of scylla-operator, just status couldn’t be updated? May I know if there is a issue opened for it?
@Maciej_Zimnoch: yes, just status isn’t updated, main resource is reconciled.
there’s no issue, just PR fixing other issue with Condition.reason, but it reduces length of it as well: https://github.com/scylladb/scylla-operator/pull/2581
GitHub: Remove Type prefix for aggregated Condition Reasons by zimnx · Pull Request #2581 · scylladb/scylla-operator