Critical Is this expected behavior on a system with a new Jenkins 2.0 installation? How would a first user have been created if I do not have a previous version of Jenkins installed?
HTTP ERROR 401
Problem accessing /securityRealm/createFirstAccount. Reason: First user was already created
Powered by Jetty://
[JENKINS-34255] Cannot create first user on new install for Jenkins 2.0
Xin Chen
added a comment - Thanks Daniel! I'm able to access the URL right now with the workaround. emily_mstr danielbeck rtyler I'll see what I can do to reproduce this and examine the code to see if there's anything else to do to prevent it, it must be a timing issue after the 'jenkins is working...' refresh happens at startup time...
kzantow I just reproduced this on Jenkins 2.37. Have you made any progress here?
Ethan Strominger
added a comment - I ran into the same problem and before I saw this issue, I logged https://issues.jenkins-ci.org/browse/JENKINS-48352 Issue occurred in Chrome. If I try http://localhost:8080/ from a different Chrome tab or from Firefox, I get a log in screen asking for user name and password and cannot go further.
Ethan Strominger
added a comment - I ran into the same problem and before I saw this issue, I logged https://issues.jenkins-ci.org/browse/JENKINS-48352 Issue occurred in Chrome. If I try http://localhost:8080/ from a different Chrome tab or from Firefox, I get a log in screen asking for user name and password and cannot go further.
Ethan Strominger
added a comment - I was using 2.73.3. I still have the frozen setup wizard window open.
Ethan Strominger
added a comment - I was using 2.73.3. I still have the frozen setup wizard window open. The form shown to users is not the Jenkins 2 setup wizard at all, but a regular Jenkins "first user" form that has existed forever and is the way to set up a user when the security realm is Jenkins user DB, and no user exists.
This issue seems to be with the CREATE_FIRST_USER_FILTER in HudsonPrivateSecurityRealm.
First, the security realm is set. Then, a user is added. Between the two, the servlet filter is installed. Only after the setup wizard finishes installation is its servlet filter installed.
Either there's an ordering issue here, or a race condition. Not sure why HudsonIsLoading would no longer handle requests at that time, though. Doesn't look like it's happening in separate threads.
Ethan Strominger
added a comment - danielbeck Does this pertain to my logged issue as well (https://issues.jenkins-ci.org/browse/JENKINS-48352) that you said is unrelated to the current thread? How are the two different?
Ethan Strominger
added a comment - danielbeck Does this pertain to my logged issue as well ( https://issues.jenkins-ci.org/browse/JENKINS-48352 ) that you said is unrelated to the current thread? How are the two different? ethanstrominger Since they're unrelated, no. This issue, as I and the reporter explained, doesn't even show the setup wizard.
This is my first time play with Jenkins so I don't think anything leftover there.