| Summary: | devmode fails to start successfully after deploying 7.2.7 from 7.3 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Micah Abbott <miabbott> |
| Component: | atomic-devmode | Assignee: | Jonathan Lebon <jlebon> |
| Status: | CLOSED CANTFIX | QA Contact: | Micah Abbott <miabbott> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | Keywords: | Extras |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-29 21:14:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Micah Abbott
2016-09-29 19:34:25 UTC
Right, this is because 7.3 includes: https://code.engineering.redhat.com/gerrit/gitweb?p=spin-kickstarts.git;a=commitdiff;h=c8e803e3f7c3c464a78fc5c451c6c4c5bdec256d Which means that there is now a .bash_profile in /root. The way atomic-devmode started up before that was to have a .bash_login which automatically executed on login. However, in 7.3, .bash_profile has priority over .bash_login, so atomic-devmode had to be adapted: https://github.com/projectatomic/atomic-devmode/commit/8abf921f5a18eebc812885809ed12a39c58b7d6f But obviously, that fix is not in the old 7.2.7 tree. I don't think there's much we can do about this. A workaround would be `rm /root/.bash_profile && reboot` (with the caveat it carries). But in the big picture, devmode is just supposed to help you try out the cloud image easily without setting anything else up. If you want to keep re-using the same VM, you're better off just going the whole way and writing a cloud-config. Or is there a valid use case I'm not considering here? What do you think? This is a perfectly reasonable explanation. I just wanted to make sure I wasn't missing anything. I agree with your statement about devmode being a way to try things out, so we shouldn't be investing too much effort in handling these scenarios. I'll close this as CANTFIX. |