On Wed, Apr 03, 2019 at 08:54:58AM +, Kenn Leth Hansen wrote:
> I've discovered the CloudStack datasource causes cloud-init to wait for 120
> seconds before continuing to the next datasource if no service is responding
> on port 80 on the DHCP server address. As I am using an Ec2-style
On 4/3/19 6:42 PM, Paul Graydon wrote:
> On 4/3/19 08:29, Thomas Goirand wrote:
>> On 4/3/19 10:54 AM, Kenn Leth Hansen wrote:
>>> Hi list,
>>>
>>> I've discovered the CloudStack datasource causes cloud-init to wait
>>> for 120 seconds before continuing to the next datasource if no
>>> service is
> On 4/3/19 08:29, Thomas Goirand wrote:
>> On 4/3/19 10:54 AM, Kenn Leth Hansen wrote:
>>> Hi list,
>>>
>>> I've discovered the CloudStack datasource causes cloud-init to wait for 120
>>> seconds before continuing to the next datasource if no service is
>>> responding on port 80 on the DHCP
> > > > Would it be possible to move the Ec2 datasource up the list like "[
> > > > NoCloud, AltCloud, ConfigDrive, OpenStack, Ec2, CloudStack,
> > > > ${DIGITAL_OCEAN_SOURCE} MAAS, OVF, GCE, None ]"? This also seems to
> > > > be in line with expectations on how the datasources have been
> > > >
On 4/3/19 08:29, Thomas Goirand wrote:
On 4/3/19 10:54 AM, Kenn Leth Hansen wrote:
Hi list,
I've discovered the CloudStack datasource causes cloud-init to wait for 120 seconds
before continuing to the next datasource if no service is responding on port 80 on the
DHCP server address. As I am
On Thu, Apr 04, 2019 at 09:27:11AM +1300, Andrew Ruthven wrote:
> > > Would it be possible to move the Ec2 datasource up the list like "[
> > > NoCloud, AltCloud, ConfigDrive, OpenStack, Ec2, CloudStack,
> > > ${DIGITAL_OCEAN_SOURCE} MAAS, OVF, GCE, None ]"? This also seems to
> > > be in line
On 4/3/19 10:54 AM, Kenn Leth Hansen wrote:
> Hi list,
>
> I've discovered the CloudStack datasource causes cloud-init to wait for 120
> seconds before continuing to the next datasource if no service is responding
> on port 80 on the DHCP server address. As I am using an Ec2-style metadata
>
Hi list,
I've discovered the CloudStack datasource causes cloud-init to wait for 120
seconds before continuing to the next datasource if no service is responding on
port 80 on the DHCP server address. As I am using an Ec2-style metadata server,
I need to wait 120 seconds every time i boot an
