StarlingX

  1. Bug #1829403
  2. Comment #27

Comment 27 for bug 1829403

Revision history for this message
Abraham Arce (xe1gyq) wrote : Re: compute node keeps offline after unlock due to vswitch error

Ghada, I deployed according to the instructions from our current official Wiki Containers Dedicated Storage:
  https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandardStorage

I have executed the section "Configure the vswitch type (optional)" only in step 1, step 2 did not completed since I got confused due to reference for controller-0, for the full log of the deployment see same section"Configure the vswitch type (optional)" where my error is reflected, under:
  https://github.com/xe1gyq/starlingx/blob/master/deployment/baremetal/dedicatedstorage.md

Let me know if the following steps if a valid use case to allow the configuration of the compute-0 even if controller-0 has been unlocked:

  $ system host-lock compute-0
  $ system host-cpu-modify -f vswitch -p0 1 compute-0
  $ system host-unlock compute-0

If the above is not a valid use case, should it be tested with a new deployment?
I am taking this learning to reflect those changes in our docs.starlingx.io site.