Fuel plugin builder: Privileges are not managed for plugin repositories
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Documentation Team |
Bug Description
Packages needed for deployment should have 755 mode, so wrong mode on packages included into plugin may lead to deployment failure during repositories merge:
...
multipath-tools
Authentication warning overridden.
Err http://
403 Forbidden
Failed to fetch http://
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Error: /Stage[
...
Issue:
The issue is that plugin builder not manages situation when privileges mode is different from expected by deployment framework.
FPB version:
fuel-plugin-
affects: | fuel-plugins → fuel |
Changed in fuel: | |
importance: | Undecided → Medium |
assignee: | nobody → Fuel Python Team (fuel-python) |
Changed in fuel: | |
importance: | Medium → Wishlist |
tags: | added: fuel-plugin-builder |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Andriy Popovych (popovych-andrey) |
status: | New → Confirmed |
milestone: | none → next |
milestone: | next → 7.0 |
importance: | Wishlist → Medium |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | added: area-docs |
I would like to see other people's opinions about this issue, as for me fuel plugin builder should not set priorities for packages which user adds, permissions should be management by user.