[osci] MOS CRs sometimes do not trigger package build
Bug #1405263 reported by
Dmitry Mescheryakov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
High
|
Unassigned | ||
Bug Description
Check out the following CRs into MOS:
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
They all do not have any mark or message from either from openstack-
| Changed in fuel: | |
| status: | New → Confirmed |
Revision history for this message
| Dmitry Mescheryakov (dmitrymex) wrote | #1 |
| Changed in fuel: | |
| status: | Confirmed → Invalid |
| Changed in fuel: | |
| assignee: | Registry Administrators (registry) → nobody |
To post a comment you must log in.
Ok, we actually already discussed that with OSCI team: the CI was triggered, but manually aborted by the team. Hence the bug is invalid.