Bug in Splunk app for lookup file editor?

[mf182407]

https://splunkbase.splunk.com/app/1724

recently upgraded to the new 4.0.0 version and am seeing a bug w the csvs now. it seems to be adding e and f columns and cannot delete them. which is causing an unwanted column in the actual | inputlookup asdf.csv

is this a known bug? is anyone else seeing this?

[mf182407]

has anyone heard of any more updates from the slack channel?

it does look like they removed the 4.0 version history from the https://splunkbase.splunk.com/app/1724 page (under version history). it is still on the release notes page in the docs.splunk.com, however.

[mf182407]

thanks for the feedback and updates here. i should have mentioned that i am on 9x. hopefully the bugs will be patched soon

[andrewtrobec]

Hello All,

I am also facing issues post upgrade.  When trying to save via web UI after specifying to not save a backup I get the error "The lookup file could not be saved".

One of the best apps for Splunk has effectively become useless 😞

Is this being investigated at all?

Thanks!

Andrew

[wryanthomas]

I haven't seen that one.  But we're seeing other issues with 4.0.0.  Edits made via the GUI are not getting saved -- with no error message (in GUI).  Same user can edit it via outputlookup, so it's not permissions-related.  They were editing via Lookup File Editor prior to the upgrade.  😞 

[burwell]

Hi there's a conversation about this in the Splunk Slack channel for Splunk 9 upgrade issues and a user has reported the issue to Splunk. See https://splunk-usergroups.slack.com/archives/C03M9ENE6AD/p1679754016483519 for reference.