Re: [rdo-users] errors after installation packstack
by Javier Pena
Hi Andrej,
Looking at the Packstack logs, it looks like the relevant part is here:
[1;31mError: Systemd start for httpd failed!
journalctl log for httpd:
-- Logs begin at Tue 2018-02-27 13:03:14 CET, end at Tue 2018-02-27 13:20:57 CET. --
Feb 27 13:19:26 andy.linuz systemd[1]: Starting The Apache HTTP Server...
So Apache failed to start. During its first start, it will compile some django files, which takes some time. So either something failed in that part or the VM was too slow and the service start timed out.
Can you check your apache logs under /var/log/httpd? Also, if you try to start the httpd service manually, does it work?
Regards,
Javier
----- Original Message -----
> Hi Javier,
> all logs attached.
> There are several errors as per bellow.
> 1. Connection to controller hooked on IP 192.168.162.130 failed. Is it some
> external server where packstack need to talk during start?
> 2. All log files tarred and attached
> Please help me and make me sure if my packstack IDE enviroment is ready and I
> can start configuration with dashboard.
> Anyway dashboard is reachable on what ip address?
> My ifconfig -a bellow
> [root@andy manifests]# ifconfig -a
> ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.162.130 netmask 255.255.255.0 broadcast 192.168.162.255
> inet6 fe80::b0f2:1065:8a33:a305 prefixlen 64 scopeid 0x20<link>
> ether 00:0c:29:5c:59:c4 txqueuelen 1000 (Ethernet)
> RX packets 35982 bytes 27272489 (26.0 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 19765 bytes 2069558 (1.9 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 1 (Local Loopback)
> RX packets 534946 bytes 53561019 (51.0 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 534946 bytes 53561019 (51.0 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
> ether 52:54:00:02:f3:04 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
> ether 52:54:00:02:f3:04 txqueuelen 1000 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> Bez virů. www.avast.com
> On Mon, Feb 26 , 2018 at 10:58 AM, Javier Pena < jpena(a)redhat.com > wrote:
> > Oops, my reply skipped the list.
>
> > Can you check what's on /var/tmp/packstack/latest/manifests ? There should
> > be
> > some log files there.
>
> > Regards,
>
> > Javier
>
> > > Dear Javier
> >
>
> > > Many thanks for advice.
> >
>
> > > But I am not sure if I catched up entire packstack installation.
> >
>
> > > Would you be so kind how, what logs to check in order to be sure in what
> > > state is installation?
> >
>
> > > Many thanks.
> >
>
> > > Best regards
> >
>
> > > Andrej
> >
>
> > > On 26 Feb 2018 10:46, "Javier Pena" < jpena(a)redhat.com > wrote:
> >
>
> > > > Hi Andy,
> > >
> >
>
> > > > I can't see any error message in the output you pasted, just Packstack
> > > > waiting to complete the Puppet execution for the controller.
> > >
> >
>
> > > > Does it get stuck there for 30+ minutes? If so, then we can check the
> > > > contents of /var/tmp/packstack/<long uuid>/manifests. There will be a
> > > > 192.168.162.130_controller.pp.running file there, with all output from
> > > > the
> > > > Puppet run. This should give us a hint on what is going wrong.
> > >
> >
>
> > > > Regards,
> > >
> >
>
> > > > Javier
> > >
> >
>
> > > > > Dear gents
> > > >
> > >
> >
>
> > > > > I am newbie trying to setup my first openstack IDE all-in-one
> > > > > enviroment
> > > > > in
> > > > > CentOS.
> > > >
> > >
> >
>
> > > > > I have started packstack but I am ending up with errors as bellow. I
> > > > > guess
> > > > > that configuration services is not done and something is missing. Any
> > > > > advice
> > > > > would be highly welcomed.
> > > >
> > >
> >
>
> > > > > Kindest regards
> > > >
> > >
> >
>
> > > > > Andy
> > > >
> > >
> >
>
> > > > > [root@andy ~]# sudo packstack --allinone
> > > >
> > >
> >
>
> > > > > Welcome to the Packstack setup utility
> > > >
> > >
> >
>
> > > > > The installation log file is available at: /var/tmp/packstack/
> > > > > 20180225-081340 -6acLmT/openstack-setup.log
> > > >
> > >
> >
>
> > > > > Installing:
> > > >
> > >
> >
>
> > > > > Clean Up [ DONE ]
> > > >
> > >
> >
>
> > > > > Discovering ip protocol version [ DONE ]
> > > >
> > >
> >
>
> > > > > Setting up ssh keys [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing servers [ DONE ]
> > > >
> > >
> >
>
> > > > > Pre installing Puppet and discovering hosts' details [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing pre-install entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Setting up CACERT [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing AMQP entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing MariaDB entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Fixing Keystone LDAP config parameters to be undef if empty[ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Keystone entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Glance entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Checking if the Cinder server has a cinder-volumes vg[ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Cinder entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Nova API entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Creating ssh keys for Nova migration [ DONE ]
> > > >
> > >
> >
>
> > > > > Gathering ssh host keys for Nova migration [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Nova Compute entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Nova Scheduler entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Nova VNC Proxy entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing OpenStack Network-related Nova entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Nova Common entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Neutron LBaaS Agent entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Neutron API entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Neutron L3 entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Neutron L2 Agent entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Neutron DHCP Agent entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Neutron Metering Agent entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Checking if NetworkManager is enabled and running [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing OpenStack Client entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Horizon entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Swift builder entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Swift proxy entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Swift storage entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Gnocchi entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Redis entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Ceilometer entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Aodh entries [ DONE ]
> > > >
> > >
> >
>
> > > > > Preparing Puppet manifests [ DONE ]
> > > >
> > >
> >
>
> > > > > Copying Puppet modules and manifests [ DONE ]
> > > >
> > >
> >
>
> > > > > Applying 192.168.162.130_controller.pp
> > > >
> > >
> >
>
> > > > > Testing if puppet apply is finished: 192.168.162.130_controller.pp [
> > > > > /
> > > > > ]
> > > >
> > >
> >
>
> > > > > Testing if puppet apply is finished: 192.168.162.130_controller.pp [
> > > > > /
> > > > > ]
> > > >
> > >
> >
>
> > > > > Testing if puppet apply is finished: 192.168.162.130_controller.pp [
> > > > > |
> > > > > ]
> > > >
> > >
> >
>
> > > > > Bez virů. www.avast.com
> > > >
> > >
> >
>
> > > > > _______________________________________________
> > > >
> > >
> >
>
> > > > > users mailing list
> > > >
> > >
> >
>
> > > > > users(a)lists.rdoproject.org
> > > >
> > >
> >
>
> > > > > http://lists.rdoproject.org/mailman/listinfo/users
> > > >
> > >
> >
>
> > > > > To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
> > > >
> > >
> >
>
6 years, 12 months
[all] Revisiting RDO Technical Definition of Done
by Alan Pevec
Hi all,
we as a community last discussed RDO definition of done more than a
year ago and it was documented[1]
In the meantime we have multiple changes in the RDO promotion
process, most significant is that we do not run all the CI promotion
jobs in the single Jenkins pipeline, instead there is now an
increasing number of periodic Zuul jobs in review.rdoproject.org
reporting to DLRN API database.
Promotion is performed asynchronously when all the required jobs report success.
At the same time, TripleO as the deployment project with the most
coverage in the promotion CI, has moved to be completely containerized
in Queens.
While RDO does provide container registry which is used with RDO
Trunk, there aren't currently plans to provide containers built from
the stable RPM builds as discussed on this list [2] around Pike GA.
Even if we do all the work listed in [2] problem stays that containers
are currently installer specific and we cannot realistically provide
separate set of containers for each of TripleO, Kolla, OSA...
Proposal would be to redefine DoD as follows:
- RDO GA release delivers RPM packages via CentOS Cloud SIG repos,
built from pristine upstream source tarballs
- CI promotion GA criteria is changed from Jenkins pipeline to the
list of jobs running with RPM packages directly, initial set would be
all weirdo jobs running in [3]
- TripleO jobs would not be part of RDO GA criteria since TripelO now
requires containers which RDO will not ship.TripleO promotion CI will
continue running with containers built with RDO Trunk packages.
I'm adding this topic on the agenda for the RDO meeting today, I won't
be able to join but we need to get that discussion going so we have
updated DoD ready for Queens GA.
Cheers,
Alan
[1] https://www.rdoproject.org/blog/2016/05/technical-definition-of-done/
[2] https://www.redhat.com/archives/rdo-list/2017-August/msg00069.html
[3] https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo_trunk-prom...
6 years, 12 months
Quickstart and containers
by James LaBarre
If I am trying to familiarize myself with the newer containerized
overcloud (Queens & upwards), is there a way to build a TripleO
Quickstart on a single node? As I say, it's mainly to get some
experience in the newer configurations, after which I could probably
grab some more baremetal and do proper setups.
I do find myself wondering, though, with the way Quickstart worked with
images, if it's been doing containers all along...
6 years, 12 months
Re: [rdo-users] errors after installation packstack
by Javier Pena
Oops, my reply skipped the list.
Can you check what's on /var/tmp/packstack/latest/manifests ? There should be some log files there.
Regards,
Javier
----- Original Message -----
> Dear Javier
> Many thanks for advice.
> But I am not sure if I catched up entire packstack installation.
> Would you be so kind how, what logs to check in order to be sure in what
> state is installation?
> Many thanks.
> Best regards
> Andrej
> On 26 Feb 2018 10:46, "Javier Pena" < jpena(a)redhat.com > wrote:
> > Hi Andy,
>
> > I can't see any error message in the output you pasted, just Packstack
> > waiting to complete the Puppet execution for the controller.
>
> > Does it get stuck there for 30+ minutes? If so, then we can check the
> > contents of /var/tmp/packstack/<long uuid>/manifests. There will be a
> > 192.168.162.130_controller.pp.running file there, with all output from the
> > Puppet run. This should give us a hint on what is going wrong.
>
> > Regards,
>
> > Javier
>
> > > Dear gents
> >
>
> > > I am newbie trying to setup my first openstack IDE all-in-one enviroment
> > > in
> > > CentOS.
> >
>
> > > I have started packstack but I am ending up with errors as bellow. I
> > > guess
> > > that configuration services is not done and something is missing. Any
> > > advice
> > > would be highly welcomed.
> >
>
> > > Kindest regards
> >
>
> > > Andy
> >
>
> > > [root@andy ~]# sudo packstack --allinone
> >
>
> > > Welcome to the Packstack setup utility
> >
>
> > > The installation log file is available at:
> > > /var/tmp/packstack/20180225-081340-6acLmT/openstack-setup.log
> >
>
> > > Installing:
> >
>
> > > Clean Up [ DONE ]
> >
>
> > > Discovering ip protocol version [ DONE ]
> >
>
> > > Setting up ssh keys [ DONE ]
> >
>
> > > Preparing servers [ DONE ]
> >
>
> > > Pre installing Puppet and discovering hosts' details [ DONE ]
> >
>
> > > Preparing pre-install entries [ DONE ]
> >
>
> > > Setting up CACERT [ DONE ]
> >
>
> > > Preparing AMQP entries [ DONE ]
> >
>
> > > Preparing MariaDB entries [ DONE ]
> >
>
> > > Fixing Keystone LDAP config parameters to be undef if empty[ DONE ]
> >
>
> > > Preparing Keystone entries [ DONE ]
> >
>
> > > Preparing Glance entries [ DONE ]
> >
>
> > > Checking if the Cinder server has a cinder-volumes vg[ DONE ]
> >
>
> > > Preparing Cinder entries [ DONE ]
> >
>
> > > Preparing Nova API entries [ DONE ]
> >
>
> > > Creating ssh keys for Nova migration [ DONE ]
> >
>
> > > Gathering ssh host keys for Nova migration [ DONE ]
> >
>
> > > Preparing Nova Compute entries [ DONE ]
> >
>
> > > Preparing Nova Scheduler entries [ DONE ]
> >
>
> > > Preparing Nova VNC Proxy entries [ DONE ]
> >
>
> > > Preparing OpenStack Network-related Nova entries [ DONE ]
> >
>
> > > Preparing Nova Common entries [ DONE ]
> >
>
> > > Preparing Neutron LBaaS Agent entries [ DONE ]
> >
>
> > > Preparing Neutron API entries [ DONE ]
> >
>
> > > Preparing Neutron L3 entries [ DONE ]
> >
>
> > > Preparing Neutron L2 Agent entries [ DONE ]
> >
>
> > > Preparing Neutron DHCP Agent entries [ DONE ]
> >
>
> > > Preparing Neutron Metering Agent entries [ DONE ]
> >
>
> > > Checking if NetworkManager is enabled and running [ DONE ]
> >
>
> > > Preparing OpenStack Client entries [ DONE ]
> >
>
> > > Preparing Horizon entries [ DONE ]
> >
>
> > > Preparing Swift builder entries [ DONE ]
> >
>
> > > Preparing Swift proxy entries [ DONE ]
> >
>
> > > Preparing Swift storage entries [ DONE ]
> >
>
> > > Preparing Gnocchi entries [ DONE ]
> >
>
> > > Preparing Redis entries [ DONE ]
> >
>
> > > Preparing Ceilometer entries [ DONE ]
> >
>
> > > Preparing Aodh entries [ DONE ]
> >
>
> > > Preparing Puppet manifests [ DONE ]
> >
>
> > > Copying Puppet modules and manifests [ DONE ]
> >
>
> > > Applying 192.168.162.130_controller.pp
> >
>
> > > Testing if puppet apply is finished: 192.168.162.130_controller.pp [ / ]
> >
>
> > > Testing if puppet apply is finished: 192.168.162.130_controller.pp [ / ]
> >
>
> > > Testing if puppet apply is finished: 192.168.162.130_controller.pp [ | ]
> >
>
> > > Bez virů. www.avast.com
> >
>
> > > _______________________________________________
> >
>
> > > users mailing list
> >
>
> > > users(a)lists.rdoproject.org
> >
>
> > > http://lists.rdoproject.org/mailman/listinfo/users
> >
>
> > > To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
> >
>
6 years, 12 months
errors after installation packstack
by andrej krnac
Dear gents
I am newbie trying to setup my first openstack IDE all-in-one enviroment in
CentOS.
I have started packstack but I am ending up with errors as bellow. I guess
that configuration services is not done and something is missing. Any
advice would be highly welcomed.
Kindest regards
Andy
[root@andy ~]# sudo packstack --allinone
Welcome to the Packstack setup utility
The installation log file is available at:
/var/tmp/packstack/20180225-081340-6acLmT/openstack-setup.log
Installing:
Clean Up [ DONE ]
Discovering ip protocol version [ DONE ]
Setting up ssh keys [ DONE ]
Preparing servers [ DONE ]
Pre installing Puppet and discovering hosts' details [ DONE ]
Preparing pre-install entries [ DONE ]
Setting up CACERT [ DONE ]
Preparing AMQP entries [ DONE ]
Preparing MariaDB entries [ DONE ]
Fixing Keystone LDAP config parameters to be undef if empty[ DONE ]
Preparing Keystone entries [ DONE ]
Preparing Glance entries [ DONE ]
Checking if the Cinder server has a cinder-volumes vg[ DONE ]
Preparing Cinder entries [ DONE ]
Preparing Nova API entries [ DONE ]
Creating ssh keys for Nova migration [ DONE ]
Gathering ssh host keys for Nova migration [ DONE ]
Preparing Nova Compute entries [ DONE ]
Preparing Nova Scheduler entries [ DONE ]
Preparing Nova VNC Proxy entries [ DONE ]
Preparing OpenStack Network-related Nova entries [ DONE ]
Preparing Nova Common entries [ DONE ]
Preparing Neutron LBaaS Agent entries [ DONE ]
Preparing Neutron API entries [ DONE ]
Preparing Neutron L3 entries [ DONE ]
Preparing Neutron L2 Agent entries [ DONE ]
Preparing Neutron DHCP Agent entries [ DONE ]
Preparing Neutron Metering Agent entries [ DONE ]
Checking if NetworkManager is enabled and running [ DONE ]
Preparing OpenStack Client entries [ DONE ]
Preparing Horizon entries [ DONE ]
Preparing Swift builder entries [ DONE ]
Preparing Swift proxy entries [ DONE ]
Preparing Swift storage entries [ DONE ]
Preparing Gnocchi entries [ DONE ]
Preparing Redis entries [ DONE ]
Preparing Ceilometer entries [ DONE ]
Preparing Aodh entries [ DONE ]
Preparing Puppet manifests [ DONE ]
Copying Puppet modules and manifests [ DONE ]
Applying 192.168.162.130_controller.pp
Testing if puppet apply is finished: 192.168.162.130_controller.pp [ / ]
Testing if puppet apply is finished: 192.168.162.130_controller.pp [ / ]
Testing if puppet apply is finished: 192.168.162.130_controller.pp [ | ]
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...>
Bez
virů. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
6 years, 12 months
[Meeting] RDO meeting (2018-02-21) minutes
by Javier Pena
==============================
#rdo: RDO meeting - 2018-02-21
==============================
Meeting started by jpena at 15:00:15 UTC. The full logs are available
at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_02_21/2018/rdo...
.
Meeting summary
---------------
* roll call (jpena, 15:00:20)
* Status of Cloud SIG Meeting? (jpena, 15:04:02)
* ACTION: number80 post on centos-devel that current schedule for
cloud SIG meeting will be confirmed until another slot is chosen
(number80, 15:05:57)
* PTG next week in Dublin. Will the RDO people present be doing an
interview? (jpena, 15:06:58)
* 28 days since promotion? What's up? (jpena, 15:14:29)
* LINK: https://review.rdoproject.org/r/#/c/12558/ and
https://review.rdoproject.org/r/#/c/12540/ (amoralej, 15:17:14)
* open floor (jpena, 15:23:29)
* LINK: https://www.openstack.org/ptg/#tab_schedule (dmsimard,
15:30:07)
* LINK: https://www.openstack.org/ptg#tab_schedule (rbowen, 15:30:08)
* chair for next meeting (jpena, 15:33:10)
* ACTION: move next meeting to March 7 (jpena, 15:34:40)
* ACTION: rbowen to chair the next meeting, on March 7 (jpena,
15:36:03)
Meeting ended at 15:37:25 UTC.
Action items, by person
-----------------------
* number80
* number80 post on centos-devel that current schedule for cloud SIG
meeting will be confirmed until another slot is chosen
* rbowen
* rbowen to chair the next meeting, on March 7
People present (lines said)
---------------------------
* rbowen (32)
* jpena (25)
* dmsimard (20)
* number80 (15)
* amoralej (8)
* openstack (6)
* rlandy|rover (5)
* chandankumar (3)
* leanderthal (3)
* mary_grace (3)
* dmellado (2)
* sshnaidm (2)
* mjturek (2)
* rasca (1)
* rdobot (1)
* myoung (1)
Generated by `MeetBot`_ 0.1.4
7 years
