adietrich-ussignal opened a new issue, #8795:
URL: https://github.com/apache/cloudstack/issues/8795

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   Agent
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.19.0.0
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   
   Advanced Networking
   
   cloudbr0 - Guest/Private (VXLAN)
   cloudbr1 - Public Network (VLAN)
   cloudbr2 - Management Network (VLAN)
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   Ubuntu 22.04 LTS 
   KVM Hypervisor 
   
   Netplan configuration: 
   ```
   ---
   network:
     version: 2
     ethernets:
       ens1f0: {}
       ens1f1: {}
       lo:
         match:
           name: lo
         addresses:
           - 10.255.255.12/32
     bonds:
       bond0:
         dhcp4: false
         dhcp6: false
         interfaces:
           - ens1f0
           - ens1f1
         parameters:
           mode: 802.3ad
           mii-monitor-interval: 100
     bridges:
       cloudbr0:
         interfaces:
           - bond0.2007
         addresses:
           - 10.255.0.4/24
         parameters:
           stp: false
           forward-delay: 5
         mtu: 9000
       cloudbr2:
         interfaces:
           - bond0.2003
         addresses:
           - 10.120.0.5/24
         dhcp4: false
         routes:
           - to: default
             via: 10.120.0.1
         nameservers:
           addresses:
             - 10.10.0.10
             - 10.10.0.11
         mtu: 1500
       cloudbr1:
         interfaces:
           - bond0
         parameters:
           stp: false
         mtu: 1500
     vlans:
       bond0.2000:
         id: 2000
         link: bond0
       bond0.2003:
         id: 2003
         link: bond0
         mtu: 1500
       bond0.2007:
         id: 2007
         link: bond0
         mtu: 9000
   ```
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   When adding a host to CloudStack, the auto-detected private NIC value is 
cloudbr2, which does not appear to respect the assigned traffic labels in 
CloudStack. When attempting to hard-code the values in `agent.properties` the 
values are not respected and are modified to values that do not correctly 
reflect the traffic labels. 
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   1. Update agent.properties with a private.network.device=cloudbr0. 
   2. Start cloudstack-agent. 
   3. Add host in CloudStack UI using the IP address associated with cloudbr2. 
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   Host is added successfully to CloudStack. 
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Host does not add and times out with a 530 error. 
   
   Manually updating private.nic.device agent.properties during the host add 
process can successfully complete the host add. 
   ~~~
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to