Skip to content

incus cluster set fails when there is only one node #2963

@bensmrs

Description

@bensmrs

Is there an existing issue for this?

  • There is no existing issue for this bug

Is this happening on an up to date version of Incus?

  • This is happening on a supported version of Incus

Incus system details

HEAD

Instance details

No response

Instance log

No response

Current behavior

if clientNodes+1 >= nodesCount {

always passes when the node count is 1.

I’m wondering why we are i) skipping the current node in the DB tx and ii) not checking whether database-client is asked for the current node.

Expected behavior

No response

Steps to reproduce

# incus cluster set foobar user.foo=bar
Error: Assigning the 'database-client' role to all nodes is not allowed

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions