Jira (PDB-4682) PuppetDB sync status doesn't get updated when finished

20 views
Skip to first unread message

Austin Blatt (Jira)

unread,
Apr 2, 2020, 2:55:03 PM4/2/20
to puppe...@googlegroups.com
Austin Blatt created an issue
 
PuppetDB / Improvement PDB-4682
PuppetDB sync status doesn't get updated when finished
Issue Type: Improvement Improvement
Affects Versions: PDB 5.2.13
Assignee: Austin Blatt
Created: 2020/04/02 11:54 AM
Priority: Normal Normal
Reporter: Austin Blatt

In an fresh HA install of 2018.1 with only one node the `puppet infra status` command outputs 

PuppetDB: Running on Primary Master Replica, https://shifty-syndrome.delivery.puppetlabs.net:8081/pdb
 
    Info: Transferring 1 catalogs
 
    Info: Transferring 1 facts
 
    Info: Transferring 1 reports

when it is expected to output something like

PuppetDB: Running on Primary Master, https://prewar-aunt.delivery.puppetlabs.net:8081/pdb
 
    Info: Last sync successfully completed 84 seconds ago (at 2020-04-02T18:26:45.702Z)

the puppet infra status pulls information from the PuppetDB status endpoint, which also appears to not get updated.

[root@prewar-aunt ~]# curl -k https://shifty-syndrome.delivery.puppetlabs.net:8081/status/v1/services/puppetdb-status | python -m json.toolssage":"Transferring 1 reports"}],"service_name":"puppetdb-status"}[rpet  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
 
                                 Dload  Upload   Total   Spent    Left  Speed
 
100   628  100   628    0     0   3895      0 --:--:-- --:--:-- --:--:--  3900
 
{
 
    "active_alerts": [
 
        {
 
            "message": "Transferring 1 catalogs",
 
            "severity": "info"
 
        },
 
        {
 
            "message": "Transferring 1 facts",
 
            "severity": "info"
 
        },
 
        {
 
            "message": "Transferring 1 reports",
 
            "severity": "info"
 
        }
 
    ],
 
    "detail_level": "info",
 
    "service_name": "puppetdb-status",
 
    "service_status_version": 1,
 
    "service_version": "5.2.13-20200306_164346-g6063f2b",
 
    "state": "running",
 
    "status": {
 
        "maintenance_mode?": false,
 
        "queue_depth": 0,
 
        "rbac_status": "running",
 
        "read_db_up?": true,
 
        "sync_status": {
 
            "entity_status": {
 
                "catalogs": {
 
                    "phase": "transfer",
 
                    "total": 1
 
                },
 
                "factsets": {
 
                    "phase": "transfer",
 
                    "total": 1
 
                },
 
                "reports": {
 
                    "phase": "transfer",
 
                    "total": 1
 
                }
 
            },
 
            "state": "syncing"
 
        },
 
        "write_db_up?": true
 
    }
 
}

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Joshua Partlow (Jira)

unread,
Apr 2, 2020, 3:21:04 PM4/2/20
to puppe...@googlegroups.com
Joshua Partlow commented on Improvement PDB-4682
 
Re: PuppetDB sync status doesn't get updated when finished

Working on master 2019.6.0-rc2-60-ge16e31b, but that's with replication streaming, so probably no sync after. I'll check 2019.5.0.

[root@medical-singing pe_manager]# cat /opt/puppetlabs/server/pe_build ; echo
 
2019.6.0-rc2-60-ge16e31b
 
[root@medical-singing pe_manager]# puppet infra status
 
Notice: Contacting services for status information...
 
Code Manager: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8170/
 
File Sync Storage Service: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8140/
 
File Sync Client Service: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8140/
 
Puppet Server: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8140/
 
Classifier: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:4433/classifier-api
 
RBAC: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:4433/rbac-api
 
Activity Service: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:4433/activity-api
 
Orchestrator: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8143/orchestrator
 
PCP Broker: Running on Primary Master, wss://medical-singing.delivery.puppetlabs.net:8142/pcp
 
PCP Broker v2: Running on Primary Master, wss://medical-singing.delivery.puppetlabs.net:8142/pcp2
 
PuppetDB: Running on Primary Master, https://medical-singing.delivery.puppetlabs.net:8081/pdb
 
    Info: Last sync successfully completed 60 seconds ago (at 2020-04-02T19:18:02.681Z)
 
File Sync Client Service: Running on Primary Master Replica, https://unorthodox-hick.delivery.puppetlabs.net:8140/
 
Puppet Server: Running on Primary Master Replica, https://unorthodox-hick.delivery.puppetlabs.net:8140/
 
Classifier: Running on Primary Master Replica, https://unorthodox-hick.delivery.puppetlabs.net:4433/classifier-api
 
RBAC: Running on Primary Master Replica, https://unorthodox-hick.delivery.puppetlabs.net:4433/rbac-api
 
Activity Service: Running on Primary Master Replica, https://unorthodox-hick.delivery.puppetlabs.net:4433/activity-api
 
PuppetDB: Running on Primary Master Replica, https://unorthodox-hick.delivery.puppetlabs.net:8081/pdb
 
    Info: Last sync successfully completed 136 seconds ago (at 2020-04-02T19:16:47.107Z)
 
2020-04-02 19:19:03 +0000
 
17 of 17 services are fully operational.

Joshua Partlow (Jira)

unread,
Apr 2, 2020, 5:18:04 PM4/2/20
to puppe...@googlegroups.com

Don't see it in 2019.5.0, which relies on puppetdb sync like 2018.1, to sync the replica:

[root@wrong-coastline ~]# cat /opt/puppetlabs/server/pe_build ; echo
 
2019.5.0
 
[root@wrong-coastline ~]# puppet infra status
 
Notice: Contacting services for status information...
 
File Sync Client Service: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:8140/
 
Puppet Server: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:8140/
 
Classifier: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:4433/classifier-api
 
RBAC: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:4433/rbac-api
 
Activity Service: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:4433/activity-api
 
PuppetDB: Running on Primary Master Replica, https://neutralist-mill.delivery.puppetlabs.net:8081/pdb
 
    Info: Last sync successfully completed 141 seconds ago (at 2020-04-02T21:14:00.710Z)
 
Code Manager: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:8170/
 
File Sync Storage Service: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:8140/
 
File Sync Client Service: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:8140/
 
Puppet Server: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:8140/
 
Classifier: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:4433/classifier-api
 
RBAC: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:4433/rbac-api
 
Activity Service: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:4433/activity-api
 
Orchestrator: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:8143/orchestrator
 
PCP Broker: Running on Primary Master, wss://wrong-coastline.delivery.puppetlabs.net:8142/pcp
 
PCP Broker v2: Running on Primary Master, wss://wrong-coastline.delivery.puppetlabs.net:8142/pcp2
 
PuppetDB: Running on Primary Master, https://wrong-coastline.delivery.puppetlabs.net:8081/pdb
 
    Info: Last sync successfully completed 117 seconds ago (at 2020-04-02T21:14:24.740Z)
 
2020-04-02 21:16:22 +0000
 
17 of 17 services are fully operational.

Austin Blatt (Jira)

unread,
Apr 13, 2020, 12:45:02 PM4/13/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
 
Change By: Austin Blatt
Sprint: HA Team 2020-04-22 (SS 4/15)

Nick Burgan (Jira)

unread,
Apr 22, 2020, 2:14:02 PM4/22/20
to puppe...@googlegroups.com
Nick Burgan updated an issue
Change By: Nick Burgan
Sprint: HA Team 2020-04-22 (SS 4/15) , HA Team 2020-05-05

Nick Burgan (Jira)

unread,
Apr 22, 2020, 2:20:02 PM4/22/20
to puppe...@googlegroups.com
Nick Burgan updated an issue
Change By: Nick Burgan
Story Points: 2

Austin Blatt (Jira)

unread,
Apr 29, 2020, 12:35:03 PM4/29/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Fix Version/s: PDB 6.10.0

Austin Blatt (Jira)

unread,
Apr 29, 2020, 12:35:04 PM4/29/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Fix Version/s: PDB 5.2.14

Austin Blatt (Jira)

unread,
Apr 29, 2020, 1:02:04 PM4/29/20
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Release Notes Summary: Fixed a bug that would cause PE's sync to fail and never retry when one PuppetDB had been upgraded and the other had not. Now it will fail and retry.

Austin Boyd (Jira)

unread,
Aug 18, 2020, 10:01:08 AM8/18/20
to puppe...@googlegroups.com
Austin Boyd updated an issue
Change By: Austin Boyd
Labels: jira_escalated

Austin Boyd (Jira)

unread,
Aug 18, 2020, 10:05:03 AM8/18/20
to puppe...@googlegroups.com
Austin Boyd updated an issue
Change By: Austin Boyd
Zendesk Ticket Count: 1
Zendesk Ticket IDs: 39812

Austin Blatt (Jira)

unread,
Feb 9, 2021, 4:26:03 PM2/9/21
to puppe...@googlegroups.com
Austin Blatt updated an issue
Change By: Austin Blatt
Affects Version/s: PDB 6.9.1
Reply all
Reply to author
Forward
0 new messages