Bug 1925429 - Add documentation button for Azure
Summary: Add documentation button for Azure
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: 6.9.0
Hardware: x86_64
OS: Linux
Target Milestone: 6.10.0
Assignee: Chris Roberts
QA Contact: Jitendra Yejare
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-05 08:00 UTC by Kenny Tordeurs
Modified: 2021-11-16 14:10 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman_theme_satellite-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-16 14:10:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
gem (41.50 KB, application/x-tar)
2021-03-10 16:11 UTC, Chris Roberts
no flags Details

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31837 0 Normal Closed Add documentation button for Azure 2021-02-16 19:56:52 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:10:12 UTC

Description Kenny Tordeurs 2021-02-05 08:00:10 UTC
Description of problem:
All compute resource providers have a 'Documentation' button aside from Azure Resource Manager when creating the Compute Resource

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

How reproducible:

Steps to Reproduce:
1. Go to Compute Resources
2. Attempt to create Azure CR

Actual results:
No Documentation button

Expected results:
Documentation button

Additional info:

Comment 2 Chris Roberts 2021-02-08 20:46:58 UTC
GH Link:


Comment 3 Patrick Creech 2021-03-09 16:38:41 UTC
Hey Chris!

Can we get a release of the foreman_azure_rm 2.1.z line with these fixes in it?

Comment 5 Chris Roberts 2021-03-10 16:11:14 UTC
Created attachment 1762372 [details]

Comment 6 Jitendra Yejare 2021-03-22 10:37:08 UTC
Failed QA!

Steps to Reproduce:
1. Go to Compute Resources
2. Attempt to create Azure CR
3. Click on the documentation button.


The documentation button redirects to upstream documentation `https://theforeman.org/plugins/foreman_azure/2.1.x/` for Azure CR whereas for other CRs its pointing to downstream documentation `https://access.redhat.com/documentation`.


Azure CR also should point to the Downstream documentaion.

Comment 9 Jitendra Yejare 2021-06-16 12:03:43 UTC

I was trying to verify this on 6.10 latest snap but I see the documentation button is still pointing to upstream documentation (https://theforeman.org/plugins/foreman_azure/2.2.x/). 

This is the same reason for which I failedQA this bug in Comment 6.

Is the behaviour expected ? else Shall I FailQA this bug ?

Comment 10 Evgeni Golov 2021-06-23 17:31:30 UTC
Which version of tfm-rubygem-foreman_theme_satellite did you try this with?

I think this is only fixed in 8.0.x, which will ship in *this* snap.

Comment 12 Jitendra Yejare 2021-06-28 15:03:11 UTC
Failed QA! 

RPM : tfm-rubygem-foreman_theme_satellite-

Snap : Satellite 6.10 Snap 6.0

This is still redirecting to the foreman URL - https://theforeman.org/plugins/foreman_azure/2.2.x/

Expected Result: This should redirect to the downstream documentation!

Comment 14 Jitendra Yejare 2021-08-09 08:50:47 UTC

@Satellite 6.10.0 Snap 12

1. Go to Infrastructure -> Azure Compute Resource.
2. Click on the documentation link.

1. The 6.10 satellite redirects to the correct URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/provisioning_guide/provisioning-cloud-instances-azure
2. Even though the redirected URL is not functional right now(since this testing is performed before the 6.10 release and the documentation for 6.10 published), but the corresponding URL for released version 6.9 works as expected: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html/provisioning_guide/provisioning-cloud-instances-azure

If post GA, the Azure documentation is changed for 6.10 then this bug should be reopened or recreated.

Comment 17 errata-xmlrpc 2021-11-16 14:10:01 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 (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.

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


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