fab: Live migration may fail if the uid and gid of nova are different in the compute nodes
Bug #1335344 reported by
Vinod Nair
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Fix Committed
|
Medium
|
Jeya ganesh babu J | ||
R1.1 |
Won't Fix
|
Medium
|
Jeya ganesh babu J | ||
R2.0 |
Won't Fix
|
Medium
|
Jeya ganesh babu J | ||
R2.1 |
Won't Fix
|
Medium
|
Jeya ganesh babu J | ||
R2.20 |
Fix Committed
|
High
|
Jeya ganesh babu J |
Bug Description
Live migration will fail if the UID and GID of nova is different in the compute nodes.
All though most of the times it will be same , but users can easily run in this if the user adds any other packages on the computes manually which in turn add a users as in post fix etc on the computes.. Usually the case with yum install or apt-get
Although the provisioning will go through fine with a mismatched UID on the computes, the actual live migration will fail.
Workaround: Ensure that no other packages other than the ones done by fab is added to the system till the live migration provisioning is complete
summary: |
- Live migration may fail if the uid and gid of nova is diffeent in the + Live migration may fail if the uid and gid of nova is different in the compute nodes |
summary: |
- Live migration may fail if the uid and gid of nova is different in the - compute nodes + fab: Live migration may fail if the uid and gid of nova is different in + the compute nodes |
Changed in juniperopenstack: | |
milestone: | r1.10-beta → none |
To post a comment you must log in.
Need to understand how to 'doc' this PR for 1.1.