Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1389691 - Wrong links on Set resource requests and limits
Wrong links on Set resource requests and limits
Status: CLOSED CURRENTRELEASE
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.4.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Samuel Padgett
Yadan Pei
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-10-28 05:14 EDT by Yadan Pei
Modified: 2017-03-08 13 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-12-12 08:02:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Description Yadan Pei 2016-10-28 05:14:55 EDT
Description of problem:
When add autoscaler for this DC does not have any container with CPU request set,there is warning message:
This deployment config does not have any containers with a CPU request set. Autoscaling will not work without a CPU request. Set resource requests and limits

"Set resource requests and limits" is a link and it should links to Set Resource Limits page, but now clicking on this link directs to error page "An error has occurred.Kind or name parameter missing."

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

How reproducible:
Always

Steps to Reproduce:
1.Create DC
# oc run myrun  --image=aosqe/hello-openshift
2.Go to Applications -> Deployments -> myrun -> Add Autoscaler -> set Max Pods -> Create
3.Check autoscaler info on DC page, there is warning info on page:
This deployment config does not have any containers with a CPU request set. Autoscaling will not work without a CPU request. Set resource requests and limits
4.Click "Set resource requests and limits" link in warning info

Actual results:
4.Directs to error page, follow info given:
An error has occurred
Kind or name parameter missing.

Expected results:
4.Clicking on "Set resource requests and limits" link should redirects to Set Resource Limits page

Additional info:
Comment 2 Troy Dawson 2016-11-02 13:59:57 EDT
This has been merged into ose and is in OSE v3.4.0.19 or newer.
Comment 4 Yadan Pei 2016-11-02 22:56:23 EDT
Checked against v3.4.0.19+346a31d

Now links in warning info changed to "Edit resource requests and limits", clicking it will redirect to Edit Resource Limits page

Move to VERIFIED

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