Possibly not then, the device that was in use has a net-<dev>.conf file;
If we don't have iscsi then what other script is going to create the
.interface file?
On Tue, Aug 29, 2017 at 10:19 AM, Blake Rouse <email address hidden>
wrote:
> Scott,
>
> Since we are no longer using iscsi and using the squashfs over HTTP,
> would open-iscsi even be used?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1711760
>
> Title:
> [2.3] resolv.conf is not set (during commissioning or testing)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions
>
Possibly not then, the device that was in use has a net-<dev>.conf file;
If we don't have iscsi then what other script is going to create the
.interface file?
Here's the conf file for ens3 (the device in use)
% cat run/net-ens3.conf '10.0.0. 54' '10.0.0. 255' '255.255. 255.0' '10.0.0. 1' '10.0.0. 2' 'pxelinux. 0'
DEVICE='ens3'
PROTO='dhcp'
IPV4ADDR=
IPV4BROADCAST=
IPV4NETMASK=
IPV4GATEWAY=
IPV4DNS0='10.0.0.2'
IPV4DNS1='0.0.0.0'
HOSTNAME=''
DNSDOMAIN='maas'
NISDOMAIN=''
ROOTSERVER=
ROOTPATH=''
filename=
UPTIME='10'
DHCPLEASETIME='600'
DOMAINSEARCH=''
On Tue, Aug 29, 2017 at 10:19 AM, Blake Rouse <email address hidden>
wrote:
> Scott, /bugs.launchpad .net/bugs/ 1711760 /bugs.launchpad .net/maas/ +bug/1711760/ +subscriptions
>
> Since we are no longer using iscsi and using the squashfs over HTTP,
> would open-iscsi even be used?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [2.3] resolv.conf is not set (during commissioning or testing)
>
> To manage notifications about this bug go to:
> https:/
>