3:34 p.m.
Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released at the
end of September 2016. When is the right time to update RDO to ship OVS
2.6?
In general, what's the process here as new releases come out? When should
RDO get updated?
My interest is primarily because OVS 2.6 includes some new sub-packages for
OVN. We test using copr builds from OVS master, but it would be nice to
have official release packages as the default way to start testing.
--
Russell Bryant
5:16 p.m.
OVS 2.6.1 has already been tagged in our "pending" [1] repositories
but hasn't been promoted to the "testing" repositories yet.
We're starting to be fairly late in the Ocata cycle, if we want to do
it, we should move forward ASAP.
Alan, Haikel (cc) - We have a lot of packages in there right now [2],
did we plan on "flushing" them soon ?
It's not clear to me when the pending jobs would have run last to test
pending so I just fired one [3] to get a picture.
[1]: https://cbs.centos.org/koji/buildinfo?buildID=14916
[2]: http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Pac...
[3]: https://ci.centos.org/view/rdo/view/weirdo/job/weirdo-generic-wrapper/17/
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Jan 4, 2017 at 4:34 PM, Russell Bryant <rbryant(a)redhat.com> wrote:
Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released
at the
end of September 2016. When is the right time to update RDO to ship OVS
2.6?
In general, what's the process here as new releases come out? When should
RDO get updated?
My interest is primarily because OVS 2.6 includes some new sub-packages for
OVN. We test using copr builds from OVS master, but it would be nice to
have official release packages as the default way to start testing.
--
Russell Bryant
_______________________________________________
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
5:18 p.m.
Russel,
I forgot to mention, if you'd like to test the OVS 2.6.1 package from
the pending repository, the repository config is the following:
===
[centos-openstack-pending]
name=CentOS-7 - OpenStack Pending
baseurl=http://cbs.centos.org/repos/cloud7-openstack-common-pending/$base...
gpgcheck=0
enabled=1
===
It needs to be added on top of the full repositories you're using as
it's just a subset of packages, not the whole thing.
It should automatically win due to higher NVR.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Jan 4, 2017 at 6:16 PM, David Moreau Simard <dms(a)redhat.com> wrote:
OVS 2.6.1 has already been tagged in our "pending" [1]
repositories
but hasn't been promoted to the "testing" repositories yet.
We're starting to be fairly late in the Ocata cycle, if we want to do
it, we should move forward ASAP.
Alan, Haikel (cc) - We have a lot of packages in there right now [2],
did we plan on "flushing" them soon ?
It's not clear to me when the pending jobs would have run last to test
pending so I just fired one [3] to get a picture.
[1]: https://cbs.centos.org/koji/buildinfo?buildID=14916
[2]: http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Pac...
[3]: https://ci.centos.org/view/rdo/view/weirdo/job/weirdo-generic-wrapper/17/
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Jan 4, 2017 at 4:34 PM, Russell Bryant <rbryant(a)redhat.com> wrote:
> Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released at the
> end of September 2016. When is the right time to update RDO to ship OVS
> 2.6?
>
> In general, what's the process here as new releases come out? When should
> RDO get updated?
>
> My interest is primarily because OVS 2.6 includes some new sub-packages for
> OVN. We test using copr builds from OVS master, but it would be nice to
> have official release packages as the default way to start testing.
>
> --
> Russell Bryant
>
> _______________________________________________
> 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
8:29 a.m.
Thanks for info! It's good to know that OVS 2.6 is in the queue. I also
didn't know about enabling the pending repo in general. That will be
helpful for testing, even if we only grab OVS from there for now.
On Wed, Jan 4, 2017 at 6:18 PM, David Moreau Simard <dms(a)redhat.com> wrote:
Russel,
I forgot to mention, if you'd like to test the OVS 2.6.1 package from
the pending repository, the repository config is the following:
===
[centos-openstack-pending]
name=CentOS-7 - OpenStack Pending
baseurl=http://cbs.centos.org/repos/cloud7-openstack-common-
pending/$basearch/os/
gpgcheck=0
enabled=1
===
It needs to be added on top of the full repositories you're using as
it's just a subset of packages, not the whole thing.
It should automatically win due to higher NVR.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Jan 4, 2017 at 6:16 PM, David Moreau Simard <dms(a)redhat.com>
wrote:
> OVS 2.6.1 has already been tagged in our "pending" [1] repositories
> but hasn't been promoted to the "testing" repositories yet.
>
> We're starting to be fairly late in the Ocata cycle, if we want to do
> it, we should move forward ASAP.
>
> Alan, Haikel (cc) - We have a lot of packages in there right now [2],
> did we plan on "flushing" them soon ?
> It's not clear to me when the pending jobs would have run last to test
> pending so I just fired one [3] to get a picture.
>
> [1]: https://cbs.centos.org/koji/buildinfo?buildID=14916
> [2]: http://cbs.centos.org/repos/cloud7-openstack-common-
pending/x86_64/os/Packages/
> [3]: https://ci.centos.org/view/rdo/view/weirdo/job/weirdo-
generic-wrapper/17/
>
> David Moreau Simard
> Senior Software Engineer | Openstack RDO
>
> dmsimard = [irc, github, twitter]
>
>
> On Wed, Jan 4, 2017 at 4:34 PM, Russell Bryant <rbryant(a)redhat.com>
wrote:
>> Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released at
the
>> end of September 2016. When is the right time to update RDO to ship OVS
>> 2.6?
>>
>> In general, what's the process here as new releases come out? When
should
>> RDO get updated?
>>
>> My interest is primarily because OVS 2.6 includes some new sub-packages
for
>> OVN. We test using copr builds from OVS master, but it would be nice to
>> have official release packages as the default way to start testing.
>>
>> --
>> Russell Bryant
>>
>> _______________________________________________
>> 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
--
Russell Bryant
6:33 p.m.
On Wed, Jan 4, 2017 at 6:16 PM, David Moreau Simard <dms(a)redhat.com> wrote:
OVS 2.6.1 has already been tagged in our "pending" [1]
repositories
but hasn't been promoted to the "testing" repositories yet.
We're starting to be fairly late in the Ocata cycle, if we want to do
it, we should move forward ASAP.
have we run packstack/puppet/tripleo CI jobs with it?
Alan, Haikel (cc) - We have a lot of packages in there right now
[2],
did we plan on "flushing" them soon ?
It's not clear to me when the pending jobs would have run last to test
pending so I just fired one [3] to get a picture.
[1]: https://cbs.centos.org/koji/buildinfo?buildID=14916
[2]: http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Pac...
[3]: https://ci.centos.org/view/rdo/view/weirdo/job/weirdo-generic-wrapper/17/
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Jan 4, 2017 at 4:34 PM, Russell Bryant <rbryant(a)redhat.com> wrote:
> Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released at the
> end of September 2016. When is the right time to update RDO to ship OVS
> 2.6?
>
> In general, what's the process here as new releases come out? When should
> RDO get updated?
>
> My interest is primarily because OVS 2.6 includes some new sub-packages for
> OVN. We test using copr builds from OVS master, but it would be nice to
> have official release packages as the default way to start testing.
>
> --
> Russell Bryant
>
> _______________________________________________
> 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
--
Emilien Macchi
8:11 a.m.
Additionally I'd be curious to know if we have CI jobs to cover
in-place upgrades so we understand the implications for systems that
are already set up and would like to move to a newer OVS version.
On Thu, Jan 5, 2017 at 7:33 PM, Emilien Macchi <emilien(a)redhat.com> wrote:
On Wed, Jan 4, 2017 at 6:16 PM, David Moreau Simard
<dms(a)redhat.com> wrote:
> OVS 2.6.1 has already been tagged in our "pending" [1] repositories
> but hasn't been promoted to the "testing" repositories yet.
>
> We're starting to be fairly late in the Ocata cycle, if we want to do
> it, we should move forward ASAP.
have we run packstack/puppet/tripleo CI jobs with it?
> Alan, Haikel (cc) - We have a lot of packages in there right now [2],
> did we plan on "flushing" them soon ?
> It's not clear to me when the pending jobs would have run last to test
> pending so I just fired one [3] to get a picture.
>
> [1]: https://cbs.centos.org/koji/buildinfo?buildID=14916
> [2]: http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Pac...
> [3]: https://ci.centos.org/view/rdo/view/weirdo/job/weirdo-generic-wrapper/17/
>
> David Moreau Simard
> Senior Software Engineer | Openstack RDO
>
> dmsimard = [irc, github, twitter]
>
>
> On Wed, Jan 4, 2017 at 4:34 PM, Russell Bryant <rbryant(a)redhat.com> wrote:
>> Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released at the
>> end of September 2016. When is the right time to update RDO to ship OVS
>> 2.6?
>>
>> In general, what's the process here as new releases come out? When should
>> RDO get updated?
>>
>> My interest is primarily because OVS 2.6 includes some new sub-packages for
>> OVN. We test using copr builds from OVS master, but it would be nice to
>> have official release packages as the default way to start testing.
>>
>> --
>> Russell Bryant
>>
>> _______________________________________________
>> 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
--
Emilien Macchi
_______________________________________________
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
8:35 a.m.
Packstack and Puppet-OpenStack passed (one p-o-i job failed but due to an
unrelated Cinder tempest test failure).
The two TripleO Quickstart jobs failed and I'll reach out for help
troubleshooting today, these jobs have not been particularly successful
(ever) so I'm not confident this would be OVS' fault.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Jan 5, 2017 7:33 PM, "Emilien Macchi" <emilien(a)redhat.com> wrote:
On Wed, Jan 4, 2017 at 6:16 PM, David Moreau Simard <dms(a)redhat.com> wrote:
OVS 2.6.1 has already been tagged in our "pending" [1]
repositories
but hasn't been promoted to the "testing" repositories yet.
We're starting to be fairly late in the Ocata cycle, if we want to do
it, we should move forward ASAP.
have we run packstack/puppet/tripleo CI jobs with it?
Alan, Haikel (cc) - We have a lot of packages in there right now
[2],
did we plan on "flushing" them soon ?
It's not clear to me when the pending jobs would have run last to test
pending so I just fired one [3] to get a picture.
[1]: https://cbs.centos.org/koji/buildinfo?buildID=14916
[2]: http://cbs.centos.org/repos/cloud7-openstack-common-
pending/x86_64/os/Packages/
generic-wrapper/17/
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Jan 4, 2017 at 4:34 PM, Russell Bryant <rbryant(a)redhat.com> wrote:
> Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released at
the
> end of September 2016. When is the right time to update RDO to
ship OVS
> 2.6?
>
> In general, what's the process here as new releases come out? When
should
> RDO get updated?
>
> My interest is primarily because OVS 2.6 includes some new sub-packages
for
> OVN. We test using copr builds from OVS master, but it would be
nice to
> have official release packages as the default way to start testing.
>
> --
> Russell Bryant
>
> _______________________________________________
> 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
--
Emilien Macchi
8:41 a.m.
(+Wes)
We have jobs that test upgrades from N-1 to N but unless mistaken, these do
not have the pending repository (where OVS 2.6.1 is currently staged)
enabled.
As of now, these upgrade jobs would pick up the new OVS only when it is
promoted to the testing repositories.
This is an excellent point though. Since this is a significant OVS version
upgrade, we should definitely put some effort into testing it. Testing it
in the context of CI (i.e and run ping test at the end) and looking at what
really happens to running virtual machines in production are two different
things though.
There could be a loss of connectivity for example.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Jan 6, 2017 9:11 AM, "Michael Orazi" <morazi(a)redhat.com> wrote:
Additionally I'd be curious to know if we have CI jobs to cover
in-place upgrades so we understand the implications for systems that
are already set up and would like to move to a newer OVS version.
On Thu, Jan 5, 2017 at 7:33 PM, Emilien Macchi <emilien(a)redhat.com> wrote:
> On Wed, Jan 4, 2017 at 6:16 PM, David Moreau Simard <dms(a)redhat.com>
wrote:
>> OVS 2.6.1 has already been tagged in our "pending" [1] repositories
>> but hasn't been promoted to the "testing" repositories yet.
>>
>> We're starting to be fairly late in the Ocata cycle, if we want to do
>> it, we should move forward ASAP.
>
> have we run packstack/puppet/tripleo CI jobs with it?
>
>> Alan, Haikel (cc) - We have a lot of packages in there right now [2],
>> did we plan on "flushing" them soon ?
>> It's not clear to me when the pending jobs would have run last to test
>> pending so I just fired one [3] to get a picture.
>>
>> [1]: https://cbs.centos.org/koji/buildinfo?buildID=14916
>> [2]: http://cbs.centos.org/repos/cloud7-openstack-common-
pending/x86_64/os/Packages/
>> [3]: https://ci.centos.org/view/rdo/view/weirdo/job/weirdo-
generic-wrapper/17/
>>
>> David Moreau Simard
>> Senior Software Engineer | Openstack RDO
>>
>> dmsimard = [irc, github, twitter]
>>
>>
>> On Wed, Jan 4, 2017 at 4:34 PM, Russell Bryant <rbryant(a)redhat.com>
wrote:
>>> Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released at
the
>>> end of September 2016. When is the right time to update RDO to ship
OVS
>>> 2.6?
>>>
>>> In general, what's the process here as new releases come out? When
should
>>> RDO get updated?
>>>
>>> My interest is primarily because OVS 2.6 includes some new
sub-packages for
>>> OVN. We test using copr builds from OVS master, but it would be nice
to
>>> have official release packages as the default way to start testing.
>>>
>>> --
>>> Russell Bryant
>>>
>>> _______________________________________________
>>> 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
>
>
>
> --
> Emilien Macchi
>
> _______________________________________________
> 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
>
>
10:37 a.m.
This is an excellent point though. Since this is a significant OVS
version
upgrade, we should definitely put some effort into testing it.
Also test with RDO Newton and Mitaka releases, I'd like to push OVS
2.6 into common-testing/release eventually because I don't think
keeping old version branch for Newton and Mitaka users is sustainable.
In RDO we are rebuilding OVS from Fedora[1] and there have not been
maintenance updates for older releases e.g. 2.5.1 [2]
Cheers,
Alan
[1] https://koji.fedoraproject.org/koji/packageinfo?packageID=13455
[2] https://github.com/openvswitch/ovs/releases/tag/v2.5.1
5:26 a.m.
On Fri, Jan 6, 2017 at 9:11 AM, Michael Orazi <morazi(a)redhat.com> wrote:
Additionally I'd be curious to know if we have CI jobs to cover
in-place upgrades so we understand the implications for systems that
are already set up and would like to move to a newer OVS version.
Indeed the 2.4 to 2.5 upgrade was tricky.
On Thu, Jan 5, 2017 at 7:33 PM, Emilien Macchi <emilien(a)redhat.com> wrote:
> On Wed, Jan 4, 2017 at 6:16 PM, David Moreau Simard <dms(a)redhat.com> wrote:
>> OVS 2.6.1 has already been tagged in our "pending" [1] repositories
>> but hasn't been promoted to the "testing" repositories yet.
>>
>> We're starting to be fairly late in the Ocata cycle, if we want to do
>> it, we should move forward ASAP.
>
> have we run packstack/puppet/tripleo CI jobs with it?
>
>> Alan, Haikel (cc) - We have a lot of packages in there right now [2],
>> did we plan on "flushing" them soon ?
>> It's not clear to me when the pending jobs would have run last to test
>> pending so I just fired one [3] to get a picture.
>>
>> [1]: https://cbs.centos.org/koji/buildinfo?buildID=14916
>> [2]:
http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Pac...
>> [3]: https://ci.centos.org/view/rdo/view/weirdo/job/weirdo-generic-wrapper/17/
>>
>> David Moreau Simard
>> Senior Software Engineer | Openstack RDO
>>
>> dmsimard = [irc, github, twitter]
>>
>>
>> On Wed, Jan 4, 2017 at 4:34 PM, Russell Bryant <rbryant(a)redhat.com> wrote:
>>> Right now the delorean-deps repo has OVS 2.5. OVS 2.6 was released at the
>>> end of September 2016. When is the right time to update RDO to ship OVS
>>> 2.6?
>>>
>>> In general, what's the process here as new releases come out? When
should
>>> RDO get updated?
>>>
>>> My interest is primarily because OVS 2.6 includes some new sub-packages for
>>> OVN. We test using copr builds from OVS master, but it would be nice to
>>> have official release packages as the default way to start testing.
>>>
>>> --
>>> Russell Bryant
>>>
>>> _______________________________________________
>>> 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
>
>
>
> --
> Emilien Macchi
>
> _______________________________________________
> 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
6:44 p.m.
On Mon, Jan 9, 2017 at 12:26 PM, Assaf Muller <assaf(a)redhat.com> wrote:
On Fri, Jan 6, 2017 at 9:11 AM, Michael Orazi
<morazi(a)redhat.com> wrote:
> Additionally I'd be curious to know if we have CI jobs to cover
> in-place upgrades so we understand the implications for systems that
> are already set up and would like to move to a newer OVS version.
Indeed the 2.4 to 2.5 upgrade was tricky.
And so will be 2.6 :(
Test upgrade job with pending repo enabled failed:
http://logs.openstack.org/44/422244/2/experimental/gate-tripleo-ci-centos...
...
ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection
failed (No such file or directory)
Assaf, can you get those who worked on ovs 2.4 -> 2.5 upgrade to look
at this, if it might sound familiar to them?
Potential patches in tripleo can be tested against OVS 2.6 in pending
repo by adding
Depends-On: I19293cfef76384598511c9b278cdf887eaa5dc5c
Cheers,
Alan
5:48 a.m.
+ Sofer, Brent, Terry.
On Wed, Jan 18, 2017 at 7:44 PM, Alan Pevec <apevec(a)redhat.com> wrote:
On Mon, Jan 9, 2017 at 12:26 PM, Assaf Muller
<assaf(a)redhat.com> wrote:
> On Fri, Jan 6, 2017 at 9:11 AM, Michael Orazi <morazi(a)redhat.com> wrote:
>> Additionally I'd be curious to know if we have CI jobs to cover
>> in-place upgrades so we understand the implications for systems that
>> are already set up and would like to move to a newer OVS version.
>
> Indeed the 2.4 to 2.5 upgrade was tricky.
And so will be 2.6 :(
Test upgrade job with pending repo enabled failed:
http://logs.openstack.org/44/422244/2/experimental/gate-tripleo-ci-centos...
...
ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection
failed (No such file or directory)
Assaf, can you get those who worked on ovs 2.4 -> 2.5 upgrade to look
at this, if it might sound familiar to them?
Potential patches in tripleo can be tested against OVS 2.6 in pending
repo by adding
Depends-On: I19293cfef76384598511c9b278cdf887eaa5dc5c
Terry, Brent, updating OVS to 2.6 is a priority for the Ocata release.
Can you please take a look?
Cheers,
Alan
8:43 a.m.
On 01/18/2017 07:44 PM, Alan Pevec wrote:
On Mon, Jan 9, 2017 at 12:26 PM, Assaf Muller
<assaf(a)redhat.com> wrote:
> On Fri, Jan 6, 2017 at 9:11 AM, Michael Orazi <morazi(a)redhat.com> wrote:
>> Additionally I'd be curious to know if we have CI jobs to cover
>> in-place upgrades so we understand the implications for systems that
>> are already set up and would like to move to a newer OVS version.
>
> Indeed the 2.4 to 2.5 upgrade was tricky.
And so will be 2.6 :(
Test upgrade job with pending repo enabled failed:
http://logs.openstack.org/44/422244/2/experimental/gate-tripleo-ci-centos...
...
ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection
failed (No such file or directory)
Technically, this is not only happening on the upgrades job[1]. However,
it is happening in the infra setup stage for the multinode jobs, and the
image from infra has older OVS and we upgrade before running the
ovs-vsctl command.
This was actually pretty easy for me to reproduce by just upgrading OVS
to 2.6 and running `ovs-vsctl --add-br foo`. I get the same error.
[1]
http://logs.openstack.org/44/422244/2/check/gate-tripleo-ci-centos-7-nonh...
Assaf, can you get those who worked on ovs 2.4 -> 2.5 upgrade to
look
at this, if it might sound familiar to them?
Potential patches in tripleo can be tested against OVS 2.6 in pending
repo by adding
Depends-On: I19293cfef76384598511c9b278cdf887eaa5dc5c
Cheers,
Alan
10:48 a.m.
Assaf & co, any updates on this ?
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Thu, Jan 19, 2017 at 6:48 AM, Assaf Muller <assaf(a)redhat.com> wrote:
+ Sofer, Brent, Terry.
On Wed, Jan 18, 2017 at 7:44 PM, Alan Pevec <apevec(a)redhat.com> wrote:
> On Mon, Jan 9, 2017 at 12:26 PM, Assaf Muller <assaf(a)redhat.com> wrote:
>> On Fri, Jan 6, 2017 at 9:11 AM, Michael Orazi <morazi(a)redhat.com> wrote:
>>> Additionally I'd be curious to know if we have CI jobs to cover
>>> in-place upgrades so we understand the implications for systems that
>>> are already set up and would like to move to a newer OVS version.
>>
>> Indeed the 2.4 to 2.5 upgrade was tricky.
>
> And so will be 2.6 :(
>
> Test upgrade job with pending repo enabled failed:
>
http://logs.openstack.org/44/422244/2/experimental/gate-tripleo-ci-centos...
> ...
> ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection
> failed (No such file or directory)
>
> Assaf, can you get those who worked on ovs 2.4 -> 2.5 upgrade to look
> at this, if it might sound familiar to them?
> Potential patches in tripleo can be tested against OVS 2.6 in pending
> repo by adding
> Depends-On: I19293cfef76384598511c9b278cdf887eaa5dc5c
Terry, Brent, updating OVS to 2.6 is a priority for the Ocata release.
Can you please take a look?
>
> Cheers,
> Alan
_______________________________________________
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
7:17 a.m.
+ Flavio.
On Thu, Jan 26, 2017 at 11:48 AM, David Moreau Simard <dms(a)redhat.com> wrote:
Assaf & co, any updates on this ?
Indeed Terry reproduced the issue, we got in contact with Flavio, he
knows what's going on and we're waiting on a fix and a new 2.6 build.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Thu, Jan 19, 2017 at 6:48 AM, Assaf Muller <assaf(a)redhat.com> wrote:
> + Sofer, Brent, Terry.
>
> On Wed, Jan 18, 2017 at 7:44 PM, Alan Pevec <apevec(a)redhat.com> wrote:
>> On Mon, Jan 9, 2017 at 12:26 PM, Assaf Muller <assaf(a)redhat.com> wrote:
>>> On Fri, Jan 6, 2017 at 9:11 AM, Michael Orazi <morazi(a)redhat.com>
wrote:
>>>> Additionally I'd be curious to know if we have CI jobs to cover
>>>> in-place upgrades so we understand the implications for systems that
>>>> are already set up and would like to move to a newer OVS version.
>>>
>>> Indeed the 2.4 to 2.5 upgrade was tricky.
>>
>> And so will be 2.6 :(
>>
>> Test upgrade job with pending repo enabled failed:
>>
http://logs.openstack.org/44/422244/2/experimental/gate-tripleo-ci-centos...
>> ...
>> ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection
>> failed (No such file or directory)
>>
>> Assaf, can you get those who worked on ovs 2.4 -> 2.5 upgrade to look
>> at this, if it might sound familiar to them?
>> Potential patches in tripleo can be tested against OVS 2.6 in pending
>> repo by adding
>> Depends-On: I19293cfef76384598511c9b278cdf887eaa5dc5c
>
> Terry, Brent, updating OVS to 2.6 is a priority for the Ocata release.
> Can you please take a look?
>
>>
>> Cheers,
>> Alan
>
> _______________________________________________
> 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
1:13 p.m.
On Jan 29, 2017 2:18 PM, "Assaf Muller" <assaf(a)redhat.com> wrote:
Indeed Terry reproduced the issue, we got in contact with Flavio, he
knows what's going on and we're waiting on a fix and a new 2.6 build.
Was that
https://bugzilla.redhat.com/show_bug.cgi?id=1403958#c31
?
Cheers,
Alan
5:20 a.m.
On Sun, Jan 29, 2017 at 2:13 PM, Alan Pevec <apevec(a)redhat.com> wrote:
On Jan 29, 2017 2:18 PM, "Assaf Muller" <assaf(a)redhat.com> wrote:
Indeed Terry reproduced the issue, we got in contact with Flavio, he
knows what's going on and we're waiting on a fix and a new 2.6 build.
Ack.
Was that
https://bugzilla.redhat.com/show_bug.cgi?id=1403958#c31
?
Cheers,
Alan
2645
days inactive
2671
days old
16 comments
7 participants
participants (7)
-
Alan Pevec -
Assaf Muller -
David Moreau Simard -
Emilien Macchi -
John Trowbridge -
Michael Orazi -
Russell Bryant