Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCUMENT-189

PE upgrade docs incorrectly document the use of "puppetdb-export"

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Component/s: None
    • Labels:
    • Template:
    • Story Points:
      2
    • Sprint:
      Dastardly Dingo 9.29.14, Enervating Echidna 10.13.14, Fiendish Flamingo 10.27.14, Gruff Goanna 11.10.14, Heartless Hedgehog 12.1.14, Ignominious Indri 12.15.14, Jaded Jellyfish 12.31.14, Killer Kakapo 1.19.15

      Description

      So, I'm doing an upgrade of PE from 3.2.3. to 3.3.1. Along the way I got here:
      https://docs.puppetlabs.com/pe/latest/install_upgrading.html#before-upgrading-back-up-your-databases-and-other-pe-files

      which got me quickly here:
      https://docs.puppetlabs.com/puppetdb/1.6/migrate.html#exporting-data-from-an-existing-puppetdb-database

      which says to run this command:
      sudo puppetdb export --outfile ./my-puppetdb-export.tar.gz

      2 problems:

      1) In 3.2.3, it looks like it's a single command called "puppetdb-export" – no space between the words. There is no standalone command "puppetdb", so this command will fail. The command "puppetdb" does exist in 3.3.1 however - so the docs could be more version-specific on this.

      2) in both 3.2.3 and 3.3.1, the command "puppetdb-export" is not by default on the path. So it would help to mention that it's sitting in "/opt/puppet/sbin". It might be good to go through the docs and find references to some of the other puppetdb commands and make this note on those pages too. Based on 3.3.1, here is the list of relevant commands:

      puppetdb
      puppetdb-anonymize
      puppetdb-export
      puppetdb-foreground
      puppetdb-import
      puppetdb-ssl-setup

        Attachments

          Activity

            People

            Assignee:
            dan.stadler Dan Stadler
            Reporter:
            dan.stadler Dan Stadler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support