#9359 Demo FreeIPA - Login failed due to an unknown reason
Closed: fixed by pvoborni. Opened by fischerdouglas.

Request for enhancement

As network admin , I want test/take a look on UI of FreeIPA so that we consider adopting it or not.

Issue

[description of the issue]

Steps to Reproduce

  1. Access https://ipa.demo1.freeipa.org/ipa/ui/
  2. Cancel the html auth box twice
    Obs.: I Tried to put admin/Secret123 in there also...
  3. Enter "admin" on Username field
    Obs.: I Tried with the other users listed on the page explaining the Demo.
  4. Enter "Secret123" on Password field

Actual behavior

It presents the red error message:
"Login failed due to an unknown reason"

Expected behavior

Allow-me to access the UI

Version/Release/Distribution

Not appliable. Online Demo Version.

Additional info:

Not appliable. Online Demo Version.

Demo_FreeIPA_LoginFailed.jpg


It will reset itself at 05:00-UTC tomorrow morning.

I will wait...
I bring some news here.

It will reset itself at 05:00-UTC tomorrow morning.

I repeated the test a few seconds ago and the error persists.

Looks like something is wrong with the recorded image. I can login as admin over ssh but not over Web UI.

We need to investigate what's exactly is broken. It will take some time. Meanwhile, you can deploy FreeIPA on a VM for testing purposes. Thank you for reporting this issue!

There is a pkinit failing on the server while doing password_login. I have a bigger maintenance of the demo planned for next week as there were more issues. CS was failing mostly because of OOM issues, probably caused by smaller flavor of the vm.

I think reinstall of the whole vm and thus also upgrade to more recent versions is due.

I remembered this a few moments ago...
And I just tried to access.

Now seems that there is no DNS entry for ipa.demo1.freeipa.org

Just reporting.

Metadata Update from @pvoborni:
- Issue assigned to pvoborni

I saw some movements on this issue and resolved to see how it was...

I just got success in accessing the demo environment.

Thank you all!

There were some improvements yesterday, but the maintenance work is still ongoing.

So far I:
- reinstalled the vm from scratch using Fedora 38 and FreeIPA 4.10.1 - this should fix the main issues
- adjusted start timeout for pki-tomcatd@pki-tomcat.service as PKI did not start fast enough (i.e. in 45s) after image reset and thus pki and certmonger failed. This was visible in UI when going to Certificate pages.

I'll monitor
- how stable the image reset automation is
- probably adjust some timeouts for ^^

The reset automation seems to be working well. Thus closing this ticket.

Metadata Update from @pvoborni:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata