oVirt node 4.4.1 deploy FQDN not reachable
Hi all I have an issue while trying to deploy hyperconverged solution on three ovirt node boxes. ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso. When from cockpit I choose gluster deployment, I have a form where I can insert both gluster fqdn names and public fqdn names (that is what I need, due to distinct network cards & networks) If I insert right names, that are resolved by nodes, I receive, anyway, FQDN is not reachable below Host1 entries. As already stated, these names are certainly resolved by DNS used. Any hints about ? -- Roberto Nunin
Il giorno ven 7 ago 2020 alle ore 12:59 Roberto Nunin <robnunin@gmail.com> ha scritto:
Hi all
I have an issue while trying to deploy hyperconverged solution on three ovirt node boxes. ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso.
When from cockpit I choose gluster deployment, I have a form where I can insert both gluster fqdn names and public fqdn names (that is what I need, due to distinct network cards & networks)
If I insert right names, that are resolved by nodes, I receive, anyway, FQDN is not reachable below Host1 entries.
As already stated, these names are certainly resolved by DNS used. Any hints about ?
Using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso (4.4.2 RC2) the same issue do not happen. -- Roberto Nunin
I'm running into the same problem. I just wiped my CentOS 8.2 system, and in place of that, installed oVirt Node 4.4.1. I'm downloading 4.4.2-2020081922 now. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, August 7, 2020 11:55 AM, Roberto Nunin <robnunin@gmail.com> wrote:
Il giorno ven 7 ago 2020 alle ore 12:59 Roberto Nunin <robnunin@gmail.com> ha scritto:
Hi all
I have an issue while trying to deploy hyperconverged solution on three ovirt node boxes. ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso.
When from cockpit I choose gluster deployment, I have a form where I can insert both gluster fqdn names and public fqdn names (that is what I need, due to distinct network cards & networks)
If I insert right names, that are resolved by nodes, I receive, anyway, FQDN is not reachable below Host1 entries.
As already stated, these names are certainly resolved by DNS used. Any hints about ?
Using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso (4.4.2 RC2) the same issue do not happen.
-- Roberto Nunin
Getting the same problem on 4.4.2-2020081922. I'll try the image that Roberto found to work, and will report back. Perhaps I'm still too new to this. :) Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, August 22, 2020 7:12 PM, David White via Users <users@ovirt.org> wrote:
I'm running into the same problem. I just wiped my CentOS 8.2 system, and in place of that, installed oVirt Node 4.4.1.
I'm downloading 4.4.2-2020081922 now.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, August 7, 2020 11:55 AM, Roberto Nunin <robnunin@gmail.com> wrote:
Il giorno ven 7 ago 2020 alle ore 12:59 Roberto Nunin <robnunin@gmail.com> ha scritto:
Hi all
I have an issue while trying to deploy hyperconverged solution on three ovirt node boxes. ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso.
When from cockpit I choose gluster deployment, I have a form where I can insert both gluster fqdn names and public fqdn names (that is what I need, due to distinct network cards & networks)
If I insert right names, that are resolved by nodes, I receive, anyway, FQDN is not reachable below Host1 entries.
As already stated, these names are certainly resolved by DNS used. Any hints about ?
Using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso (4.4.2 RC2) the same issue do not happen.
-- Roberto Nunin
On Sun, Aug 23, 2020 at 3:25 AM David White via Users <users@ovirt.org> wrote:
Getting the same problem on 4.4.2-2020081922.
I'll try the image that Roberto found to work, and will report back.
Thanks. Perhaps one of you would like to open a bug, and/or check/share relevant logs when this happens? Best regards,
Perhaps I'm still too new to this. :)
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, August 22, 2020 7:12 PM, David White via Users <users@ovirt.org> wrote:
I'm running into the same problem. I just wiped my CentOS 8.2 system, and in place of that, installed oVirt Node 4.4.1.
I'm downloading 4.4.2-2020081922 now.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, August 7, 2020 11:55 AM, Roberto Nunin <robnunin@gmail.com> wrote:
Il giorno ven 7 ago 2020 alle ore 12:59 Roberto Nunin <robnunin@gmail.com> ha scritto:
Hi all
I have an issue while trying to deploy hyperconverged solution on three ovirt node boxes. ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso.
When from cockpit I choose gluster deployment, I have a form where I can insert both gluster fqdn names and public fqdn names (that is what I need, due to distinct network cards & networks)
If I insert right names, that are resolved by nodes, I receive, anyway, FQDN is not reachable below Host1 entries.
As already stated, these names are certainly resolved by DNS used. Any hints about ?
Using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso (4.4.2 RC2) the same issue do not happen.
-- Roberto Nunin
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FUJOBNZDE2B6H6...
-- Didi
I ran out of time to finish properly testing things Saturday evening (I'm in Eastern Time in the States), and wasn't able to spend any time on it Sunday or Monday. I intend to finish testing this evening (for the RC2 image that Roberto found worked), and will update the list at that point. I want to make sure the problem isn't me. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, August 25, 2020 3:47 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Sun, Aug 23, 2020 at 3:25 AM David White via Users users@ovirt.org wrote:
Getting the same problem on 4.4.2-2020081922. I'll try the image that Roberto found to work, and will report back.
Thanks.
Perhaps one of you would like to open a bug, and/or check/share relevant logs when this happens?
Best regards,
Perhaps I'm still too new to this. :) Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, August 22, 2020 7:12 PM, David White via Users users@ovirt.org wrote: I'm running into the same problem. I just wiped my CentOS 8.2 system, and in place of that, installed oVirt Node 4.4.1. I'm downloading 4.4.2-2020081922 now. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, August 7, 2020 11:55 AM, Roberto Nunin robnunin@gmail.com wrote: Il giorno ven 7 ago 2020 alle ore 12:59 Roberto Nunin robnunin@gmail.com ha scritto:
Hi all I have an issue while trying to deploy hyperconverged solution on three ovirt node boxes. ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso. When from cockpit I choose gluster deployment, I have a form where I can insert both gluster fqdn names and public fqdn names (that is what I need, due to distinct network cards & networks) If I insert right names, that are resolved by nodes, I receive, anyway, FQDN is not reachable below Host1 entries. As already stated, these names are certainly resolved by DNS used. Any hints about ?
Using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso (4.4.2 RC2) the same issue do not happen. -- Roberto Nunin
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FUJOBNZDE2B6H6...
--
Didi
participants (3)
-
David White -
Roberto Nunin -
Yedidyah Bar David