snapshots of cloud images will share an iSCSI initiator name

Bug #1677726 reported by Nish Aravamudan on 2017-03-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-images
Medium
Unassigned
open-iscsi (Ubuntu)
Medium
Unassigned

Bug Description

After fixing LP: #1444992, smoser pointed out that there is still a gap if a cloud-image is booted and then the once-run instance is used as a template for future instances, as the iSCSI initiator name has been generated.

From IRC:

11:35 < smoser> nacc, there is 'machine-id' which is systemd's attempt at something pretty similar to what an instance-id woudl provide.
11:38 < nacc> smoser: ah so we could, in theory, store /etc/machine-id in the initiatorname.iscsi file (in a comment) and say it only applies to that config. then on startup
              in the script, check if /etc/machine-id matches what's in the iscsi initiator file and leave it if so, re-gen otherwise?
11:41 < smoser> yeah, tahts kind of what i was suggesting.
11:41 < smoser> that doesnt really fix the issue of having to clean though

Scott Moser (smoser) on 2017-06-28
Changed in cloud-images:
status: New → Confirmed
Changed in open-iscsi (Ubuntu):
status: New → Confirmed
Changed in cloud-images:
importance: Undecided → Medium
Changed in open-iscsi (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers