action #53762

/admin/needles can be misleading in mentioning needle as "never used" when it is referenced from a symlinked needles repo

Added by okurz 8 months ago. Updated 5 days ago.

Status:In ProgressStart date:03/07/2019
Priority:NormalDue date:
Assignee:Xiaojing_liu% Done:


Category:Concrete Bugs
Target version:Current Sprint





showing the search results for a needle "user_settings_root-inst-rootpassword-20190306.json" that appears twice even though it is the same needle. It is reported as correctly used within the directory "opensuse" but "never/never" for "kubic-Tumbleweed". The bigger problem is when I limit using the provided filters which can cause one of the entries to not show at all. This can mislead the user into thinking a needle can be deleted when it is actually actively used by the other "directory" aka. "distri".

This mislead me into deleting quite some needles which caused a lot of tests to fail on o3 and I had to recover all these needles :D

Acceptance criteria

  • AC1: Needles that are recently referenced as in use by any symlinked repo are not reported as "never used" within /admin/needles


  • Dereference symlinks when loading needles for evaluating if they are still used
  • Ensure the same needle files are either only referenced once or shown with the use information regardless of the used "distri"

Screenshot_20190703_110831.png (24.5 KB) okurz, 03/07/2019 09:10 am

before.png (41.5 KB) Xiaojing_liu, 23/01/2020 08:55 am

after.png (42 KB) Xiaojing_liu, 23/01/2020 08:55 am



#1 Updated by coolo 7 months ago

  • Priority changed from High to Normal
  • Target version set to Ready

I don't think it's high prio as not many people actually bother to delete needles - and those who do learn about this obstacle quickly :(

#2 Updated by okurz 2 months ago

  • Description updated (diff)
  • Status changed from New to Workable

#3 Updated by Xiaojing_liu about 1 month ago

I added two picture, does the result shown in after.png work as expected?

#4 Updated by okurz about 1 month ago

yes, that's how it should look like.

#5 Updated by cdywan 20 days ago

  • Assignee set to Xiaojing_liu
  • Target version changed from Ready to Current Sprint

#6 Updated by Xiaojing_liu 19 days ago

  • Status changed from Workable to In Progress

Also available in: Atom PDF