Bug 1644651 - azure.log without EOL
Summary: azure.log without EOL
Keywords:
Status: CLOSED DUPLICATE of bug 1640718
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Bronagh Sorota
QA Contact: Angelina Vasileva
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-31 10:30 UTC by Imaan
Modified: 2022-03-13 15:54 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-01 14:01:42 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Imaan 2018-10-31 10:30:45 UTC
Description of problem:

The azure.log has content but no EOL.

For Example:

[root@unused log]# ls -l azure.log
-rw-r--r--. 1 root root 7681442 Oct 31 06:24 azure.log

[root@unused log]# wc azure.log
      0   88963 7692273 azure.log

[root@unused log]# wc -l azure.log
0 azure.log

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

Version 5.9.4.7.20180829201904_ced41ae

How reproducible: 100%

Actual results: Log has content but showing 0 EOL

Expected results: It should print newline counts with a command "wc -l azure.log"

Comment 4 dmetzger 2018-11-01 14:01:42 UTC

*** This bug has been marked as a duplicate of bug 1640718 ***


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