This repository was archived by the owner on Apr 25, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Worker volume name hardcoded and may be wrong in crc_libvirt.sh #19
Comments
Right, this part is variable... but since this is a POC we hadn't come
around to perform a full flow from generation of the images to generation
of scripts using a template. However, this might even change in the near
future.
…On Fri, Jan 18, 2019 at 10:16 PM Ben Browning ***@***.***> wrote:
On line 116 and the 2nd argument on line 118 of
https://github.com/praveenkumar/osp4/blob/6f7d3ea9bf2ac194aceac4b3ae1be81d509c6615/libvirt/crc_libvirt.sh#L116
you see the actual on-disk filename of the worker volume is hardcoded.
However, when building, the last part of that worker volume name can vary.
I hit this when trying to run this script from a tgz release linked to me
via email. Inside that tgz the worker volume file name did not match the
hardcoded value here and I had to manually update those lines to get crc_libvirt.sh
create to succeed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/praveenkumar/osp4/issues/19>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZqx-ln123d0W1iEoDaEUD7KPME9Qks5vEdc2gaJpZM4aH_Ag>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
An other issue is in lines 118 and later down where file operations expect the worker-0-98nsr names, but in reality (in my download) the worker file is `test1-worker-0-vqgct |
This is a known issue and due to thre respin of a new version.
This will be resolved (currently still PoC)
…On Tue, Feb 12, 2019 at 4:13 PM Heiko W. Rupp ***@***.***> wrote:
An other issue is in lines 118 and later down where file operations expect
the worker-0-98nsr names, but in reality (in my download) the worker file
is `test1-worker-0-vqgct
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#19 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZuQFqbQjf1eLGXYB1UacKslpUjE9ks5vMne7gaJpZM4aH_Ag>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
The following fixes it for me (if anyone runs into the same issue)
|
Also grepping for dnsmasq setup in NetworkManager may check that it is not listed as disabled
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On line 116 and the 2nd argument on line 118 of https://github.com/praveenkumar/osp4/blob/6f7d3ea9bf2ac194aceac4b3ae1be81d509c6615/libvirt/crc_libvirt.sh#L116 you see the actual on-disk filename of the worker volume is hardcoded. However, when building, the last part of that worker volume name can vary.
I hit this when trying to run this script from a tgz release linked to me via email. Inside that tgz the worker volume file name did not match the hardcoded value here and I had to manually update those lines to get
crc_libvirt.sh create
to succeed.The text was updated successfully, but these errors were encountered: