During migration, improve info about usage on ssl-password and logs(bsc#1243009)

[mbussolotto]

What does this PR change?

Codespace

Check if you already have a running container clicking on

Test coverage

• Unit tests were added

• DONE

Links

Issue(s): https://github.com/SUSE/spacewalk/issues/27192

• DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

If you don't need a changelog check, please mark this checkbox:

• No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Before you merge

Check How to branch and merge properly!

[cbosdo]

I haven't seen where we make the SSL error message a bit more obvious, but may be I'm blind

[mbussolotto]

I haven't seen where we make the SSL error message a bit more obvious, but may be I'm blind

You're not blind, it's not present. But since the with REDACT is fixed, now the output should be the one of rhn-ssl-tool (maybe wrong password or something like that)

[mbussolotto]

I haven't seen where we make the SSL error message a bit more obvious, but may be I'm blind

You're not blind, it's not present. But since the with REDACT is fixed, now the output should be the one of rhn-ssl-tool (maybe wrong password or something like that)

I added it

[cbosdo]

I'm not sure we should get the hostname rename change in the same PR as this one: it's a bit risky at this phase of the release

[deneb-alpha]

I'm not sure we should get the hostname rename change in the same PR as this one: it's a bit risky at this phase of the release

I agree. can we split the changes and have the hostname rename in a separate PR?
The rename bsc is even not mentioned in the PR description...

[cbosdo]

I'm not sure we should get the hostname rename change in the same PR as this one: it's a bit risky at this phase of the release

I agree. can we split the changes and have the hostname rename in a separate PR? The rename bsc is even not mentioned in the PR description...

The hostname rename has its own PR, it's just that this one is based on it to reuse some refactoring I made. Let me see if we can just extract the refactoring in a small commit and share it between the two PRs.

[mbussolotto]

this was not intended. I cherrypicked that change so the rebase would be easier once we'll merge it.

[mbussolotto]

Just to be more clear, this PR requires changes present in the other PR. Resolving conflict after might be a real mess, so the idea is simply to remove that commit once the other PR will be merged (maybe rebase it will be smart enough).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud