Open Stack

Hi Team,

I have deployed Openstack through manual installation-Yoga release. I
encountered the attached error and can't have access to Openstack dashboard.
When I entered the login credentials it displays something went wrong and
you don't have permission to use /horizon/.

Can anyone have a solution for this error.

-----Original Message-----
From: openstack-discuss-request at lists.openstack.org
<openstack-discuss-request at lists.openstack.org> 
Sent: Monday, September 4, 2023 8:27 PM
To: openstack-discuss at lists.openstack.org
Subject: ***UNCHECKED*** openstack-discuss Digest, Vol 59, Issue 10

Send openstack-discuss mailing list submissions to
	openstack-discuss at lists.openstack.org

To subscribe or unsubscribe via the World Wide Web, visit
	
https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss

or, via email, send a message with subject or body 'help' to
	openstack-discuss-request at lists.openstack.org

You can reach the person managing the list at
	openstack-discuss-owner at lists.openstack.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of openstack-discuss digest..."


Today's Topics:

   1. Re: Live migration error (Karera Tony)
   2. What is the difference between 4 and 8 virtual sockets to
      physical sockets? (Jorge Visentini)
   3. [all][stable][ptl] Propose to EOL Stein series (El?d Ill?s)


----------------------------------------------------------------------

Message: 1
Date: Mon, 4 Sep 2023 14:11:37 +0200
From: Karera Tony <tonykarera at gmail.com>
To: smooney at redhat.com
Cc: Danny Webb <Danny.Webb at thehutgroup.com>,  openstack-discuss
	<openstack-discuss at lists.openstack.org>
Subject: Re: Live migration error
Message-ID:
	<CA+69TL3=7GwfgRgAjfxvx5q4aZCstXxtBeB2mGb9ofa0JCZmbA at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello Smooney,

I can confirm that it is disabled on all the servers.

Regards

Tony Karera




On Mon, Sep 4, 2023 at 1:25?PM <smooney at redhat.com> wrote:

> On Mon, 2023-09-04 at 12:59 +0200, Karera Tony wrote:
> > Hello Danny,
> >
> > I am actually using Broadwell-noTSX-IBRS on all the servers but I 
> > have
> seen
> > that some flags are not there in the older servers.
> >
> > The flags below to be specific.
> >
> > hwp hwp_act_window hwp_pkg_req
> so hwp is apprentlly intels pstate contol based on 
> https://unix.stackexchange.com/a/43540
>
> i dont belive this is normally exposed to a guest but if you are 
> seeign differnce between hosts then that likely means you have 
> disabled pstates also know as "intel speedstep" on some of the host 
> and not others.
>
> >
> > Regards
> >
> > Tony Karera
> >
> >
> >
> >
> > On Fri, Sep 1, 2023 at 4:05?PM <smooney at redhat.com> wrote:
> >
> > > On Fri, 2023-09-01 at 14:56 +0200, Karera Tony wrote:
> > > > Hello Danny,
> > > >
> > > > Thanks for the feedback.
> > > >
> > > > use a lowest common denominator cpu_model : Does this mean 
> > > > changing
> the
> > > > servers ?
> > >
> > > it means tha tif you have a mix of cpus in the deployment you 
> > > shoudl hardcod to the older of the diffent cpu models i.e skylake 
> > > or whatever it may
> be
> > > in your case.
> > >
> > >
> > >
> https://docs.openstack.org/nova/latest/configuration/config.html#libvi
> rt.cpu_models
> > >
> > > [libvirt]
> > > cpu_mode=custom
> > > cpu_models=skylake
> > >
> > > in more recent release we replaced the older cpu_model with 
> > > cpu_models with is a comma sperated list of models in prefernce 
> > > order. i.e. nova will use the first
> cpu_modle
> > > in the list that work
> > > on the current host. not that while this give extra flexiblity it 
> > > vs
> just
> > > using the oldest cpu model
> > > it does limit the set of hosts you can migrate too but means you 
> > > can
> have
> > > better perfromance so its
> > > a tradeoff. performance vs portablity.
> > >
> > > the error you mentioned can also be caused by micorocode updates.
> > > intel remove TSX and MPX i beilve in the last 2 years form come of
> there
> > > cpus
> > > that breaks live migration if a vm was create with access to that 
> > > cpu instruction
> > >
> > > the only way to resolve that is to cold migrate the guest.
> > > i.e. if a vm is currently booted with cpu_model X it cannot be 
> > > modifed while the guest is running so you either need to update 
> > > the config option and reboot all the vms
> or
> > > more particlaly update the config
> > > and then cold migrate them which will allow you to move the
> instnace(your
> > > orginal goal) while allowing
> > > the new cpu model to take effect.
> > >
> > > novas default for the cpu model when not set is with our default
> cpu_mode
> > > is host_model
> > > meaning whatever model best matches the current hosts cpu.
> > >
> > > that is the correct default in general but if you have mixed cpu 
> > > generatiosn in your cloud its not ideal.
> > >
> > > hopefuly that helps
> > >
> > > >
> > > > Regards
> > > >
> > > > Tony Karera
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, Sep 1, 2023 at 12:37?PM Danny Webb <
> Danny.Webb at thehutgroup.com>
> > > > wrote:
> > > >
> > > > > It means that you have CPUs with incompatible flags or you've 
> > > > > got differing kernel versions that expose different flags or 
> > > > > you've got differing libvirt versions that expose different 
> > > > > flags.  You either
> > > need to
> > > > > use a lowest common denominator cpu_model or do a cold migration.
> > > > > ------------------------------
> > > > > *From:* Karera Tony <tonykarera at gmail.com>
> > > > > *Sent:* 01 September 2023 10:13
> > > > > *To:* openstack-discuss 
> > > > > <openstack-discuss at lists.openstack.org>
> > > > > *Subject:* Live migration error
> > > > >
> > > > >
> > > > > * CAUTION: This email originates from outside THG *
> > > > > ------------------------------ Hello Team,
> > > > >
> > > > > I am trying to migrate instances from one host to another but 
> > > > > I am
> > > getting
> > > > > this error.
> > > > >
> > > > > *Error: *Failed to live migrate instance to host "compute1".
> Details
> > > > > <http://10.10.13.31/admin/instances/#message_details>
> > > > > Migration pre-check error: Unacceptable CPU info: CPU doesn't 
> > > > > have compatibility. 0 Refer to
> > > > >
> http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult
> > > > > (HTTP 400) (Request-ID: 
> > > > > req-9dfdfe2e-70fa-481a-bd3d-c2c76a6e93da)
> > > > >
> > > > > Any idea on how to fix this?
> > > > >
> > > > > Regards
> > > > >
> > > > > Tony Karera
> > > > >
> > > > >
> > > > >
> > >
> > >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.openstack.org/pipermail/openstack-discuss/attachments/2023090
4/8dcdbdf5/attachment-0001.htm>

------------------------------

Message: 2
Date: Mon, 4 Sep 2023 11:51:07 -0300
From: Jorge Visentini <jorgevisentini at gmail.com>
To: openstack-discuss at lists.openstack.org
Subject: What is the difference between 4 and 8 virtual sockets to
	physical sockets?
Message-ID:
	<CAG=j6fpruTk5EG0dZTyL3M-ud2tCq7CBQHZiCBmbsr5sd6Z8Ow at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello Team,

What is the difference between creating an instance with *4* or *8 virtual
sockets*, since the hypervisor has only *4 physical sockets*.
My question is where do sockets, cores and virtual threads fit into the
physical hardware. I think this question is not just related to Openstack,
but with any virtualization.

My hypervisor configuration is as follows:

CPU(s): 192
Online CPU(s) list: 0-191
Thread(s) per core: 2
Core(s) per socket: 24
Socket(s): 4
NUMA node(s): 4

Do you have any documentation that I can read and understand better?

That we have a nice week!
--
Att,
Jorge Visentini
+55 55 98432-9868
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.openstack.org/pipermail/openstack-discuss/attachments/2023090
4/c5702749/attachment-0001.htm>

------------------------------

Message: 3
Date: Mon, 4 Sep 2023 15:26:39 +0000
From: El?d Ill?s <elod.illes at est.tech>
To: "openstack-discuss at lists.openstack.org"
	<openstack-discuss at lists.openstack.org>
Subject: [all][stable][ptl] Propose to EOL Stein series
Message-ID:
	
<VI1P18901MB075178B60ADE8475F17D3751FFE9A at VI1P18901MB0751.EURP189.PROD.OUTLO
OK.COM>
	
Content-Type: text/plain; charset="utf-8"

Hi,

Core projects announced and deleted their stable/stein branches for some
time already. Furthermore, most of the projects, where stable/stein is still
open, have broken gates.

So, the same way as we transitioned Rocky series to End of Life [1][2], now
is the time to do the same with Stein.

I'll propose the stein-eol transition patches for the rest of the open
projects. I ask again the teams to signal their decision (with a +1 if the
team is ready for the transition). Thanks in advance!

(Please note, that the Extended Maintenance process is phasing out /
transforming soon, see details in Technical Committee's resolution [3],
which was accepted and merged in August.)

Thanks,

El?d Ill?s
irc: elodilles @ #openstack-stable / #openstack-release

[1]
https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031922.
html
[2]
https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033386.ht
ml
[3]
https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branch
es.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.openstack.org/pipermail/openstack-discuss/attachments/2023090
4/a124c0b6/attachment.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
openstack-discuss mailing list
openstack-discuss at lists.openstack.org


------------------------------

End of openstack-discuss Digest, Vol 59, Issue 10
*************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: apache2.err log with neutron.PNG
Type: image/png
Size: 24954 bytes
Desc: not available
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230905/4e5e9471/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: neutron-server.error.PNG
Type: image/png
Size: 86403 bytes
Desc: not available
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230905/4e5e9471/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openstack error_pic.PNG
Type: image/png
Size: 24672 bytes
Desc: not available
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230905/4e5e9471/attachment-0005.png>