<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 2, 2020 at 3:59 PM Ruslanas Gžibovskis <<a href="mailto:ruslanas@lpic.lt">ruslanas@lpic.lt</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">by the way in CentOS8, here is an error message I receive when searching around<div><br></div><div>[stack@rdo-u ~]$ dnf list --enablerepo="*" --disablerepo "c8-media-BaseOS,c8-media-AppStream" | grep osops-tools-monitoring-oschecks<br>Errors during downloading metadata for repository 'rdo-trunk-ussuri-tested':<br> - Status code: 403 for <a href="https://trunk.rdoproject.org/centos8-ussuri/current-passed-ci/repodata/repomd.xml" target="_blank">https://trunk.rdoproject.org/centos8-ussuri/current-passed-ci/repodata/repomd.xml</a> (IP: 3.87.151.16)<br>Error: Failed to download metadata for repo 'rdo-trunk-ussuri-tested': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried<br>[stack@rdo-u ~]$ <br></div></div><br></blockquote><div><br></div><div>Yep, rdo-trunk-ussuri-tested repo included in the release rpm is disabled by default and not longer usable (i'll send a patch to retire it), don't enable it.</div><div><br></div><div>Sorry, I'm not sure how adding osops-tools-monitoring-oschecks may lead to install CentOS8 maintained kvm. BTW, i think that package should not be required in CentOS8:</div><div><br></div><div><a href="https://opendev.org/openstack/tripleo-puppet-elements/commit/2d2bc4d8b20304d0939ac0cebedac7bda3398def">https://opendev.org/openstack/tripleo-puppet-elements/commit/2d2bc4d8b20304d0939ac0cebedac7bda3398def</a></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 2 Jul 2020 at 15:56, Ruslanas Gžibovskis <<a href="mailto:ruslanas@lpic.lt" target="_blank">ruslanas@lpic.lt</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div>I have one idea, why it might be the issue.</div><div><br></div><div>during image creation step, I have hadd missing packets:</div><div>pacemaker-remote osops-tools-monitoring-oschecks pacemaker pcs<br></div><div>PCS thing can be found in HA repo, so I enabled it, but "osops-tools-monitoring-oschecks" ONLY in delorene for CentOS8...</div><div><br></div><div>I believe that is a case...</div><div>so it installed non CentOS8 maintained kvm or some dependent packages....</div><div><br></div><div>How can I get
osops-tools-monitoring-oschecks from centos repos? it is last seen in CentOS7 repos....</div><div><br></div><div>$ yum list --enablerepo=* --disablerepo "c7-media" | grep osops-tools-monitoring-oschecks -A2<br>osops-tools-monitoring-oschecks.noarch 0.0.1-0.20191202171903.bafe3f0.el7<br> rdo-trunk-train-tested<br>ostree-debuginfo.x86_64 2019.1-2.el7 base-debuginfo<br>(undercloud) [stack@ironic-poc ~]$ <br></div><div><br></div><div>can I somehow not include that package in image creation? OR if it is essential, can I create a different repo for that one?</div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 1 Jul 2020 at 14:19, Ruslanas Gžibovskis <<a href="mailto:ruslanas@lpic.lt" target="_blank">ruslanas@lpic.lt</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi all!<div><br></div><div>Here we go, we are in the second part of this interesting troubleshooting!</div><div><br></div><div>1) I have LogTool setup.Thank you Arkady.</div><div><br></div><div>2) I have user OSP to create instance, and I have used virsh to create instance.</div><div>2.1) OSP way is failing in either way, if it is volume-based or image-based, it is failing either way.. [1] and [2]</div><div>2.2) when I create it using CLI: [0] [3]</div><div><br></div><div>any ideas what can be wrong? What options I should choose?</div><div>I have one network/vlan for whole cloud. I am doing proof of concept of remote booting, so I do not have br-ex setup. and I do not have br-provider.</div><div><br></div><div>There is my compute[5] and controller[6] yaml files, Please help, how it should look like so it would have br-ex and br-int connected? as br-int now is in UNKNOWN state. And br-ex do not exist.</div><div>As I understand, in roles data yaml, when we have tag external it should create br-ex? or am I wrong?</div><div><br></div><div>[0] <a href="http://paste.openstack.org/show/Rdou7nvEWMxpGECfQHVm/" target="_blank">http://paste.openstack.org/show/Rdou7nvEWMxpGECfQHVm/</a> VM is running.<br></div><div>[1] <a href="http://paste.openstack.org/show/tp8P0NUYNFcl4E0QR9IM/" target="_blank">http://paste.openstack.org/show/tp8P0NUYNFcl4E0QR9IM/</a> < compute logs</div><div>[2] <a href="http://paste.openstack.org/show/795431/" target="_blank">http://paste.openstack.org/show/795431/</a> < controller logs<br></div></div>[3] <a href="http://paste.openstack.org/show/HExQgBo4MDxItAEPNaRR/" target="_blank">http://paste.openstack.org/show/HExQgBo4MDxItAEPNaRR/</a> <div>[4] <a href="http://paste.openstack.org/show/795433/" target="_blank">http://paste.openstack.org/show/795433/</a> < xml file for </div><div>[5] <a href="https://github.com/qw3r3wq/homelab/blob/master/overcloud/net-config/computeS01.yaml" target="_blank">https://github.com/qw3r3wq/homelab/blob/master/overcloud/net-config/computeS01.yaml</a></div><div>[6] <a href="https://github.com/qw3r3wq/homelab/blob/master/overcloud/net-config/controller.yaml" target="_blank">https://github.com/qw3r3wq/homelab/blob/master/overcloud/net-config/controller.yaml</a></div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 30 Jun 2020 at 16:02, Arkady Shtempler <<a href="mailto:ashtempl@redhat.com" target="_blank">ashtempl@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi all!</div><div><br></div><div>I was able to analyze the attached log files and I hope that the results may help you understand what's going wrong with instance creation.</div><div>You can find <b><i>Log_Tool's unique exported Error blocks</i></b> here: <a href="http://paste.openstack.org/show/795356/" target="_blank">http://paste.openstack.org/show/795356/</a></div><div><br></div><div><b><u>Some statistics and problematical messages:</u></b></div><div><span style="color:rgb(0,0,255)">##### Statistics - Number of Errors/Warnings per Standard OSP log since: 2020-06-30 12:30:00 #####</span><br></div><div><font color="#0000ff">Total_Number_Of_Errors --> 9<br>/home/ashtempl/Ruslanas/controller/neutron/server.log --> 1<br>/home/ashtempl/Ruslanas/compute/stdouts/ovn_controller.log --> 1<br>/home/ashtempl/Ruslanas/compute/nova/nova-compute.log --> 7</font><br><br></div><div><b>nova-compute.log</b><br></div><div><font color="#ff0000"><b>default default] Error launching a defined domain with XML: <domain type='kvm'></b><br></font></div><div><font color="#ff0000">368-2020-06-30 12:30:10.815 7 <b>ERROR</b> nova.compute.manager [req-87bef18f-ad3d-4147-a1b3-196b5b64b688 7bdb8c3bf8004f98aae1b16d938ac09b 69134106b56941698e58c61...<br></font></div><div><font color="#ff0000">70dc50f] Instance <b>failed</b> to spawn: <b>libvirt.libvirtError</b>: internal <b>error</b>: qemu unexpectedly closed the monitor: 2020-06-30T10:30:10.182675Z qemu-kvm: <b>error</b>: failed to set MSR 0...<br>he monitor: 2020-06-30T10:30:10.182675Z <b>qemu-kvm: error: failed to set MSR 0x48e to 0xfff9fffe04006172</b><br>_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' <b>failed</b>.<br> [instance: 128f372c-cb2e-47d9-b1bf-ce17270dc50f] <b>Traceback</b> (most recent call last):<br>375-2020-06-30 12:30:10.815 7<b> ERROR</b> nova.compute.manager [instance: 128f372c-cb2e-47d9-b1bf-ce17270dc50f] File "/usr/lib/python3.6/site-packages/nova/vir...</font><br></div><div><br></div><div><b>server.log </b><br></div><div><font color="#ff0000">5821c815-d213-498d-9394-fe25c6849918', 'status': 'failed', <b>'code': 422} returned with failed status</b></font><br></div><div><br></div><div><b>ovn_controller.log</b><br></div><div><font color="#ff0000">272-2020-06-30T12:30:10.126079625+02:00 stderr F 2020-06-30T10:30:10Z|00247|patch|WARN|<b>Bridge 'br-ex' not found for network 'datacentre'</b></font><br></div><div><br></div><div>Thanks!</div><div></div></div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Compute nodes are baremetal or virtualized?, I've seen similar bug reports when using nested virtualization in other OSes.</div></blockquote></div></div></blockquote><div>baremetal. Dell R630 if to be VERY precise. </div><div><br></div><div>Thank you, I will try. I also modified a file, and it looked like it relaunched podman container once config was changed. Either way, if I understand Linux config correctly, the default value for user and group is root, if commented out:</div><div>#user = "root"<br>#group = "root"<br></div><div><br></div><div>also in some logs, I saw, that it detected, that it is not AMD CPU :) and it is really not AMD CPU.</div><div><br></div><div><br></div><div>Just for fun, it might be important, here is how my node info looks.<br> ComputeS01Parameters:<br> NovaReservedHostMemory: 16384<br> KernelArgs: "crashkernel=no rhgb"<br> ComputeS01ExtraConfig:<br> nova::cpu_allocation_ratio: 4.0<br> nova::compute::libvirt::rx_queue_size: 1024<br> nova::compute::libvirt::tx_queue_size: 1024<br> nova::compute::resume_guests_state_on_host_boot: true<br></div></div></div>
_______________________________________________<br><br></blockquote></div></blockquote></div></blockquote></div></blockquote></div></blockquote></div><div dir="ltr"><div dir="ltr"><div><br></div></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div>Ruslanas Gžibovskis<br>+370 6030 7030<br></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div>Ruslanas Gžibovskis<br>+370 6030 7030<br></div></div></div>
_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@lists.rdoproject.org" target="_blank">users@lists.rdoproject.org</a><br>
<a href="http://lists.rdoproject.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rdoproject.org/mailman/listinfo/users</a><br>
<br>
To unsubscribe: <a href="mailto:users-unsubscribe@lists.rdoproject.org" target="_blank">users-unsubscribe@lists.rdoproject.org</a><br>
</blockquote></div></div></div></div></div></div>