Uploaded image for project: 'XenServer Org'
  1. XenServer Org
  2. XSO-612

XenServer Tools is unable to report CoreOS' VM IP address to parent XenServer after CoreOS 1122.2.0 update

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.0
    • Fix Version/s: None
    • Component/s: API, Networking, XenCenter
    • Labels:
      None
    • Environment:

      Description

      Bug

      Basically, VM's XenServer Tools agent fails to register itself with host XenServer.
      This means there is no IP address shown in Networking tab, resulting in inability to enable Docker management (along with any other functionality, when a connection from XenServer to VM is required), due to XenServer being unable to connect to host VM.

      I want to explicitly state that this is not a XenOrchestra issue and is occuring even when using only XenCenter. In fact, it is not related to the environment controller, but rather the XenServer Tools agent.

      Expected Behavior

      CoreOS boots
      XenServer Tools agent starts - no errors
      XenCenter shows 'Virtualization state: Optimized (version 7.0 installed)' in VM's General tab
      XenCenter shows IP address(es) related to VM in Networking tab
      XenCenter is able to turn on Docker management via an SSH connection

      Actual Behavior

      CoreOS boots
      XenServer Tools agent starts - no errors
      XenCenter shows 'Virtualization state: Optimized (version 6.2 installed)' in VM's General tab
      XenCenter missing IP address(es) related to VM in Networking tab
      XenCenter is not able to turn on Docker management via an SSH connection. Failing due to missing IP address.

      Reproduction Steps

      1. Boot CoreOS from ISO image with a default XenOrchestra cloud-config
      2. Open XenCenter, navigate to VM's Networking tab

      Cloud config template from XenOrchestra
      #cloud-config
      
      hostname: %VMNAMETOHOSTNAME%
      ssh_authorized_keys:
        # - ssh-rsa <Your public key>
        # The following entry will automatically be replaced with a public key
        # generated by container management plugin. The key-entry must exist,
        # in order to enable container management for this VM.
        - ssh-rsa %CONTAINERRSAPUB%
      coreos:
        units:
          - name: etcd.service
            command: start
          - name: fleet.service
            command: start
          # Hypervisor Linux Guest Agent
          - name: xe-linux-distribution.service
            command: start
            content: |
              [Unit]
              Description=Hypervisor Linux Guest Agent
              After=docker.service
      
              [Service]
              ExecStartPre=/media/configdrive/agent/xe-linux-distribution /var/cache/xe-linux-distribution
              ExecStart=/media/configdrive/agent/xe-daemon
        etcd:
          name: %VMNAMETOHOSTNAME%
          # generate a new token for each unique cluster at https://discovery.etcd.io/
      new
          # discovery: https://discovery.etcd.io/<token>
      write_files:
        # Enable ARP notifications for smooth network recovery after migrations
        - path: /etc/sysctl.d/10-enable-arp-notify.conf
          permissions: 0644
          owner: root
          content: |
            net.ipv4.conf.all.arp_notify = 1
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              cryptogate Semjon Inkin
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: