-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Generate new initiatorname from scratch (Fixes: #14) #19
Conversation
e2dcdde
to
074d81a
Compare
074d81a
to
d73a410
Compare
weird. let me try another PR... |
#15 worked ok...hm |
d73a410
to
197d2c6
Compare
@lveyde any idea why it fails? |
197d2c6
to
385f0d1
Compare
Missed this one :) |
aaah, thanks!:) |
385f0d1
to
bfd069b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please note that iscsi-iname itself generates a unique iSCSI node name on every invocation.
Thus it's output can be used directly, without the need to split it and then combine with the split uuid.
bfd069b
to
a128728
Compare
a128728
to
b05cbe3
Compare
Since the el9 packages don't build an initiatorname by default, we should not depend/use the file in factory anymore, but just generate the string ourselves.
Fixes: #14