Bug 33770 – Regression by redirect rule affects (at least) EC2 system setup

Bug 33770 - Regression by redirect rule affects (at least) EC2 system setup


Summary:	Regression by redirect rule affects (at least) EC2 system setup

Status:	CLOSED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P4 minor (vote)
Target Milestone:	UCS 3.2-0-errata
Assigned To:	Erik Damrose
QA Contact:	Florian Best

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-12-18 14:31 CET by Erik Damrose
Modified:	2014-02-17 09:28 CET (History)
CC List:	5 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Design, Usability
Max CVSS v3 score:

Attachments
Screenshot (107.37 KB, image/png) 2013-12-18 17:08 CET, Alexander Kläser	Details
View All Add an attachment (proposed patch, testcase, etc.)

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

Description Erik Damrose

2013-12-18 14:31:14 CET

The bugfix introduced by UCS 3.2 errata 10 affects system setup in our ec2 images: After the system setup completes, the user has to click on continue. In the background, apache and umc-(web-)server are restarted, then the user should be redirected to the umc login page (https://). 

With erratum 10 installed, this does no longer work. No page is loaded, the apache logs show no activity. It does however work when using http:// instead of https://

If i revert the changes from r46243, it works as expected -> The rewrite rules should be revised.

+++ This bug was initially created as a clone of Bug #29588 +++

Comment 1 Alexander Kläser

2013-12-18 17:08:25 CET

Created attachment 5704 [details]
Screenshot

To me it seems that this has something to do with the incognito mode in Chrome. I tried it with a normal session (update to latest errata via UMC) and could not find any problems. After the reload, Chromium prompts the attached warning, after continuing, the normal login screen appears.

Comment 2 Alexander Kläser

2013-12-18 17:11:09 CET

(In reply to Alexander Kläser from comment #1)
> Created attachment 5704 [details]
> Screenshot
> 
> To me it seems that this has something to do with the incognito mode in
> Chrome. I tried it with a normal session (update to latest errata via UMC)
> and could not find any problems. After the reload, Chromium prompts the
> attached warning, after continuing, the normal login screen appears.

Same applies to Chromium's incongito mode, it worked fine for my case.

Chromium Version: 31.0.1650.63

Comment 3 Stefan Gohmann

2013-12-30 10:22:57 CET

Eric, could you provide Alex a test instance where he is able to reproduce it?

Comment 4 Erik Damrose

2014-02-04 13:10:26 CET

I could not reproduce the bug with chromium (newer version) and firefox. It probably was a specific bug with the chromium version at that time.

worksforme

Comment 5 Florian Best

2014-02-11 15:40:27 CET

I couldn't reproduce this either. Also code review of the redirections seems fine plus manual tests for http and https.

Comment 6 Moritz Muehlenhoff

2014-02-17 09:28:13 CET

This erratum was resolved w/o a fixed package. Marking the bug as closed, so
that it doesn't show up in the list of to-be-released packages.