Project

General

Profile

Actions

Bug #13967

closed

[replaces #10115] FileNotFoundException when looking for deleted history file

Added by Alexis MOUSSET over 2 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

I tried to look to a deleted history file and got:

java.io.FileNotFoundException: /var/rudder/inventories/historical/729be5c4-55a2-4b97-8529-5154cbb63a18/2014-03-21_17:57.57.486 (Aucun fichier ou dossier de ce type)
    at java.io.FileInputStream.open0(FileInputStream.java)
    at java.io.FileInputStream.open(FileInputStream.java:195)
    at java.io.FileInputStream.<init>(FileInputStream.java:138)
    at com.unboundid.ldif.LDIFReader.<init>(LDIFReader.java:320)
    at com.normation.inventory.ldap.core.FullInventoryFileMarshalling.fromFile(InventoryHistoryLogRepository.scala:62)
    at com.normation.history.impl.FileHistoryLogRepository.$anonfun$get$3(FileHistoryLogRepository.scala:185)
    at net.liftweb.common.Full.flatMap(Box.scala:808)
    at com.normation.history.impl.FileHistoryLogRepository.$anonfun$get$1(FileHistoryLogRepository.scala:184)

I should have had a nice message.
I was in 4.1-beta but there is a lot of change it happens also in 3.1.

Actions #1

Updated by Alexis MOUSSET over 2 years ago

  • Category set to Web - Nodes & inventories
Actions #2

Updated by Alexis MOUSSET over 2 years ago

  • Subject changed from FileNotFoundException when looking for deleted history file to [replaces 10115] FileNotFoundException when looking for deleted history file
Actions #3

Updated by Alexis MOUSSET over 2 years ago

  • Subject changed from [replaces 10115] FileNotFoundException when looking for deleted history file to [replaces #10115] FileNotFoundException when looking for deleted history file
Actions #4

Updated by Alexis MOUSSET over 2 years ago

  • Target version set to 3.1.18
Actions #5

Updated by Alexis MOUSSET over 2 years ago

This bug has been fixed in Rudder 3.1.18, 3.2.11, 4.0.3 and 4.1.0~beta3 which were released on 2017-02-20.

Actions #6

Updated by Alexis MOUSSET over 2 years ago

  • Status changed from New to Released
Actions

Also available in: Atom PDF