Bug 1554518
Summary: | Azure load balancer does not create | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ryan Cook <rcook> |
Component: | Networking | Assignee: | Ben Bennett <bbennett> |
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.0 | CC: | aos-bugs, bbennett, zzhao |
Target Milestone: | --- | ||
Target Release: | 3.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: The documentation for how to create an Azure LB was incomplete.
Consequence: You could not make a working LB on Azure by following the docs.
Fix: The docs were corrected to add the missing steps.
Result: Azure LB creation is now correctly documented.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-07-30 19:10:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ryan Cook
2018-03-12 20:32:29 UTC
@ben this can be resolved if the ga docs include the following tenantId: <value> subscriptionId: <value> aadClientId: <value> aadClientSecret: <null> aadTenantId: <value> resourceGroup: <value> cloud: <value> location: <value> vnetName: <value> securityGroupName: <value> primaryAvailabilitySetName: <value> The above ^^ can create load balancers in 3.9 This was fixed by https://github.com/openshift/openshift-docs/pull/8550 (Thanks for the PR @Ryan) The document has been updated according to the comment#1 Set the bug as verified. 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/RHBA-2018:1816 |