RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1951936 - [Edge] After upgrade, user cannot login if upgrade bp has no user defined
Summary: [Edge] After upgrade, user cannot login if upgrade bp has no user defined
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: osbuild-composer
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Achilleas Koutsou
QA Contact: Yi He
Eliane Ramos Pereira
URL:
Whiteboard:
Depends On:
Blocks: 2060575 2062766
TreeView+ depends on / blocked
 
Reported: 2021-04-21 08:21 UTC by Yi He
Modified: 2022-05-10 14:20 UTC (History)
8 users (show)

Fixed In Version: osbuild-composer-46.1-1.el8
Doc Type: Bug Fix
Doc Text:
.Users can now specify user accounts in the RHEL for Edge Installer blueprint Previously, performing an update on your blueprint without a user account defined in the RHEL for Edge Commit for the upgrade, such as adding a rpm package, would cause users to be locked out of their system, after the upgrade was applied. It caused users to have redefine user accounts when upgrading an existing system. This issue has been fixed to allow users to specify user accounts in the RHEL for Edge Installer blueprint, that creates a user on the system at installation time, rather than having the user as part of the `ostree` commit.
Clone Of:
: 2060575 2062766 (view as bug list)
Environment:
Last Closed: 2022-05-10 13:49:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2022:1841 0 None None None 2022-05-10 13:49:45 UTC

Description Yi He 2021-04-21 08:21:51 UTC 
Description of problem:
Create a rhel-edge-container image with bp that a user is added, then install rhel for edge. Can use that user to login system. Then make an upgrade bp, add additional RPMs, but do not define any user, create an upgrade image. 
Upgrade rhel for edge, after upgrade, cannot login with that user.


Version-Release number of selected component (if applicable):
RHEL 8.4

How reproducible:
Everytime

Steps to Reproduce:
1. Create blueprint like this, define a user named admin.
name = "container"
description = "A base rhel-edge container image"
version = "0.0.1"
modules = []
groups = []

[[packages]]
name = "python36"
version = "*"

[customizations]
[customizations.kernel]
name = "kernel-rt"
append = ""

[[customizations.user]]
name = "admin"
description = "Administrator account"
password = "$6$GRmb7S0p8vsYmXzH$o0E020S.9JQGaHkszoog4ha4AQVs3sk8q0DvLjSMxoxHBKnB2FBXGQ/OkwZQfW/76ktHd0NX5nls2LPxPuUdl."
key = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCzxo5dEcS+LDK/OFAfHo6740EyoDM8aYaCkBala0FnWfMMTOq7PQe04ahB0eFLS3IlQtK5bpgzxBdFGVqF6uT5z4hhaPjQec0G3+BD5Pxo6V+SxShKZo+ZNGU3HVrF9p2V7QH0YFQj5B8F6AicA3fYh2BVUFECTPuMpy5A52ufWu0r4xOFmbU7SIhRQRAQz2u4yjXqBsrpYptAvyzzoN4gjUhNnwOHSPsvFpWoBFkWmqn0ytgHg3Vv9DlHW+45P02QH1UFedXR2MqLnwRI30qqtaOkVS+9rE/dhnR+XPpHHG+hv2TgMDAuQ3IK7Ab5m/yCbN73cxFifH4LST0vVG3Jx45xn+GTeHHhfkAfBSCtya6191jixbqyovpRunCBKexI5cfRPtWOitM3m7Mq26r7LpobMM+oOLUm4p0KKNIthWcmK9tYwXWSuGGfUQ+Y8gt7E0G06ZGbCPHOrxJ8lYQqXsif04piONPA/c9Hq43O99KPNGShONCS9oPFdOLRT3U= ostree-image-test"
home = "/home/admin/"
groups = ["wheel"]

2. Use this blueprint to build image, "composer-cli compose start-ostree container rhel-edge-container --ref rhel/8/x86_64/edge", after build finished, download image and run container, container serves ostree image content at http://192.168.100.1/repo/.


3. Create a Kickstart file, includes the ostree url http://192.168.100.1/repo/.

4. Use kickstart file to install RHEL for Edge, after installation, I can login as user admin.

5. Create a blueprint for upgrade like this, additional pkg added, but no user defined.
name = "upgrade-container"
description = "An upgrade rhel-edge container image"
version = "0.0.2"
modules = []
groups = []

[[packages]]
name = "python36"
version = "*"

[[packages]]
name = "expect"
version = "*"

[customizations]
[customizations.kernel]
name = "kernel-rt"
append = ""

6. Use this blueprint to build a rhel-edge-container image, "composer-cli compose start-ostree upgrade-container rhel-edge-container --url http://192.168.100.1/repo/ --ref rhel/8/x86_64/edge", after build finished, download image and run container.

7. Upgrade rhel for edge image, upgrade finished successfully. After reboot, I cannot login with user admin, error message is 'Login incorrect.'

vm login: admin
Password: 
Login incorrect



Actual results:
Cannot login as user admin after upgrade


Expected results:
Can login as user admin after upgrade


Additional info:
Comment 1 Christian Kellner 2022-03-01 11:14:01 UTC 
That is sadly expected behaviour and why I think we should discourage people from putting users into blueprints.
Comment 12 Xiaofeng Wang 2022-04-05 16:08:19 UTC 
Verified on:
osbuild-53-2.el8.noarch                                                       
osbuild-composer-46.1-1.el8.x86_64                                            
osbuild-composer-core-46.1-1.el8.x86_64                                       
osbuild-composer-dnf-json-46.1-1.el8.x86_64                                   
osbuild-composer-worker-46.1-1.el8.x86_64                                     
osbuild-luks2-53-2.el8.noarch                                                 
osbuild-lvm2-53-2.el8.noarch                                                  
osbuild-ostree-53-2.el8.noarch                                                
osbuild-selinux-53-2.el8.noarch
Comment 14 errata-xmlrpc 2022-05-10 13:49:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (osbuild-composer bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1841
Note You need to log in before you can comment on or make changes to this bug.