Reject collect command where --name value has a name longer than 239 char
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Girish Subramanya |
Bug Description
Brief Description
Suggest reject/check collect command where --name value has lenthyname ie. >239 characters
Severity
Minor
Steps to Reproduce
$ collect --name <lengthyname> --subcloud subcloud1
or from a standalone system controller
$collect --list controller-0 --verbose --name <lengthyname>
Where the lenthyname is 239 characters or more (resulting in final tgz file name of 255 char)
Expected Behavior
Suggest the <lengthyname> should not exceed 239 char (ie would not result in a tarball name more than 255 char, with appropriate failure code.
Actual Behavior
Error in log collection from subclouds (reason 11)
$ collect all --name Longname3398093
[sudo] password for sysadmin:
collecting data from 2 host(s)
monitoring host collect ; please standby .....
Error: operation timeout ; failed to get file from controller-1 (reason:11)
Error: operation timeout ; failed to collect from controller-1 [get file] (reason:11)
stats error)
collected from 3 hosts
Error: /scratch/
On standalone system, the result is an Error in creating empty <lengthyname>.tar file
2021-09-
2021-09-
Reproducibility
---------------
The issue is 100% reproducible.
System Configuration
DC and standalone
Branch/Pull Time/Commit
2021-09-15_00-00-06
Last Pass
This is a new test scenario
Test Activity
Feature testing
Workaround
specify short value for --name
Changed in starlingx: | |
assignee: | nobody → Girish Subramanya (gisubram) |
Changed in starlingx: | |
status: | Fix Released → Confirmed |
status: | Confirmed → Fix Committed |
status: | Fix Committed → Confirmed |
status: | Confirmed → In Progress |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.tools |
tags: | added: stx.8.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /utilities/ +/858920
Review: https:/