[Starlingx-discuss] stx-openstack application applying failed
Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status *osh-openstack-garbd-garbd-7d4957d9f4-kz95v * is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/ describe nodes http://paste.openstack.org/show/805589/ Regards, Danishka
Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra <openinfradn@gmail.com> Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$> describe nodes http://paste.openstack.org/show/805589/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$> Regards, Danishka
thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack? for controllers: system host-label-assign $NODE openstack-control-plane=enabled For worker nodes: system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled Because these labels are not visible in the release 5 installation guide. On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote:
Hi again Danishka, we discussed this too.
It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on.
Thanks, Bill...
*From:* open infra <openinfradn@gmail.com> *Sent:* Saturday, May 22, 2021 2:28 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] stx-openstack application applying failed
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hi,
I have deployed StarlingX R4 (bare metal dedicated storage installation).
stx-openstack application applying was failed.
When I retrieve openstack pods, I can see the status *osh-openstack-garbd-garbd-7d4957d9f4-kz95v *is pending.
I have re-uploaded stx-openstack but the same results.
I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week.
More details available here.
describe pod osh-openstack-garbd-garbd
http://paste.openstack.org/show/805587/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$>
describe nodes http://paste.openstack.org/show/805589/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$>
Regards,
Danishka
Here is more information about the issue. http://paste.openstack.org/show/806872/ Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%. I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network. On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com> wrote:
thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack?
for controllers:
system host-label-assign $NODE openstack-control-plane=enabled
For worker nodes:
system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled
Because these labels are not visible in the release 5 installation guide.
On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote:
Hi again Danishka, we discussed this too.
It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on.
Thanks, Bill...
*From:* open infra <openinfradn@gmail.com> *Sent:* Saturday, May 22, 2021 2:28 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] stx-openstack application applying failed
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hi,
I have deployed StarlingX R4 (bare metal dedicated storage installation).
stx-openstack application applying was failed.
When I retrieve openstack pods, I can see the status *osh-openstack-garbd-garbd-7d4957d9f4-kz95v *is pending.
I have re-uploaded stx-openstack but the same results.
I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week.
More details available here.
describe pod osh-openstack-garbd-garbd
http://paste.openstack.org/show/805587/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$>
describe nodes http://paste.openstack.org/show/805589/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$>
Regards,
Danishka
I managed to deploy stx-monitoring that require labelling only in controller nodes. Definitely something wrong with worker-0 labelling On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com> wrote:
Here is more information about the issue. http://paste.openstack.org/show/806872/
Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%.
I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network.
On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com> wrote:
thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack?
for controllers:
system host-label-assign $NODE openstack-control-plane=enabled
For worker nodes:
system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled
Because these labels are not visible in the release 5 installation guide.
On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote:
Hi again Danishka, we discussed this too.
It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on.
Thanks, Bill...
*From:* open infra <openinfradn@gmail.com> *Sent:* Saturday, May 22, 2021 2:28 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] stx-openstack application applying failed
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hi,
I have deployed StarlingX R4 (bare metal dedicated storage installation).
stx-openstack application applying was failed.
When I retrieve openstack pods, I can see the status *osh-openstack-garbd-garbd-7d4957d9f4-kz95v *is pending.
I have re-uploaded stx-openstack but the same results.
I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week.
More details available here.
describe pod osh-openstack-garbd-garbd
http://paste.openstack.org/show/805587/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$>
describe nodes http://paste.openstack.org/show/805589/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$>
Regards,
Danishka
Finally managed to deploy OpenStack but not sure what caused the issue. Increased disk capacity for docker in worker and reviewed network. On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com> wrote:
I managed to deploy stx-monitoring that require labelling only in controller nodes. Definitely something wrong with worker-0 labelling
On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com> wrote:
Here is more information about the issue. http://paste.openstack.org/show/806872/
Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%.
I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network.
On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com> wrote:
thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack?
for controllers:
system host-label-assign $NODE openstack-control-plane=enabled
For worker nodes:
system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled
Because these labels are not visible in the release 5 installation guide.
On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote:
Hi again Danishka, we discussed this too.
It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on.
Thanks, Bill...
*From:* open infra <openinfradn@gmail.com> *Sent:* Saturday, May 22, 2021 2:28 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] stx-openstack application applying failed
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hi,
I have deployed StarlingX R4 (bare metal dedicated storage installation).
stx-openstack application applying was failed.
When I retrieve openstack pods, I can see the status *osh-openstack-garbd-garbd-7d4957d9f4-kz95v *is pending.
I have re-uploaded stx-openstack but the same results.
I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week.
More details available here.
describe pod osh-openstack-garbd-garbd
http://paste.openstack.org/show/805587/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$>
describe nodes http://paste.openstack.org/show/805589/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$>
Regards,
Danishka
Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size. We have plans to fix this. Greg. From: open infra <openinfradn@gmail.com> Sent: Friday, June 25, 2021 10:30 AM To: Zvonar, Bill <Bill.Zvonar@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Finally managed to deploy OpenStack but not sure what caused the issue. Increased disk capacity for docker in worker and reviewed network. On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: I managed to deploy stx-monitoring that require labelling only in controller nodes. Definitely something wrong with worker-0 labelling On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: Here is more information about the issue. http://paste.openstack.org/show/806872/<https://urldefense.com/v3/__http:/paste.openstack.org/show/806872/__;!!AjveYdw8EvQ!IqDey86XgSsb-XFryEq6evajkKBtzO0iqfvrTOhcD3HlCvV9FgK4c5QV8wSfkRJp74Y$> Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%. I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network. On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack? for controllers: system host-label-assign $NODE openstack-control-plane=enabled For worker nodes: system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled Because these labels are not visible in the release 5 installation guide. On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com<mailto:Bill.Zvonar@windriver.com>> wrote: Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$> describe nodes http://paste.openstack.org/show/805589/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$> Regards, Danishka
Hi Greg, Thanks for your reply. I was following Standard with Dedicated Storage and can't remember exact URL. I even did search for "system host-label-assign" but may I made a mistake while searching for labels, apologies for the inconvenience. I found stx-monitor when I was looking for performance and usage monitoring and ended up with StarlingX training slide set. Regards, Danishka On Sat, Jun 26, 2021 at 6:47 PM Waines, Greg <Greg.Waines@windriver.com> wrote:
Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size. We have plans to fix this.
Greg.
*From:* open infra <openinfradn@gmail.com> *Sent:* Friday, June 25, 2021 10:30 AM *To:* Zvonar, Bill <Bill.Zvonar@windriver.com> *Cc:* starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] stx-openstack application applying failed
[Please note: This e-mail is from an EXTERNAL e-mail address]
Finally managed to deploy OpenStack but not sure what caused the issue.
Increased disk capacity for docker in worker and reviewed network.
On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com> wrote:
I managed to deploy stx-monitoring that require labelling only in controller nodes.
Definitely something wrong with worker-0 labelling
On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com> wrote:
Here is more information about the issue.
http://paste.openstack.org/show/806872/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/806872/__;!!AjveYdw8EvQ!IqDey86XgSsb-XFryEq6evajkKBtzO0iqfvrTOhcD3HlCvV9FgK4c5QV8wSfkRJp74Y$>
Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test).
Then stx-openstack applying progress continued up to 55%.
I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network.
On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com> wrote:
thank you Bill and Thiago.
Now I have switched to Release 5.
Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack?
for controllers:
system host-label-assign $NODE openstack-control-plane=enabled
For worker nodes:
system host-label-assign $NODE openstack-compute-node=enabled
system host-label-assign $NODE openvswitch=enabled
Because these labels are not visible in the release 5 installation guide.
On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote:
Hi again Danishka, we discussed this too.
It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on.
Thanks, Bill...
*From:* open infra <openinfradn@gmail.com> *Sent:* Saturday, May 22, 2021 2:28 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] stx-openstack application applying failed
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hi,
I have deployed StarlingX R4 (bare metal dedicated storage installation).
stx-openstack application applying was failed.
When I retrieve openstack pods, I can see the status *osh-openstack-garbd-garbd-7d4957d9f4-kz95v *is pending.
I have re-uploaded stx-openstack but the same results.
I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week.
More details available here.
describe pod osh-openstack-garbd-garbd
http://paste.openstack.org/show/805587/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$>
describe nodes http://paste.openstack.org/show/805589/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$>
Regards,
Danishka
On Saturday 26 June 2021 20:17:36 PM (+07:00), Waines, Greg wrote: Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size. We have plans to fix this. Yupp seems this is exactly what i need also right now, as im running into the system host-fs-modify controller-0 docker=60 HostFs update failed: Not enough free space on cgts-vg. Current free space 16 GiB, requested total increase 30 GiB Greg. From: open infra <openinfradn@gmail.com> Sent: Friday, June 25, 2021 10:30 AM To: Zvonar, Bill <Bill.Zvonar@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Finally managed to deploy OpenStack but not sure what caused the issue. Increased disk capacity for docker in worker and reviewed network. On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com> wrote: I managed to deploy stx-monitoring that require labelling only in controller nodes. Definitely something wrong with worker-0 labelling On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com> wrote: Here is more information about the issue. http://paste.openstack.org/show/806872/ Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%. I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network. On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com> wrote: thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack? for controllers: system host-label-assign $NODE openstack-control-plane=enabled For worker nodes: system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled Because these labels are not visible in the release 5 installation guide. On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote: Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra <openinfradn@gmail.com> Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/ describe nodes http://paste.openstack.org/show/805589/ Regards, Danishka -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
On Sun, Jun 27, 2021 at 4:48 PM Embedded Devel <lists@optimcloud.com> wrote:
On Saturday 26 June 2021 20:17:36 PM (+07:00), Waines, Greg wrote:
Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size. We have plans to fix this.
Yupp seems this is exactly what i need also right now, as im running into the
system host-fs-modify controller-0 docker=60 HostFs update failed: Not enough free space on cgts-vg. Current free space 16 GiB, requested total increase 30 GiB
Please check if you have enough space (either disk or partitions) available and if so, you can extend the logical volume. I have used both methods (GUI and CLI).
Greg.
*From:* open infra <openinfradn@gmail.com> *Sent:* Friday, June 25, 2021 10:30 AM *To:* Zvonar, Bill <Bill.Zvonar@windriver.com> *Cc:* starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] stx-openstack application applying failed
[Please note: This e-mail is from an EXTERNAL e-mail address]
Finally managed to deploy OpenStack but not sure what caused the issue.
Increased disk capacity for docker in worker and reviewed network.
On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com> wrote:
I managed to deploy stx-monitoring that require labelling only in controller nodes.
Definitely something wrong with worker-0 labelling
On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com> wrote:
Here is more information about the issue.
http://paste.openstack.org/show/806872/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/806872/__;!!AjveYdw8EvQ!IqDey86XgSsb-XFryEq6evajkKBtzO0iqfvrTOhcD3HlCvV9FgK4c5QV8wSfkRJp74Y$>
Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test).
Then stx-openstack applying progress continued up to 55%.
I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network.
On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com> wrote:
thank you Bill and Thiago.
Now I have switched to Release 5.
Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack?
for controllers:
system host-label-assign $NODE openstack-control-plane=enabled
For worker nodes:
system host-label-assign $NODE openstack-compute-node=enabled
system host-label-assign $NODE openvswitch=enabled
Because these labels are not visible in the release 5 installation guide.
On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote:
Hi again Danishka, we discussed this too.
It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on.
Thanks, Bill...
*From:* open infra <openinfradn@gmail.com> *Sent:* Saturday, May 22, 2021 2:28 AM *To:* starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] stx-openstack application applying failed
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hi,
I have deployed StarlingX R4 (bare metal dedicated storage installation).
stx-openstack application applying was failed.
When I retrieve openstack pods, I can see the status *osh-openstack-garbd-garbd-7d4957d9f4-kz95v *is pending.
I have re-uploaded stx-openstack but the same results.
I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week.
More details available here.
describe pod osh-openstack-garbd-garbd
http://paste.openstack.org/show/805587/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$>
describe nodes http://paste.openstack.org/show/805589/ <https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$>
Regards,
Danishka
-- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
On Monday 28 June 2021 12:52:04 PM (+07:00), open infra wrote: On Sun, Jun 27, 2021 at 4:48 PM Embedded Devel <lists@optimcloud.com> wrote: On Saturday 26 June 2021 20:17:36 PM (+07:00), Waines, Greg wrote: Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size. We have plans to fix this. Yupp seems this is exactly what i need also right now, as im running into the system host-fs-modify controller-0 docker=60 HostFs update failed: Not enough free space on cgts-vg. Current free space 16 GiB, requested total increase 30 GiB Please check if you have enough space (either disk or partitions) available and if so, you can extend the logical volume. I have used both methods (GUI and CLI). yeah im aware of what to do, question is where the doc with the resize commands that i had to do the same for on the last cluster i built. [ 1.626293] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) controller-0:~# pvdisplay --- Physical volume --- PV Name /dev/sda6 VG Name nova-local PV Size 34.00 GiB / not usable 4.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 8703 Free PE 0 Allocated PE 8703 PV UUID H4XSXd-6nbV-UVML-5UzC-CBRW-Nibt-XcqqYh --- Physical volume --- PV Name /dev/sda5 VG Name cgts-vg PV Size 179.00 GiB / not usable 32.00 MiB Allocatable yes PE Size 32.00 MiB Total PE 5727 Free PE 517 Allocated PE 5210 PV UUID EuOPqF-b3vF-L8cu-ULB5-40Q0-g0W9-07N5lW controller-0:~# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 16G 0 16G 0% /dev tmpfs 16G 212K 16G 1% /dev/shm tmpfs 16G 13M 16G 1% /run tmpfs 16G 0 16G 0% /sys/fs/cgroup /dev/sda4 20G 8.0G 11G 44% / tmpfs 1.0G 112K 1.0G 1% /tmp /dev/mapper/cgts--vg-backup--lv 25G 45M 24G 1% /opt/backups /dev/mapper/cgts--vg-scratch--lv 16G 69M 15G 1% /scratch /dev/mapper/cgts--vg-ceph--mon--lv 20G 95M 19G 1% /var/lib/ceph/mon /dev/sda1 9.5G 37M 9.0G 1% /opt/platform-backup /dev/sda3 477M 106M 343M 24% /boot /dev/mapper/cgts--vg-docker--lv 30G 22G 8.6G 72% /var/lib/docker /dev/sda2 300M 11M 290M 4% /boot/efi /dev/mapper/cgts--vg-kubelet--lv 9.8G 38M 9.2G 1% /var/lib/kubelet /dev/mapper/cgts--vg-log--lv 7.6G 230M 7.0G 4% /var/log
Here is what you need to do … we will update this in docs. Greg. # Increase size of cgts-vg LVG in order to increase size of docker fs export NODE=controller-1 ROOT_DISK=$(system host-show ${NODE} | grep rootfs | awk '{print $4}') ROOT_DISK_UUID=$(system host-disk-list ${NODE} --nowrap | grep ${ROOT_DISK} | awk '{print $2}') NEW_SIZE=35 NEW_PARTITION=$(system host-disk-partition-add -t lvm_phys_vol ${NODE} ${ROOT_DISK_UUID} ${NEW_SIZE}) NEW_PARTITION_UUID=$(echo ${NEW_PARTITION} | grep -ow "| uuid | [a-z0-9\-]* |" | awk '{print $4}') system host-pv-add ${NODE} cgts-vg ${NEW_PARTITION_UUID} system host-fs-modify controller-1 docker=60 From: Embedded Devel <lists@optimcloud.com> Sent: Sunday, June 27, 2021 7:18 AM To: Waines, Greg <Greg.Waines@windriver.com>; open infra <openinfradn@gmail.com>; Zvonar, Bill <Bill.Zvonar@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] On Saturday 26 June 2021 20:17:36 PM (+07:00), Waines, Greg wrote: Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size. We have plans to fix this. Yupp seems this is exactly what i need also right now, as im running into the system host-fs-modify controller-0 docker=60 HostFs update failed: Not enough free space on cgts-vg. Current free space 16 GiB, requested total increase 30 GiB Greg. From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Friday, June 25, 2021 10:30 AM To: Zvonar, Bill <Bill.Zvonar@windriver.com<mailto:Bill.Zvonar@windriver.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Finally managed to deploy OpenStack but not sure what caused the issue. Increased disk capacity for docker in worker and reviewed network. On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: I managed to deploy stx-monitoring that require labelling only in controller nodes. Definitely something wrong with worker-0 labelling On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: Here is more information about the issue. http://paste.openstack.org/show/806872/<https://urldefense.com/v3/__http:/paste.openstack.org/show/806872/__;!!AjveYdw8EvQ!IqDey86XgSsb-XFryEq6evajkKBtzO0iqfvrTOhcD3HlCvV9FgK4c5QV8wSfkRJp74Y$> Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%. I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network. On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack? for controllers: system host-label-assign $NODE openstack-control-plane=enabled For worker nodes: system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled Because these labels are not visible in the release 5 installation guide. On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com<mailto:Bill.Zvonar@windriver.com>> wrote: Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$> describe nodes http://paste.openstack.org/show/805589/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$> Regards, Danishka -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com<https://urldefense.com/v3/__http:/vivaldi.com__;!!AjveYdw8EvQ!Kbxgv5BsZhAoZvkbltiAc5Pyqy-5iUhxTbLCvA6Vwg6BAWOrtRaJKjf6dMwe9HeLzaE$>
On Monday 28 June 2021 19:06:17 PM (+07:00), Waines, Greg wrote: Here is what you need to do … we will update this in docs. Greg. # Increase size of cgts-vg LVG in order to increase size of docker fs export NODE=controller-1 ROOT_DISK=$(system host-show ${NODE} | grep rootfs | awk '{print $4}') ROOT_DISK_UUID=$(system host-disk-list ${NODE} --nowrap | grep ${ROOT_DISK} | awk '{print $2}') NEW_SIZE=35 NEW_PARTITION=$(system host-disk-partition-add -t lvm_phys_vol ${NODE} ${ROOT_DISK_UUID} ${NEW_SIZE}) NEW_PARTITION_UUID=$(echo ${NEW_PARTITION} | grep -ow "| uuid | [a-z0-9\-]* |" | awk '{print $4}') system host-pv-add ${NODE} cgts-vg ${NEW_PARTITION_UUID} system host-fs-modify controller-1 docker=60 ROOT_DISK=$(system host-show ${NODE} | grep rootfs | awk '{print $4}') fails on my stx 5.0 simplex [sysadmin@controller-0 ~(keystone_admin)]$ system host-show ${NODE} +-----------------------+----------------------------------------------------------------------+ | Property | Value | +-----------------------+----------------------------------------------------------------------+ | action | none | | administrative | unlocked | | availability | available | | bm_ip | None | | bm_type | none | | bm_username | None | | boot_device | /dev/disk/by-path/pci-0000:00:17.0-ata-1.0 | | capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Active'} | | clock_synchronization | ntp | | config_applied | 65c1c5ac-546a-45fc-8d82-e9644f1930a2 | | config_status | None | | config_target | 65c1c5ac-546a-45fc-8d82-e9644f1930a2 | | console | tty0 | | created_at | 2021-06-26T10:51:25.595104+00:00 | | device_image_update | None | | hostname | controller-0 | | id | 1 | | install_output | text | | install_state | None | | install_state_info | None | | inv_state | inventoried | | invprovision | provisioned | | location | {} | | mgmt_ip | 192.168.204.2 | | mgmt_mac | 00:00:00:00:00:00 | | operational | enabled | | personality | controller | | reboot_needed | False | | reserved | False | | rootfs_device | /dev/disk/by-path/pci-0000:00:17.0-ata-1.0 | | serialid | None | | software_load | 21.05 | | subfunction_avail | available | | subfunction_oper | enabled | | subfunctions | controller,worker | | task | | | tboot | false | | ttys_dcd | None | | updated_at | 2021-06-28T12:13:20.119581+00:00 | | uptime | 15240 | | uuid | 2b237d4f-fc3d-4f83-bdf2-b2689469b89e | | vim_progress_status | services-enabled | +-----------------------+----------------------------------------------------------------------+ From: Embedded Devel <lists@optimcloud.com> Sent: Sunday, June 27, 2021 7:18 AM To: Waines, Greg <Greg.Waines@windriver.com>; open infra <openinfradn@gmail.com>; Zvonar, Bill <Bill.Zvonar@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] On Saturday 26 June 2021 20:17:36 PM (+07:00), Waines, Greg wrote: Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size. We have plans to fix this. Yupp seems this is exactly what i need also right now, as im running into the system host-fs-modify controller-0 docker=60 HostFs update failed: Not enough free space on cgts-vg. Current free space 16 GiB, requested total increase 30 GiB Greg. From: open infra <openinfradn@gmail.com> Sent: Friday, June 25, 2021 10:30 AM To: Zvonar, Bill <Bill.Zvonar@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Finally managed to deploy OpenStack but not sure what caused the issue. Increased disk capacity for docker in worker and reviewed network. On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com> wrote: I managed to deploy stx-monitoring that require labelling only in controller nodes. Definitely something wrong with worker-0 labelling On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com> wrote: Here is more information about the issue. http://paste.openstack.org/show/806872/ Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%. I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network. On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com> wrote: thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack? for controllers: system host-label-assign $NODE openstack-control-plane=enabled For worker nodes: system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled Because these labels are not visible in the release 5 installation guide. On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com> wrote: Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra <openinfradn@gmail.com> Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/ describe nodes http://paste.openstack.org/show/805589/ Regards, Danishka -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
when I cut & paste your output into grep rootfs | awk ‘{print $4}’ I get /dev/disk/by-path/pci-0000:00:17.0-ata-1.0 the command is basically setting ROOT_DISK to rootfs_device Greg. From: Embedded Devel <lists@optimcloud.com> Sent: Monday, June 28, 2021 8:15 AM To: Waines, Greg <Greg.Waines@windriver.com>; open infra <openinfradn@gmail.com>; Zvonar, Bill <Bill.Zvonar@windriver.com> Cc: starlingx-discuss@lists.starlingx.io; Camp, MaryX <maryx.camp@intel.com> Subject: Re: RE: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] On Monday 28 June 2021 19:06:17 PM (+07:00), Waines, Greg wrote: Here is what you need to do … we will update this in docs. Greg. # Increase size of cgts-vg LVG in order to increase size of docker fs export NODE=controller-1 ROOT_DISK=$(system host-show ${NODE} | grep rootfs | awk '{print $4}') ROOT_DISK_UUID=$(system host-disk-list ${NODE} --nowrap | grep ${ROOT_DISK} | awk '{print $2}') NEW_SIZE=35 NEW_PARTITION=$(system host-disk-partition-add -t lvm_phys_vol ${NODE} ${ROOT_DISK_UUID} ${NEW_SIZE}) NEW_PARTITION_UUID=$(echo ${NEW_PARTITION} | grep -ow "| uuid | [a-z0-9\-]* |" | awk '{print $4}') system host-pv-add ${NODE} cgts-vg ${NEW_PARTITION_UUID} system host-fs-modify controller-1 docker=60 ROOT_DISK=$(system host-show ${NODE} | grep rootfs | awk '{print $4}') fails on my stx 5.0 simplex [sysadmin@controller-0 ~(keystone_admin)]$ system host-show ${NODE} +-----------------------+----------------------------------------------------------------------+ | Property | Value | +-----------------------+----------------------------------------------------------------------+ | action | none | | administrative | unlocked | | availability | available | | bm_ip | None | | bm_type | none | | bm_username | None | | boot_device | /dev/disk/by-path/pci-0000:00:17.0-ata-1.0 | | capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Active'} | | clock_synchronization | ntp | | config_applied | 65c1c5ac-546a-45fc-8d82-e9644f1930a2 | | config_status | None | | config_target | 65c1c5ac-546a-45fc-8d82-e9644f1930a2 | | console | tty0 | | created_at | 2021-06-26T10:51:25.595104+00:00 | | device_image_update | None | | hostname | controller-0 | | id | 1 | | install_output | text | | install_state | None | | install_state_info | None | | inv_state | inventoried | | invprovision | provisioned | | location | {} | | mgmt_ip | 192.168.204.2 | | mgmt_mac | 00:00:00:00:00:00 | | operational | enabled | | personality | controller | | reboot_needed | False | | reserved | False | | rootfs_device | /dev/disk/by-path/pci-0000:00:17.0-ata-1.0 | | serialid | None | | software_load | 21.05 | | subfunction_avail | available | | subfunction_oper | enabled | | subfunctions | controller,worker | | task | | | tboot | false | | ttys_dcd | None | | updated_at | 2021-06-28T12:13:20.119581+00:00 | | uptime | 15240 | | uuid | 2b237d4f-fc3d-4f83-bdf2-b2689469b89e | | vim_progress_status | services-enabled | +-----------------------+----------------------------------------------------------------------+ From: Embedded Devel <lists@optimcloud.com<mailto:lists@optimcloud.com>> Sent: Sunday, June 27, 2021 7:18 AM To: Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>>; open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>>; Zvonar, Bill <Bill.Zvonar@windriver.com<mailto:Bill.Zvonar@windriver.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] On Saturday 26 June 2021 20:17:36 PM (+07:00), Waines, Greg wrote: Agreed that increased docker fs is not documented well … especially if you need to increase the cgts_vg logical volume group in order to increase the docker filesystem size. We have plans to fix this. Yupp seems this is exactly what i need also right now, as im running into the system host-fs-modify controller-0 docker=60 HostFs update failed: Not enough free space on cgts-vg. Current free space 16 GiB, requested total increase 30 GiB Greg. From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Friday, June 25, 2021 10:30 AM To: Zvonar, Bill <Bill.Zvonar@windriver.com<mailto:Bill.Zvonar@windriver.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Finally managed to deploy OpenStack but not sure what caused the issue. Increased disk capacity for docker in worker and reviewed network. On Thu, Jun 24, 2021 at 1:59 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: I managed to deploy stx-monitoring that require labelling only in controller nodes. Definitely something wrong with worker-0 labelling On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: Here is more information about the issue. http://paste.openstack.org/show/806872/<https://urldefense.com/v3/__http:/paste.openstack.org/show/806872/__;!!AjveYdw8EvQ!IqDey86XgSsb-XFryEq6evajkKBtzO0iqfvrTOhcD3HlCvV9FgK4c5QV8wSfkRJp74Y$> Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%. I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network. On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack? for controllers: system host-label-assign $NODE openstack-control-plane=enabled For worker nodes: system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled Because these labels are not visible in the release 5 installation guide. On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com<mailto:Bill.Zvonar@windriver.com>> wrote: Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$> describe nodes http://paste.openstack.org/show/805589/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$> Regards, Danishka -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com<https://urldefense.com/v3/__http:/vivaldi.com__;!!AjveYdw8EvQ!Kbxgv5BsZhAoZvkbltiAc5Pyqy-5iUhxTbLCvA6Vwg6BAWOrtRaJKjf6dMwe9HeLzaE$> -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com<https://urldefense.com/v3/__http:/vivaldi.com__;!!AjveYdw8EvQ!PJXeYXF3dUb3gTymFwQS4n1pTNbyEnCGKt_N1hVjTM58QJFinv8JkhACiyycLwXm6Hc$>
Which deployment type are you configuring ? and which install guide are you following ? Also where did you find documentation on stx-monitoring ? I don’t believe this is being maintained any longer. Greg. From: open infra <openinfradn@gmail.com> Sent: Thursday, June 24, 2021 4:29 AM To: Zvonar, Bill <Bill.Zvonar@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] I managed to deploy stx-monitoring that require labelling only in controller nodes. Definitely something wrong with worker-0 labelling On Wed, Jun 23, 2021 at 8:52 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: Here is more information about the issue. http://paste.openstack.org/show/806872/<https://urldefense.com/v3/__http:/paste.openstack.org/show/806872/__;!!AjveYdw8EvQ!M39BOsCm74rLt4pr88Td5EbvaBdr079k5uoEq1qHgw5D_oVBQ_sg3lQRFNPIyXYmRD4$> Then I set the openstack-compute-node label to the controller-0 and re-apply stx-openstack (just to test). Then stx-openstack applying progress continued up to 55%. I can lock/unlcok the worker-0 via controller nodes. So, it should not be a problem with management network. On Mon, Jun 21, 2021 at 4:40 PM open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> wrote: thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack? for controllers: system host-label-assign $NODE openstack-control-plane=enabled For worker nodes: system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled Because these labels are not visible in the release 5 installation guide. On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com<mailto:Bill.Zvonar@windriver.com>> wrote: Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$> describe nodes http://paste.openstack.org/show/805589/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$> Regards, Danishka
… just following up on comment that these labels are not visible in the release 5 installation guide. I checked the worker node section of the following guides, and it appears these labels are described there: * https://docs.starlingx.io/deploy_install_guides/r5_release/bare_metal/aio_du... * https://docs.starlingx.io/deploy_install_guides/r5_release/bare_metal/contro... * https://docs.starlingx.io/deploy_install_guides/r5_release/bare_metal/dedica... * https://docs.starlingx.io/deploy_install_guides/r5_release/virtual/controlle... * https://docs.starlingx.io/deploy_install_guides/r5_release/virtual/dedicated... Can you let us know which page you thought the labels were missing from ? Greg. From: open infra <openinfradn@gmail.com> Sent: Monday, June 21, 2021 7:11 AM To: Zvonar, Bill <Bill.Zvonar@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] thank you Bill and Thiago. Now I have switched to Release 5. Don't we need to set following labels for release 5 deployment if we supposed to deploy stx-openstack? for controllers: system host-label-assign $NODE openstack-control-plane=enabled For worker nodes: system host-label-assign $NODE openstack-compute-node=enabled system host-label-assign $NODE openvswitch=enabled Because these labels are not visible in the release 5 installation guide. On Wed, May 26, 2021 at 9:11 PM Zvonar, Bill <Bill.Zvonar@windriver.com<mailto:Bill.Zvonar@windriver.com>> wrote: Hi again Danishka, we discussed this too. It was suggested that you check /var/logs/armada to see if there are any Armada startup logs that’d help understand what’s going on. Thanks, Bill... From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Saturday, May 22, 2021 2:28 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] stx-openstack application applying failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have deployed StarlingX R4 (bare metal dedicated storage installation). stx-openstack application applying was failed. When I retrieve openstack pods, I can see the status osh-openstack-garbd-garbd-7d4957d9f4-kz95v is pending. I have re-uploaded stx-openstack but the same results. I highly appreciate it if someone can help to fix resolve this matter as we have a demo next week. More details available here. describe pod osh-openstack-garbd-garbd http://paste.openstack.org/show/805587/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805587/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFhtiucGoh$> describe nodes http://paste.openstack.org/show/805589/<https://urldefense.com/v3/__http:/paste.openstack.org/show/805589/__;!!AjveYdw8EvQ!IP_slcx9_D_pSzhjpom6niaG_xdFTyB63HZ2yV5p24SAYzk2f4dmWqMTpvLFht7VU1um$> Regards, Danishka
participants (4)
-
Embedded Devel
-
open infra
-
Waines, Greg
-
Zvonar, Bill