Hi Edward,
Could you please test with 4.16.0.0-rc2 ?
I have tested network and vpc with redundant routers in 4.16.0.0, both look
good.
data-server and data-server. can be resolved as VIP.
-Wei
On Thu, 4 Nov 2021 at 10:44, Edward St Pierre
wrote:
> Hi Wei,
>
> cloud-init can resolve 'data-se
Hi Wei,
cloud-init can resolve 'data-server' with and without the '.' but on a
redundant setup using the 4.15.1 template it resolves to the guest IP
address and not the VIP on the VR and therefore cannot access the password
server.
on a non-redundant VR setup it works as expected.
Ed
On Thu,
to be clear, in my 4.16 testing, 'data-server' and 'data-server.' can be
both resolved as VIP, in VR and centos5 VMs. but "data-server." cannot be
resolved in ubuntu 18 VM.
If 'data-server.' cannot be resolved in your vm (ubuntu or other OS
distributions), it is not an issue with cloudstack or clou
Hi Edward,
Sorry I am a bit confused.
Is cloud-init not working in your vm, because 'data-server.' is not
resolved ? But why did you check the issue in the VR not the VM ?
Can 'data-server' (without dot) be resolved in the vm ?
I confirm that the password server listens only on the VIP, it shou
Hi,
The diagnostics I provided shows that it only appears to be listening on
the VIP and not the guest IP..
The DNS does resolve (DNS resolution provided earlier), however I believe
it should resolve to the VIP address as the password server is only
listening on the VIP.
I am using the template '
It is not a problem, in my opinion. The password server and userdata server
listen on both guest ip and vip.
As I commented on the link in previous reply, if cloud-init does not work
in your vm template, it might be caused by systemd-resolved.
-Wei
On Wednesday, 3 November 2021, Edward St Pierr
Hi,
Thanks for your input, it actually looks like a bug with the redundant VR
setup.
See diagnostics directly on master VR:
root@r-418-VM:~# netstat -anpl | grep 8080
tcp0 0 10.1.1.1:8080 0.0.0.0:* LISTEN
1610/python
root@r-418-VM:~# ip addr show
1: lo:
Hi Edward,
You may face an issue which has recently been fixed in cloud-init .
Please refer to https://github.com/canonical/cloud-init/pull/1004
-Wei
On Wed, 3 Nov 2021 at 12:48, Edward St Pierre
wrote:
> Hi Guys,
>
> Just a really quick question.
>
> Should 'data-server.' resolve to the virtu
Hi
It should resolve to the ip of router on the same network as your vm is
connected to it.
If you are using isolated network, it should be the gateway of your vm.
In case of shared network, it is the ip of dhcp server.
On Wed, Nov 3, 2021, 15:29 Edward St Pierre
wrote:
> Just need to add,
>
> I
Just need to add,
I mean it is resolving to the guest IP of the virtual router, and not the
address that it is listening on:
root@r-418-VM:~# netstat -anpl | grep 8080
tcp0 0 10.1.1.1:8080 0.0.0.0:* LISTEN
1610/python
root@r-418-VM:~# ip addr show
1: lo:
Hi Guys,
Just a really quick question.
Should 'data-server.' resolve to the virtual router or the guest?
Basically the cloud-init datasource for Cloudstack that comes with CentOS
Stream seems to use this as the address for the VR.
Just looking to see if this is a VR bug or a bug with this modul
11 matches
Mail list logo
