[SERVER-2615] subcommands "ca" does not work Created: 2019/08/28  Updated: 2020/02/05

Status: Open
Project: Puppet Server
Component/s: Puppet Server
Affects Version/s: SERVER 6.5.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Sam Ding Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

x86_84-Linux , ubuntu 16.04


Template: PUP Bug Template
Team: Froyo
Method Found: Needs Assessment
QA Risk Assessment: Needs Assessment

 Description   

According to document https://github.com/puppetlabs/puppetserver/blob/6.5.0/documentation/subcommands.markdown

When running from source, the subcommand is :
   lein
<subcommand> -c /path/to/puppetserver.conf [--] [<args>]



However "lein ca ...." does not work, it gets errors like:

          'ca' is not a task. See 'lein help'.
          Did you mean this?
               jar
              do
              vcs

`Lein help` also show no option of `ca`. 
Probably the document does not match the actual usage of `lein`.

Can you let me know how to run the similar subcommand of  `puppetserver ca ... ` when I run from source?

 



 Comments   
Comment by Sam Ding [ 2019/09/04 ]

More info:

To run puppetserver and agent on different VMs, it needs commands
    puppetserver ca sign --all

    puppetserver ca list --all

But what is the similar subcommands if running from source? in which case there is no "puppetserver" but "lein".

Comment by Sam Ding [ 2019/11/27 ]

Is there any update on this issue? Thx.

Comment by Rune Juhl Jacobsen [ 2020/02/05 ]

That looks like an error in the documentation. For the command to work that way it has to be implemented as a Leiningen alias, which is done here https://github.com/puppetlabs/puppetserver/blob/e3874b2360501a26518d2f904035a6b84f25b9d9/project.clj#L224-L227.

Since the ca command is a puppetserver command I believe you need to do something like this:

lein run – -c dev/puppetserver.conf ca

Generated at Sat Feb 29 06:24:05 PST 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.