[DPB] dynamic port breakout configuration not present in CONFIG_DB after the image installation

[vadymhlushko-mlnx]

Description

"BREAKOUT_CFG" keys are not presented in CONFIG_DB after installation of latest SONiC master branch image with DPB support.
Capability files are presented on the switch like in this PR_6003

Steps to reproduce the issue:

1. Install the latest master image on the switch
2. Do the next command - config interface breakout Ethernet4 2x50G -y

Describe the results you received:

root@arc-switch1004:~# config interface breakout Ethernet4 2x50G -y
[ERROR] Breakout feature is not available without platform.json file
Aborted!

But actually platform.json is presented on the switch.

root@arc-switch1004:~# redis-cli -n 4 KEYS "*BREAKOUT_CFG*" - the output of this command is empty.

Describe the results you expected:

root@arc-switch1004:~# config interface breakout Ethernet4 4x25G[10G]
Do you want to Breakout the port, continue? [y/N]: y

Running Breakout Mode : 2x50G
Target Breakout Mode : 4x25G[10G]

Ports to be deleted :
 {
    "Ethernet6": "50000",
    "Ethernet4": "50000"
}
Ports to be added :
 {
    "Ethernet6": "25000",
    "Ethernet7": "25000",
    "Ethernet4": "25000",
    "Ethernet5": "25000"
}

After running Logic to limit the impact

Final list of ports to be deleted :
 {
    "Ethernet6": "50000",
    "Ethernet4": "50000"
}
Final list of ports to be added :
 {
    "Ethernet6": "25000",
    "Ethernet7": "25000",
    "Ethernet4": "25000",
    "Ethernet5": "25000"
}
Loaded below Yang Models
['sonic-acl', 'sonic-breakout_cfg', 'sonic-crm', 'sonic-device_metadata', 'sonic-device_neighbor', 'sonic-extension', 'sonic-interface', 'sonic-loopback-interface', 'sonic-port', 'sonic-portchannel', 'sonic-types', 'sonic-versions', 'sonic-vlan']
Note: Below table(s) have no YANG models:
FLEX_COUNTER_TABLE, TELEMETRY, FEATURE,
Below Config can not be verified, It may cause harm to the system
 {}
Do you wish to Continue? [y/N]: y
Breakout process got successfully completed.
Please note loaded setting will be lost after system reboot. To preserve setting, run `config save`.

Additional information you deem important (e.g. issue happens only occasionally):

**Output of `show version`:**

root@arc-switch1004:~# show version

SONiC Software Version: SONiC.SONIC.master.38-5410290_Internal
Distribution: Debian 10.6
Kernel: 4.19.0-9-2-amd64
Build commit: 5410290b
Build date: Mon Nov 23 17:35:15 UTC 2020
Built by: sw-r2d2-bot@r-build-sonic-ci02

Platform: x86_64-mlnx_msn2700-r0
HwSKU: Mellanox-SN2700-D48C8
ASIC: mellanox
Serial Number: MT1822K07823
Uptime: 12:51:16 up 39 min,  2 users,  load average: 4.00, 4.16, 4.17

Docker images:
REPOSITORY                    TAG                                IMAGE ID            SIZE
docker-syncd-mlnx             SONIC.master.38-5410290_Internal   f5095d1abfb4        586MB
docker-syncd-mlnx             latest                             f5095d1abfb4        586MB
docker-snmp                   SONIC.master.38-5410290_Internal   0a3cbcf521e2        478MB
docker-snmp                   latest                             0a3cbcf521e2        478MB
docker-teamd                  SONIC.master.38-5410290_Internal   f294c5873c25        485MB
docker-teamd                  latest                             f294c5873c25        485MB
docker-sonic-mgmt-framework   SONIC.master.38-5410290_Internal   8d923d051f4f        599MB
docker-sonic-mgmt-framework   latest                             8d923d051f4f        599MB
docker-nat                    SONIC.master.38-5410290_Internal   03c1edf1c093        488MB
docker-nat                    latest                             03c1edf1c093        488MB
docker-router-advertiser      SONIC.master.38-5410290_Internal   97880fd96c53        442MB
docker-router-advertiser      latest                             97880fd96c53        442MB
docker-platform-monitor       SONIC.master.38-5410290_Internal   7c08d3489769        647MB
docker-platform-monitor       latest                             7c08d3489769        647MB
docker-database               SONIC.master.38-5410290_Internal   81dac0700284        442MB
docker-database               latest                             81dac0700284        442MB
docker-lldp                   SONIC.master.38-5410290_Internal   9cc6abebc125        516MB
docker-lldp                   latest                             9cc6abebc125        516MB
docker-orchagent              SONIC.master.38-5410290_Internal   93fb40536a57        499MB
docker-orchagent              latest                             93fb40536a57        499MB
docker-dhcp-relay             SONIC.master.38-5410290_Internal   591fabc41a10        449MB
docker-dhcp-relay             latest                             591fabc41a10        449MB
docker-sonic-telemetry        SONIC.master.38-5410290_Internal   4fe1116e6d53        511MB
docker-sonic-telemetry        latest                             4fe1116e6d53        511MB
docker-fpm-frr                SONIC.master.38-5410290_Internal   5c89a49d5d80        501MB
docker-fpm-frr                latest                             5c89a49d5d80        501MB
docker-sflow                  SONIC.master.38-5410290_Internal   1b92bd1f40aa        486MB
docker-sflow                  latest                             1b92bd1f40aa        486MB

**Attach debug file `sudo generate_dump`:**

[sonic_dump_arc-switch1004_20201124_123816.tar.gz](https://github.com/Azure/sonic-buildimage/files/5589963/sonic_dump_arc-switch1004_20201124_123816.tar.gz)

[vadymhlushko-mlnx]

sudo generate_dump

sonic_dump_arc-switch1004_20201124_123816.tar.gz

[anshuv-mfst]

Hi @zhenggen-xu , @praveen-li - Could you please look into this issue.

Thanks.

[praveen-li]

@samaity : It says breakout table is not created even if platform.json is present, after image installation. Do we need to do anything here, please take a look thanks.

[zhenggen-xu]

@vadymhlushko-mlnx If the image is fresh installed like ONIE, it should have that tables. In case of the sonic_installer, since we take the config_db.json from old image where it might not have the table, we will hit this issue.

This seems to be a generic issue where the new SONiC version introduce new tables in config_db.json and we use sonic_installer. I think we should load all default tables before config load, which can be achieved by "config reload -l"

@lguohan what is your opinion?

[vadymhlushko-mlnx]

@zhenggen-xu
If the image is freshly installed via ONIE, BREAKOUT_CFG tables exist in CONFIG_DB