Bug 1602382

Hey Douglas
Dan and I discuss the possibility of running this on pre 4.2 channels, by installing the 4.2 repo on the manager, running the tool, then disabling the repo and continuing with standard upgrade path.

Is this something that you have discussed?
If yes, which of the previous versions have you tested this on?

If no, please let me know exactly what environment this tool is currently capable of analysing, and please provide instructions for how this is done, and what anomalies you may find that would prevent you from performing the upgrade.

Yaniv
Can you please define what scenario this tool should be used in?

Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc

or also prior to major upgrades?

What is the main outcome you expect to see after running this tool that would prevent a customer from upgrading?

(In reply to Emma Heftman from comment #6)
> Yaniv
> Can you please define what scenario this tool should be used in?
> 
> Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc
> 
> or also prior to major upgrades?
> 
> What is the main outcome you expect to see after running this tool that
> would prevent a customer from upgrading?

Yaniv will provide the info but here some data:

This tool creates a HTML report file that provides an overview of customer environment and if detects a know issue from our knowledge base, it will raise on the report.

On RHVM 4.2.5 or higher:

# yum install rhv-log-collector-analyzer

# rhv-log-collector-analyzer --live
Generating reports:
===================
Generated analyzer_report.html

# rhv-log-collector-analyzer --live --html=/foo/bar.html
Generating reports:
===================
Generated /foo/bar.html

(In reply to Emma Heftman from comment #6)
> Yaniv
> Can you please define what scenario this tool should be used in?

- When planning a upgrade.
- When analyzing a problem with the environment. 
- When you want to get a environment status.

> 
> Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc
> 
> or also prior to major upgrades?

It is a recommended step, but not mandatory for any planned upgrade.
More useful before major upgrades probably. 

> 
> What is the main outcome you expect to see after running this tool that
> would prevent a customer from upgrading?

Make sure the system is in good state for upgrade.
Get a output of the status of the environment.

(In reply to Yaniv Lavi from comment #10)
> (In reply to Emma Heftman from comment #6)
> > Yaniv
> > Can you please define what scenario this tool should be used in?
> 
> - When planning a upgrade.
> - When analyzing a problem with the environment. 
> - When you want to get a environment status.
> 
> > 
> > Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc
> > 
> > or also prior to major upgrades?
> 
> It is a recommended step, but not mandatory for any planned upgrade.
> More useful before major upgrades probably. 
> 
> > 
> > What is the main outcome you expect to see after running this tool that
> > would prevent a customer from upgrading?
> 
> Make sure the system is in good state for upgrade.
> Get a output of the status of the environment.

So you recommend this to be used for general troubleshooting and prior to upgrades. I'll make this a module that can be reused in the Admin and Upgrade Guides.

Douglas/Jiri
Can you explain the exact steps that are required in order to run this on 4.0 and 4.1.
For example, is it only provided on a 4.2 channel?

Would they need to subscribe to a channel?
Is it possible to make the tool available online so that it could be used without   the 4.2 channel?

(In reply to Yaniv Lavi from comment #10)
> (In reply to Emma Heftman from comment #6)
> > Yaniv
> > Can you please define what scenario this tool should be used in?
> 
> - When planning a upgrade.
> - When analyzing a problem with the environment. 
> - When you want to get a environment status.
> 
> > 
> > Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc
> > 
> > or also prior to major upgrades?
> 
> It is a recommended step, but not mandatory for any planned upgrade.
> More useful before major upgrades probably. 
> 
> > 
> > What is the main outcome you expect to see after running this tool that
> > would prevent a customer from upgrading?
> 
> Make sure the system is in good state for upgrade.
> Get a output of the status of the environment.

Yaniv/Dan, please explain whether we want to provide the tool on channels other than 4.2 to enable it to be used in major upgrades. If not I will document it for minor upgrades only.

(In reply to Emma Heftman from comment #14)
> (In reply to Yaniv Lavi from comment #10)
> > (In reply to Emma Heftman from comment #6)
> > > Yaniv
> > > Can you please define what scenario this tool should be used in?
> > 
> > - When planning a upgrade.
> > - When analyzing a problem with the environment. 
> > - When you want to get a environment status.
> > 
> > > 
> > > Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc
> > > 
> > > or also prior to major upgrades?
> > 
> > It is a recommended step, but not mandatory for any planned upgrade.
> > More useful before major upgrades probably. 
> > 
> > > 
> > > What is the main outcome you expect to see after running this tool that
> > > would prevent a customer from upgrading?
> > 
> > Make sure the system is in good state for upgrade.
> > Get a output of the status of the environment.
> 
> Yaniv/Dan, please explain whether we want to provide the tool on channels
> other than 4.2 to enable it to be used in major upgrades. If not I will
> document it for minor upgrades only.

Let's start with 4.2.
We have KBase on using it in older releases.

(In reply to Douglas Schilling Landgraf from comment #7)
> (In reply to Emma Heftman from comment #6)
> > Yaniv
> > Can you please define what scenario this tool should be used in?
> > 
> > Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc
> > 
> > or also prior to major upgrades?
> > 
> > What is the main outcome you expect to see after running this tool that
> > would prevent a customer from upgrading?
> 
> Yaniv will provide the info but here some data:
> 
> This tool creates a HTML report file that provides an overview of customer
> environment and if detects a know issue from our knowledge base, it will
> raise on the report.
> 
> On RHVM 4.2.5 or higher:
> 
> # yum install rhv-log-collector-analyzer
> 
> # rhv-log-collector-analyzer --live
> Generating reports:
> ===================
> Generated analyzer_report.html
> 
> # rhv-log-collector-analyzer --live --html=/foo/bar.html
> Generating reports:
> ===================
> Generated /foo/bar.html

Hey Douglas
I just noticed that in your example you say "on RHVM 4.2.5 or higher". I just wanted to confirm that this tool CANNOT be used for upgrading from 4.2.3 to 4.2.6 or 4.2.4 to 4.2.6.

(In reply to Emma Heftman from comment #16)
> (In reply to Douglas Schilling Landgraf from comment #7)
> > (In reply to Emma Heftman from comment #6)
> > > Yaniv
> > > Can you please define what scenario this tool should be used in?
> > > 
> > > Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc
> > > 
> > > or also prior to major upgrades?
> > > 
> > > What is the main outcome you expect to see after running this tool that
> > > would prevent a customer from upgrading?
> > 
> > Yaniv will provide the info but here some data:
> > 
> > This tool creates a HTML report file that provides an overview of customer
> > environment and if detects a know issue from our knowledge base, it will
> > raise on the report.
> > 
> > On RHVM 4.2.5 or higher:
> > 
> > # yum install rhv-log-collector-analyzer
> > 
> > # rhv-log-collector-analyzer --live
> > Generating reports:
> > ===================
> > Generated analyzer_report.html
> > 
> > # rhv-log-collector-analyzer --live --html=/foo/bar.html
> > Generating reports:
> > ===================
> > Generated /foo/bar.html
> 
> Hey Douglas
> I just noticed that in your example you say "on RHVM 4.2.5 or higher". I
> just wanted to confirm that this tool CANNOT be used for upgrading from
> 4.2.3 to 4.2.6 or 4.2.4 to 4.2.6.

We only provide the rpm in >= 4.2.5 repo. If users want to use in previous versions, they will need to add 4.2.5 repo first and install the tool.

(In reply to Douglas Schilling Landgraf from comment #17)
> (In reply to Emma Heftman from comment #16)
> > (In reply to Douglas Schilling Landgraf from comment #7)
> > > (In reply to Emma Heftman from comment #6)
> > > > Yaniv
> > > > Can you please define what scenario this tool should be used in?
> > > > 
> > > > Prior to minor 4.2 upgrades only? 4.2.3.> 4.2.5 etc
> > > > 
> > > > or also prior to major upgrades?
> > > > 
> > > > What is the main outcome you expect to see after running this tool that
> > > > would prevent a customer from upgrading?
> > > 
> > > Yaniv will provide the info but here some data:
> > > 
> > > This tool creates a HTML report file that provides an overview of customer
> > > environment and if detects a know issue from our knowledge base, it will
> > > raise on the report.
> > > 
> > > On RHVM 4.2.5 or higher:
> > > 
> > > # yum install rhv-log-collector-analyzer
> > > 
> > > # rhv-log-collector-analyzer --live
> > > Generating reports:
> > > ===================
> > > Generated analyzer_report.html
> > > 
> > > # rhv-log-collector-analyzer --live --html=/foo/bar.html
> > > Generating reports:
> > > ===================
> > > Generated /foo/bar.html
> > 
> > Hey Douglas
> > I just noticed that in your example you say "on RHVM 4.2.5 or higher". I
> > just wanted to confirm that this tool CANNOT be used for upgrading from
> > 4.2.3 to 4.2.6 or 4.2.4 to 4.2.6.
> 
> We only provide the rpm in >= 4.2.5 repo. If users want to use in previous
> versions, they will need to add 4.2.5 repo first and install the tool.

Unless someone tells me differently, I will document that this is from 4.2.5.

The updated guide is available in the Customer Portal: 
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/upgrade_guide/#Analyzing_the_Environment_minor_updates