Error building overcloud images
by wodel youchi
Hi,
I am using Wallaby.
Using this documentation (
https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deplo...),
I am trying to build the overcloud images like this :
export OS_YAML="/usr/share/openstack-tripleo-common/image-yaml/overcloud-images-centos8.yaml"
export DIB_YUM_REPO_CONF="/etc/yum.repos.d/delorean*
/etc/yum.repos.d/tripleo-centos-*"
export STABLE_RELEASE="wallaby"
openstack overcloud image build --config-file
/usr/share/openstack-tripleo-common/image-yaml/overcloud-images-python3.yaml
--config-file $OS_YAML
But I got these errors at the end :
> ...
> *2021-05-26 18:14:45.815 | ERROR:root:overcloud-base has no valid mapping
> for package openssl-perl *
> 2021-05-26 18:14:46.543 | INFO:root:Mapping for overcloud-base : lvm2
> *2021-05-26 18:14:46.554 | ERROR:root:overcloud-base has no valid mapping
> for package lvm2 *
> 2021-05-26 18:14:47.241 | INFO:root:Mapping for overcloud-base : sysstat
> 2021-05-26 18:14:47.933 | INFO:root:Mapping for overcloud-ceph-storage :
> chrony_package
> 2021-05-26 18:14:48.645 | Running install-packages install.
> ....
> ....
>
>
>
> *2021-05-26 18:15:02.588 | Error: 2021-05-26 18:15:02.589 | Problem:
> conflicting requests 2021-05-26 18:15:02.589 | - nothing provides
> pacemaker-libs(x86-64) = 2.0.5-9.el8 needed by
> pacemaker-remote-2.0.5-9.el8.x86_64 2021-05-26 18:15:02.592 | (You could
> try using --skip-broken to work around the problem or --nobest to use more
> than the best choice package)*
> 2021-05-26 18:15:11.699 | INFO diskimage_builder.block_device.blockdevice
> [-] State already cleaned - no way to do anything here
> Exception occured while running the command
> Traceback (most recent call last):
> File "/usr/lib/python3.6/site-packages/tripleoclient/command.py", line
> 34, in run
> super(Command, self).run(parsed_args)
> File "/usr/lib/python3.6/site-packages/osc_lib/command/command.py", line
> 39, in run
> return super(Command, self).run(parsed_args)
> File "/usr/lib/python3.6/site-packages/cliff/command.py", line 185, in
> run
> return_code = self.take_action(parsed_args) or 0
> File
> "/usr/lib/python3.6/site-packages/tripleoclient/v1/overcloud_image.py",
> line 120, in take_action
> manager.build()
> File "/usr/lib/python3.6/site-packages/tripleo_common/image/build.py",
> line 85, in build
> elements, options, packages, extra_options)
> File
> "/usr/lib/python3.6/site-packages/tripleo_common/image/image_builder.py",
> line 140, in build_image
> raise subprocess.CalledProcessError(process.returncode, cmd)
> subprocess.CalledProcessError: Command '['disk-image-create', '-a',
> 'amd64', '-o', './overcloud-full', '-t', 'qcow2', '-p',
> 'python3-psutil,python3-debtcollector,sos,device-mapper-multipat
> h,openstack-heat-agents,os-net-config,jq,python3-dbus', '--min-tmpfs=7',
> '--mkfs-options', '-s size=4096', 'centos', 'baremetal', 'openvswitch',
> 'overcloud-agent', 'overcloud-base', 'overc
> loud-controller', 'overcloud-compute', 'overcloud-ceph-storage',
> 'puppet-modules', 'stable-interface-names', 'grub2', 'element-manifest',
> 'dynamic-login', 'iptables', 'enable-packages-inst
> all', 'override-pip-and-virtualenv', 'dracut-regenerate',
> 'remove-machine-id', 'remove-resolvconf', 'openssh', 'disable-nouveau',
> 'selinux-permissive', 'interface-names']' returned non-zer
> o exit status 1.
> Command '['disk-image-create', '-a', 'amd64', '-o', './overcloud-full',
> '-t', 'qcow2', '-p',
> 'python3-psutil,python3-debtcollector,sos,device-mapper-multipath,openstack-heat-agents,os-net-
>
> config,jq,python3-dbus', '--min-tmpfs=7', '--mkfs-options', '-s
> size=4096', 'centos', 'baremetal', 'openvswitch', 'overcloud-agent',
> 'overcloud-base', 'overcloud-controller', 'overcloud-co
> mpute', 'overcloud-ceph-storage', 'puppet-modules',
> 'stable-interface-names', 'grub2', 'element-manifest', 'dynamic-login',
> 'iptables', 'enable-packages-install', 'override-pip-and-virtual
> env', 'dracut-regenerate', 'remove-machine-id', 'remove-resolvconf',
> 'openssh', 'disable-nouveau', 'selinux-permissive', 'interface-names']'
> returned non-zero exit status 1.
>
What did I miss?
Regards.
1 year, 12 months
Re: [rdo-users] install tripleO Vectoria failed
by wodel youchi
Hi,
I was able to deploy the undercloud using the "container-tools:3.0"; thanks
to Alex.
Regards.
Le mar. 25 mai 2021 à 17:32, wodel youchi <wodel.youchi(a)gmail.com> a écrit :
> Hi,
>
> Thanks I will try with container-tools:3.0 and report back.
>
> My goal is to have a production plateforme at the end, so my question is :
> what modules do I have to choose to have a stable platform? do I have to
> avoid "Most recent (rolling)" releases even if I am following the tripleO
> documentation and using "stable version of openstack".
>
> In other words, how do I choose the version to implement in production?
>
> Regards.
>
> Le lun. 24 mai 2021 à 14:16, Alex Schultz <aschultz(a)redhat.com> a écrit :
>
>> There is an issue with the latest version of container tools. You'll
>> want to enable container-tools:3.0 or container-tools:2.0 prior to the
>> installation of tripleoclient.
>>
>> On Sun, May 23, 2021 at 8:15 AM wodel youchi <wodel.youchi(a)gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Sorry for the half mail.
>>> I tried the deployment using victoria then I tried with wallaby, and I
>>> get the same error.
>>>
>>> Regards.
>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...> Virus-free.
>>> www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...>
>>> <#m_6448373989928374698_m_662210471086875738_m_-3901142281429443165_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>> Le dim. 23 mai 2021 à 14:40, wodel youchi <wodel.youchi(a)gmail.com> a
>>> écrit :
>>>
>>>> Hi,
>>>>
>>>> I am a newbie in openstack and in tripleO.
>>>> I am trying to deploy openstack using tripleO documentation.
>>>> The undercloud is a VM.
>>>> I am getting these error every time I execute the deploy :
>>>>
>>>> 2021-05-23 14:16:45.974486 | 525400e2-c5d3-0dc6-0f2e-00000000234b |
>>>> FATAL | Manage container systemd servic
>>>> es and cleanup old systemd healthchecks for
>>>> /var/lib/tripleo-config/container-startup-config/step_3 | ooo1 | err
>>>> or={"changed": false, "msg": "Service iscsid has not started yet"}
>>>>
>>>>
>>>> I tried vicor
>>>>
>>>> Regards.
>>>>
>>>>
>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...> Virus-free.
>>>> www.avast.com
>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...>
>>>> <#m_6448373989928374698_m_662210471086875738_m_-3901142281429443165_m_7065432774213793991_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>
>>> _______________________________________________
>>> users mailing list
>>> users(a)lists.rdoproject.org
>>> http://lists.rdoproject.org/mailman/listinfo/users
>>>
>>> To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
>>>
>>
2 years
RDO IRC Information
by Amy Marrich
Dear RDO Community Members,
As many of you know, there have been changes in Freenode which affect the
RDO channel, OpenInfra channels, and the channels of many other communities
we work closely with. After careful consideration, the OpenDev team has
chosen to move the Open Infrastructure Foundation IRC related
infrastructure to OFTC[0]. As of Monday, May 31st, OFTC will become the
primary home of RDO (#rdo) including where we host our meeting.
The Fedora and CentOS Communities have chosen to move to Libera[1] and due
to our close relationship with these projects RDO will have a presence on
this system as well also in #rdo.
Our channel is already created on both systems and are ready for you to
join them and it is recommended you register your Nick[2][3] on both these
systems.
While not a total solution, we would like to mention Matrix[4] which we hope
in the future will be able to bridge OFTC and Libera.chat into one location.
Thanks,
Amy Marrich (spotz)
0 - https://www.oftc.net/
1 - https://libera.chat/
2 - https://www.oftc.net/Services/#register-your-account
3 - https://libera.chat/guides/registration
4 - https://matrix.org
2 years
Wallaby RDO Release Announcement
by Amy Marrich
If you're having trouble with the formatting, this release
announcement isavailable online at
https://blogs.rdoproject.org/2021/05/rdo-wallaby-released/
---
*RDO Wallaby Released*
The RDO community is pleased to announce the general availability of the
RDO build for OpenStack Wallaby for RPM-based distributions, CentOS Stream
and Red Hat Enterprise Linux. RDO is suitable for building private, public,
and hybrid clouds. Wallaby is the 23rd release from the OpenStack project,
which is the work of more than 1,000 contributors from around the world.
The release is already available on the CentOS mirror network at
http://mirror.centos.org/centos/8
<http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-wallaby/>
-stream
<http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-wallaby/>
/cloud/x86_64/openstack-
<http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-wallaby/>
wallaby
<http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-wallaby/>/
<http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-wallaby/>.
The RDO community project curates, packages, builds, tests and maintains a
complete OpenStack component set for RHEL and CentOS Stream and is a member
of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG
focuses on delivering a great user experience for CentOS users looking to
build and maintain their own on-premise, public or hybrid clouds.
All work on RDO and on the downstream release, Red Hat OpenStack Platform,
is 100% open source, with all code changes going upstream first.
PLEASE NOTE: RDO Wallaby provides packages for CentOS Stream 8 and Python 3
only. Please use the Victoria release for CentOS8. For CentOS7 and python
2.7, please use the Train release.
*Interesting things in the Wallaby release include:*
- RBAC supported added in multiple projects including Designate, Glance,
Horizon, Ironic, and Octavia
- Glance added support for distributed image import
- Ironic added deployment and cleaning enhancements including UEFI
Partition Image handling, NVMe Secure Erase, per-instance deployment driver
interface overrides, deploy time “deploy_steps”, and file injection.
- Kuryr added nested mode with node VMs running in multiple subnets is
now available. To use that functionality a new option
[pod_vif_nested]worker_nodes_subnets is introduced accepting multiple
Subnet IDs.
- Manila added the ability for Operators to now set maximum and minimum
share sizes as extra specifications on share types.
- Neutron added a new subnet type network:routed is now available. IPs
of this subnet type can be advertised with BGP over a provider network.
- TripleO moved network and network port creation out of the Heat stack
and into the baremetal provisioning workflow.
Other highlights of the broader upstream OpenStack project may be read via
https://releases.openstack.org/wallaby/highlights.html
*Contributors*
- During the Wallaby cycle, we saw the following new RDO contributors:
- Adriano Petrich
- Ananya Banerjee
- Artom Lifshitz
- Attila Fazekas
- Brian Haley
- David J Peacock
- Jason Joyce
- Jeremy Freudberg
- Jiri Podivin
- Martin Kopec
- Waleed Mousa
Welcome to all of you and Thank You So Much for participating!
But we wouldn’t want to overlook anyone. A super massive Thank You to all
58 contributors who participated in producing this release. This list
includes commits to rdo-packages, rdo-infra, and redhat-website
repositories:
- Adriano Petrich
- Alex Schultz
- Alfredo Moralejo
- Amol Kahat
- Amy Marrich
- Ananya Banerjee
- Artom Lifshitz
- Arx Cruz
- Attila Fazekas
- Bhagyashri Shewale
- Brian Haley
- Cédric Jeanneret
- Chandan Kumar
- Daniel Pawlik
- David J Peacock
- Dmitry Tantsur
- Emilien Macchi
- Eric Harney
- Fabien Boucher
- frenzyfriday
- Gabriele Cerami
- Gael Chamoulaud
- Grzegorz Grasza
- Harald Jensas
- Jason Joyce
- Javier Pena
- Jeremy Freudberg
- Jiri Podivin
- Joel Capitao
- Kevin Carter
- Luigi Toscano
- Marc Dequenes
- Marios Andreou
- Martin Kopec
- Mathieu Bultel
- Matthias Runge
- Mike Turek
- Nicolas Hicher
- Pete Zaitcev
- Pooja Jadhav
- Rabi Mishra
- Riccardo Pittau
- Roman Gorshunov
- Ronelle Landy
- Sagi Shnaidman
- Sandeep Yadav
- Slawek Kaplonski
- Sorin Sbarnea
- Steve Baker
- Takashi Kajinami
- Tristan Cacqueray
- Waleed Mousa
- Wes Hayutin
- Yatin Karel
*The Next Release Cycle*
At the end of one release, focus shifts immediately to the next release i.e
Xena.
*Get Started*
There are three ways to get started with RDO.
To spin up a proof of concept cloud, quickly, and on limited hardware, try
an All-In-One Packstack installation. You can run RDO on a single node to
get a feel for how it works.
For a production deployment of RDO, use TripleO and you’ll be running a
production cloud in short order.
Finally, for those that don’t have any hardware or physical resources,
there’s the OpenStack Global Passport Program. This is a collaborative
effort between OpenStack public cloud providers to let you experience the
freedom, performance and interoperability of open source infrastructure.
You can quickly and easily gain access to OpenStack infrastructure via
trial programs from participating OpenStack public cloud providers around
the world.
*Get Help*
The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users
and operators. For more developer-oriented content we recommend joining the
dev(a)lists.rdoproject.org mailing list. Remember to post a brief
introduction about yourself and your RDO story. The mailing lists archives
are all available at https://mail.rdoproject.org. You can also find
extensive documentation on RDOproject.org.
The #rdo channel on Freenode IRC is also an excellent place to find and
give help.
We also welcome comments and requests on the CentOS devel mailing list and
the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo
on irc.freenode.net), however we have a more focused audience within the
RDO venues.
*Get Involved*
To get involved in the OpenStack RPM packaging effort, check out the RDO
contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO
packaging documentation.
Join us in #rdo and #tripleo on the Freenode IRC network and follow us on
Twitter @RDOCommunity. You can also find us on Facebook and YouTube.
2 years
