Skip to content

Weird error while copy factory-config running-config #956

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
troglobit opened this issue Feb 23, 2025 · 2 comments · Fixed by #957
Closed

Weird error while copy factory-config running-config #956

troglobit opened this issue Feb 23, 2025 · 2 comments · Fixed by #957
Assignees
Labels
bug Something isn't working
Milestone

Comments

@troglobit
Copy link
Contributor

Current Behavior

admin@R2:/> copy factory-config running-config 
Error: setting owner (null) on admin: Bad address
admin@R2:/> 

Expected Behavior

admin@R2:/> copy factory-config running-config 
admin@R2:/> 

Steps To Reproduce

This was reproduced with the lingering-containers branch on cn:styx after having run the ci:main build tests.

Additional information

No response

@troglobit troglobit added bug Something isn't working triage Pending investigation & classification (CCB) labels Feb 23, 2025
@troglobit
Copy link
Contributor Author

Seems to be from the "new" copy command, split out from the klish-plugin-infix package.

src/bin/copy.c: fprintf(stderr, ERRMSG "setting owner %s on %s: %s\n", fn, user, strerror(errno));

@troglobit troglobit self-assigned this Feb 23, 2025
@troglobit troglobit removed the triage Pending investigation & classification (CCB) label Feb 23, 2025
@troglobit troglobit moved this to In progress in Infix & C:o Feb 23, 2025
@troglobit troglobit added this to the Infix v25.02 milestone Feb 23, 2025
@troglobit
Copy link
Contributor Author

Oversight in handling of copy.c:set_owner(), the system running-config is not a file. Skip for non(-local) files.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant