Jira (PUP-9496) Unable to use remote URI as source parameter with package provider on Windows

Geoff Nichols (JIRA)

unread,

Feb 12, 2019, 9:31:03 PM2/12/19

to puppe...@googlegroups.com

Geoff Nichols created an issue

Puppet /

PUP-9496

Unable to use remote URI as source parameter with package provider on Windows

Issue Type:	Bug
Assignee:	Unassigned
Created:	2019/02/12 6:30 PM
Priority:	Normal
Reporter:	Geoff Nichols

Prior to Puppet 5.5.7, it was possible with the 'windows' provider for the Package resource to use HTTP sources on MSI packages. As of Puppet 5.5.7, this functionality no longer works.

Example:

package { 'my software':

ensure => '1.0.0',

source => 'http://my-web-repo.net/my-package.msi',

Error message:

'Error: Could not update: Working directory http://my-web-repo.net does not exist!'

Puppet 5.5.7 implemented https://tickets.puppetlabs.com/browse/PUP-6920, which allows for the working directory to be the same, which breaks the unintended functionality of the windows provider using a remote URI. It previously worked because MSI was actually handling the download of the installer rather than Puppet handling the download.

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Geoff Nichols (JIRA)

unread,

Feb 12, 2019, 9:31:03 PM2/12/19

to puppe...@googlegroups.com

Geoff Nichols updated an issue

Puppet /

PUP-9496

Unable to use remote URI as source parameter with package provider on Windows

Change By:	Geoff Nichols
Labels:	customer package type_and_provider windows

Add Comment

Geoff Nichols (JIRA)

unread,

Feb 12, 2019, 9:31:03 PM2/12/19

to puppe...@googlegroups.com

Geoff Nichols updated an issue

Puppet /

PUP-9496

Unable to use remote URI as source parameter with package provider on Windows

Change By:	Geoff Nichols
Team:	Platform OS

Add Comment

Geoff Nichols (JIRA)

unread,

Feb 12, 2019, 9:32:03 PM2/12/19

to puppe...@googlegroups.com

Geoff Nichols updated an issue

Puppet /

PUP-9496

Unable to use remote URI as source parameter with package provider on Windows

Change By:	Geoff Nichols
Affects Version/s:	PUP 5.5.7

Add Comment

Geoff Nichols (JIRA)

unread,

Feb 12, 2019, 9:35:03 PM2/12/19

to puppe...@googlegroups.com

Geoff Nichols commented on

PUP-9496

Re: Unable to use remote URI as source parameter with package provider on Windows

/cc Sean McDonald, William Hurt, Branan Riley

Add Comment

Geoff Nichols (JIRA)

unread,

Feb 13, 2019, 10:38:05 AM2/13/19

to puppe...@googlegroups.com

Geoff Nichols updated an issue

Puppet /

PUP-9496

Unable to use remote URI as source parameter with package provider on Windows

Change By:	Geoff Nichols

Prior to Puppet 5.5.7, it was possible with the 'windows' provider for the Package resource to use HTTP sources on for MSI packages. As of Puppet 5.5.7, this functionality no longer works.

Example:
{code}package { 'my software':

ensure => '1.0.0',
source => 'http://my-web-repo.net/my-package.msi',
}

{code}
Error message:
{code}'Error: Could not update: Working directory http://my-web-repo.net does not exist!'
{code}
Puppet 5.5.7 implemented https://tickets.puppetlabs.com/browse/PUP-6920, which allows for the working directory to be the same directory as the package source , which breaks the unintended functionality of the windows provider using a remote URI. It previously worked because MSI was actually handling the download of the installer rather than Puppet handling the download.