Re: [OpenStack-Infra] Zuul feature/zuulv3 branch to be rewound

2017-09-21 Thread James E. Blair
Darragh Bailey writes: >> The abandon/restore steps are required by Gerrit in order to delete the >> branch. We could force-push the branch tip, but this is the procedure >> we have asked and would ask any other project to use in a similar >> situation, in order to

Re: [OpenStack-Infra] Zuul feature/zuulv3 branch to be rewound

2017-09-21 Thread Darragh Bailey
On 21 Sep 2017 6:38 pm, "James E. Blair" wrote: Hi, Snipped 1) Abandon all open changes on feature/zuulv3. 2) Delete the feature/zuulv3 branch. 3) Re-create the feature/zuulv3 branch at the commit before the Sem-Ver change: 027ba992595d23e920a9cf84f67c87959a4b2a13. 4)

[OpenStack-Infra] Zuul feature/zuulv3 branch to be rewound

2017-09-21 Thread James E. Blair
Hi, A change recently landed on the feature/zuulv3 branch of Zuul with a Sem-Ver commit message footer. This is used by PBR to alter the way it constructs version numbers. It's pretty nifty, but in my opinion, it has a fundamental flaw: it can't be undone. I think use of this by a project

Re: [OpenStack-Infra] First member of networking-lagopus gerrit group

2017-09-21 Thread Hirofumi Ichihara
On 2017/09/21 23:10, Paul Belanger wrote: On Thu, Sep 21, 2017 at 10:17:20AM +0900, Hirofumi Ichihara wrote: Hi Infra team, I proposed networking-lagopus project[1] and then it looks like the project was created[2, 3]. Could you add me into the groups? [1]:

Re: [OpenStack-Infra] First member of networking-lagopus gerrit group

2017-09-21 Thread Paul Belanger
On Thu, Sep 21, 2017 at 10:17:20AM +0900, Hirofumi Ichihara wrote: > Hi Infra team, > > I proposed networking-lagopus project[1] and then it looks like the project > was created[2, 3]. > Could you add me into the groups? > > [1]: https://review.openstack.org/#/c/501730/ > [2]:

Re: [OpenStack-Infra] [incident] OVH-BHS1 mirror disappeared

2017-09-21 Thread Paul Belanger
On Thu, Sep 21, 2017 at 12:58:58PM +1000, Ian Wienand wrote: > > At around Sep 21 02:30UTC mirror01.bhs1.ovh.openstack.org became > uncontactable and jobs in the region started to fail. > > The server was in an ACTIVE state but uncontactable. I attempted to > get a console but either a log or