Unable to add host to cluster after network
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wpZp1lXIp0HebVbu4y6zgdCRNbux5JF9k Content-Type: multipart/mixed; boundary="fS6uz3Cdx3VgmMNdCTCfBDBxhOFDTGmDZ"; protected-headers="v1" From: ~Stack~ <i.am.stack@gmail.com> To: users <users@ovirt.org> Message-ID: <1d9816aa-6d14-d62b-279b-95c13adec21d@gmail.com> Subject: Unable to add host to cluster after network --fS6uz3Cdx3VgmMNdCTCfBDBxhOFDTGmDZ Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Greetings, After a few days of trial, error, and madness - I *think* I found the source of my problem. Or at least I can now replicate it reliably. These are the basics of my speed-run-to-test-failures setup. Fresh minimal install of Scientific Linux 7.4 on a physical host for my engine. Add the 4.2 repo and run engine-setup - just blast through the defaults. Configure it with default DC and cluster. Fresh minimal install of Scientific Linux 7.4 on node1 - configure only the primary network card. Add the ovirt repo. Add the host into cluster. Provisions just fine. Life is good. Now here is where things split. Scenario 1: build node2 same as node 1 configuring only the primary network card and add it as a host. Provisions just fine. Life is good. Scenario 2: Configure a second network. In my case a BMC/IPMI network. Doesn't matter if it is required or not - both will cause failures however the errors are slightly more evident with required. Make sure the network is assigned to your node1 and is properly assigned an IP and configured in the up state. Now build node2 same as before with only the primary network configured and add it as a host. Failure followed by infinite loop of setting it into Non-Operational! The pop-up gives you some crap about "Host has no default route." but that is 100% a red-herring. Dig a little deeper and you get a message like this: "node2 does not comply with the cluster Default networks, the following networks are missing on host: 'ovirtmgmt'" Ah. That's a bit more relevant, but why can't it configure it? Or at least get to the point where it asks me "Hey, networking is a bit off - do you want to configure that now?" That would be nice... Fortunately the troubleshooting guide has something about that! https://www.ovirt.org/documentation/how-to/troubleshooting/troubleshootin= g/ Unfortunately, it doesn't do anything to help. Even after doing these steps, the loop just keeps going...nothing changes. https://www.ovirt.org/develop/developer-guide/vdsm/installing-vdsm-from-r= pm/ Scratch it all and completely rebuild AGAIN for... Scenario 3: Configure a second network (BMC) and assign it to node1 just like before. Build out node2 same as node1 but this time add in the EXACT SAME NETWORK CONFIGURATION THAT IS WORKING ON NODE1 - ALL of the ifcfg-* files (but update the IP address to correct host, obviously). Now add it as a host. Doh! Same error. :-/ OK fine. Let's really get into it. First off, the networking page for the host is blank. It never pulls back the network cards so you can't actually make changes via the web page. Nor can you assign networks. So the web interface doesn't help at all. Let's look at the engine log instead. 2018-04-17 14:33:00,336-05 INFO [org.ovirt.engine.core.bll.VdsEventListener] (EE-ManagedThreadFactory-engine-Thread-1091) [] ResourceManager::vdsNotResponding entered for Host 'f0a3d515-8ba2-490e-8d65-54edbb52cefc', '192.168.1.4' 2018-04-17 14:33:00,360-05 INFO [org.ovirt.engine.core.bll.pm.VdsNotRespondingTreatmentCommand] (EE-ManagedThreadFactory-engine-Thread-1091) [5291eee5] Lock Acquired to object 'EngineLock:{exclusiveLocks=3D'[f0a3d515-8ba2-490e-8d65-54edbb52cefc=3DVD= S_FENCE]', sharedLocks=3D''}' 2018-04-17 14:33:00,388-05 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [2b853e43] Host 'node2' is set to Non-Operational, it is missing the following networks: 'ovirtmgmt' 2018-04-17 14:33:00,403-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [2b853e43] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node2 does not comply with the cluster Default networks, the following networks are missing on host: 'ovirtmgmt' 2018-04-17 14:33:00,407-05 INFO [org.ovirt.engine.core.bll.pm.VdsNotRespondingTreatmentCommand] (EE-ManagedThreadFactory-engine-Thread-1091) [5291eee5] Running command: VdsNotRespondingTreatmentCommand internal: true. Entities affected : ID: f0a3d515-8ba2-490e-8d65-54edbb52cefc Type: VDS There's the message from before. Good. On the right track. Not sure why it thinks the host is unreachable because the host is just fine. 2018-04-17 14:33:01,978-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [] Command 'GetAllVmStatsVDSCommand(HostName =3D node2, VdsIdVDSCommandParametersBase:{hostId=3D'f0a3d515-8ba2-490e-8d65-54edbb52= cefc'})' execution failed: java.net.NoRouteToHostException: No route to host Huh. Again with the no route to host. But THERE IS! The network is functioning perfectly. IP's all work. DNS all works. Routing is fine. I have no idea what it is complaining about. 2018-04-17 14:33:03,873-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [4f72afaa] START, SetVdsStatusVDSCommand(HostName =3D node2, SetVdsStatusVDSCommandParameters:{hostId=3D'f0a3d515-8ba2-490e-8d65-54edb= b52cefc', status=3D'NonOperational', nonOperationalReason=3D'NETWORK_UNREACHABLE', stopSpmFailureLogged=3D'false', maintenanceReason=3D'null'}), log id: 745= 9a748 Which network is unreachable? Because every single one of them is fine! U= gh! I am completely stumped as to why it works perfectly pre-additional-networks but fails every time after a network is configure= d. A couple of questions. 1. I assume people have added hosts _after_ they've configured multiple networks. So what am I doing wrong? Why am I unable to add a host? Again, if I don't configure that second network, it will happily add all my hosts. But what happens when I want to add a host in the future? 2. How do I break that infuriating infinite non-operational loop? I can't put it into maintenance mode, I can't delete the host, or anything else. The options are greyed out. The only solution I've found is yank the power and after it freaks out for about 30 minutes because it can't find the host, it will stop trying. But I still can't seem to remove the bad host. There has to be a way via command-line to say "stop timing out, knock that off, and delete this host!" but I'm not finding it in my searching. 3. I feel like I go through periods with oVirt where everything is running exactly the way I want then something happens (like me trying to add a host! Or thinking I can just change a host IP without the whole thing dying on me!) and it all just falls apart. I feel like I am just stumbling through most of it. I've previously gotten a lot out of the Red Hat classes and work has offered to send me to a training of my choice this year. I am really considering taking the 318 Virtualization class. I'm curious though, how close is that to what I would be working with oVirt? I'm guessing that since 4.2 recently came out, there is probably minimal chance the class will be over 4.2 but maybe it is close enough? I would love to hear feedback. Thanks! ~Stack~ --fS6uz3Cdx3VgmMNdCTCfBDBxhOFDTGmDZ-- --wpZp1lXIp0HebVbu4y6zgdCRNbux5JF9k Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa1lqlAAoJELkej+ysXJPmxgEP/2wLapco/OJfpCYB/5cVvlRc TvU7/a8DiYh/CLBW7mjdM4+tDifa8BbI9nt5iFWs7nPUKEybIKMEncGoGmKTcGwZ mo1L462BrPo6XlXvpjy1T7YxocmHULWDx8CO3d5xY20VrKmzH05W60LTXEcNIHyA 8zJYYyGbleUUTbOTFYpzm5TIjEPqriCsw70HsnDJqX4lDYVIMf6RJ+xTuBjYwY2z /nu5K+XhU3wTOMWcrQo1Bg76p3/EqYUQnzdh6RJ6QjH8VsECGUpeaaZzLAOt5UID ElMG1BubtU9uPwPHO/9S3brYItbfxhn8uda7TexaeUOUni1RG28rAWS/fBUL3LES vBt5OxBPNKjdqVxPhP3whaUEM+5YbMt4m2kWkUVDXaTfj1gNSuZylQwy/9yF0Rv9 I1XodWIU+MFm6WVgzPS73dmyH2wCsHRfATrSnEozixPx2uSB4G0QSh4aVCaJ3sBz Sbyly5ScQxLSbVrbgHJ1gfiLbKKqmjIjfhKQNcfCDKbcAe7sAaeFZnx7SCO4LZBc ldxWALi5h78trPFZnfnHW+dYVjxctnB5d7ucscsVfqlsH9mBfp+6sQS0mQt7GbM/ NO5gcGSuMl31t83LKr6FORuiK8aMnmSwwSWcC99AW6zD8tmE5RdOjIyTMvV4jGZ6 rb8RgxQ2VwN4WGYKsQT6 =03nu -----END PGP SIGNATURE----- --wpZp1lXIp0HebVbu4y6zgdCRNbux5JF9k--
Hi Stack, I read through your ordeal and I would like to post a few comments: - When I try to reproduce your scenario with the second network set to 'not required' before on-boarding the second host, it is processed and set to 'up' by the engine without any hiccups or any errors in the log. - On the other hand, if the network is 'required' the scenario reproduces, but on my setup it can be resolved: initially the second network is proclaimed missing and the host becomes non-operational, with its interfaces disappearing from the engine as you reported. But if the second network is rendered 'not-required' or even deleted for that matter from the engine, engine succeeds in reconnecting to the second host within a couple of minutes, and the host gains 'up' status. HTH On Tue, Apr 17, 2018 at 11:35 PM, ~Stack~ <i.am.stack@gmail.com> wrote:
Greetings,
After a few days of trial, error, and madness - I *think* I found the source of my problem. Or at least I can now replicate it reliably. These are the basics of my speed-run-to-test-failures setup.
Fresh minimal install of Scientific Linux 7.4 on a physical host for my engine. Add the 4.2 repo and run engine-setup - just blast through the defaults. Configure it with default DC and cluster.
Fresh minimal install of Scientific Linux 7.4 on node1 - configure only the primary network card. Add the ovirt repo.
Add the host into cluster. Provisions just fine. Life is good.
Now here is where things split.
Scenario 1: build node2 same as node 1 configuring only the primary network card and add it as a host. Provisions just fine. Life is good.
Scenario 2: Configure a second network. In my case a BMC/IPMI network. Doesn't matter if it is required or not - both will cause failures however the errors are slightly more evident with required. Make sure the network is assigned to your node1 and is properly assigned an IP and configured in the up state. Now build node2 same as before with only the primary network configured and add it as a host.
Failure followed by infinite loop of setting it into Non-Operational!
The pop-up gives you some crap about "Host has no default route." but that is 100% a red-herring.
Dig a little deeper and you get a message like this: "node2 does not comply with the cluster Default networks, the following networks are missing on host: 'ovirtmgmt'"
Ah. That's a bit more relevant, but why can't it configure it? Or at least get to the point where it asks me "Hey, networking is a bit off - do you want to configure that now?" That would be nice...
Fortunately the troubleshooting guide has something about that! https://www.ovirt.org/documentation/how-to/troubleshooting/ troubleshooting/
Unfortunately, it doesn't do anything to help. Even after doing these steps, the loop just keeps going...nothing changes. https://www.ovirt.org/develop/developer-guide/vdsm/ installing-vdsm-from-rpm/
Scratch it all and completely rebuild AGAIN for... Scenario 3: Configure a second network (BMC) and assign it to node1 just like before. Build out node2 same as node1 but this time add in the EXACT SAME NETWORK CONFIGURATION THAT IS WORKING ON NODE1 - ALL of the ifcfg-* files (but update the IP address to correct host, obviously). Now add it as a host.
Doh! Same error. :-/
OK fine. Let's really get into it. First off, the networking page for the host is blank. It never pulls back the network cards so you can't actually make changes via the web page. Nor can you assign networks. So the web interface doesn't help at all.
Let's look at the engine log instead.
2018-04-17 14:33:00,336-05 INFO [org.ovirt.engine.core.bll.VdsEventListener] (EE-ManagedThreadFactory-engine-Thread-1091) [] ResourceManager::vdsNotResponding entered for Host 'f0a3d515-8ba2-490e-8d65-54edbb52cefc', '192.168.1.4' 2018-04-17 14:33:00,360-05 INFO [org.ovirt.engine.core.bll.pm.VdsNotRespondingTreatmentCommand] (EE-ManagedThreadFactory-engine-Thread-1091) [5291eee5] Lock Acquired to object 'EngineLock:{exclusiveLocks='[f0a3d515-8ba2-490e-8d65- 54edbb52cefc=VDS_FENCE]', sharedLocks=''}' 2018-04-17 14:33:00,388-05 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [2b853e43] Host 'node2' is set to Non-Operational, it is missing the following networks: 'ovirtmgmt' 2018-04-17 14:33:00,403-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [2b853e43] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node2 does not comply with the cluster Default networks, the following networks are missing on host: 'ovirtmgmt' 2018-04-17 14:33:00,407-05 INFO [org.ovirt.engine.core.bll.pm.VdsNotRespondingTreatmentCommand] (EE-ManagedThreadFactory-engine-Thread-1091) [5291eee5] Running command: VdsNotRespondingTreatmentCommand internal: true. Entities affected : ID: f0a3d515-8ba2-490e-8d65-54edbb52cefc Type: VDS
There's the message from before. Good. On the right track. Not sure why it thinks the host is unreachable because the host is just fine.
2018-04-17 14:33:01,978-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [] Command 'GetAllVmStatsVDSCommand(HostName = node2, VdsIdVDSCommandParametersBase:{hostId='f0a3d515-8ba2-490e- 8d65-54edbb52cefc'})' execution failed: java.net.NoRouteToHostException: No route to host
Huh. Again with the no route to host. But THERE IS! The network is functioning perfectly. IP's all work. DNS all works. Routing is fine. I have no idea what it is complaining about.
2018-04-17 14:33:03,873-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [4f72afaa] START, SetVdsStatusVDSCommand(HostName = node2, SetVdsStatusVDSCommandParameters:{hostId='f0a3d515-8ba2- 490e-8d65-54edbb52cefc', status='NonOperational', nonOperationalReason='NETWORK_UNREACHABLE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 7459a748
Which network is unreachable? Because every single one of them is fine! Ugh!
I am completely stumped as to why it works perfectly pre-additional-networks but fails every time after a network is configured.
A couple of questions.
1. I assume people have added hosts _after_ they've configured multiple networks. So what am I doing wrong? Why am I unable to add a host? Again, if I don't configure that second network, it will happily add all my hosts. But what happens when I want to add a host in the future?
2. How do I break that infuriating infinite non-operational loop? I can't put it into maintenance mode, I can't delete the host, or anything else. The options are greyed out. The only solution I've found is yank the power and after it freaks out for about 30 minutes because it can't find the host, it will stop trying. But I still can't seem to remove the bad host. There has to be a way via command-line to say "stop timing out, knock that off, and delete this host!" but I'm not finding it in my searching.
3. I feel like I go through periods with oVirt where everything is running exactly the way I want then something happens (like me trying to add a host! Or thinking I can just change a host IP without the whole thing dying on me!) and it all just falls apart. I feel like I am just stumbling through most of it. I've previously gotten a lot out of the Red Hat classes and work has offered to send me to a training of my choice this year. I am really considering taking the 318 Virtualization class. I'm curious though, how close is that to what I would be working with oVirt? I'm guessing that since 4.2 recently came out, there is probably minimal chance the class will be over 4.2 but maybe it is close enough? I would love to hear feedback.
Thanks! ~Stack~
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Eitan Raviv IRC: erav (#ovirt #vdsm #devel #rhev-dev)
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GgKOKS9dKuvaGXhsv0OySgdzWeGX9F53M Content-Type: multipart/mixed; boundary="Uxz42q1pZK2pn27GiOl1euQurREujPVHS"; protected-headers="v1" From: ~Stack~ <i.am.stack@gmail.com> To: users <users@ovirt.org> Message-ID: <a03943a4-0db1-9e5f-50fc-0736606eea20@gmail.com> Subject: Re: [ovirt-users] Unable to add host to cluster after network References: <1d9816aa-6d14-d62b-279b-95c13adec21d@gmail.com> <CAFS8XSUKAmyXZ6wKW1O7un74pHp9V0rTfu6TfiZRcZRO8FO+yA@mail.gmail.com> In-Reply-To: <CAFS8XSUKAmyXZ6wKW1O7un74pHp9V0rTfu6TfiZRcZRO8FO+yA@mail.gmail.com> --Uxz42q1pZK2pn27GiOl1euQurREujPVHS Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 04/18/2018 08:41 AM, Eitan Raviv wrote:
Hi Stack, =20 I read through your ordeal and I would like to post a few comments:
Thanks I appreciate it!
* When I try to reproduce your scenario with the second network set t= o 'not required' before on-boarding the second host, it=C2=A0 is proc= essed and set to 'up' by the engine without any hiccups or any errors in the log.
Hrm. Yeah, I think I can reproduce the failure. I've only done it once, but I have the chance to test so just to make sue I've got the right information I'm going to run a another test specifically for it.
* On the other hand, if the network is 'required' the scenario reproduces,
Whoo! I'm not completely crazy! I'm just lucky to discover a new bug I suppose. :-)
but on my setup it can be resolved: initially the second network is proclaimed missing and the host becomes non-operational,=
with its interfaces disappearing from the engine as you reported. But if the second network is rendered 'not-required' or even delete=
d
for that matter from the engine, engine succeeds in reconnecting to=
the second host within a couple of minutes, and the host gains 'up'=
status.
Setting the second network to 'not-required' does not seem to break my hosts out of their infinite loop. I haven't tried deleting the second network yet. Let me try that before I rebuild to test the first point. Thank you for your feedback. It is much appreciated. ~Stack~ --Uxz42q1pZK2pn27GiOl1euQurREujPVHS-- --GgKOKS9dKuvaGXhsv0OySgdzWeGX9F53M Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa11x/AAoJELkej+ysXJPmuFEQAIsZw+TCjvQbmg8zwaGgeUR4 Ge033BttEqz0jwaNFoVLBnsyzjJ1xY+TILNXOxiMiXMguKdRnEVNRy16DBv0060x HFBTtlk1ZDLmbWLXox7sfWcXq2ec/OJJL2VKqhKqkXVYhq1GQjLZvETHz5Op+EUv DPAWDXvckWvRoWHgaZ4y1TnYvPvPNAHrULjY2rZ6fymTCHfK4cZT9oxCBcIg+87k noSB+qjlmJxAafKnMP4Tl55tY8rB8Mj49qK7pI2D95Lxu8aQCbTrwThWWzj0RDe4 q9lZMqYnvki87bjblQn1VCPX8s0jfoq83+s9XpnGaor6TVIh5PSlHgbBT+l+CatQ /numEuPwE5B11Gg+1rm93JZNv/JQ9QFVxlm5nk452uf+Gs16c3UnKhbFIlQnFE7P FTNYuNJDwI4WKw7tk7Z+i8ROkcZQT7x/0E0TP+VXZvxfdF6V8+WsVjn8uSMV7aPt 1ZzDOT2rUsqcaX6Upfa9XqD/q3gZBMQbQx3m2K4PCcAZU61WArHqFySMQ9izoY87 E+q1Jp/J2/NoQHF0gxTtl7xOlHayECnHnbruXYrPOI7td5LhmWwqBemD8b447w9f R1M899dp0FBGEmtNmYqOtID0Lasch+D+9GXkt4QnqKBdp24cSUjY6QQZUNMtdJ5Y Wnv6vBYwSS5EotR1agWf =9Nj+ -----END PGP SIGNATURE----- --GgKOKS9dKuvaGXhsv0OySgdzWeGX9F53M--
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WatmNZr3C2B2qK5i4Sa474rnxTI8aKREL Content-Type: multipart/mixed; boundary="tlG7m91eIk58UwN2PmDAunvpoovg9tXC6"; protected-headers="v1" From: ~Stack~ <i.am.stack@gmail.com> To: users <users@ovirt.org> Message-ID: <ae77cd1f-6d1b-9ae9-3075-396bf3ecde8e@gmail.com> Subject: Re: [ovirt-users] Unable to add host to cluster after network References: <1d9816aa-6d14-d62b-279b-95c13adec21d@gmail.com> <CAFS8XSUKAmyXZ6wKW1O7un74pHp9V0rTfu6TfiZRcZRO8FO+yA@mail.gmail.com> <a03943a4-0db1-9e5f-50fc-0736606eea20@gmail.com> In-Reply-To: <a03943a4-0db1-9e5f-50fc-0736606eea20@gmail.com> --tlG7m91eIk58UwN2PmDAunvpoovg9tXC6 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 04/18/2018 09:55 AM, ~Stack~ wrote:
On 04/18/2018 08:41 AM, Eitan Raviv wrote: [snip]
but on my setup it can be resolved: initially the second network is proclaimed missing and the host becomes non-operational=
,
with its interfaces disappearing from the engine as you reported. But if the second network is rendered 'not-required' or even delet=
ed
for that matter from the engine, engine succeeds in reconnecting t=
o
the second host within a couple of minutes, and the host gains 'up=
'
status.
=20 Setting the second network to 'not-required' does not seem to break my hosts out of their infinite loop.
Confirmed. Setting the second network to 'not required' did not break the loop. I hard powered off the box, let ovirt set it as down (thus breaking the loop), then powered it back on. The loop continued (at least twice anyway - takes roughly 5 minutes for a loop).
=20 I haven't tried deleting the second network yet. Let me try that before=
I rebuild to test the first point.
Confirmed. Same thing as above only this time I deleted every network but ovirtmgmt. Again, went through 2 full loops without resolving. I am going to do a fresh rebuild and test by having the second network set to 'not required' before adding a second host. ~Stack~ --tlG7m91eIk58UwN2PmDAunvpoovg9tXC6-- --WatmNZr3C2B2qK5i4Sa474rnxTI8aKREL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa12JVAAoJELkej+ysXJPmyQIP/jLBHZADJpQIfveKJCoL12b7 1GkcsxYJ926W/P3r1ZPC2IuYssG9/mv7H5VTNK3F0mvkjoqmJ+0UcO2t4x6sETNC yJnwBrvgP3JPvcsfznULqPvf6Iy0fRB43cNss8SPxpEy3KQdATeJ8zulOxXM8rMk BbFhGmzN9Ati8DAoBK/x4eDHj9kDpnHWyrBCsrfS4aLTvHC8hYryHYPBjyFWZ3Xf ycDuvg7Y5xtWmY1XeFoLIyBzrNpcV2cW/zUeRLFEKM//p0oomxtHHTYd1ck3FKmg GXSZ4eftzULkVyfJfTzeYOeozU9wSXcoo++dFtyNmcA1nyI/mnbR8NswmLrIca7m 0K9tWQi6wr3Q6mkxPwZy7uqwTD+xGboj6hgIe7QLtjUMh0yf14DVGMSyN2q5DPtk uO/m0xf61YrWgf53yOY96bcOOUX3mmsFmZr9HlsjIfUaqpi0H53yM5CK3ObL0LDd SkGY5YvhxHNukC1Bey7PvHZeBLlNdfKyChuL/lYpLBuSAVScfiMhsoucVAd/l7bd Go5o1CRe0w9DKgdfy5xh291W/1RayHe9ONOnwoNXjAg+4cJxudkXKmktNFvWBDkt cxRPshAq3+6L4vRvVzDsj2k7i7+awd5QOE96XbTJFca45y/RAvwsMx8jJY235c79 LUx0qDE4Pizv11yJ0I6f =x+4F -----END PGP SIGNATURE----- --WatmNZr3C2B2qK5i4Sa474rnxTI8aKREL--
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CTqEogRVvdvs5Rcjw8BUMQ7hDIb46Q92h Content-Type: multipart/mixed; boundary="eQ8wfCuuLIlxKPBPoCu34LrY89VCxXbpP"; protected-headers="v1" From: ~Stack~ <i.am.stack@gmail.com> To: users <users@ovirt.org> Message-ID: <45dde7d2-1c20-c867-0e8f-60b5e8320dcc@gmail.com> Subject: Re: [ovirt-users] Unable to add host to cluster after network References: <1d9816aa-6d14-d62b-279b-95c13adec21d@gmail.com> <CAFS8XSUKAmyXZ6wKW1O7un74pHp9V0rTfu6TfiZRcZRO8FO+yA@mail.gmail.com> <a03943a4-0db1-9e5f-50fc-0736606eea20@gmail.com> In-Reply-To: <a03943a4-0db1-9e5f-50fc-0736606eea20@gmail.com> --eQ8wfCuuLIlxKPBPoCu34LrY89VCxXbpP Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 04/18/2018 09:55 AM, ~Stack~ wrote:
On 04/18/2018 08:41 AM, Eitan Raviv wrote:
Hi Stack,
I read through your ordeal and I would like to post a few comments: =20 Thanks I appreciate it! =20 * When I try to reproduce your scenario with the second network set = to 'not required' before on-boarding the second host, it=C2=A0 is pro= cessed and set to 'up' by the engine without any hiccups or any errors in=
the log.
=20 Hrm. Yeah, I think I can reproduce the failure. I've only done it once,=
but I have the chance to test so just to make sue I've got the right information I'm going to run a another test specifically for it. =20
I agree with you, Eitan. I did a complete rebuild and made sure my alternate network was set to 'not required' before adding the second host. I successfully added a second host. It is possible I did something else wrong in that first test. Since this is an acceptable work-around for now, I am going to finish building my hosts out so I can move forward with this project. I would still like feedback on my other questions in the original post if anyone is willing. Thanks! ~Stack~ --eQ8wfCuuLIlxKPBPoCu34LrY89VCxXbpP-- --CTqEogRVvdvs5Rcjw8BUMQ7hDIb46Q92h Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa14HOAAoJELkej+ysXJPmuLkQAI7+NNgh1VJdYbsnW8BqmvD9 sYj75oxuWjUmw58sjkd7STlRxfcG0XTCaAhrICjjHCL949AZ7My83vpY2wuXNnSY y/+IZhAxCSZztlWgKjYgXSNgcrVfIZoIIr66s2WbmPspGLsb16lu9flkS/U1sd4k osG/KtxkKIYvvuD/LK+45+eH+HqzAgufGt1uTy56JKP6eSwg8rr5zMIM7mU0GbTU faU6DB+CA7/6KL1DM2vHjcuksujMw/qZhDoK+Cjwm7FhTaxMopitxwMuMeEI4aSd Kh3kKiaCxR3Ry3ETaV2NyW9CoflwznUJOmb7lqYqIU/FvY/Bt2/UEd18Hxt7OKFl s4rRGkTVTYgb/Plex1Em3m67fT2vvTTLtAHbyGoP6wJTHHmg+bSi9I6L6Fw/lY3x wTzsdNl94Y2WJYKm/pc+YjqxT0xXn6kOPEyEaZsXWbZ2YwTqaQEbRXYY+h7gXpRC JT6tyHRotWWNRX1gVAD1wjljCgt9Aqfpy+Zo8IQQhjyCL3RLRhIwXtNABJOzwabv ABYpf9KidjBSwaDbo8ZwEbsYQ6Wj5wc2tyLfHCciMJQ7Pqr9Pt1DraNd+zAK1aEv uad4m+F9c8mgH/G3Wq7ITVIuPcg7Yp7JYdq7V858QC/B2iwJuBxP6nXeoO8FVZM9 G9PQil3Jfp0AI822Rroe =5v4K -----END PGP SIGNATURE----- --CTqEogRVvdvs5Rcjw8BUMQ7hDIb46Q92h--
Hi Stack, Indeed this is a bug in the engine. We have opened a case [1] and are working to fix it on 4.2 ASAP Thanks for posting... [1] https://bugzilla.redhat.com/show_bug.cgi?id=1570388 Eitan oVirt | Redhat On Wed, Apr 18, 2018 at 8:35 PM, ~Stack~ <i.am.stack@gmail.com> wrote:
On 04/18/2018 09:55 AM, ~Stack~ wrote:
On 04/18/2018 08:41 AM, Eitan Raviv wrote:
Hi Stack,
I read through your ordeal and I would like to post a few comments:
Thanks I appreciate it!
* When I try to reproduce your scenario with the second network set to 'not required' before on-boarding the second host, it is processed and set to 'up' by the engine without any hiccups or any errors in the log.
Hrm. Yeah, I think I can reproduce the failure. I've only done it once, but I have the chance to test so just to make sue I've got the right information I'm going to run a another test specifically for it.
I agree with you, Eitan. I did a complete rebuild and made sure my alternate network was set to 'not required' before adding the second host. I successfully added a second host. It is possible I did something else wrong in that first test.
Since this is an acceptable work-around for now, I am going to finish building my hosts out so I can move forward with this project.
I would still like feedback on my other questions in the original post if anyone is willing.
Thanks! ~Stack~
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Eitan Raviv IRC: erav (#ovirt #vdsm #devel #rhev-dev)
participants (2)
-
Eitan Raviv -
~Stack~