onitake commented on issue #3557:
URL: https://github.com/apache/cloudstack/issues/3557#issuecomment-738760809
It's not a CloudStack issue any more, but there is still a PR open to make
the documentation clearer:
https://github.com/apache/cloudstack-documentation/pull/132
I think
onitake commented on issue #3557: cloud-init fails to fetch metadata when
shared networks are present
URL: https://github.com/apache/cloudstack/issues/3557#issuecomment-524920883
@joschi36 has pushed a proposed fix:
onitake commented on issue #3557: cloud-init fails to fetch metadata when
shared networks are present
URL: https://github.com/apache/cloudstack/issues/3557#issuecomment-524793882
I think we found the "right" way to do this: If the metadata server is
enabled on an interface, it will offer
onitake commented on issue #3557: cloud-init fails to fetch metadata when
shared networks are present
URL: https://github.com/apache/cloudstack/issues/3557#issuecomment-522110868
There are many different ways in which networks can be configured, and I
agree that my point of view might not
onitake commented on issue #3557: cloud-init fails to fetch metadata when
shared networks are present
URL: https://github.com/apache/cloudstack/issues/3557#issuecomment-521967733
The bug fix is fine, I think. If the user wishes to rely on DHCP leases,
that's all right.
What you
onitake commented on issue #3557: cloud-init fails to fetch metadata when
shared networks are present
URL: https://github.com/apache/cloudstack/issues/3557#issuecomment-521924587
That's a good point. The shared network offering we're using in this case
does not have the UserData flag
onitake commented on issue #3557: cloud-init fails to fetch metadata when
shared networks are present
URL: https://github.com/apache/cloudstack/issues/3557#issuecomment-521678991
@ustcweizhou I don't think this has any influence on the issue here.
cloud-init lists all lease files and
