| 2018-10-11 07:25:02 |
Austin Sun |
bug |
|
|
added bug |
| 2018-10-11 07:25:02 |
Austin Sun |
attachment added |
|
The log https://bugs.launchpad.net/bugs/1797320/+attachment/5199849/+files/log.tar.gz |
|
| 2018-10-11 07:26:53 |
Austin Sun |
description |
Title
-----
Compute Node will continuously rebooting on KVM virtual deployment env(OVS and DPDK related)
Brief Description
-----------------
When Deploy system on KVM virtual env, The Compute will continuously rebooting
The Alarm is 200.011 - r5-multi-compute-0 experienced a configuration failure. and
200.004 - r5-multi-compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful.
Severity
--------
<Critical: System/Feature is not usable after the defect>
Steps to Reproduce
------------------
Create Compute Node in KVM use attached kvm xml. the NIC type is setting to e1000
and deploy it on NUC.
Expected Behavior
------------------
Compute can be successfully provision and work
Actual Behavior
----------------
Compute re-boot continuously
Reproducibility
---------------
<Reproducible/Intermittent>
if using attached KVM xml, this is 100% reproducible
System Configuration
--------------------
<One node system, Two node system, Multi-node system, Dedicated storage, https, IPv4, IPv6 etc.>
Multi-node System (1 controller and 1 compute) on KVM VM env.
Branch/Pull Time/Commit
-----------------------
latest Mainline and r/2018.10 branch
Timestamp/Logs
-------------- |
Title
-----
Compute Node will continuously rebooting on KVM virtual deployment env(OVS and DPDK related)
Brief Description
-----------------
When Deploy system on KVM virtual env, The Compute will continuously rebooting
The Alarm is 200.011 - r5-multi-compute-0 experienced a configuration failure. and
200.004 - r5-multi-compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful.
Severity
--------
<Critical: System/Feature is not usable after the defect>
Steps to Reproduce
------------------
Create Compute Node in KVM use attached kvm xml. the NIC type is setting to e1000
and deploy it on NUC.
Expected Behavior
------------------
Compute can be successfully provision and work
Actual Behavior
----------------
Compute re-boot continuously
Reproducibility
---------------
<Reproducible/Intermittent>
if using attached KVM xml, this is 100% reproducible
System Configuration
--------------------
<One node system, Two node system, Multi-node system, Dedicated storage, https, IPv4, IPv6 etc.>
Multi-node System (1 controller and 1 compute) on KVM VM env.
Branch/Pull Time/Commit
-----------------------
latest Mainline and r/2018.10 branch
Timestamp/Logs
--------------
openvswitch/ovs-vswitchd.log
2018-10-11T07:02:25.418Z|00075|bridge|INFO|bridge br-phy0: added interface lldpdbfaf9d1-0f on port 1
2018-10-11T07:02:25.727Z|00076|dpdk|ERR|EAL: Driver cannot attach the device (0000:00:06.0)
2018-10-11T07:02:25.727Z|00077|dpdk|ERR|EAL: No port found for device (0000:00:06.0)
2018-10-11T07:02:25.727Z|00078|netdev_dpdk|WARN|Error attaching device '0000:00:06.0' to DPDK
2018-10-11T07:02:25.727Z|00079|netdev|WARN|eth0: could not set configuration (Invalid argument)
2018-10-11T07:02:30.395Z|00080|memory|INFO|105820 kB peak resident set size after 10.1 seconds
2018-10-11T07:02:30.395Z|00081|memory|INFO|handlers:2 ports:2 revalidators:2 rules:5 udpif keys:7
2018-10-11T07:02:33.429Z|00082|dpdk|ERR|EAL: Driver cannot attach the device (0000:00:06.0) |
|
| 2018-10-11 07:27:31 |
Austin Sun |
attachment added |
|
KVM xml to define compute node https://bugs.launchpad.net/starlingx/+bug/1797320/+attachment/5199850/+files/r5-multi-compute-0.xml |
|
| 2018-10-11 08:16:41 |
Austin Sun |
description |
Title
-----
Compute Node will continuously rebooting on KVM virtual deployment env(OVS and DPDK related)
Brief Description
-----------------
When Deploy system on KVM virtual env, The Compute will continuously rebooting
The Alarm is 200.011 - r5-multi-compute-0 experienced a configuration failure. and
200.004 - r5-multi-compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful.
Severity
--------
<Critical: System/Feature is not usable after the defect>
Steps to Reproduce
------------------
Create Compute Node in KVM use attached kvm xml. the NIC type is setting to e1000
and deploy it on NUC.
Expected Behavior
------------------
Compute can be successfully provision and work
Actual Behavior
----------------
Compute re-boot continuously
Reproducibility
---------------
<Reproducible/Intermittent>
if using attached KVM xml, this is 100% reproducible
System Configuration
--------------------
<One node system, Two node system, Multi-node system, Dedicated storage, https, IPv4, IPv6 etc.>
Multi-node System (1 controller and 1 compute) on KVM VM env.
Branch/Pull Time/Commit
-----------------------
latest Mainline and r/2018.10 branch
Timestamp/Logs
--------------
openvswitch/ovs-vswitchd.log
2018-10-11T07:02:25.418Z|00075|bridge|INFO|bridge br-phy0: added interface lldpdbfaf9d1-0f on port 1
2018-10-11T07:02:25.727Z|00076|dpdk|ERR|EAL: Driver cannot attach the device (0000:00:06.0)
2018-10-11T07:02:25.727Z|00077|dpdk|ERR|EAL: No port found for device (0000:00:06.0)
2018-10-11T07:02:25.727Z|00078|netdev_dpdk|WARN|Error attaching device '0000:00:06.0' to DPDK
2018-10-11T07:02:25.727Z|00079|netdev|WARN|eth0: could not set configuration (Invalid argument)
2018-10-11T07:02:30.395Z|00080|memory|INFO|105820 kB peak resident set size after 10.1 seconds
2018-10-11T07:02:30.395Z|00081|memory|INFO|handlers:2 ports:2 revalidators:2 rules:5 udpif keys:7
2018-10-11T07:02:33.429Z|00082|dpdk|ERR|EAL: Driver cannot attach the device (0000:00:06.0) |
Title
-----
Compute Node will continuously rebooting on KVM virtual deployment env(OVS and DPDK related)
Brief Description
-----------------
When Deploy system on KVM virtual env, The Compute will continuously rebooting
The Alarm is 200.011 - r5-multi-compute-0 experienced a configuration failure. and
200.004 - r5-multi-compute-0 experienced a service-affecting failure. Auto-recovery in progress. Manual Lock and Unlock may be required if auto-recovery is unsuccessful.
Severity
--------
<Critical: System/Feature is not usable after the defect>
Steps to Reproduce
------------------
Create Compute Node in KVM use attached kvm xml. the NIC type is setting to e1000
and deploy it on NUC.
Expected Behavior
------------------
Compute can be successfully provision and work
Actual Behavior
----------------
Compute re-boot continuously
Reproducibility
---------------
<Reproducible/Intermittent>
if using attached KVM xml, this is 100% reproducible
System Configuration
can use stx-2018-10-07-15-r-2018.10.iso to reproduce.
--------------------
<One node system, Two node system, Multi-node system, Dedicated storage, https, IPv4, IPv6 etc.>
Multi-node System (1 controller and 1 compute) on KVM VM env.
Branch/Pull Time/Commit
-----------------------
latest Mainline and r/2018.10 branch
Timestamp/Logs
--------------
openvswitch/ovs-vswitchd.log
2018-10-11T07:02:25.418Z|00075|bridge|INFO|bridge br-phy0: added interface lldpdbfaf9d1-0f on port 1
2018-10-11T07:02:25.727Z|00076|dpdk|ERR|EAL: Driver cannot attach the device (0000:00:06.0)
2018-10-11T07:02:25.727Z|00077|dpdk|ERR|EAL: No port found for device (0000:00:06.0)
2018-10-11T07:02:25.727Z|00078|netdev_dpdk|WARN|Error attaching device '0000:00:06.0' to DPDK
2018-10-11T07:02:25.727Z|00079|netdev|WARN|eth0: could not set configuration (Invalid argument)
2018-10-11T07:02:30.395Z|00080|memory|INFO|105820 kB peak resident set size after 10.1 seconds
2018-10-11T07:02:30.395Z|00081|memory|INFO|handlers:2 ports:2 revalidators:2 rules:5 udpif keys:7
2018-10-11T07:02:33.429Z|00082|dpdk|ERR|EAL: Driver cannot attach the device (0000:00:06.0) |
|
| 2018-10-16 14:25:04 |
Ghada Khalil |
tags |
|
stx.networking |
|
| 2018-10-16 14:25:54 |
Ghada Khalil |
tags |
stx.networking |
stx.2018.10 stx.networking |
|
| 2018-10-16 14:26:25 |
Ghada Khalil |
starlingx: importance |
Undecided |
High |
|
| 2018-10-16 14:26:47 |
Ghada Khalil |
starlingx: assignee |
|
Steven Webster (swebster-wr) |
|
| 2018-10-16 14:26:51 |
Ghada Khalil |
starlingx: status |
New |
Triaged |
|
| 2018-10-16 14:28:05 |
Ghada Khalil |
marked as duplicate |
|
1796380 |
|
| 2018-10-19 07:07:13 |
Austin Sun |
attachment added |
|
log.tar.gz https://bugs.launchpad.net/starlingx/+bug/1797320/+attachment/5202901/+files/log.tar.gz |
|
| 2018-10-22 07:27:04 |
Austin Sun |
removed duplicate marker |
1796380 |
|
|
| 2018-10-22 07:27:17 |
Austin Sun |
starlingx: status |
Triaged |
Invalid |
|
| 2018-10-27 02:15:18 |
Ghada Khalil |
starlingx: assignee |
Steven Webster (swebster-wr) |
Austin Sun (sunausti) |
|
| 2019-04-06 16:13:54 |
Ken Young |
tags |
stx.2018.10 stx.networking |
stx.1.0 stx.networking |
|
