Red Hat Bugzilla – Bug 906227
The "Follow these steps to install the client" link on get started page of application will redirect to a page which has no expected content.
Last modified: 2017-03-08 12:34 EST
Version-Release number of selected component (if applicable): http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.x/2013-01-29.1/ How reproducible: always Steps to Reproduce: 1.Go to website and login 2.Create an application and add mysql cartridge 3.Click the "Follow these steps to install the client" link on cartridge get started page +++ This bug was initially created as a clone of Bug #892906 +++ Description of problem: After adding mysql cartridge, click the "Follow these steps to install the client" link on the get started page of application, the url of the link is "https://openshift.redhat.com/community/get-started#install_client_tools", but the page has no expected content. Version-Release number of selected component (if applicable): devenv_2643 How reproducible:always Steps to Reproduce: 1.Go to openshift website and login 2.Create an application and add mysql cartridge 3.Click the "Follow these steps to install the client" link on cartridge get started page Actual results: The link will redirect to a page which has no expected content. Expected results: The link should redirect to a page which has expected content. Maybe the correct url of that link is https://openshift.redhat.com/community/get-started#cli Additional info: --- Additional comment from Clayton Coleman on 2013-01-10 13:15:47 EST --- Fixed in https://github.com/openshift/origin-server/pull/1138 --- Additional comment from Yujie Zhang on 2013-01-10 22:11:20 EST --- (In reply to comment #1) Tested on devenv_2661, the link can redirect to the right page now, thanks.
pull request is opened for enterprise-1.1
Version: http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.z/2013-02-06.2/ openshift-console-0.0.16-1.el6op.noarch Verify: The link is correct.
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. http://rhn.redhat.com/errata/RHSA-2013-0582.html