Bug 1395364 - [Docs] Update docs version to 1.1
Summary: [Docs] Update docs version to 1.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: doc-Release_Notes
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.1
Assignee: Julie
QA Contact: Thom Carlin
URL:
Whiteboard:
Depends On:
Blocks: 1404000
TreeView+ depends on / blocked
 
Reported: 2016-11-15 19:28 UTC by Fabian von Feilitzsch
Modified: 2017-02-28 01:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1404000 (view as bug list)
Environment:
Last Closed: 2017-02-28 01:41:26 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1397187 0 unspecified CLOSED [Docs] Add a troubleshooting section to docs 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2017:0335 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.1 2017-02-28 06:36:13 UTC

Internal Links: 1397187

Description Fabian von Feilitzsch 2016-11-15 19:28:08 UTC
Description of problem:
We now do our RHV provisioning with ansible, so we need to document where the logs can be found. 

The ansible log is located at $FOREMAN_LOG_DIR/deployments/$LABEL-$ID/ansible.log. Most failures should appear here. This file is also visible through the UI, by selecting the 'ansible.log' log option in the progress overview page.

Dev docs for logs: https://engineering.redhat.com/trac/RHCI/wiki/Debugging/RHEV_Provisioning

Comment 2 Julie 2016-12-01 06:24:19 UTC
Added ansible.log to the log files table in Chapter 5.

Comment 4 Thom Carlin 2016-12-12 17:46:40 UTC
Verified in latest doc spin, Section 5.5

Julie, is there a separate Install Guide for 1.1?

Comment 5 Derek 2016-12-12 19:09:02 UTC
There is.  Julie is working on it now (a draft has just been delivered to QE) and it will be available at the GA of QCI 1.1.

Comment 6 Thom Carlin 2016-12-12 19:44:26 UTC
Derek, Given this bz is filed against 1.0, do we need a separate bz for 1.1 or should I change this one back to ASSIGNED?

Comment 7 Derek 2016-12-12 19:49:16 UTC
I see this bug has a target release and version both saying 1.1 already...?

Comment 8 Thom Carlin 2016-12-12 20:07:13 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1404000 is for 1.0.  This bz is for 1.1, changing back to ASSIGNED until 1.1 docs are ready...

Comment 9 Thom Carlin 2016-12-12 20:08:10 UTC
Clearing needinfo? since Derek answered it ;-)

Comment 10 Julie 2016-12-12 20:24:04 UTC
(In reply to Thom Carlin from comment #9)
Good catch on the version. We don't maintain individual y-stream releases so the changes should only be in 1.1 and not 1.0. I will need to update the version number for the internal build. We can use this bug to track that.

Cheers,
Julie

Comment 12 Thom Carlin 2016-12-13 11:52:53 UTC
VERIFIED in 1.1 docs also :-D

Comment 16 errata-xmlrpc 2017-02-28 01:41:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:0335


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