Issue #7499: pulp_installer is unpredictable about when it resets the admin password - Pulp

Actions

Send by e-mail Copy link

Issue #7499

closed

pulp_installer is unpredictable about when it resets the admin password

Added by mdepaulo@redhat.com about 4 years ago. Updated about 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Category:

Installer - Moved to GitHub issues

Sprint/Milestone:

3.8.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Description

As mentioned in #7493 and https://github.com/pulp/pulp_installer/pull/427 , it is unpredictable about when it is run. From a user's perspective.

#7493 is about to make it run more often.

The current thinking is to not run change the password after initial install ever.

However, we still need pulp_default_admin_password to be defined in pulp_devel and pulp_health_check . The beginning of pulp_database_config also makes sure it is defined, we may remove that.

Related issues

Actions

Copy link

Updated by mdepaulo@redhat.com about 4 years ago

Related to Issue #7493: Installer: remove auth migration task added

Actions

Copy link

Updated by mdepaulo@redhat.com about 4 years ago

My proposed solution is this:

For initial install, always set it.
For upgrades or re-running the installer for any other reason, let it be determined by a variable like "pulp_always_reset_admin_pw"
Ignore whether or not migrations were run.

Actions

Copy link

Updated by mdellweg about 4 years ago

Since the health check tests seem to need the password, it looks like we assume that the installer needs to know the current pulp admin password anyway. So we could go a step further and say, that the password is managed by the installer. We can than add a test whether the password still works and (re-)set it. I'd say the variable should be named pulp_admin_password in that case.

On the other hand, i don't think the status endpoint (used in the health check) needs the password. So we could use the set-only-if-touched-file-is-absent approach. We would instruct the user to delete that file in order to reset the password via the installer.

Actions

Copy link