Skip to content

deactivating a non-existent node leaves inconsistent state #4008

Open
@traylenator

Description

@traylenator

Describe the Bug

Deactivating a not existing node .e.g

puppet node deactivate notexisting.example.ch

Create an entry in the nodes table:

/pdb/query/v4/nodes/notexisting.example.ch                                                                                                
{                                                                                                                                                                                           
  "deactivated" : "2024-10-02T12:57:22.565Z",                                                                                                                                               
  "latest_report_hash" : null,
  "facts_environment" : null,
  "cached_catalog_status" : null,

however the entry never appears in the inventory.

i.e

inventory[certname] { node_state = "inactive" }

never contains the node notexisting.example.ch.

Expected Behavior

It seems inconsistent that you can have a node that is nor present in the inventory.

Environment

  • Version PuppetDB 8.7

Additional Context

As highlighted on slack:

It is likely not showing up in inventory because all three of fact, catalog, and report are null.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions