Control: clone 876239 -1 Control: retitle -1 reproducible: re-deploy odxu4a (disk failure)
On 2017-10-02, Mattia Rizzolo wrote: > On Mon, Oct 02, 2017 at 10:33:37AM -0700, Vagrant Cascadian wrote: >> On 2017-10-02, Mattia Rizzolo wrote: >> > Actually, hostname is different: you reinstalled it as odxu4a instead >> > of odxu4, therefore our scripts are not going to be happy. ... >> Oh, I suppose I did change the local hostname ... > It isn't disruptive to bring it back online! > Just the different hostname is a problem :P Of course... >> > I've already run init_node, so what's left to do would be to IMHO rename >> > all occourrence of odxu4 to odxu4a (including dns) and then run >> > update_jdn again. Sadly I don't have the time for all of this right >> > now. >> >> I can update DNS and propose a patch for jenkins git. > > tbh, I'd prefer that, making things just a tad more uniform. > I can take care of creating/delating jobs without problem. Ok, will try to follow up on this soon... >> It will be a shame to loose the munin history and build history in the >> db... > > Oh, if you find munin's history so helpful, I can manually carry it > over, it's just about renaming a few files :) I do prefer to keep munin history. How hard is it to update the build history in the database? > BTW, not sure if you noticed, but you hijacked a previous bug that was > already closed somehow (seems like you kept a #xxxxxx in the subject > while mailing submit@, and that does mail the previous bug instead of > filing a new one indeed). Didn't notice that; hopefully this mail successfully fixes that. live well, vagrant
signature.asc
Description: PGP signature