Re: Adding Host in new Zone fails

[Nux <nu...@li.nux.ro>]

Glad you got it working.
Usually you'd have a regular interface such as "eth0" connected in that 
bridge.

On 2023-01-31 20:02, Evan Marchman wrote:
> Thank you for the help Nux!
> 
> Your comment on the bridges put me on the right path. Everything was 
> indeed
> configured correctly. BUT, as VMs were created the MAC address of 
> cloudbr0
> changed. This explains why the host was mostly configured and then 
> dropped
> off at the end.
> 
> My fix was to add a dummy interface to the cloudbr0 bridge with a low 
> MAC.
> This keeps the bridge MAC stable throughout the setup and subsequent
> operation. Maybe this is brute force but it got me over the hump.
> 
> -Evan
> 
> 
> On Tue, Jan 31, 2023 at 10:28 AM Nux <nu...@li.nux.ro> wrote:
> 
>> Making sure that indeed all your bridges are in order, your agent can
>> connect to the management server (eg telnet to mgmt:8250) and starting
>> with a clean /etc/cloudstack/agent as well as libvirtd set to
>> listen_tcp=1 and listen_tls=0, try to add the host again and if it 
>> fails
>> send us again DEBUG logs.
>> Also make sure iptables and selinux are off.
>> 
>> On 2023-01-31 15:45, Evan Marchman wrote:
>> > I've tried a few more things with no luck. Fully re-installed the
>> > agent,
>> > further verified open ports, checked the disks, etc. I keep getting the
>> > same errors. Any pointers are appreciated!
>> >
>> > Thanks!
>> > -Evan
>> >
>> >
>> > On Thu, Jan 26, 2023 at 5:47 PM Evan Marchman
>> > <em...@evermoresystems.com>
>> > wrote:
>> >
>> >> I'm stumped. I am trying to add a new off-site zone, which I've
>> >> already
>> >> done 3 times from the same management server. This fourth system is
>> >> thwarting my efforts. It should be a clone of the process I used on
>> >> the
>> >> last two. The only delta is this one is a bare metal system in a data
>> >> center I can't touch. The base OS was installed by the data center but
>> >> is
>> >> still CentOS 7.9. It is possible the host has something in the network
>> >> config I have missed but I cannot find it.
>> >>
>> >> The GUI is giving me "Error 530 - Unable to add the host: Cannot find
>> >> the
>> >> server resources at http://10.120.10.2" In the management log I see:
>> >>
>> >> Failed to handle host connection:
>> >> com.cloud.exception.ConnectionException:
>> >> Incorrect Network setup on agent, Reinitialize agent after network
>> >> names
>> >> are setup, details : Can not find network: cloudbr0
>> >>
>> >>
>> >> I have checked and rechecked the network config on the host. cloudbr0
>> >> is
>> >> there and properly configured as a bridge. All of my communications
>> >> with
>> >> the host are via this interface so I know it's up. I've compared
>> >> settings
>> >> on the host and in the Physical Network to my working zones and
>> >> everything
>> >> matches. The agent.properties file has the correct "cloudbr0" entries
>> >> as
>> >> expected (and no extras).
>> >>
>> >> The remote system is connected via VPN. I have verified the VPN is
>> >> fully
>> >> functional. The new host has the firewall disabled and iptables
>> >> entries for
>> >> all the host/agent ports. I've used nmap to verify connectivity
>> >> between the
>> >> management server and the host and that the required ports are
>> >> actually
>> >> open. The zone, pod and cluster are all correctly added. I manually
>> >> added
>> >> secondary NFS storage successfully.
>> >>
>> >> I have posted the relevant management and agent logs here.
>> >> management.log
>> >> <
>> https://drive.google.com/file/d/1UuiD85rzgrJ9zA9_snhad76CAm1b8BTU/view?usp=sharing
>> >
>> >> agent.log
>> >> <
>> https://drive.google.com/file/d/1z9FfeCuHw05R1Zk5Hqr6IIPW8_W5Wr-N/view?usp=sharing
>> >
>> >>
>> >> You'll see where I removed the host at the start of the logs then
>> >> re-add
>> >> it. On the host side, I cleared relevant agent.properties, deleted the
>> >> cloud.* key files and restarted the agent prior to this test.
>> >>
>> >> I'm still a cloudstack newbie so I totally expect that I missed
>> >> something
>> >> or slipped in a typo; but I'm not seeing it. Help and pointers are
>> >> very
>> >> appreciated!
>> >>
>> >> Regards,
>> >> Evan
>> >>
>>