Jira (PUP-6421) puppet module install no longer working over http

2016-06-21 Thread Darren Hart (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Darren Hart updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6421 
 
 
 
  puppet module install no longer working over http  
 
 
 
 
 
 
 
 
 

Change By:
 
 Darren Hart 
 
 
 

Summary:
 
 puppet module install  not  no  longer working over http 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6421) puppet module install not longer working over http

2016-06-21 Thread Darren Hart (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Darren Hart created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6421 
 
 
 
  puppet module install not longer working over http  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/21 6:14 AM 
 
 
 

Environment:
 
 
Windows Server 2012 R2 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Darren Hart 
 
 
 
 
 
 
 
 
 
 
I can no longer install a module via http. This used to work was also breaking in 3.4.2 updated to check if it was an issue with outdated version.  
I ran the following  
puppet module install --module_repository http://forge.puppetlabs.com puppetlabs-dism  
This returns the following error  
Error: Request to Puppet Forge failed. 
 

The server being queried was http://forge.puppetlabs.com/v3/releases?module=puppetlabs-dism
 

The HTTP response we received was '301 Moved Permanently'