[Starlingx-discuss] FW: FW: Ansible Error

[Kung, John]

In this case, it appears populate_initial_config.py (under /usr/share/ansible) encountered an error in populate_controller_config() attempting to update the system via sysinv-api. Other system configuration, dependent also on sysinv-api,  appeared to have succeeded just before hand.  The standard_root_disk_size should be restored to default settings; as at least 500GB hard disk is recommended.

It would be of interest to see:
 
1. /var/log/sysinv.log if there were unexpected Error around the time of the attempt to populate controller-0 into the system

"Host values = {'tboot': 'false', 'install_output': 'text', 'rootfs_device': '/dev/disk/by-path/pci-0000:01:01.0-scsi-0:0:0:0', 'boot_device': '/dev/disk/by-path/pci-0000:01:01.0-scsi-0:0:0:0', 'availability': 'offline', 'mgmt_mac': '00:00:00:00:00:00', 'console': 'tty0', 'mgmt_ip': '192.168.200.11', 'hostname': 'controller-0', 'operational': 'disabled', 'invprovision': 'provisioning', 'administrative': 'locked', 'personality': 'controller'}"

The sysinv.log* and sysinv-api.log logs could be attached for review.

2. check the required sysinv services are running; expect at least sysinv-api, sysinv-conductor, sysinv-agent
ps aux |grep sysinv-
    root      102771  0.4  0.1 443084 100976 ?       S    13:16   1:35 /usr/bin/python /usr/bin/sysinv-agent
    root      114118  2.4  0.3 458956 211040 ?       S<   13:18   7:47 /usr/bin/python /bin/sysinv-conductor --config-file=/etc/sysinv/sysinv.conf
    sysinv    114167  0.7  0.1 341656 115700 ?       S<   13:18   2:29 /usr/bin/python /bin/sysinv-api --config-file=/etc/sysinv/sysinv.conf
    ...

3. if any of those services are not running, could try starting from command line (as sudo) and check for error message

(Had controller-0 been provisioned, would be able to perform a collect of all logs for further analysis:
 https://docs.starlingx.io/fault-mgmt/kubernetes/troubleshooting-log-collection.html )



----------------------------------------------------------------------

Message: 1
Date: Tue, 1 Feb 2022 16:44:56 +0000
From: Mohammed Abuibaid <MohammedAAAbuibaid at cmail.carleton.ca>
To: "starlingx-discuss (starlingx-discuss at lists.starlingx.io)"
        <starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] FW: FW: Ansible Error
Message-ID:
        <YT1PR01MB8890372B8603E2869BC848D685269 at YT1PR01MB8890.CANPRD01.PROD.OUTLOOK.COM>

Content-Type: text/plain; charset="utf-8"

Hi StarlingX Community

My group is running into an error which in brief says

?"No handlers could be found for logger \"cgtsclient.common.http\"

We have adjusted the parameter ?standard_root_disk_size: ? parameter in main.yml  from the directory /usr/share/ansiblestz-ansible/playbooks/roles/bootstrap/prepare-env/vars/

Previous it was 500, we adjusted it to 100, then 50 and then 1 but still received the same error.

This seems more like an HTTP issue moreso than a physical disk problem. I have attached the entire console output of stderr, formatted a bit for readability.

I found this ticket from last week but it includes ?Disk size requirements not met? which isn?t included in our output so it?s likely different.

http://lists.starlingx.io/pipermail/starlingx-discuss/2021-January/010647.html



Any help this is would be appreciated.

Thanks,
Elijah Mendez

This email contains links to content or websites. Always be cautious when opening external links or attachments.

Please visit https://carleton.ca/its/help-centre/report-phishing/ for information on reporting phishing messages.

When in doubt, the ITS Service Desk can provide assistance. https://carleton.ca/its/chat

-----End of Disclaimer-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20220201/72ce7bd3/attachment-0001.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: failedtoprovision.txt
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20220201/72ce7bd3/attachment-0001.txt