swact is not triggered after killing dnsmasq process within 90 seconds

Bug #1893669 reported by Francisco Giana
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Medium
Bin Qian

Bug Description

Brief Description
-----------------
When a process fails twice whitin 90 seconds SM does not execute the expected impact.
for instance, I have tested it against dnsmasq process and after killing it twice swact is not triggered.
dnsmasq is an example, but I tested against

* dcmanager-audit
* dcmanager-api
* dcmanager-manager
* dcdbsync-api
* dcorch-engine
* hw-mond
* hbsAgent
* rabbitmq
* sysinv-conductor
* mtcAgent
* fmManager
* (it seems all the processes monitored by sm)

and they have the same behavior.

Severity
--------
Critical

Steps to Reproduce
------------------
I've created a script to test it.

1. Kill process
2. wait 60 seconds.
3. kill it again.

====== script ====
pid_file=$1
t=$2
date;
pid=$(cat $pid_file 2>/dev/null)
echo "killing $pid"
echo "ROOT_PASSWORD" | sudo -S kill -9 $pid &>/dev/null;
sleep 5;
date;
fm alarm-list;
sleep $(expr $t - 5);
date;
pid=$(cat $pid_file 2>/dev/null)
echo "killing $pid"
echo "ROOT_PASSWORD" | sudo -S kill -9 $pid &>/dev/null;
sleep 5;
date;
fm alarm-list;
======= end script ===

run it with: ./script_name.sh PID_FILE INTERVAL
for instance: sh ./script_name.sh /var/run/dnsmasq.pid 60

here are the output logs:

[sysadmin@controller-1 ~(keystone_admin)]$ sh kill_2.sh /var/run/dnsmasq.pid 60
vie ago 28 03:17:49 UTC 2020
killing 3410146
vie ago 28 03:17:54 UTC 2020
+----------+-------------------------------------------------------------------+-------------------+----------+--------------+
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+----------+-------------------------------------------------------------------+-------------------+----------+--------------+
+----------+-------------------------------------------------------------------+-------------------+----------+--------------+
vie ago 28 03:18:50 UTC 2020
killing 3434943
vie ago 28 03:18:55 UTC 2020
+----------+-------------------------------------------------------------------+-------------------+----------+--------------+
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+----------+-------------------------------------------------------------------+-------------------+----------+--------------+
+----------+-------------------------------------------------------------------+-------------------+----------+--------------+

and swact was not triggered.

Expected Behavior
------------------
swact has to be triggered if process was killed more than once within 90 seconds.

Actual Behavior
----------------
swact is not triggered.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
IPv4 distributed cloud

Branch/Pull Time/Commit
-----------------------
BUILD_ID="2020-08-25_09-07-26"

Last Pass
---------
N/A

Timestamp/Logs
--------------
N/A: logs are above.

Test Activity
-------------
Feature Testing

CVE References

description: updated
Yang Liu (yliu12)
summary: - dnsmasq process monitoring expected impact doesn't work.
+ swact is not triggered after killing dnsmasq process within 90 seconds
description: updated
Ghada Khalil (gkhalil)
tags: added: stx.ha
Revision history for this message
Ghada Khalil (gkhalil) wrote :

stx.5.0 / medium priority - issue related to process recovery

Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
tags: added: stx.5.0
Changed in starlingx:
assignee: nobody → Bin Qian (bqian20)
Revision history for this message
Anujeyan Manokeran (anujeyan) wrote :

This issue was seen in mtc-agent process kill .reproduced in Build
BUILD_DATE="2021-03-19 00:10:23 .

Revision history for this message
Bin Qian (bqian20) wrote :

The "SERVICE_GROUP_AGGREGATE" is missing for the service groups of oam-services, controller-services, cloud-services, and vim-services in DX. The change was recent, only in DEV branch.

https://opendev.org/starlingx/stx-puppet/commit/fbb4cdef07c52acb66cfcaf91bc2d029ffb00ff1

Because the service_group_aggregate is missing, when the service failed, instead of rescheduling all aggregated service groups to peer controller (swact), the impacted service group (controller-services) is rescheduled to the peer controller, which also failed (b/c it depends other services, which are scheduled in different node).

Revision history for this message
Anujeyan Manokeran (anujeyan) wrote :

This was reproduced in load 2021-03-27_00-00-06

Revision history for this message
Don Penney (dpenney) wrote :

The following review is posted to starling/master:
https://review.opendev.org/c/starlingx/stx-puppet/+/783980

Changed in starlingx:
assignee: Bin Qian (bqian20) → Don Penney (dpenney)
status: Triaged → In Progress
Revision history for this message
Don Penney (dpenney) wrote :

My review to add the missing aggregate info has merged:
https://opendev.org/starlingx/stx-puppet/commit/28ef813cda9fd0191d8cee9c1f2bd80d64175f6f

There will still need to be investigation into why SM is not triggering a swact when services are killed repeatedly..

Dariush Eslimi (deslimi)
Changed in starlingx:
assignee: Don Penney (dpenney) → Bin Qian (bqian20)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/config/+/786147

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/c/starlingx/config/+/786147
Committed: https://opendev.org/starlingx/config/commit/8cc522bed57aac4699fed1b2cdf7cf4b213a4dc7
Submitter: "Zuul (22348)"
Branch: master

commit 8cc522bed57aac4699fed1b2cdf7cf4b213a4dc7
Author: Adriano Oliveira <email address hidden>
Date: Tue Apr 13 19:21:54 2021 -0400

    sysinv-api script to return ERROR

    Remove NOT_RUNNING return in case sysinv-api pid is still active but
    fails to ping. This scenario can happen in case sysinv-api is manually
    killed and SM triggers a start.
    Also, on the new routine to check if sysinv-api is properly replying,
    return ERROR instead of NOT_RUNNING for SM consistency.

    Testing:
    Tested double sysinv-api kill withing 90 seconds as per SM
    configuration. Upon first sysinv-api kill it should be restarted,
    upon second sysinv-api kill, if done within 90 seconds, a swact is
    triggered. Also verified that sysinv-api request routine was engaged.
    Also tested AIO-DX boostrap, manual swact via host-swact and patch
    application. After boostrap and patch application tested double
    sysinv-api kill and manual swact.

    Other fix related to this issue was addressed by this change:
    https://review.opendev.org/c/starlingx/stx-puppet/+/783980

    Closes-Bug: 1893669
    Signed-off-by: Adriano Oliveira <email address hidden>
    Change-Id: I1b1ab0560237f602dadf074331f6a165d12330c7

Changed in starlingx:
status: In Progress → Fix Released
Revision history for this message
Ghada Khalil (gkhalil) wrote :

@Adriano, please cherrypick this change to the r/stx.5.0 release branch asap and no later than April 30

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (r/stx.5.0)

Fix proposed to branch: r/stx.5.0
Review: https://review.opendev.org/c/starlingx/config/+/787237

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (r/stx.5.0)

Reviewed: https://review.opendev.org/c/starlingx/config/+/787237
Committed: https://opendev.org/starlingx/config/commit/7d38399521dc058a75031fcf1e5d5bf12eb5d4b7
Submitter: "Zuul (22348)"
Branch: r/stx.5.0

commit 7d38399521dc058a75031fcf1e5d5bf12eb5d4b7
Author: Adriano Oliveira <email address hidden>
Date: Tue Apr 13 19:21:54 2021 -0400

    sysinv-api script to return ERROR

    Remove NOT_RUNNING return in case sysinv-api pid is still active but
    fails to ping. This scenario can happen in case sysinv-api is manually
    killed and SM triggers a start.
    Also, on the new routine to check if sysinv-api is properly replying,
    return ERROR instead of NOT_RUNNING for SM consistency.

    Testing:
    Tested double sysinv-api kill withing 90 seconds as per SM
    configuration. Upon first sysinv-api kill it should be restarted,
    upon second sysinv-api kill, if done within 90 seconds, a swact is
    triggered. Also verified that sysinv-api request routine was engaged.
    Also tested AIO-DX boostrap, manual swact via host-swact and patch
    application. After boostrap and patch application tested double
    sysinv-api kill and manual swact.

    Other fix related to this issue was addressed by this change:
    https://review.opendev.org/c/starlingx/stx-puppet/+/783980

    Closes-Bug: 1893669
    Signed-off-by: Adriano Oliveira <email address hidden>
    Change-Id: I1b1ab0560237f602dadf074331f6a165d12330c7
    (cherry picked from commit 8cc522bed57aac4699fed1b2cdf7cf4b213a4dc7)

Ghada Khalil (gkhalil)
tags: added: in-r-stx50
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ha (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/ha/+/790474

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ha (master)

Reviewed: https://review.opendev.org/c/starlingx/ha/+/790474
Committed: https://opendev.org/starlingx/ha/commit/9f70df63fd0d83bf0f94d1b9ac2f98516d5971c8
Submitter: "Zuul (22348)"
Branch: master

commit 9f70df63fd0d83bf0f94d1b9ac2f98516d5971c8
Author: Bin Qian <email address hidden>
Date: Fri May 7 16:36:23 2021 -0400

    Fix no swact for failure of critical services

    This fix is to ensure keeping service failure counting over successful
    audit.

    When service enabled audit successfully completes, SM reset the service
    failure state. However it should not reset the service fail-count.
    The fail-count should only be reset after the grace period.

    Closes-Bug: 1893669
    Change-Id: I6996fe3f1c08c38da6f26243aee2b95b083069f0
    Signed-off-by: Bin Qian <email address hidden>

Revision history for this message
Ghada Khalil (gkhalil) wrote :

@Bin Qian, please cherrypick the most recent commit above to the r/stx.5.0 release branch since this LP is tagged for that release.

tags: added: stx.cherrypickneeded
removed: in-r-stx50
tags: added: stx.6.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to stx-puppet (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/stx-puppet/+/792009

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on stx-puppet (f/centos8)

Change abandoned by "Chuck Short <email address hidden>" on branch: f/centos8
Review: https://review.opendev.org/c/starlingx/stx-puppet/+/792009

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to stx-puppet (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/stx-puppet/+/792013

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on stx-puppet (f/centos8)

Change abandoned by "Chuck Short <email address hidden>" on branch: f/centos8
Review: https://review.opendev.org/c/starlingx/stx-puppet/+/792013

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to stx-puppet (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/stx-puppet/+/792018

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on stx-puppet (f/centos8)

Change abandoned by "Chuck Short <email address hidden>" on branch: f/centos8
Review: https://review.opendev.org/c/starlingx/stx-puppet/+/792018

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to stx-puppet (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/stx-puppet/+/792029

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ha (r/stx.5.0)

Fix proposed to branch: r/stx.5.0
Review: https://review.opendev.org/c/starlingx/ha/+/792159

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ha (r/stx.5.0)

Reviewed: https://review.opendev.org/c/starlingx/ha/+/792159
Committed: https://opendev.org/starlingx/ha/commit/12f7ea91efb79aee858b3101223081f918edfb30
Submitter: "Zuul (22348)"
Branch: r/stx.5.0

commit 12f7ea91efb79aee858b3101223081f918edfb30
Author: Bin Qian <email address hidden>
Date: Fri May 7 16:36:23 2021 -0400

    Fix no swact for failure of critical services

    This fix is to ensure keeping service failure counting over successful
    audit.

    When service enabled audit successfully completes, SM reset the service
    failure state. However it should not reset the service fail-count.
    The fail-count should only be reset after the grace period.

    Closes-Bug: 1893669
    Change-Id: I6996fe3f1c08c38da6f26243aee2b95b083069f0
    Signed-off-by: Bin Qian <email address hidden>
    (cherry picked from commit 9f70df63fd0d83bf0f94d1b9ac2f98516d5971c8)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ha (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/ha/+/792251

Revision history for this message
Ghada Khalil (gkhalil) wrote :

Most recent commit has merged in the r/stx.5.0 release branch

tags: added: in-r-stx50
removed: stx.cherrypickneeded
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/config/+/793460

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/config/+/793696

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ha (f/centos8)
Download full text (20.2 KiB)

Reviewed: https://review.opendev.org/c/starlingx/ha/+/792251
Committed: https://opendev.org/starlingx/ha/commit/85bab5d2b394114feabe524504339a55eb8904e0
Submitter: "Zuul (22348)"
Branch: f/centos8

commit 9f70df63fd0d83bf0f94d1b9ac2f98516d5971c8
Author: Bin Qian <email address hidden>
Date: Fri May 7 16:36:23 2021 -0400

    Fix no swact for failure of critical services

    This fix is to ensure keeping service failure counting over successful
    audit.

    When service enabled audit successfully completes, SM reset the service
    failure state. However it should not reset the service fail-count.
    The fail-count should only be reset after the grace period.

    Closes-Bug: 1893669
    Change-Id: I6996fe3f1c08c38da6f26243aee2b95b083069f0
    Signed-off-by: Bin Qian <email address hidden>

commit 0b99b594f83b7c626cc0c4f7dc970ce373a7b748
Author: Bin Qian <email address hidden>
Date: Tue May 4 11:33:43 2021 -0400

    Fix AIO-DX failover issues

    This fix is to fix AIO unexpected failover behaviors.
    1. active controller reboots itself when standby controller
       reboot/lost power
    2. standby controller becomes degraded after active controller
       reboot/lost power

    Closes-bug: 1927133
    Change-Id: If3c9f6251f689a89cd206c672092ba296f00bd6b
    Signed-off-by: Bin Qian <email address hidden>

commit cb5fa9510f3ebda66f9850ac697e542bf041ce8c
Author: Eric MacDonald <email address hidden>
Date: Tue Apr 27 09:43:00 2021 -0400

    Remove hbsAgent restart in failover failure recovery handling

    A forced reboot of the active controller in an AIO DC system
    puts SM into a failover failure recovery loop that prevents
    maintenance from detecting the heartbeat failure of the just-
    rebooted controller.

    The SM's failover failure recovery handling algorithm includes
    a self (sm process) restart preceded by a restart of the
    hbsAgent, both added by the following update last year.

    update: Add unhealthy state recovery audit to service management (sm)
    review: https://review.opendev.org/c/starlingx/ha/+/735219

    The self restart of SM was and is required in this case. However,
    the restart of the hbsAgent was only included as a safety measure,
    at the time, to ensure SM received updated cluster state info. The
    hbsAgent restart was only added at that time with the longer term
    intention to have it removed once the hbsAgent cluster state change
    notification improvement was implemented. That change is now
    implemented and merged by the following update.

    update: Mtce heartbeat cluster state change notification improvement
    review: https://review.opendev.org/c/starlingx/metal/+/769936

    Testing of the fix for the following issue in an AIO DC system
    resulted in the takeover controller not detecting a heartbeat loss
    of the just rebooted standby controller.

    title: Force active controller reboot results in a second reboot
    issue: https://bugs.launchpad.net/starlingx/+bug/1922584

    The hbsAgent is not able to detect the heartbeat loss of the just-
    booted controller because SM keeps re...

tags: added: in-f-centos8
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/config/+/794611

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to stx-puppet (f/centos8)
Download full text (48.0 KiB)

Reviewed: https://review.opendev.org/c/starlingx/stx-puppet/+/792029
Committed: https://opendev.org/starlingx/stx-puppet/commit/2b026190a3cb6d561b6ec4a46dfb3add67f1fa69
Submitter: "Zuul (22348)"
Branch: f/centos8

commit 3e3940824dfb830ebd39fd93265b983c6a22fc51
Author: Dan Voiculeasa <email address hidden>
Date: Thu May 13 18:03:45 2021 +0300

    Enable kubelet support for pod pid limit

    Enable limiting the number of pids inside of pods.

    Add a default value to protect against a missing value.
    Default to 750 pids limit to align with service parameter default
    value for most resource consuming StarlingX optional app (openstack).
    In fact any value above service parameter minimum value is good for the
    default.

    Closes-Bug: 1928353
    Signed-off-by: Dan Voiculeasa <email address hidden>
    Change-Id: I10c1684fe3145e0a46b011f8e87f7a23557ddd4a

commit 0c16d288fbc483103b7ba5dad7782e97f59f4e17
Author: Jessica Castelino <email address hidden>
Date: Tue May 11 10:21:57 2021 -0400

    Safe restart of the etcd SM service in etcd upgrade runtime class

    While upgrading the central cloud of a DC system, activation failed
    because there was an unexpected SWACT to controller-1. This was due
    to the etcd upgrade script. Part of this script runs the etcd
    manifest. This triggers a reload/restart of the etcd service. As this
    is done outside of the sm, sm saw the process failure and triggered
    the SWACT.

    This commit modifies platform::etcd::upgrade::runtime puppet class
    to do a safe restart of the etcd SM service and thus, solve the
    issue.

    Change-Id: I3381b6976114c77ee96028d7d96a00302ad865ec
    Signed-off-by: Jessica Castelino <email address hidden>
    Closes-Bug: 1928135

commit eec3008f600aeeb69a42338ed44332228a862d11
Author: Mihnea Saracin <email address hidden>
Date: Mon May 10 13:09:52 2021 +0300

    Serialize updates to global_filter in the AIO manifest

    Right now, looking at the aio manifest:
    https://review.opendev.org/c/starlingx/stx-puppet/+/780600/15/puppet-manifests/src/manifests/aio.pp
    there are 3 classes that update
    in parallel the lvm global_filter:
    - include ::platform::lvm::controller
    - include ::platform::worker::storage
    - include ::platform::lvm::compute
    And this generates some errors.

    We fix this by adding dependencies between the above classes
    in order to update the global_filter in a serial mode.

    Closes-Bug: 1927762
    Signed-off-by: Mihnea Saracin <email address hidden>
    Change-Id: If6971e520454cdef41138b2f29998c036d8307ff

commit 97371409b9b2ae3f0db6a6a0acaeabd74927160e
Author: Steven Webster <email address hidden>
Date: Fri May 7 15:33:43 2021 -0400

    Add SR-IOV rate-limit dependency

    Currently, the binding of an SR-IOV virtual function (VF) to a
    driver has a dependency on platform::networking. This is needed
    to ensure that SR-IOV is enabled (VFs created) before actually
    doing the bind.

    This dependency does not exist for configuring the VF rate-limits
    however. There is a cha...

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (f/centos8)

Fix proposed to branch: f/centos8
Review: https://review.opendev.org/c/starlingx/config/+/794906

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on config (f/centos8)

Change abandoned by "Chuck Short <email address hidden>" on branch: f/centos8
Review: https://review.opendev.org/c/starlingx/config/+/794611

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (f/centos8)
Download full text (147.3 KiB)

Reviewed: https://review.opendev.org/c/starlingx/config/+/794906
Committed: https://opendev.org/starlingx/config/commit/75758b37a5a23c8811355b67e2a430a1713cd85b
Submitter: "Zuul (22348)"
Branch: f/centos8

commit 9e420d9513e5fafb1df4d29567bc299a9e04d58d
Author: Bin Qian <email address hidden>
Date: Mon May 31 14:45:52 2021 -0400

    Add more logging to run docker login

    Add error log for running docker login. The new log could
    help identify docker login failure.

    Closes-Bug: 1930310
    Change-Id: I8a709fb6665de8301fbe3022563499a92b2a0211
    Signed-off-by: Bin Qian <email address hidden>

commit 31c77439d2cea590dfcca13cfa646522665f8686
Author: albailey <email address hidden>
Date: Fri May 28 13:42:42 2021 -0500

    Fix controller-0 downgrade failing to kill ceph

    kill_ceph_storage_monitor tried to manipulate a pmon
    file that does not exist in an AIO-DX environment.

    We no longer invoke kill_ceph_storage_monitor in an
    AIO SX or DX env.

    This allows: "system host-downgrade controller-0"
    to proceed in an AIO-DX environment where that second
    controller (controller-0) was upgraded.

    Partial-Bug: 1929884
    Signed-off-by: albailey <email address hidden>
    Change-Id: I633853f75317736084feae96b5b849c601204c13

commit 0dc99eee608336fe01b58821ea404286371f1408
Author: albailey <email address hidden>
Date: Fri May 28 11:05:43 2021 -0500

    Fix file permissions failure during duplex upgrade abort

    When issuing a downgrade for controller-0 in a duplex upgrade
    abort and rollback scenario, the downgrade command was failing
    because the sysinv API does not have root permissions to set
    a file flag.
    The fix is to use RPC so the conductor can create the flag
    and allow the downgrade for controller-0 to get further.

    Partial-Bug: 1929884
    Signed-off-by: albailey <email address hidden>
    Change-Id: I913bcad73309fe887a12cbb016a518da93327947

commit 7ef3724dad173754e40b45538b1cc726a458cc1c
Author: Chen, Haochuan Z <email address hidden>
Date: Tue May 25 16:16:29 2021 +0800

    Fix bug rook-ceph provision with multi osd on one host

    Test case:
    1, deploy simplex system
    2, apply rook-ceph with below override value
    value.yaml
    cluster:
      storage:
        nodes:
        - name: controller-0
          devices:
          - name: sdb
          - name: sdc
    3, reboot

    Without this fix, only osd pod could launch successfully after boot
    as vg start with ceph could not correctly add in sysinv-database

    Closes-bug: 1929511

    Change-Id: Ia5be599cd168d13d2aab7b5e5890376c3c8a0019
    Signed-off-by: Chen, Haochuan Z <email address hidden>

commit 23505ba77d76114cf8a0bf833f9a5bcd05bc1dd1
Author: Angie Wang <email address hidden>
Date: Tue May 25 18:49:21 2021 -0400

    Fix issue in partition data migration script

    The created partition dictonary partition_map is not
    an ordered dict so we need to sort it by its key -
    device node when iterating it to adjust the device
    nodes/paths for user created extra partitions to ensure
    the number of device node...

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on config (f/centos8)

Change abandoned by "Chuck Short <email address hidden>" on branch: f/centos8
Review: https://review.opendev.org/c/starlingx/config/+/793696

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by "Chuck Short <email address hidden>" on branch: f/centos8
Review: https://review.opendev.org/c/starlingx/config/+/793460

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.