Bug 1481952
| Summary: | Logging in new layer failed as root get "/bin/bash: Permission denied" when upgrade from rhvh-4.x(el7.3) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-node | Reporter: | Huijuan Zhao <huzhao> | ||||||
| Component: | Installation & Update | Assignee: | Ryan Barry <rbarry> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Huijuan Zhao <huzhao> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.1 | CC: | bugs, cshao, dguo, dougsland, jiawu, leiwang, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yzhao | ||||||
| Target Milestone: | ovirt-4.1.5 | Keywords: | Regression | ||||||
| Target Release: | 4.1 | Flags: | rule-engine:
ovirt-4.1+
rule-engine: blocker+ rbarry: devel_ack+ cshao: testing_ack+ |
||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | imgbased-0.9.44-0.1.el7ev | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-08-23 08:02:03 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1476650 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1313964 [details]
All logs in new layer booting with "selinux=0"
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. Test version:
From: rhvh-4.0-0.20170307.0
To: rhvh-4.1-0.20170816.2
imgbased-0.9.47-0.1.el7ev.noarch
# imgbase layout
rhvh-4.0-0.20170307.0
+- rhvh-4.0-0.20170307.0+1
rhvh-4.1-0.20170817.0
+- rhvh-4.1-0.20170817.0+1
Test steps:
Same as comment 0
Test results:
After step 3, log in rhvh-4.1 successful with root both in direct console and ssh.
So this bug is fixed in imgbased-0.9.47-0.1.el7ev.noarch, change the status to VERIFIED.
|
Created attachment 1313963 [details] All logs in old layer (sosreport, /tmp/imgbased.log, /var/log) Description of problem: Logging in new layer failed as root get "/bin/bash: Permission denied" when upgrade from rhvh-4.x(el7.3) to rhvh-4.1-0.20170815.0. Booting the kernel with selinux=0 solved this problem. Note: No such issue when upgrade from rhvh-4.1-0.20170808.0(el7.4) to rhvh-4.1-0.20170815.0. Version-Release number of selected component (if applicable): From: rhvh-4.0-0.20170307.0 To: rhvh-4.1-0.20170815.0 imgbased-0.9.43-0.1.el7ev.noarch # imgbase layout rhvh-4.0-0.20170307.0 +- rhvh-4.0-0.20170307.0+1 rhvh-4.1-0.20170815.0 +- rhvh-4.1-0.20170815.0+1 How reproducible: 100% Steps to reproduce: 1. Clean install rhvh-4.0-0.20170307.0 2. Set local repo and upgrade to rhvh-4.1-0.20170815.0: #yum update 3. Reboot and log in new layer rhvh-4.1-0.20170815.0 with root in direct console, and ssh rhvh-4.1 with root 4. Reboot and choose new layer rhvh-4.1-0.20170815.0 in boot entry, add "selinux=0" to kernel command, log in rhvh-4.1 with root in direct console, and ssh rhvh-4.1 with root Actual results: 1. After step 3, log in rhvh-4.1 failed with root both in direct console and ssh. $ ssh root.10.16 Warning: Permanently added '10.66.10.16' (ECDSA) to the list of known hosts. root.10.16's password: Last login: Wed Aug 16 05:40:16 2017 /bin/bash: Permission denied Connection to 10.66.10.16 closed. 2. After step 4, log in rhvh-4.1 successful with root both in direct console and ssh. Expected results: 1. After step 3, should log in rhvh-4.1 successful with root both in direct console and ssh. Additional info: 1. Also encountered this issue when upgrade from rhvh-4.1-0.20170616.0(el7.3) to rhvh-4.1-0.20170815.0. But no such issue when upgrade from rhvh-4.1-0.20170808.0(el7.4) to rhvh-4.1-0.20170815.0. 2. No such issue in rhvh-4.1-0.20170808.0, so this is regression issue.