2:58 a.m.
Dear rdo-list,
Due to a planned maintenance on the underlying infrastructure, the Delorean server will be
under maintenance on January 21, from 9:00 UTC to 23:00 UTC time.
During the maintenance window, the Delorean repositories will be available (served from
the backup system), but no new commits will be processed.
If you have any questions or concerns, please do not hesitate to contact us.
Regards,
Javier Peña
11:25 a.m.
----- Original Message -----
Dear rdo-list,
Due to a planned maintenance on the underlying infrastructure, the Delorean
server will be under maintenance on January 21, from 9:00 UTC to 23:00 UTC
time.
During the maintenance window, the Delorean repositories will be available
(served from the backup system), but no new commits will be processed.
Dear all,
The maintenance is now finished (earlier than expected!), and the Delorean instance is
processing commits.
Regards,
Javier
2:34 p.m.
There was also an impact on the delorean CI jenkins slave due to the
maintenance.
If you have submitted a review or patchset to delorean-related
repositories (packages, delorean), Jenkins did not pick it up.
Feel free to submit a new patchset (i.e, slight commit message edit)
to trigger a CI run.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Thu, Jan 21, 2016 at 12:25 PM, Javier Pena <javier.pena(a)redhat.com> wrote:
----- Original Message -----
> Dear rdo-list,
>
> Due to a planned maintenance on the underlying infrastructure, the Delorean
> server will be under maintenance on January 21, from 9:00 UTC to 23:00 UTC
> time.
>
> During the maintenance window, the Delorean repositories will be available
> (served from the backup system), but no new commits will be processed.
>
Dear all,
The maintenance is now finished (earlier than expected!), and the Delorean instance is
processing commits.
Regards,
Javier
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
2:11 a.m.
2016-01-21 21:34 GMT+01:00 David Moreau Simard <dms(a)redhat.com>:
There was also an impact on the delorean CI jenkins slave due to the
maintenance.
If you have submitted a review or patchset to delorean-related
repositories (packages, delorean), Jenkins did not pick it up.
Feel free to submit a new patchset (i.e, slight commit message edit)
to trigger a CI run.
git review -Fshould do the trick too
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Thu, Jan 21, 2016 at 12:25 PM, Javier Pena <javier.pena(a)redhat.com> wrote:
>
>
> ----- Original Message -----
>> Dear rdo-list,
>>
>> Due to a planned maintenance on the underlying infrastructure, the Delorean
>> server will be under maintenance on January 21, from 9:00 UTC to 23:00 UTC
>> time.
>>
>> During the maintenance window, the Delorean repositories will be available
>> (served from the backup system), but no new commits will be processed.
>>
>
> Dear all,
>
> The maintenance is now finished (earlier than expected!), and the Delorean instance
is processing commits.
>
> Regards,
> Javier
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
12:43 p.m.
New subject: [Rdo-list] EXCLUDE_SERVERS BUG AFFECTING RDO Kilo 2015.1.1
Please, see https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1254389
Commit contains fix per https://review.openstack.org/#/c/257033/ is
https://review.openstack.org/gitweb?p=openstack/packstack.git;a=commitdif...
I attempted to rebuild openstack-packstack-2015.1-0.16.dev1637.g2bb5c1d.el7.src.rpm ( the
most recent available)
adding fourth patch
https://review.openstack.org/gitweb?p=openstack/packstack.git;a=patch;h=0...
as 004-Fix-exclude-servers.patch.
Build failed with errors :-
+ echo 'Patch #1 (0001-Do-not-enable-Keystone-in-httpd-by-default.patch):'
Patch #1 (0001-Do-not-enable-Keystone-in-httpd-by-default.patch):
+ /usr/bin/cat
/root/rpmbuild/SOURCES/0001-Do-not-enable-Keystone-in-httpd-by-default.patch
+ /usr/bin/patch -p1 --fuzz=0
patching file packstack/plugins/keystone_100.py
Hunk #1 succeeded at 168 (offset 16 lines).
+ echo 'Patch #2 (0002-Do-not-enable-EPEL-when-installing-RDO.patch):'
Patch #2 (0002-Do-not-enable-EPEL-when-installing-RDO.patch):
+ /usr/bin/cat /root/rpmbuild/SOURCES/0002-Do-not-enable-EPEL-when-installing-RDO.patch
+ /usr/bin/patch -p1 --fuzz=0
patching file packstack/plugins/prescript_000.py
Hunk #1 succeeded at 1113 (offset 21 lines).
+ echo 'Patch #3 (0003-Fix-nagios-service-configuration.patch):'
Patch #3 (0003-Fix-nagios-service-configuration.patch):
+ /usr/bin/cat /root/rpmbuild/SOURCES/0003-Fix-nagios-service-configuration.patch
+ /usr/bin/patch -p1 --fuzz=0
patching file packstack/puppet/modules/packstack/manifests/nagios_config_wrapper.pp
+ echo 'Patch #4 (004-Fix-exclude-servers.patch):'
Patch #4 (004-Fix-exclude-servers.patch): <==== my patch placed in SOURCES
+ /usr/bin/cat /root/rpmbuild/SOURCES/004-Fix-exclude-servers.patch
+ /usr/bin/patch -p1 --fuzz=0
patching file docs/packstack.rst
Hunk #1 succeeded at 838 (offset -19 lines).
patching file packstack/plugins/neutron_350.py
Hunk #2 succeeded at 515 (offset -59 lines).
Hunk #3 FAILED at 670.
1 out of 3 hunks FAILED -- saving rejects to file packstack/plugins/neutron_350.py.rej
error: Bad exit status from /var/tmp/rpm-tmp.ZVNRrt (%prep)
So Hunk #1,#2 were absent in the most recent openstack-packstack build for RDO Kilo.
I am aware of ` yum downgrade openstack-packstack openstack-packstack-doc
openstack-packstack-puppet`
until version of openctack--packstack will become
openstack-packstack-puppet-2015.1-0.1.dev1537.gba5183c.el7.noarch
openstack-packstack-2015.1-0.1.dev1537.gba5183c.el7.noarch
allows to use EXCLUDE_SERVERS directive ( already tested)
Version installed via `rpm -iv rdo-release-kilo-1.noarch.rpm` was 2015.1-0.14
Please, advise
Boris
6:30 p.m.
New subject: [Rdo-list] EXCLUDE_SERVERS BUG AFFECTING RDO Kilo 2015.1.1
Commit contains fix per https://review.openstack.org/#/c/257033/ is
This was only recently merged to packstack upstream master branch and
needs to be cherry-picked to stable/kilo branch used to build the
package in RDO Kilo.
Version installed via `rpm -iv rdo-release-kilo-1.noarch.rpm` was
2015.1-0.14
Kilo updates have been pushed to the CentOS Cloud SIG repo
http://mirror.centos.org/centos/7/cloud/x86_64/openstack-kilo/
and rdo-release-kilo-1 still points to the old repository location on
fedorapeople.org.
I'll push rdo-release update for Kilo to point to the new location.
Cheers,
Alan
12:42 a.m.
New subject: [Rdo-list] EXCLUDE_SERVERS BUG AFFECTING RDO Kilo 2015.1.1
________________________________________
From: Alan Pevec <apevec(a)gmail.com>
Sent: Friday, January 22, 2016 7:30 PM
To: Boris Derzhavets
Cc: rdo-list
Subject: Re: EXCLUDE_SERVERS BUG AFFECTING RDO Kilo 2015.1.1
Commit contains fix per https://review.openstack.org/#/c/257033/ is
This was only recently merged to packstack upstream master branch and
needs to be cherry-picked to stable/kilo branch used to build the
package in RDO Kilo.
Could I expect openstack-packstack-2015.1-0.17 to have mentioned patch applied ?
I believe this issue to be critical for landscape where 10 new Compute Nodes
have to be added ASAP.
Any time estimate , if possible.
Thank you
Boris
Version installed via `rpm -iv rdo-release-kilo-1.noarch.rpm` was
2015.1-0.14
Kilo updates have been pushed to the CentOS Cloud SIG repo
http://mirror.centos.org/centos/7/cloud/x86_64/openstack-kilo/
and rdo-release-kilo-1 still points to the old repository location on
fedorapeople.org.
I'll push rdo-release update for Kilo to point to the new location.
Cheers,
Alan
5:57 a.m.
New subject: [Rdo-list] EXCLUDE_SERVERS BUG AFFECTING RDO Kilo 2015.1.1
Could I expect openstack-packstack-2015.1-0.17 to have mentioned
patch applied ?
I believe this issue to be critical for landscape where 10 new Compute Nodes
have to be added ASAP.
It does make sense to backport this fix, I've requested it in
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1254389#c9
Cheers,
Alan
3023
days inactive
3027
days old
7 comments
5 participants
participants (5)
-
Alan Pevec -
Boris Derzhavets -
David Moreau Simard -
Haïkel -
Javier Pena