Puppet: System Administration Automated

Support

Ticket #1124 (closed defect: wontfix)

Opened 6 months ago

Last modified 6 months ago

Fileserver error in .24.2, unable to download file "Cannot currently copy links"

Reported by: asa Assigned to: luke
Priority: normal Milestone: 0.24.3
Component: library Version: 0.24.2
Severity: normal Keywords: file
Cc: Triage Stage: Accepted
Attached Patches: None Complexity: Unknown

Description

Installed .24.2 via gem onto an osx leopard intel client machine.

Tried to push out a file into /test/testfile.txt and recieved the following errors: 

notice: Starting catalog run
debug: Loaded state in 0.01 seconds
debug: Calling fileserver.describe
err: //Node[mini]/File[/test/testfile.txt]/source: Could not describe /dist/test.txt: Cannot currently copy links
warning: //Node[mini]/File[/test/testfile.txt]/ensure: No specified sources exist
warning: //Node[mini]/File[/test/testfile.txt]/ensure: No specified sources exist
warning: //Node[mini]/File[/test/testfile.txt]/source: No specified sources exist
d

my manifest read like: 

	file {"/test/testfile.txt":
#		owner => root,
		group => wheel,
		mode => 644,
		source	=> 'puppet://puppet/dist/test.txt',
	}

and my fileserver.conf is like: 

[dist] 
  path /etc/puppet/dist/
  allow *.localdomain
  allow 192.168.1.0/24

the file exists at /etc/puppet/dist/test.txt and will push out correctly to a .24.1 client on the same machine.

The server is .24.1 on linux.

Change History

03/12/08 19:31:54 changed by luke

  • owner changed from community to luke.
  • status changed from new to assigned.
  • stage changed from Unreviewed to Accepted.
  • milestone set to 0.24.3.

I'm not positive I'll be able to fix this, but I'll try. In general, your server should be running the most recent version of the code, since it's easiest to update.

03/17/08 04:56:14 changed by luke

  • status changed from assigned to closed.
  • resolution set to wontfix.

I took a crack at this and couldn't get it working. I agree that these two releases should be compatible, or that I should have saved this feature update for a full minor release, but it's too late now, and I can't find a straightforward way to provide backward compatibility with a new client and an old server.

If you upgrade your server first (or run a test system in virtual machines or something) you won't have this error.