Bug #31587
Some Settings have a blank name on Settings page
Pull request:
Found in Releases:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1912219
Description of problem: Some of the settings contain a blank name
Version-Release number of selected component (if applicable):
6.9 Snap7
How reproducible:
always
Steps to Reproduce:
1. Upgrade Satellite from 6.8 to 6.9
2. Upgrade complete successfully.
3. Login Satellite--> Go to -->Administrator-->Settings
Some of the entries in the "content", "Foreman-task", and "RH-Cloud " have empty names.
Actual results:
Some of the settings contain a blank name
Expected results:
Setting name should not be blank.
Additional info:
Associated revisions
History
#1
Updated by Ondřej Ezr 8 months ago
Updated by - Target version set to 2.3.2
- Subject changed from Some Settings have a blank name on Settings page to Some Settings have a blank name on Settings page
#2
Updated by Ondřej Ezr 8 months ago
- Triaged changed from No to Yes
#3
Updated by The Foreman Bot 8 months ago
Updated by - Assignee set to Ondřej Ezr
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8235 added
#4
Updated by The Foreman Bot 8 months ago
- Fixed in Releases 2.4.0 added
#5
Updated by Ondřej Ezr 8 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|2f66d66200529c78ab374f5ac381424248474d6b.
#6
Updated by The Foreman Bot 8 months ago
- Pull request https://github.com/theforeman/foreman/pull/8241 added
#7
Updated by Tomer Brisker 8 months ago
Updated by - Fixed in Releases 2.3.2 added
Fixes #31587 - SettingName fallback to name (#8235)
In 623542da3c16d4033b94317e0ac757021132b884 we've forgot to add fallback in fullName column to setting.name.
This adds fallback to `setting.name` if the `setting.fullName` is omitted.