[Starlingx-discuss] Unable to mount squashfs.img
Hi, I’m trying to build a StarlingX ISO. I got an error at step 'update-pxe-network-installer’: -rw-r--r-- 1 root root 55629360 Nov 29 07:11 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-initrd.img -rwxr-xr-x 1 root root 6588016 Nov 29 07:09 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-vmlinuz ---------------- start to make new squashfs.img ------------- /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/orig/squashfs.img /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/squashfs.mnt mount: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. Any suggestion how to fix it? Thank you. br, Xu Yun
Can you confirm the following file exists in your mirror? /import/mirrors/CentOS/stx-r1-centos75/CentOS/pike/Binary/LiveOS/squashfs.img If the file does exit, very likely it was *corrupted* because it seemed the failure came from: mount -o loop -t squashfs $ORIG_SQUASHFS $work_dir/squashfs.mnt in script: "~/cgcs-root/build-tools/make-installer-images.sh" You can manually mount "squashfs.img" to confirm it is not corrupted. On 29/11/2018, 3:30 PM, "徐蕴" <xuyun@jxresearch.com> wrote: Hi, I’m trying to build a StarlingX ISO. I got an error at step 'update-pxe-network-installer’: -rw-r--r-- 1 root root 55629360 Nov 29 07:11 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-initrd.img -rwxr-xr-x 1 root root 6588016 Nov 29 07:09 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-vmlinuz ---------------- start to make new squashfs.img ------------- /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/orig/squashfs.img /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/squashfs.mnt mount: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. Any suggestion how to fix it? Thank you. br, Xu Yun _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hello Hu Yong, Thank you for your quick help! Yes, my download of squashes.img is corrupted (only has size of 384k). I’m downloading it manually. Thanks again. Br, Xu Yun
在 2018年11月29日，下午3:41，Hu, Yong <yong.hu@intel.com> 写道：
Can you confirm the following file exists in your mirror?
/import/mirrors/CentOS/stx-r1-centos75/CentOS/pike/Binary/LiveOS/squashfs.img
If the file does exit, very likely it was *corrupted* because it seemed the failure came from:
mount -o loop -t squashfs $ORIG_SQUASHFS $work_dir/squashfs.mnt
in script: "~/cgcs-root/build-tools/make-installer-images.sh"
You can manually mount "squashfs.img" to confirm it is not corrupted.
On 29/11/2018, 3:30 PM, "徐蕴" <xuyun@jxresearch.com> wrote:
Hi,
I’m trying to build a StarlingX ISO. I got an error at step 'update-pxe-network-installer’:
-rw-r--r-- 1 root root 55629360 Nov 29 07:11 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-initrd.img -rwxr-xr-x 1 root root 6588016 Nov 29 07:09 /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/output/new-vmlinuz ---------------- start to make new squashfs.img ------------- /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/orig/squashfs.img /localdisk/loadbuild/ubuntu/starlingx/pxe-network-installer/squashfs.mnt mount: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
Any suggestion how to fix it? Thank you.
br, Xu Yun _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi, I’m trying to deploy a simplex on a bare metal server. After unlocking controller-0 following the installation_guide, two error events are reported and this node was degraded: 200.011 <http://111.111.111.1/admin/fault_management/58857199-137d-41dc-a8ab-063024695f76/detail/> controller-0 experienced a configuration failure. host=controller-0 300.004 <http://111.111.111.1/admin/fault_management/5be8292e-c1c1-4068-bce3-84b4d43d923b/detail/> No enabled compute host with connectivity to provider network. service=networking.providernet=e542cf30-a07d-41f7-be7b-cc5a4e14b0d7 Would you please give me some hints how to debug this problem? Thank you! Br, Xu Yun
300.004 is a dependency alarm that should go away once controller-0 is unlocked-enabled. Looks like an All-In-One system your trying to provision. Therefore this could be a controller or compute function configuration error. I would look for the words Error and Warning in the puppet logs and see what that shows. sudo grep �Cr /var/log/puppet �Ce Error �Ce Warning Eric. From: ���� [mailto:xuyun@jxresearch.com] Sent: Monday, December 03, 2018 4:26 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Unable to bring up controller-0 Hi, I��m trying to deploy a simplex on a bare metal server. After unlocking controller-0 following the installation_guide, two error events are reported and this node was degraded: 200.011<http://111.111.111.1/admin/fault_management/58857199-137d-41dc-a8ab-063024695f76/detail/> controller-0 experienced a configuration failure. host=controller-0 300.004<http://111.111.111.1/admin/fault_management/5be8292e-c1c1-4068-bce3-84b4d43d923b/detail/> No enabled compute host with connectivity to provider network. service=networking.providernet=e542cf30-a07d-41f7-be7b-cc5a4e14b0d7 Would you please give me some hints how to debug this problem? Thank you! Br, Xu Yun
Hello, Thanks for Eric's hint. I doubted this problem is related to OVS bridge setup yesterday controller-0:/var/log/puppet# ovs-vsctl show a98562f6-3223-4eab-a663-68cb4d8e9ece Manager "ptcp:6639:127.0.0.1" is_connected: true Bridge "br-phy0" Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "lldpd2a87771-fd" Interface "lldpd2a87771-fd" type: internal Port "phy-br-phy0" Interface "phy-br-phy0" type: patch options: {peer="int-br-phy0"} Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:02:00.1", n_rxq="1"} error: "Error attaching device '0000:02:00.1' to DPDK" Port "br-phy0" Interface "br-phy0" type: internal Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "int-br-phy0" Interface "int-br-phy0" type: patch options: {peer="phy-br-phy0"} Port br-int Interface br-int type: internal ovs_version: “2.9.0" I don’t know why ‘eth0’ was added into the br-phy0 bridge, since there is no ‘eth0’ in my machine. I configured an interface named ‘eno4’ for my data plane. [wrsroot@controller-0 log(keystone_admin)]$ system host-if-list -a 1 +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+-------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | provider networks | +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+-------------------+ | 548477c1-038f-4280-a4b1-d7c11d724b09 | eno4 | data | ethernet | None | [u'eno4'] | [] | [] | MTU=1500,accelerated=False | providernet-a | | 5c4760f5-a32b-49b9-91d1-73a72fdcabfb | eno3 | None | ethernet | None | [u'eno3'] | [] | [] | MTU=1500 | None | | 7b85e213-f435-4693-a13a-364de1e06a35 | eno1 | platform | ethernet | None | [u'eno1'] | [] | [] | MTU=1500 | None | | 96e1e865-2f7c-486e-8e9e-88fcb1c71686 | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | None | | c87ccb52-a1c7-4332-87f9-5966e6599ee6 | eno2 | None | ethernet | None | [u'eno2'] | [] | [] | MTU=1500 | None | +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+—————————+ And also the puppet log seems confirm that ovs setup failure because of ‘eth0': controller-0:/var/log/puppet# grep -r /var/log/puppet/ -e Error -e Warning /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.348 Notice: 2018-12-03 16:07:16 +0800 /Stage[main]/Platform::Vswitch::Ovs/Platform::Vswitch::Ovs::Port[eth0]/Exec[ovs-add-port: eth0]/returns: ovs-vsctl: Error detected while setting up 'eth0': Error attaching device '0000:02:00.1' to DPDK. See ovs-vswitchd log for details. /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.443 Error: 2018-12-03 16:07:16 +0800 ovs-ofctl add-flow br-phy0 dl_dst=01:80:c2:00:00:0e,dl_type=0x88cc,hard_timeout=0,idle_timeout=0,in_port=eth0,actions=output:lldpd2a87771-fd returned 1 instead of one of [0] /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.678 Error: 2018-12-03 16:07:16 +0800 /Stage[main]/Platform::Vswitch::Ovs/Platform::Vswitch::Ovs::Flow[eth0]/Exec[ovs-add-flow: eth0]/returns: change from notrun to 0 failed: ovs-ofctl add-flow br-phy0 dl_dst=01:80:c2:00:00:0e,dl_type=0x88cc,hard_timeout=0,idle_timeout=0,in_port=eth0,actions=output:lldpd2a87771-fd returned 1 instead of one of [0] /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.800 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Ceph::Post/File[/var/run/.ceph_started]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.806 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/Service[crond]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.817 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Compute::Post/File[/etc/platform/.initial_compute_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.824 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Compute::Post/File[/var/run/.compute_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.833 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/File[/etc/platform/.initial_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.839 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/File[/etc/platform/.config_applied]: Skipping because of failed dependencies Any further suggestion how to fix this problem? Thank you. Br, Xu Yun
在 2018年12月3日，下午11:02，MacDonald, Eric <Eric.MacDonald@windriver.com> 写道：
300.004 is a dependency alarm that should go away once controller-0 is unlocked-enabled.
Looks like an All-In-One system your trying to provision. Therefore this could be a controller or compute function configuration error.
I would look for the words Error and Warning in the puppet logs and see what that shows.
sudo grep จCr /var/log/puppet จCe Error จCe Warning
Eric.
From: ะ์ิฬ [mailto:xuyun@jxresearch.com <mailto:xuyun@jxresearch.com>] Sent: Monday, December 03, 2018 4:26 AM To: starlingx-discuss@lists.starlingx.io <mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Unable to bring up controller-0
Hi,
Iกฏm trying to deploy a simplex on a bare metal server. After unlocking controller-0 following the installation_guide, two error events are reported and this node was degraded:
200.011 <http://111.111.111.1/admin/fault_management/58857199-137d-41dc-a8ab-063024695f76/detail/> controller-0 experienced a configuration failure. host=controller-0 300.004 <http://111.111.111.1/admin/fault_management/5be8292e-c1c1-4068-bce3-84b4d43d923b/detail/> No enabled compute host with connectivity to provider network. service=networking.providernet=e542cf30-a07d-41f7-be7b-cc5a4e14b0d7
Would you please give me some hints how to debug this problem? Thank you!
Br, Xu Yun
Hi xuyun: Eth0 is using for dpdk , which is virtual port , not real NIC name. Could you run “python /usr/share/openvswitch/scripts/dpdk-devbind.py --status” to check what type of eno4 is ? Are you deploy in a virtual machine with libvirt ? or bare metal system ? Thanks. BR Austin Sun. From: 徐蕴 [mailto:xuyun@jxresearch.com] Sent: Tuesday, December 4, 2018 9:31 AM To: MacDonald, Eric <Eric.MacDonald@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Unable to bring up controller-0 Hello, Thanks for Eric's hint. I doubted this problem is related to OVS bridge setup yesterday controller-0:/var/log/puppet# ovs-vsctl show a98562f6-3223-4eab-a663-68cb4d8e9ece Manager "ptcp:6639:127.0.0.1" is_connected: true Bridge "br-phy0" Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "lldpd2a87771-fd" Interface "lldpd2a87771-fd" type: internal Port "phy-br-phy0" Interface "phy-br-phy0" type: patch options: {peer="int-br-phy0"} Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:02:00.1", n_rxq="1"} error: "Error attaching device '0000:02:00.1' to DPDK" Port "br-phy0" Interface "br-phy0" type: internal Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "int-br-phy0" Interface "int-br-phy0" type: patch options: {peer="phy-br-phy0"} Port br-int Interface br-int type: internal ovs_version: “2.9.0" I don’t know why ‘eth0’ was added into the br-phy0 bridge, since there is no ‘eth0’ in my machine. I configured an interface named ‘eno4’ for my data plane. [wrsroot@controller-0 log(keystone_admin)]$ system host-if-list -a 1 +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+-------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | provider networks | +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+-------------------+ | 548477c1-038f-4280-a4b1-d7c11d724b09 | eno4 | data | ethernet | None | [u'eno4'] | [] | [] | MTU=1500,accelerated=False | providernet-a | | 5c4760f5-a32b-49b9-91d1-73a72fdcabfb | eno3 | None | ethernet | None | [u'eno3'] | [] | [] | MTU=1500 | None | | 7b85e213-f435-4693-a13a-364de1e06a35 | eno1 | platform | ethernet | None | [u'eno1'] | [] | [] | MTU=1500 | None | | 96e1e865-2f7c-486e-8e9e-88fcb1c71686 | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | None | | c87ccb52-a1c7-4332-87f9-5966e6599ee6 | eno2 | None | ethernet | None | [u'eno2'] | [] | [] | MTU=1500 | None | +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+—————————+ And also the puppet log seems confirm that ovs setup failure because of ‘eth0': controller-0:/var/log/puppet# grep -r /var/log/puppet/ -e Error -e Warning /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.348 Notice: 2018-12-03 16:07:16 +0800 /Stage[main]/Platform::Vswitch::Ovs/Platform::Vswitch::Ovs::Port[eth0]/Exec[ovs-add-port: eth0]/returns: ovs-vsctl: Error detected while setting up 'eth0': Error attaching device '0000:02:00.1' to DPDK. See ovs-vswitchd log for details. /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.443 Error: 2018-12-03 16:07:16 +0800 ovs-ofctl add-flow br-phy0 dl_dst=01:80:c2:00:00:0e,dl_type=0x88cc,hard_timeout=0,idle_timeout=0,in_port=eth0,actions=output:lldpd2a87771-fd returned 1 instead of one of [0] /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.678 Error: 2018-12-03 16:07:16 +0800 /Stage[main]/Platform::Vswitch::Ovs/Platform::Vswitch::Ovs::Flow[eth0]/Exec[ovs-add-flow: eth0]/returns: change from notrun to 0 failed: ovs-ofctl add-flow br-phy0 dl_dst=01:80:c2:00:00:0e,dl_type=0x88cc,hard_timeout=0,idle_timeout=0,in_port=eth0,actions=output:lldpd2a87771-fd returned 1 instead of one of [0] /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.800 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Ceph::Post/File[/var/run/.ceph_started]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.806 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/Service[crond]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.817 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Compute::Post/File[/etc/platform/.initial_compute_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.824 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Compute::Post/File[/var/run/.compute_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.833 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/File[/etc/platform/.initial_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.839 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/File[/etc/platform/.config_applied]: Skipping because of failed dependencies Any further suggestion how to fix this problem? Thank you. Br, Xu Yun 在 2018年12月3日，下午11:02，MacDonald, Eric <Eric.MacDonald@windriver.com<mailto:Eric.MacDonald@windriver.com>> 写道： 300.004 is a dependency alarm that should go away once controller-0 is unlocked-enabled. Looks like an All-In-One system your trying to provision. Therefore this could be a controller or compute function configuration error. I would look for the words Error and Warning in the puppet logs and see what that shows. sudo grep จCr /var/log/puppet จCe Error จCe Warning Eric. From: ะ์ิฬ [mailto:xuyun@jxresearch.com] Sent: Monday, December 03, 2018 4:26 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Unable to bring up controller-0 Hi, Iกฏm trying to deploy a simplex on a bare metal server. After unlocking controller-0 following the installation_guide, two error events are reported and this node was degraded: 200.011<http://111.111.111.1/admin/fault_management/58857199-137d-41dc-a8ab-063024695f76/detail/> controller-0 experienced a configuration failure. host=controller-0 300.004<http://111.111.111.1/admin/fault_management/5be8292e-c1c1-4068-bce3-84b4d43d923b/detail/> No enabled compute host with connectivity to provider network. service=networking.providernet=e542cf30-a07d-41f7-be7b-cc5a4e14b0d7 Would you please give me some hints how to debug this problem? Thank you! Br, Xu Yun
Hi, Austin, I’m deploying an all in one node in a bare metal (an old DELL server), maybe the NIC doesn’t support DPDK? I cannot see eno4 in the output: controller-0:/var/log/puppet# python /usr/share/openvswitch/scripts/dpdk-devbind.py --status Network devices using DPDK-compatible driver ============================================ 0000:02:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' drv=vfio-pci unused= Network devices using kernel driver =================================== 0000:01:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=eno1 drv=tg3 unused=vfio-pci *Active* 0000:01:00.1 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=eno2 drv=tg3 unused=vfio-pci 0000:02:00.0 'NetXtreme BCM5720 Gigabit Ethernet PCIe 165f' if=eno3 drv=tg3 unused=vfio-pci Other Network devices ===================== <none> Since the size limitation of the email system, I upload complete log to http://paste.openstack.org/show/736607/ <http://paste.openstack.org/show/736607/> BR, Xu Yun
在 2018年12月4日，上午10:13，Sun, Austin <austin.sun@intel.com> 写道：
Hi xuyun: Eth0 is using for dpdk , which is virtual port , not real NIC name.
Could you run “python /usr/share/openvswitch/scripts/dpdk-devbind.py --status” to check what type of eno4 is ?
Are you deploy in a virtual machine with libvirt ? or bare metal system ?
Thanks. BR Austin Sun.
<> From: 徐蕴 [mailto:xuyun@jxresearch.com] Sent: Tuesday, December 4, 2018 9:31 AM To: MacDonald, Eric <Eric.MacDonald@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Unable to bring up controller-0
Hello,
Thanks for Eric's hint. I doubted this problem is related to OVS bridge setup yesterday
controller-0:/var/log/puppet# ovs-vsctl show a98562f6-3223-4eab-a663-68cb4d8e9ece Manager "ptcp:6639:127.0.0.1" is_connected: true Bridge "br-phy0" Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "lldpd2a87771-fd" Interface "lldpd2a87771-fd" type: internal Port "phy-br-phy0" Interface "phy-br-phy0" type: patch options: {peer="int-br-phy0"} Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:02:00.1", n_rxq="1"} error: "Error attaching device '0000:02:00.1' to DPDK" Port "br-phy0" Interface "br-phy0" type: internal Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "int-br-phy0" Interface "int-br-phy0" type: patch options: {peer="phy-br-phy0"} Port br-int Interface br-int type: internal ovs_version: “2.9.0"
I don’t know why ‘eth0’ was added into the br-phy0 bridge, since there is no ‘eth0’ in my machine. I configured an interface named ‘eno4’ for my data plane. [wrsroot@controller-0 log(keystone_admin)]$ system host-if-list -a 1 +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+-------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | provider networks | +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+-------------------+ | 548477c1-038f-4280-a4b1-d7c11d724b09 | eno4 | data | ethernet | None | [u'eno4'] | [] | [] | MTU=1500,accelerated=False | providernet-a | | 5c4760f5-a32b-49b9-91d1-73a72fdcabfb | eno3 | None | ethernet | None | [u'eno3'] | [] | [] | MTU=1500 | None | | 7b85e213-f435-4693-a13a-364de1e06a35 | eno1 | platform | ethernet | None | [u'eno1'] | [] | [] | MTU=1500 | None | | 96e1e865-2f7c-486e-8e9e-88fcb1c71686 | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | None | | c87ccb52-a1c7-4332-87f9-5966e6599ee6 | eno2 | None | ethernet | None | [u'eno2'] | [] | [] | MTU=1500 | None | +--------------------------------------+------+----------+----------+---------+-----------+----------+-------------+----------------------------+—————————+
And also the puppet log seems confirm that ovs setup failure because of ‘eth0':
controller-0:/var/log/puppet# grep -r /var/log/puppet/ -e Error -e Warning /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.348 Notice: 2018-12-03 16:07:16 +0800 /Stage[main]/Platform::Vswitch::Ovs/Platform::Vswitch::Ovs::Port[eth0]/Exec[ovs-add-port: eth0]/returns: ovs-vsctl: Error detected while setting up 'eth0': Error attaching device '0000:02:00.1' to DPDK. See ovs-vswitchd log for details. /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.443 Error: 2018-12-03 16:07:16 +0800 ovs-ofctl add-flow br-phy0 dl_dst=01:80:c2:00:00:0e,dl_type=0x88cc,hard_timeout=0,idle_timeout=0,in_port=eth0,actions=output:lldpd2a87771-fd returned 1 instead of one of [0] /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:16.678 Error: 2018-12-03 16:07:16 +0800 /Stage[main]/Platform::Vswitch::Ovs/Platform::Vswitch::Ovs::Flow[eth0]/Exec[ovs-add-flow: eth0]/returns: change from notrun to 0 failed: ovs-ofctl add-flow br-phy0 dl_dst=01:80:c2:00:00:0e,dl_type=0x88cc,hard_timeout=0,idle_timeout=0,in_port=eth0,actions=output:lldpd2a87771-fd returned 1 instead of one of [0] /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.800 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Ceph::Post/File[/var/run/.ceph_started]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.806 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/Service[crond]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.817 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Compute::Post/File[/etc/platform/.initial_compute_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.824 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Compute::Post/File[/var/run/.compute_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.833 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/File[/etc/platform/.initial_config_complete]: Skipping because of failed dependencies /var/log/puppet/2018-12-03-08-05-45_compute/puppet.log:2018-12-03T08:07:28.839 Warning: 2018-12-03 16:07:28 +0800 /Stage[post]/Platform::Config::Post/File[/etc/platform/.config_applied]: Skipping because of failed dependencies
Any further suggestion how to fix this problem? Thank you.
Br, Xu Yun
在 2018年12月3日，下午11:02，MacDonald, Eric <Eric.MacDonald@windriver.com <mailto:Eric.MacDonald@windriver.com>> 写道：
300.004 is a dependency alarm that should go away once controller-0 is unlocked-enabled.
Looks like an All-In-One system your trying to provision. Therefore this could be a controller or compute function configuration error.
I would look for the words Error and Warning in the puppet logs and see what that shows.
sudo grep จCr /var/log/puppet จCe Error จCe Warning
Eric.
From: ะ์ิฬ [mailto:xuyun@jxresearch.com <mailto:xuyun@jxresearch.com>] Sent: Monday, December 03, 2018 4:26 AM To: starlingx-discuss@lists.starlingx.io <mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Unable to bring up controller-0
Hi,
Iกฏm trying to deploy a simplex on a bare metal server. After unlocking controller-0 following the installation_guide, two error events are reported and this node was degraded:
200.011 <http://111.111.111.1/admin/fault_management/58857199-137d-41dc-a8ab-063024695f76/detail/> controller-0 experienced a configuration failure. host=controller-0 300.004 <http://111.111.111.1/admin/fault_management/5be8292e-c1c1-4068-bce3-84b4d43d923b/detail/> No enabled compute host with connectivity to provider network. service=networking.providernet=e542cf30-a07d-41f7-be7b-cc5a4e14b0d7
Would you please give me some hints how to debug this problem? Thank you!
Br, Xu Yun
participants (4)
-
Hu, Yong
-
MacDonald, Eric
-
Sun, Austin
-
徐蕴