Jira (PUP-10211) 'puppet module install --module_repository' never finishes

0 views
Skip to first unread message

Garrett Guillotte (JIRA)

unread,
Dec 27, 2019, 4:36:03 PM12/27/19
to puppe...@googlegroups.com
Garrett Guillotte updated an issue
 
Puppet / Bug PUP-10211
'puppet module install --module_repository' never finishes
Change By: Garrett Guillotte
Summary: {brief summary of issue} 'puppet module install --module_repository' never finishes
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Garrett Guillotte (JIRA)

unread,
Dec 27, 2019, 4:38:03 PM12/27/19
to puppe...@googlegroups.com
Garrett Guillotte updated an issue
When I add  `– {{-- module_repository [ https://artifactory |https://artifactory/] .<mydomain>.com/api/puppet/puppet-forge ` }} to my fixtures, my unit tests just hang forever.

  

 When I run  ` {{ puppet module install puppetlabs/stdlib --debug --module_repository  {color [https : #333333} //artifactory| https://artifactory /] .<mydomain>.com/api/puppet/puppet-forge {color } ` } on puppet 6.10.1 directly, or on 6.10.1 or 6.11.1 via {{ pdk bundle exec }} , I see the following:
```

 {code} Debug: HTTP GET https://artifactory. {color:#333333} <mydomain>.com/api/puppet/puppet-forge {color} /api/puppet/puppet-forge/v3/releases?limit=20&offset=20

  

 Debug: HTTP GET https://artifactory. {color:#333333} <mydomain>.com/api/puppet/puppet-forge {color} /api/puppet/puppet-forge/v3/releases?limit=20&offset=20

  

 Debug: HTTP GET https://artifactory. {color:#333333} <mydomain>.com/api/puppet/puppet-forge {color} /api/puppet/puppet-forge/v3/releases?limit=20&offset=20
 {code}
```

 

 repeating until I kill it.

  

 If I use `–module_repository { color {--module_repository [https : #333333} //artifactory| https://artifactory /] . {color}{color:#333333} <mydomain>.com {color } ` } , then I get a 404 with it trying the URL { color {[https : #333333} //artifactory| https://artifactory /] . {color}{color:#333333} <mydomain>.com/v3/releases?module=pupetlabs-stdlib&sort_by=version&exclude_fields=readme%2Cchangelog%2Clicense%2Curi%2Cmodule%2Ctags%2Csupported%2Cdownlaods%2Ccreated_at%2Cupdated_at%2Cdeleted_at
```
{color } }

{color:#333333} I've set this up using a combination of Artifactory documentation, and the documentation for puppet and puppet_spec_helper, but have not been able to get it to install  modules from my local Artifactory based forge. (FWIW, I have r10k installing modules from it successfully) {color}

Garrett Guillotte (JIRA)

unread,
Dec 27, 2019, 4:47:03 PM12/27/19
to puppe...@googlegroups.com
Garrett Guillotte commented on Bug PUP-10211
 
Re: 'puppet module install --module_repository' never finishes

Lee Lowder I'd expect to use a port number to access Artifactory, probably 8080 unless it's been changed on that end. Since r10k is working, what's the r10k config look like? Does it use a port number?

Kyle Hansel (JIRA)

unread,
Dec 27, 2019, 5:26:04 PM12/27/19
to puppe...@googlegroups.com
Kyle Hansel updated an issue
 
Change By: Kyle Hansel
When I add {{--  `– module_repository [https://artifactory|https://artifactory/].<mydomain>.com/api/puppet/puppet-forge }} ` to my fixtures, my unit tests just hang forever.

  
When I run  {{ ` puppet module install puppetlabs/stdlib --debug --module_repository  {color:#333333} [https://artifactory|https://artifactory/].<mydomain>.com/api/puppet/puppet-forge {color } } ` on puppet 6.10.1 directly, or on 6.10.1 or 6.11.1 via {{ pdk bundle exec }} , I see the following:
{code}
```

 Debug: HTTP GET https://artifactory. {color:#333333} <mydomain>.com/api/puppet/puppet-forge {color} /api/puppet/puppet-forge/v3/releases?limit=20&offset=20

  

 Debug: HTTP GET https://artifactory. {color:#333333} <mydomain>.com/api/puppet/puppet-forge {color} /api/puppet/puppet-forge/v3/releases?limit=20&offset=20

  

 Debug: HTTP GET https://artifactory. {color:#333333} <mydomain>.com/api/puppet/puppet-forge {color} /api/puppet/puppet-forge/v3/releases?limit=20&offset=20
 {code}
```

 

 repeating until I kill it.

  
If I use {{-- `– module_repository {color:#333333} [https://artifactory|https://artifactory/]. {color}{color:#333333} <mydomain>.com {color } } ` , then I get a 404 with it trying the URL { { color:#333333} [https://artifactory|https://artifactory/]. {color}{color:#333333} <mydomain>.com/v3/releases?module=pupetlabs-stdlib&sort_by=version&exclude_fields=readme%2Cchangelog%2Clicense%2Curi%2Cmodule%2Ctags%2Csupported%2Cdownlaods%2Ccreated_at%2Cupdated_at%2Cdeleted_at
```{color } }

{color:#333333} I've set this up using a combination of Artifactory documentation, and the documentation for puppet and puppet_spec_helper, but have not been able to get it to install  modules from my local Artifactory based forge. (FWIW, I have r10k installing modules from it successfully) {color}

Lee Lowder (JIRA)

unread,
Dec 27, 2019, 7:55:03 PM12/27/19
to puppe...@googlegroups.com
Lee Lowder commented on Bug PUP-10211
 
Re: 'puppet module install --module_repository' never finishes

As an update, if I "curl https://artifactory.<domain>.com/api/puppet/puppet-forge/v3/releases?limit=20&offset=20"` I get a wall of json back.

 

However, when I use `puppet module install puppetlabs/stdlib --module_repository = https://artifactory.<domain>.com/api/puppet/puppet-forge` it tries to download from `https://artifactory.<domain>.com/api/puppet/puppet-forge/api/puppet/puppet-forge/v3/releases?limit=20&offset=20` which 404s.

 

Oddly, it keeps trying this, forever (I've let it run for 30+ minutes before)

 

If I pass in `https://artifactory.<domain>.com/` then it tries to use `https://artifactory.<domain>.com/v3/releases?module....` which results in a 404.

 

 

Lee Lowder (JIRA)

unread,
Dec 27, 2019, 7:56:03 PM12/27/19
to puppe...@googlegroups.com
Lee Lowder commented on Bug PUP-10211

Garrett Guillotte We are configured to use straight https (443). That's what r10k uses, and it gives me a wall of json when I curl the correct URL directly.

Garrett Guillotte (JIRA)

unread,
Dec 27, 2019, 8:22:03 PM12/27/19
to puppe...@googlegroups.com
Garrett Guillotte updated an issue
 
Change By: Garrett Guillotte
Team: Night's Watch

Garrett Guillotte (JIRA)

unread,
Dec 27, 2019, 8:58:03 PM12/27/19
to puppe...@googlegroups.com
Garrett Guillotte commented on Bug PUP-10211
 
Re: 'puppet module install --module_repository' never finishes

Lee Lowder The mismatch in the returned URLs (.../api/puppet/puppet-forge/api/puppet/puppet-forge/v3/releases?... vs. https://artifactory.<domain>.com/v3/releases?module)  is PUP-8650.

The rest of the behavior sounds wrong, but I'm not sure I have enough information to reproduce it, or whether the issue is in PMT or Artifactory's response.

Can you attach the output of:

puppet module install saz-motd --debug --trace --http_debug --module_repository  https://artifactory.<mydomain>.com/api/puppet/puppet-forge &> pmi-debug.log

And the "wall of JSON" output from curling https://artifactory.DOMAIN.com/api/puppet/puppet-forge/v3/releases?limit=20&offset=20?

What version of Artifactory is this?

Garrett Guillotte (JIRA)

unread,
Dec 27, 2019, 9:04:03 PM12/27/19
to puppe...@googlegroups.com
Garrett Guillotte updated an issue
Change By: Garrett Guillotte
Team: Night's Watch Puppet Developer Experience

Garrett Guillotte (JIRA)

unread,
Dec 27, 2019, 9:07:02 PM12/27/19
to puppe...@googlegroups.com
 
Re: 'puppet module install --module_repository' never finishes

Lee Lowder I assume in addition to using port 443, there's also a reason why the path in the URL you're passing is api/puppet/puppet-forge instead of artifactory/api/puppet/puppet-forge?

Lee Lowder (JIRA)

unread,
Dec 28, 2019, 12:27:03 AM12/28/19
to puppe...@googlegroups.com
Lee Lowder commented on Bug PUP-10211

It's version 6.10.4, and that is what it said to use in the "set me up" section after I added the repo.

 

I'm unable to copy out the json, due to how the work network is setup and company policies, but when I captured it to a file, it looked like some sort of listing of a bunch of modules that had stdlib as a requirement. - metadata of the module, the readme. Looks to be multiple versions of about 20 modules.

 

I'll have to wait till Monday to do any further digging though, it's well past my bed time, let alone the end of my work day.

Lee Lowder (JIRA)

unread,
Dec 30, 2019, 12:20:04 PM12/30/19
to puppe...@googlegroups.com
Lee Lowder commented on Bug PUP-10211

So, I let the command run for 5 minutes, with the trace, debug, and http debug options.  Wound up with no modules and a 193 mb log file.

Garrett Guillotte (JIRA)

unread,
Dec 30, 2019, 2:05:03 PM12/30/19
to puppe...@googlegroups.com


> it looked like some sort of listing of a bunch of modules that had stdlib as a requirement. - metadata of the module, the readme. Looks to be multiple versions of about 20 modules

Was it one list of modules, or repeating?

> I let the command run for 5 minutes, with the trace, debug, and http debug options. Wound up with no modules and a 193 mb log file.

Can you run it a shorter amount of time — even just 10 or 20 seconds — and please attach the log? I'm not expecting this to install the module, and I need to be able to see the output that PMT is getting and sending in order to understand why it's not doing more expected things (paginating through results, installing the module).

Josh Cooper (JIRA)

unread,
Jan 6, 2020, 12:16:03 PM1/6/20
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-10211

Lee Lowder do you get the same behavior with puppet versions < 6.10?

Josh Cooper (JIRA)

unread,
Jan 6, 2020, 2:54:03 PM1/6/20
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-10211

Can you double check the URL? I think it's suppose to be http://<host>:<port>/artifactory/api/puppet/puppet, not a URL ending with /puppet-forge.

Lee Lowder (JIRA)

unread,
Jan 15, 2020, 11:06:03 AM1/15/20
to puppe...@googlegroups.com
Lee Lowder commented on Bug PUP-10211

Apologies for the delay - I had been pulled into other things.

The URL is correct, I copied and pasted it out of my Artifactory "set me up" section.

For the logs, I have a set now, that I have suitably sanitized, I just need to figure out how to get them off the system, as it is fairly restricted access.

Other than this master I am building, the only one I have availble to test on is running 4.5.3 - and I haven't set up the reverse prxy thing that 4.9.x and older needs, so I can't test there

 

Josh Cooper (Jira)

unread,
Jan 27, 2021, 1:27:04 PM1/27/21
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-10211

Puppet's http client has been rewritten in 6.x and now consistently uses tcp connect and read timeouts (as set via http_*_timeout puppet settings). Can you try to reproduce with a more recent version?
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Josh Cooper (Jira)

unread,
Aug 18, 2021, 1:08:05 PM8/18/21
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-10211

Lee Lowder any updates on this?
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Atlassian logo

Josh Cooper (Jira)

unread,
Sep 13, 2021, 7:31:02 PM9/13/21
to puppe...@googlegroups.com
Josh Cooper assigned an issue to Unassigned
 
Change By: Josh Cooper
Assignee: Josh Cooper

Josh Cooper (Jira)

unread,
Sep 13, 2021, 7:31:02 PM9/13/21
to puppe...@googlegroups.com
Josh Cooper assigned an issue to Josh Cooper

Josh Cooper (Jira)

unread,
Sep 13, 2021, 7:32:03 PM9/13/21
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-10211
 
Re: 'puppet module install --module_repository' never finishes

This hasn't been updated in awhile, so I'm going to close this. Please reopen if you can reproduce.
Reply all
Reply to author
Forward
0 new messages