Bug 53587 - App relution: Installation broken with Password confirmation doesn't match the requirements.
App relution: Installation broken with Password confirmation doesn't match th...
Status: NEW
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-07-16 10:53 CEST by Felix Botner
Modified: 2021-10-14 12:51 CEST (History)
1 user (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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2021-07-16 10:53:25 CEST
i used the same string for the admin username and password, installation was fine  but the docker container wasn't running, last  log message:

2021-07-16 08:25:54.622  WARN 162 [        main] ServerApplicationContext: Exception encountered during context initialization - cancelling refresh attempt: org.springframework.bean
s.factory.BeanCreationException: Error creating bean with name 'relutionWizardBootstrapper': Invocation of init method failed; nested exception is javax.validation.ConstraintViolati
onException: Password confirmation doesn't match the requirements.
Password has to match following requirements:
must not be your username,
Please try again. []

The Problem is, there is no feedback for the user, from the appcenters point of view everything work, but the apps webinterface isn't working, only solution for me was to re-install the app
Comment 1 Florian Best univentionstaff 2021-10-14 12:51:30 CEST
@Dirk: git:353418dfb0382e5e4f6324b5931c986854ee4650
Why are you adding sleeps after update_apps_via_umc in the config files instead of in that function?
Even better would be if the function update_apps_via_umc blocks from itself until the apps are upgraded / ready.