Symptom

Currently, copy RPCs do not support arbitrary file systems. The currenty RPC supports only these source/destination file systems based on the pattern: rpc copy { description "Copy from one file to another"; input { leaf source-drop-node-name { mandatory true; type string { pattern '((((bootflash:)|(harddisk:)|(flash:)|(nvram:)|(ftp:)|(http:)|(https:)|(scp:)|(tftp:)).*)|((running-config)|(startup-config)))'; } } This limits the functionality on using the copy RPC for platforms such as switch stacks whom may have multiple members with different mapping names for the mounts Switch#show file system File Systems: Size(b) Free(b) Type Flags Prefixes - - opaque rw system: - - opaque rw tmpsys: 1651314688 1363206144 disk rw crashinfo: crashinfo-1: 1651507200 1368391680 disk rw crashinfo-2: stby-crashinfo: * 11353194496 5631143936 disk rw flash: bootflash: flash-1: 11353980928 2658140160 disk rw flash-2: stby-flash: 3839950848 3725824000 disk ro webui: - - opaque rw null: A sample RPC response returned would show an invalid value: "flash-1:test" is an invalid value.source-drop-node-name

Conditions

This is only applicable to copy RPCs used by restconf/netconf-yang models.

Workaround

There are no known workarounds for this.

Further Problem Description