Description of problem: If I am viewing a page in the web UI and then select: Configure --> Environments I am often sent to a 404 error page. If I then press the browser back arrow I arrive at the Puppet Environments page. This suggest I did go to that page when I selected it from the menu, but that I was immediately forwarded to the error page. Version-Release number of selected component (if applicable): Red Hat Satellite Version 6.2 foreman-installer-katello-3.0.0.47-2.el7sat.noarch katello-3.0.0-8.el7sat.noarch How reproducible: Steps to Reproduce: 1. Visit a page such as Content -> Products 2. Select Configure --> Environments Actual results: https://rhel7-2-sat6-2.example.com/404 Expected results: https://rhel7-2-sat6-2.example.com/environments Additional info: The error message includes this "If you are the application owner check the logs for more information." Could you make that a little more verbose? Which logs exactly? I could not see anything in var/log/message but then I am not sure what to look for.
Note: This seems to be replicable only on navigating from Katello resource (page) to Puppet Environments (which is Foreman, i believe). Looks like the request to foreman is not even made (no sign of *any* processed http request in production.log). Instead, a straight request to http://server.com/404 is made according /var/log/httpd/foreman-ssl_access_ssl.log: <requestor ip> - - [02/Jul/2016:06:34:54 -0400] "GET /404 HTTP/1.1" 304 - "https://sat6.server.com/environments" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0" I'm suspecting some Javascript overrides the request and makes another one straight to /404 (Probably Bastion: https://github.com/Katello/bastion/blob/94333abda01d7634a0d19fc8c638067532f88be7/app/assets/javascripts/bastion/features/feature-flag.run.js#L14)
Looks like the following commit has revealed the issue as a side effect: https://github.com/Katello/bastion/commit/dee91a07f70d09348afc14d43597c13a4428289c reverting the code back to original (removing the conditional and redirecting to 'url' straight away) fixes the issue (I'm not suggesting reverting it back)
This also happens when navigating from a Bastion page to "Manage Organizations".
Created redmine issue http://projects.theforeman.org/issues/15665 from this bug
PR: https://github.com/Katello/bastion/pull/118
Upstream bug component is Uncategorized
*** Bug 1364251 has been marked as a duplicate of this bug. ***
Moving to POST since upstream bug http://projects.theforeman.org/issues/15665 has been closed
*** Bug 1376046 has been marked as a duplicate of this bug. ***
FAILED QA: on sat6.3.0 snap#5 I keep getting 404 on navigating from a Katello pages (e.g. Activation keys) to Hosts or New Host pages.
Upstream bug component is WebUI
(In reply to Roman Plevka from comment #15) > FAILED QA: > on sat6.3.0 snap#5 > > I keep getting 404 on navigating from a Katello pages (e.g. Activation keys) > to Hosts or New Host pages. What version of bastion?
(In reply to Walden Raines from comment #17) > (In reply to Roman Plevka from comment #15) > > FAILED QA: > > on sat6.3.0 snap#5 > > > > I keep getting 404 on navigating from a Katello pages (e.g. Activation keys) > > to Hosts or New Host pages. > > What version of bastion? Never mind.
Similar issue: If you're at https://satellite.example.com/content_hosts and you click that top left link, you get a 404 page.
Fixed in https://github.com/Katello/bastion/pull/165 with: commit 440714a1dc4cb1a8848a342edfd4e4164c257504 Author: Walden Raines <walden> Date: Tue Jan 24 15:57:41 2017 -0500 Fixes #15665: get correct root url for 404 states. We were getting the relative url instead of an absolute url when determining if a state transition should result in a 404 (which worked until nutupane was removed). This commit fixes the root url logic. http://projects.theforeman.org/issues/15665
Setting as triaged as there's a fix already upstream
*** Bug 1418695 has been marked as a duplicate of this bug. ***
*** Bug 1409818 has been marked as a duplicate of this bug. ***
Please add verifications steps for this bug to help QE verify
*** Bug 1394974 has been marked as a duplicate of this bug. ***
Verified on 6.2.9 Navigation works as intended + functionality related to Red Hat Satellite logo also works properly All of these things didn't work in 6.2.8, so verified that fix exactly delivered in 6.2.9
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-2017:1191
Changing the 'requires_doc_text' flag to '-'.