Bug 1085047 - CSV export produces obsolete 'secret' column with no value, which fails to be imported
Summary: CSV export produces obsolete 'secret' column with no value, which fails to be...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.16.2
Assignee: Amit Saha
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-07 16:42 UTC by andrew
Modified: 2018-02-06 00:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-28 23:00:37 UTC
Embargoed:


Attachments (Terms of Use)

Description andrew 2014-04-07 16:42:57 UTC
Description of problem: cvs will not import without error


Version-Release number of selected component (if applicable):


How reproducible:100%


Steps to Reproduce:
Download csv
[s]$ head -n 1 system.csv >> beaker-system.csv
[s]$ cat system.csv | grep ibm-z10-02 >> beaker-system.csv 
Then upload 

Error Log
Error importing system on line 2: ibm-z10-02: Invalid secret None


Actual results: Errors


Expected results: no Errors


Additional info:

Comment 2 Dan Callaghan 2014-04-08 00:52:51 UTC
Expected result is actually: the CSV export should not contain a secret column (and it *definitely* shouldn't contain a secret column with no values, because that fails to import).

Comment 3 Dan Callaghan 2014-04-08 00:55:01 UTC
There is supposed to be a test which covers export-and-re-import, which should have caught this. So we need to figure out why that didn't happen.

Comment 4 Dan Callaghan 2014-04-08 01:45:28 UTC
Workaround is to delete the 'secret' column from the exported CSV before you re-import it.

Comment 5 Amit Saha 2014-04-08 01:50:55 UTC
On Gerrit: http://gerrit.beaker-project.org/#/c/3002/

"secret" column is not exported.

Comment 8 Dan Callaghan 2014-04-28 23:00:37 UTC
Beaker 0.16.2 has been released.


Note You need to log in before you can comment on or make changes to this bug.