Hi,
I an sorry for the noise - and thanks for obvious question - and the
answer is that resolv.conf had the wrong dns entries on the old host.
Fixed it and now we can migrate. Unknown how it ended there - but we are
now happy and rocking.
/nikas
On 2021-12-13 09:45, Ales Musil wrote:
And
And are you able to reach from one host to another via IP and via FQDN?
Best regards,
Ales
On Mon, Dec 13, 2021 at 9:42 AM Niklas Larsson via Users
wrote:
> Hi,
>
> Can't see any errors for networking - we only have one logical network,
> that has all the features:
>
>
>
> /niklas
>
> On
Hi,
Can't see any errors for networking - we only have one logical network,
that has all the features:
/niklas
On 2021-12-13 09:26, Ales Musil wrote:
Hi,
is your engine reporting out-of-sync on that migration network?
Best regards,
Ales
On Mon, Dec 13, 2021 at 9:23 AM Niklas Larsson
Hi,
is your engine reporting out-of-sync on that migration network?
Best regards,
Ales
On Mon, Dec 13, 2021 at 9:23 AM Niklas Larsson via Users
wrote:
> Hi,
>
> we are using static ip, and the iptable-save is pretty empty - all rules
> are ACCEPT as default.
>
> We are doing this in our lab
Hi,
we are using static ip, and the iptable-save is pretty empty - all rules
are ACCEPT as default.
We are doing this in our lab environment, not yet i production - so it's
not affecting anything yet.
/niklas
On 2021-12-10 17:37, Nathanaël Blanchet wrote:
Hi,
Is your migration network
Hi,
Is your migration network provisionned by DHCP?
If so, there is a known bug that prevents NetworkManager to set ip rule
table for your migration network, and it won't be fixed before 4.5 release.
As a workaround, you can set the protocol to static or manually assign
rule table to 0 as
6 matches
Mail list logo
