July 2022 - openstack-discuss - lists.openstack.org

openstackclient: booting from image-created volume w/ delete_on_termination
by Kurt Garloff 06 Jul '22

06 Jul '22

Hi openstack CLI wizards, Having flavors without disks, I want volumes to be created from images on the fly that I can boot from. But I don't want to do bookkeeping for these volumes; they should disappear once the server disappears. On the command line with nova, I can do this: nova boot --nic net-name=$MYNET --key-name $MYKEY --flavor $MYFLAVOR \ --block-device "id=$MYIMGIFD,source=image,dest=volume,size=$MYSIZE,shutdown=remove,bootindex=0" $MYNAME I did not find a way to do this with openstack server create. Is there one? Here's what I tried: --image $MYIMGID --boot-from-volume $MYSIZE works, except that there is no way to specify delete_on_termination --block-device-mapping "sda=$MYIMGID:image:$MYSIZE:true" does complain that no --image or --volume have been passed. The option does not appear to be used for bootable volumes. I have seen a BP (merged with Ussuri) that would allow a PUT call to update delete_on_termination, but I don't see it usable with the openstackclient ... https://specs.openstack.org/openstack/nova-specs/specs/ussuri/implemented/d… Anything obvious I missed? Thanks, -- Kurt Garloff <kurt(a)garloff.de> Cologne, Germany

2 2

Re: Regarding Policy.json entries for glance image update not working for a user
by Adivya Singh 06 Jul '22

06 Jul '22

Hi Brian, Please find the response > 1> i am using Xena release version 24.0.1 > > Now the scenario is line below, my customer wants to have their login > access on setting up the properties of an image to the public. now what i > did is > > 1> i created a role in openstack using the admin credential name as "user" > 2> i assigned that user to a role user. > 3> i assigned those user to those project id, which they want to access as > a user role > > Then i went to Glance container which is controller by lxc and made a > policy.yaml file as below > > root@aio1-glance-container-724aa778:/etc/glance# cat policy.yaml > > "modify_image": "role:user" > > then i went to utility container and try to set the properties of a image > using openstack command > > openstack image set --public <image id> > > and then i got this error > > HTTP 403 Forbidden: You are not authorized to complete publicize_image > action. > > Even when i am trying the upload image with this user , i get the above > error only > > export OS_ENDPOINT_TYPE=internalURL > export OS_INTERFACE=internalURL > export OS_USERNAME=adsingh > export OS_PASSWORD='adsingh' > export OS_PROJECT_NAME=adsingh > export OS_TENANT_NAME=adsingh > export OS_AUTH_TYPE=password > export OS_AUTH_URL=https://<Internal IP of horizon>:5000/v3 > export OS_NO_CACHE=1 > export OS_USER_DOMAIN_NAME=Default > export OS_PROJECT_DOMAIN_NAME=Default > export OS_REGION_NAME=RegionOne > > Regards > Adivya Singh > > > > > On Mon, Jun 13, 2022 at 6:41 PM Alan Bishop <abishop(a)redhat.com> wrote: > >> >> >> On Mon, Jun 13, 2022 at 6:00 AM Brian Rosmaita < >> rosmaita.fossdev(a)gmail.com> wrote: >> >>> On 6/13/22 8:29 AM, Adivya Singh wrote: >>> > hi Team, >>> > >>> > Any thoughts on this >>> >>> H Adivya, >>> >>> Please supply some more information, for example: >>> >>> - which openstack release you are using >>> - the full API request you are making to modify the image >>> - the full API response you receive >>> - whether the user with "role:user" is in the same project that owns the >>> image >>> - debug level log extract for this call if you have it >>> - anything else that could be relevant, for example, have you modified >>> any other policies, and if so, what values are you using now? >>> >> >> Also bear in mind that the default policy_file name is "policy.yaml" (not >> .json). You either >> need to provide a policy.yaml file, or override the policy_file setting >> if you really want to >> use policy.json. >> >> Alan >> >> cheers, >>> brian >>> >>> > >>> > Regards >>> > Adivya Singh >>> > >>> > On Sat, Jun 11, 2022 at 12:40 AM Adivya Singh <adivya1.singh(a)gmail.com >>> > <mailto:adivya1.singh@gmail.com>> wrote: >>> > >>> > Hi Team, >>> > >>> > I have a use case where I have to give a user restriction on >>> > updating the image properties as a member. >>> > >>> > I have created a policy Json file and give the modify_image rule to >>> > the particular role, but still it is not working >>> > >>> > "modify_image": "role:user", This role is created in OpenStack. >>> > >>> > but still it is failing while updating properties with a >>> > particular user assigned to a role as "access denied" and >>> > unauthorized access >>> > >>> > Regards >>> > Adivya Singh >>> > >>> >>> >>>

3 5

[largescale-sig] Next meeting: July 6th, 15utc
by Thierry Carrez 06 Jul '22

06 Jul '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC, before taking a break for July and most of August. You can check how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220706T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[Octavia] Proposing Tom Weininger as core reviewer
by Gregory Thiemonge 06 Jul '22

06 Jul '22

Hi Folks, I would like to propose Tom Weininger as a core reviewer for the Octavia project. Since he joined the project, Tom has been a major contributor to Octavia, and he is an excellent reviewer. Please send your feedback in this thread, if there is no objection until next week, we will add him to the list of core reviewers. Thanks Gregory

4 4

[cinder] Bug deputy report for week of 07-06-2022
by Sofia Enriquez 06 Jul '22

06 Jul '22

This is a bug report from 06-29-2022 to 07-06-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1980268 "creating a bootable volume fails async when vol_size < virtual_size of image." Fix proposed to master. Cheers, Sofia -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

Re: Problem while launching an instance directly from an image "Volume did not finish being created even after we waited 203 seconds or 61 attempts"
by A Monster 06 Jul '22

06 Jul '22

Hello, I talking about launching instance from persistent volume ( cinder ), I've checked cinder logs but I've found no errors, the only error I could find is in nova compute log which says Build of instance 4cf01ba2-05b3-44e9-a685-8875d8c96b4e aborted: Volume 01739e82-9e66-41f7-be74-dfbbdcd6746e did not finish being created even after we waited 203 seconds or 61 attempts. And its status is creating. I am using openstack xena deployed with kolla ansible on centos 8 stream.

1 0

QoS Cinder, Zed Release
by Sergey Drozdov 06 Jul '22

06 Jul '22

To whom it may concern, I am helping a colleague of mine with the following pieces of work: 820027 (https://review.opendev.org/c/openstack/cinder/+/820027 <https://review.opendev.org/c/openstack/cinder/+/820027>), 820030 (https://review.opendev.org/c/openstack/cinder-specs/+/820030 <https://review.opendev.org/c/openstack/cinder-specs/+/820030>). I was wondering whether it is not too late to include the aforementioned within the Zed release? Is there anyone who can advise on this matter? Best Regards, Sergey

3 2

October 2022 PTG Dates & Registration
by Kendall Nelson 05 Jul '22

05 Jul '22

Hello Everyone! As you may have seen, we announced the next PTG[1] which will take place October 17-20, 2022 in Columbus, Ohio! Registration is now open[2]. We have also secured a limited, discounted hotel block for PTG attendees [3]. If your organization is interested in sponsoring the event, information on packages and pricing are now available on the PTG website [1] or feel free to reach out directly to ptg(a)openinfra.dev. Can't wait to SEE you all there! -Kendall Nelson (diablo_rojo) [1] https://openinfra.dev/ptg/ [2] https://openinfra-ptg.eventbrite.com/ [3] https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT

1 0

Listing instances that use a security group
by Derek O keeffe 05 Jul '22

05 Jul '22

Hi all, Is there a cli command to list all the VM's that have a specific security group attached, I need to delete some groups as a tidy up but I only get a warning that it's in use by an instance (of which there's 200) so I'd rather not go through them 1 by 1 in Horizon or show each one on the cli separately. An sql query would be acceptable also but nova db, select * from security_groups; select * from instances; & select * from security_group_instance_association; doesn't give me the required results that I can refine to search deeper. Thanks in advance for any info. Regards,Derek

2 2

Re: Issues With trove guest agent
by Hirotaka Wakabayashi 05 Jul '22

05 Jul '22

Hello, Hernando! I think Trove calls nova to inject files here: https://opendev.org/openstack/trove/src/branch/master/trove/taskmanager/mod… When cloud-init fails to inject Trove's configuration files, I think you should check the following parameters. 1. `use_nova_server_config_drive` configuration on trove.conf. This value should be True if you use config_drive to inject files. 2. `DIB_CLOUD_INIT_DATASOURCES` environment when buiding your own image. This value should contains `OpenStack` if you set `use_nova_server_config_drive` as False. and I think you should also check cloud-init log using journalctl. Thanks, Hirotaka On Tuesday, June 28, 2022, 09:55:24 PM GMT+9, <openstack-discuss-request(a)lists.openstack.org> wrote: Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)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: Regarding Floating IP is existing Setup (Adivya Singh) 2. Issues With trove guest agent (Hernando Ariza Perez) 3. Openstack keystone LDAP integration | openstack user list --domain domain.com | Internal server error (HTTP 500) (Swogat Pradhan) ---------------------------------------------------------------------- Message: 1 Date: Tue, 28 Jun 2022 18:12:51 +0530 From: Adivya Singh <adivya1.singh(a)gmail.com> To: Slawek Kaplonski <skaplons(a)redhat.com>, OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: Regarding Floating IP is existing Setup Message-ID: <CA+ykd61rKBam86Avut-7g+8EOS4snnzgTmMu5GvAETR3p5EuPg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" hi Slawek, it happens with a given router namespace at a time Regards Adivya Singh On Fri, Jun 24, 2022 at 10:13 PM Adivya Singh <adivya1.singh(a)gmail.com> wrote: > Hi, > > Thanks for the advice and the link, > > What i saw when i do testing using tcpdump was "ARP" was not working, and > it is not able to associate the FLoating IP with the MAC address of the > interface in the VM, When i do the associate and disassociate the VM , it > works fine > > But the Router NameSpace got changed. > > Regards > Adivya Singh > > On Thu, Jun 23, 2022 at 1:22 PM Slawek Kaplonski <skaplons(a)redhat.com> > wrote: > >> Hi, >> >> Dnia wtorek, 21 czerwca 2022 13:55:51 CEST Adivya Singh pisze: >> > hi Eugen, >> > >> > The current setup is 3 controller nodes, The Load is not much on each >> > controller and the number of DHCP agent is always set to 2 as per the >> > standard in the neutron.conf, The L3 agent seems to be stables as other >> > router namespace works fine under it, Only few router Namespace get >> > affected under the agent. >> >> Is it that problem happens for new floating IPs or for the FIPs which >> were working fine and then suddenly stopped working? If the latter, was >> there any action which triggered the issue to happen? >> Is there e.g. only one FIP broken in the router or maybe when it happens, >> then all FIPs which uses same router are broken? >> >> Can You also try to analyze with e.g. tcpdump where traffic is dropped >> exactly? You can check >> http://kaplonski.pl/blog/neutron-where-is-my-packet-2/ for some more >> detailed description how traffic should go from the external network to >> Your instance. >> >> > >> > Most of the template having issue , Have all instance having FLoating >> IP, a >> > Stack with a single floating IP have chance of issue very less >> > >> > Regards >> > Adivya Singh >> > >> > On Tue, Jun 21, 2022 at 1:18 PM Eugen Block <eblock(a)nde.ag> wrote: >> > >> > > Hi, >> > > >> > > this sounds very familiar to me, I had to deal with something similar >> > > a couple of times in a heavily used cluster with 2 control nodes. What >> > > does your setup look like, is it a HA setup? I would start checking >> > > the DHCP and L3 agents. After increasing dhcp_agents_per_network to 2 >> > > in neutron.conf and restarting the services this didn't occur again >> > > (yet). This would impact floating IPs as well, sometimes I had to >> > > disable and enable the affected router(s). If you only have one >> > > control node a different approach is necessary. Do you see a high load >> > > on the control node? >> > > >> > > >> > > Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: >> > > >> > > > hi Team, >> > > > >> > > > We got a issue in Xena release, where we set the environment in >> Ubuntu >> > > > Platform, But later we get some issues in Floating IP not reachable. >> > > > >> > > > In a Network node, not all router namespace are Impacted and only >> few of >> > > > them get affected, So we can not comment Network node has a issue. >> > > > >> > > > The L3 agent where the Router is tied up, Worked just fine, as other >> > > > routers work Fine. >> > > > >> > > > and the one having issue in Floating IP, if i unassigned and >> assigned it >> > > > starts working most of the time. >> > > > >> > > > Any thoughts on this >> > > > >> > > > Regards >> > > > Adivya Singh >> > > >> > > >> > > >> > > >> > > >> > >> >> >> -- >> Slawek Kaplonski >> Principal Software Engineer >> Red Hat > >

1 0