TRITON-2168: Booter: Missing hostname for linuxCNs on network.json file

Details

Issue Type:Bug
Priority:4 - Normal
Status:Resolved
Created at:2020-09-11T16:28:35.992Z
Updated at:2020-09-22T14:14:10.628Z

People

Created by:Pedro Palazón Candel
Reported by:Pedro Palazón Candel
Assigned to:Pedro Palazón Candel

Resolution

Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2020-09-22T14:14:10.600Z)

Related Issues

Labels

linuxcn

Description

Hostname value must be present into networking file for linux cns, given it's present for CNAPI.

Sample CNAPI:

[root@headnode (coal) ~]# sdc-cnapi /servers/68c24d56-f37d-67a0-8b4e-138c308d2416|json -H hostname
linux13
[root@headnode (coal) ~]# sdc-cnapi /boot/68c24d56-f37d-67a0-8b4e-138c308d2416|json -H
{
  "platform": "20200910T082825Z",
  "kernel_args": {
    "hostname": "linux13",
    "rabbitmq": "guest:guest:10.99.99.20:5672",
    "smt_enabled": true,
    "rabbitmq_dns": "guest:guest:rabbitmq.coal.joyent.us:5672"
  },
  "kernel_flags": {},
  "boot_modules": [],
  "default_console": "serial",
  "serial": "ttyb"
}

And the bogus JSON file:

[root@08a0efd7-45f1-4ccb-a593-7fa0bc041f14 (coal:dhcpd0) /tftpboot]# cat cache/00:0c:29:8d:24:16.json
{
  "platform": "20200910T082825Z",
  "kernel_args": {
    "rabbitmq": "guest:guest:10.99.99.20:5672",
    "smt_enabled": true,
    "rabbitmq_dns": "guest:guest:rabbitmq.coal.joyent.us:5672",
    "admin_nic": "00:0c:29:8d:24:16"
  },
  "kernel_flags": {},
  "boot_modules": [],
  "default_console": "serial",
  "serial": "ttyb",
  "ip": "10.99.99.57",
  "netmask": "255.255.255.0",
  "resolvers": [
    "10.99.99.11"
  ]
}

And the networking.json file:

[root@08a0efd7-45f1-4ccb-a593-7fa0bc041f14 (coal:dhcpd0) /tftpboot]# cat bootfs/000c298d2416/networking.json
{
  "nictags": [
    {
      "mtu": 1500,
      "name": "admin",
      "uuid": "171620b6-3a86-4f82-8c70-27bfbf53c196",
      "mac": "00:0c:29:8d:24:16"
    }
  ],
  "admin_tag": "admin",
  "resolvers": [
    "10.99.99.11"
  ],
  "routes": {},
  "vnics": [
    {
      "belongs_to_type": "other",
      "belongs_to_uuid": "930896af-bf8c-48d4-885c-6573a94b1853",
      "mac": "00:0c:29:8d:24:16",
      "owner_uuid": "930896af-bf8c-48d4-885c-6573a94b1853",
      "primary": false,
      "state": "provisioning",
      "created_timestamp": "2020-09-10T09:36:45.915Z",
      "modified_timestamp": "2020-09-10T09:36:45.915Z",
      "ip": "10.99.99.57",
      "mtu": 1500,
      "netmask": "255.255.255.0",
      "nic_tag": "admin",
      "resolvers": [
        "10.99.99.11"
      ],
      "vlan_id": 0,
      "network_uuid": "18566b3a-64f4-496e-b38f-2b9032b4eb37",
      "nic_tags_provided": [
        "admin"
      ]
    }
  ],
  "dns_domain": "joyent.us",
  "datacenter_name": "coal",
  "aggregations": []
}

Comments

Comment by Pedro Palazón Candel
Created at 2020-09-11T19:02:03.016Z

The problems so far are:


Comment by Pedro Palazón Candel
Created at 2020-09-11T19:02:49.093Z

We need net-agent Nic-fsm working at a minimum in order to get NICs info updated for servers in NAPI.


Comment by Pedro Palazón Candel
Created at 2020-09-22T14:14:10.625Z

This is now resolved into linuxcn branch of linux-live, sdc-config-agent and sdc-net-agent.