← Back to team overview

jiocloud-devops team mailing list archive

[Bug 1467802] [NEW] Public Cloud Certificate on API servers was the wrong one

 

Private bug reported:

Including context and initial symptoms for fixing later.

22/Jun/2015

hkumar [1:39 PM] hmmm last build has a different certificate
:disappointed: I am not sure from where it got that

hkumar[1:39 PM]and just now I did a package build, and it seems new one
have right cert

hkumar[1:39 PM]current one

hkumar[1:39 PM]dpkg -c jiocloud-ssl-certificate_99_all.deb  | grep jiocloud.com.crt
-rw-r--r-- root/root      1879 2015-06-22 13:36 ./etc/ssl/certs/jiocloud.com.crt

hkumar[1:40 PM]bad one (last one)
hkumar@lap-devops:~/Downloads$ dpkg -c jiocloud-ssl-certificate_98_all.deb  | grep jiocloud.com.crt
-rw-r--r-- root/root      1208 2015-06-17 16:14 ./etc/ssl/certs/jiocloud.com.crt

hkumar[1:40 PM]its really weird, the job just looks for secerts repo
which have certifcates/keys etc

hkumar[1:41 PM]to create the package

hkumar[1:41 PM]older packagges have right cert (before 98) and the new
one too

hkumar[1:41 PM]soren: ^^^ you have any idea on this?

hkumar[1:42 PM]@group: I know this issue will be fixed by rolling out
.99 of the package

hkumar[1:43 PM]The root cause cannot be done on servers

soren [1:43 PM] Does the build log say nything interesting?

hkumar [1:43 PM] checking that

hkumar [1:51 PM] soren: yeah....  there was something (the job was
trying to create ssl cert) - it may be because ofny git connectivity
issue?

hkumar[1:51 PM]soren:

hkumar[1:51 PM]dpkg-buildpackage: host architecture amd64
debian/rules build
dh build
  dh_testdir
  dh_auto_configure
  dh_auto_build
make[1]: Entering directory `/var/lib/jenkins/jobs/jiocloud-ssl-certificate-pkg/workspace/build'
openssl x509 -req -days 36500 -in jiocloud.com.csr.pem -signkey jiocloud.com.key.pem -out jiocloud.com.cert.pem
Signature ok
subject=/C=IN/ST=Maharashtra/L=Mumbai/O=JioCloud/CN=*.jiocloudservices.com
Getting Private key
make[1]: Leaving directory `/var/lib/jenkins/jobs/jiocloud-ssl-certificate-pkg/workspace/build'
  dh_auto_test
fakeroot debian/rules binary
dh binary

hkumar[1:51 PM]soren: ^^

hkumar[1:52 PM]anyway im just pushing new one

soren [1:52 PM] YEah, if it doesn't find a cert, it generates one.

** Affects: jio
     Importance: Low
     Assignee: Reliance Jio DevOps (jiocloud-devops)
         Status: Triaged


** Tags: operational-issue

** Changed in: jio
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Reliance
Jio DevOps, which is a bug assignee.
https://bugs.launchpad.net/bugs/1467802

Title:
  Public Cloud Certificate on API servers was the wrong one

Status in Jio:
  Triaged

Bug description:
  Including context and initial symptoms for fixing later.

  22/Jun/2015

  hkumar [1:39 PM] hmmm last build has a different certificate
  :disappointed: I am not sure from where it got that

  hkumar[1:39 PM]and just now I did a package build, and it seems new
  one have right cert

  hkumar[1:39 PM]current one

  hkumar[1:39 PM]dpkg -c jiocloud-ssl-certificate_99_all.deb  | grep jiocloud.com.crt
  -rw-r--r-- root/root      1879 2015-06-22 13:36 ./etc/ssl/certs/jiocloud.com.crt

  hkumar[1:40 PM]bad one (last one)
  hkumar@lap-devops:~/Downloads$ dpkg -c jiocloud-ssl-certificate_98_all.deb  | grep jiocloud.com.crt
  -rw-r--r-- root/root      1208 2015-06-17 16:14 ./etc/ssl/certs/jiocloud.com.crt

  hkumar[1:40 PM]its really weird, the job just looks for secerts repo
  which have certifcates/keys etc

  hkumar[1:41 PM]to create the package

  hkumar[1:41 PM]older packagges have right cert (before 98) and the new
  one too

  hkumar[1:41 PM]soren: ^^^ you have any idea on this?

  hkumar[1:42 PM]@group: I know this issue will be fixed by rolling out
  .99 of the package

  hkumar[1:43 PM]The root cause cannot be done on servers

  soren [1:43 PM] Does the build log say nything interesting?

  hkumar [1:43 PM] checking that

  hkumar [1:51 PM] soren: yeah....  there was something (the job was
  trying to create ssl cert) - it may be because ofny git connectivity
  issue?

  hkumar[1:51 PM]soren:

  hkumar[1:51 PM]dpkg-buildpackage: host architecture amd64
  debian/rules build
  dh build
    dh_testdir
    dh_auto_configure
    dh_auto_build
  make[1]: Entering directory `/var/lib/jenkins/jobs/jiocloud-ssl-certificate-pkg/workspace/build'
  openssl x509 -req -days 36500 -in jiocloud.com.csr.pem -signkey jiocloud.com.key.pem -out jiocloud.com.cert.pem
  Signature ok
  subject=/C=IN/ST=Maharashtra/L=Mumbai/O=JioCloud/CN=*.jiocloudservices.com
  Getting Private key
  make[1]: Leaving directory `/var/lib/jenkins/jobs/jiocloud-ssl-certificate-pkg/workspace/build'
    dh_auto_test
  fakeroot debian/rules binary
  dh binary

  hkumar[1:51 PM]soren: ^^

  hkumar[1:52 PM]anyway im just pushing new one

  soren [1:52 PM] YEah, if it doesn't find a cert, it generates one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/jio/+bug/1467802/+subscriptions


Follow ups

References