Logs unavailable during provisioning. {"message": "Log file not found", "errors": []}

So it does not work for provisioned nodes (if you click on node tat is deploying - issue is not reproduced), and faiked with
http://<ip_here>/api/logs?node=2&source=install/anaconda&level=INFO&_=1446206543357 with source install/anaconda is not found

so we need to fix mapping here https://github.com/openstack/fuel-web/blob/master/nailgun/static/views/cluster_page_tabs/nodes_tab_screens/node.jsx#L49-L55 and change anaconda soource to fuel-agent, according to we do not have source anaconda since we are using ibp

Fix proposed to branch: master
Review: https://review.openstack.org/240528

Reviewed: https://review.openstack.org/240528
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=af02bd8f9aac1a1007f3ce17e5d7842853bd7758
Submitter: Jenkins
Branch: master

commit af02bd8f9aac1a1007f3ce17e5d7842853bd7758
Author: Julia Aranovich <email address hidden>
Date: Fri Oct 30 15:50:37 2015 +0300

    Update default log source for provisioned node

    Closes-Bug: #1511705

    Change-Id: I1496ebce872990df887e342b957194953deffbf8

It still can be reproduced with the steps above until 'Installing Ubuntu' progress bar hits ~90%, after that it works as it should.
So reopen it back.

Reproduced at:

ISO version: fuel-8.0-147-2015-11-11_07-42-00.iso

# fuel fuel-version
api: '1.0'
astute_sha: 959b06c5ef8143125efd1727d350c050a922eb12
auth_required: true
build_id: '147'
build_number: '147'
feature_groups:
- mirantis
fuel-agent_sha: 07560a9fc3ce5301ace04d2d3e5d68db6ee4f8d5
fuel-createmirror_sha: d3949f3094248b9686a4c20caea5ae13c9738a8d
fuel-library_sha: a94bddc9ae6198510402a42ad78699cb9d70fda8
fuel-nailgun-agent_sha: 00b4b11553c250f22c0079fb74c8b782dcb7b740
fuel-nailgun_sha: fe7fe7d082b4045d34e9b2d9aac6766dbd6cd576
fuel-ostf_sha: f771e23c5cbecbbb578ee4574ae2e51aa2e91819
fuel-upgrade_sha: 1e894e26d4e1423a9b0d66abd6a79505f4175ff6
fuelmain_sha: 3b64b95f6b513b0d46b57525a858eea7a9809da3
fuelmenu_sha: f40c3ec0e0e1bdc499f4cb50d46aecefb4dbb7c7
network-checker_sha: a57e1d69acb5e765eb22cab0251c589cd76f51da
openstack_version: 2015.1.0-8.0
production: docker
python-fuelclient_sha: a88bc94b562ee511eb277183d0a750a1e3312662
release: '8.0'
release_versions:
  2015.1.0-8.0:
    VERSION:
      api: '1.0'
      astute_sha: 959b06c5ef8143125efd1727d350c050a922eb12
      build_id: '147'
      build_number: '147'
      feature_groups:
      - mirantis
      fuel-agent_sha: 07560a9fc3ce5301ace04d2d3e5d68db6ee4f8d5
      fuel-createmirror_sha: d3949f3094248b9686a4c20caea5ae13c9738a8d
      fuel-library_sha: a94bddc9ae6198510402a42ad78699cb9d70fda8
      fuel-nailgun-agent_sha: 00b4b11553c250f22c0079fb74c8b782dcb7b740
      fuel-nailgun_sha: fe7fe7d082b4045d34e9b2d9aac6766dbd6cd576
      fuel-ostf_sha: f771e23c5cbecbbb578ee4574ae2e51aa2e91819
      fuel-upgrade_sha: 1e894e26d4e1423a9b0d66abd6a79505f4175ff6
      fuelmain_sha: 3b64b95f6b513b0d46b57525a858eea7a9809da3
      fuelmenu_sha: f40c3ec0e0e1bdc499f4cb50d46aecefb4dbb7c7
      network-checker_sha: a57e1d69acb5e765eb22cab0251c589cd76f51da
      openstack_version: 2015.1.0-8.0
      production: docker
      python-fuelclient_sha: a88bc94b562ee511eb277183d0a750a1e3312662
      release: '8.0'
      shotgun_sha: 25dd78a3118267e3616df0727ce746e7dead2d67
shotgun_sha: 25dd78a3118267e3616df0727ce746e7dead2d67

Logs can not be fetched because there is no fuel-agent among log sources for provisioning node: GET /api/logs/sources/nodes/3 returns http://paste.openstack.org/show/4JPxo6mjj5ETp302lMtL/

So, we need to provide a correct log source name here: https://github.com/openstack/fuel-web/blob/master/nailgun/static/views/cluster_page_tabs/nodes_tab_screens/node.js#L53-L54

Or the absence of fuel-agent logs in the node sources should be investigated.

It does not qualify for being a Critical one according to the official specification [1]. Decreasing the priority.

1. https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Confirm_and_triage_bugs

According to the bugs definition, it qualifies to Low (doesn't affect deployment, workaround for logs - you can ssh and use Linux tools to look into logs).

View Logs button makes request to "install/fuel-agent" log
GET api/logs?node=2&source=install%2Ffuel-agent&...

But if we look in list of available logs for the same node at the same time , then we'll see that install/fuel-agent log not available.
GET api/logs/sources/nodes/2?...
In request will be only next logs:
bootstrap/
dmesg
messages
mcollective
agent

I think that "View Logs" button should be disabled while "install/fuel-agent" logs not in list of available logs.
List of available logs can be fetched by request GET api/logs/sources/nodes/2?.. where "2" is node id.

> View Logs button makes request to "install/fuel-agent" log

indeed, it stored under different path. "bootstrap/fuel-agent.log"

i think something wrong defined in settings.yaml.

https://github.com/openstack/fuel-web/blob/35396b8fb3396711ee6620bd7ebd3d3452e88139/nailgun/nailgun/settings.yaml#L332-L337

For it looks like python related bug, rather than UI one.

So, fuel-agent (provisioning) logs were accidentally placed under 'install' section (which was used only for native provisioning)

Hope this helps.

I could not reproduce this on ISO 483. Marking as incomplete.

I managed to reproduce it, thanks to apalkina. I think that this is an UI issue, as the url to node log is generated to show fuel-agent log, which is not available. Fix for this would be pointing to an actual available log in this url.

Not having fuel-agent log is an another issue, which should probably have separate bug created.

This video helps to understand how to reproduce issue