yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1182550@xxxxxxxxxxxxxxxxxx>]

[Expired for tempest because there has been no activity for 60 days.]

** Changed in: tempest
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1182550

Title:
  401 Unauthorized due to "Verify error: certificate is not yet valid"

Status in OpenStack Identity (Keystone):
  Expired
Status in Tempest:
  Expired

Bug description:
  Never reported a infra bug before, hoping to learn about the process,
  be gentle.

  This patch failed:

  https://review.openstack.org/#/c/29605/

  Since the tests passed when I ran them I don't think it should have
  failed.

  I looked at the console log and found:

  2013-05-21 15:23:48.950 | 2013-05-21 15:09:17,752 Response Body: 401
  Unauthorized

  Which when I went looking for it in the nova screen I saw:

  2013-05-21 15:09:17.748 19661 ERROR keystoneclient.common.cms [-] Verify error: Verification failure
  139833110791840:error:2E099064:CMS routines:CMS_SIGNERINFO_VERIFY_CERT:certificate verify error:cms_smime.c:304:Verify error:certificate is not yet valid

  Which I was then able to corrlate back to the test run as:

  2013-05-21 15:09:17.781 | ERROR

  Since the timestamps match I'm going all "post hoc ergo propter hoc"
  on it and saying the cert was messed up?

  But when I paw through the devstack log it looks like the .pem was
  created successfully:

  2013-05-21 15:52:33 Certificate is to be certified until May 19
  15:52:32 2023 GMT (3650 days)

  But that is like... *after* it already failed?  So... I think maybe
  there's a "bug"

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