Comments (2)
Thank you @james-munson, when I ran the command kubectl get daemonset -n longhorn-system longhorn-manager -o yaml
, I saw the following output in the longhorn-manager container spec:
spec:
containers:
- command:
- longhorn-manager
- -d
- daemon
- --engine-image
- longhornio/longhorn-engine:v1.5.3
- --instance-manager-image
- longhornio/longhorn-instance-manager:v1.5.3
- --share-manager-image
- longhornio/longhorn-share-manager:v1.5.3
- --backing-image-manager-image
- longhornio/backing-image-manager:v1.5.3
- --support-bundle-manager-image
- longhornio/support-bundle-kit:v0.0.27
- --manager-image
- longhornio/longhorn-manager:v1.5.3
- --service-account
- longhorn-service-account
...
<OUTPUT_OMITTED>
...
image:<COMPANY_ARTIFACTORY_REGISTRY>/longhornio/longhorn-manager:v1.5.3
Our company Artifactory registry FQDN was specified in the image section but not in the command section. After adding it also to the command section, the output becomes as follows and the Longhorn installation succeeds !
spec:
containers:
- command:
- longhorn-manager
- -d
- daemon
- --engine-image
- <COMPANY_ARTIFACTORY_REGISTRY>/longhornio/longhorn-engine:v1.5.3
- --instance-manager-image
- <COMPANY_ARTIFACTORY_REGISTRY>/longhornio/longhorn-instance-manager:v1.5.3
- --share-manager-image
- <COMPANY_ARTIFACTORY_REGISTRY>/longhornio/longhorn-share-manager:v1.5.3
- --backing-image-manager-image
- <COMPANY_ARTIFACTORY_REGISTRY>/longhornio/backing-image-manager:v1.5.3
- --support-bundle-manager-image
- <COMPANY_ARTIFACTORY_REGISTRY>/longhornio/support-bundle-kit:v0.0.27
- --manager-image
- <COMPANY_ARTIFACTORY_REGISTRY>/longhornio/longhorn-manager:v1.5.3
- --service-account
- longhorn-service-account
...
<OUTPUT_OMITTED>
...
image:<COMPANY_ARTIFACTORY_REGISTRY>/longhornio/longhorn-manager:v1.5.3
from longhorn.
Agree with your analysis. The question is, where does the manager image name come from that is compared to the discovered container.Image
? Following the trail backwards, it seems to be here that upgrade.Upgrade() is called:
https://github.com/longhorn/longhorn-manager/blob/8919746dcfd7929dd4dcff4813ce37e4379cc5d8/app/daemon.go#L173
In that module, it was passed in as a flag to the longhorn-manager app's command line:
https://github.com/longhorn/longhorn-manager/blob/8919746dcfd7929dd4dcff4813ce37e4379cc5d8/app/daemon.go#L123
https://github.com/longhorn/longhorn-manager/blob/8919746dcfd7929dd4dcff4813ce37e4379cc5d8/app/daemon.go#L37-L48
So although it is not possible for you to attach a support bundle, it might be interesting to see the output of kubectl get daemonset longhorn-manager -o yaml
to look at the arguments.
from longhorn.
Related Issues (20)
- [BACKPORT][v1.6.3][IMPROVEMENT] Add setting to configure support bundle timeout for node bundle collection
- [BACKPORT][v1.5.6][IMPROVEMENT] Add setting to configure support bundle timeout for node bundle collection
- [TASK] Reference Architecture and Sizing Guidelines for Longhorn v1.7.x HOT 1
- [TEST] Investigate accessing lab behind vpn
- [BACKPORT][v1.6.3][IMPROVEMENT] System restore unable to restore volume with backing image HOT 1
- [BUG] Longhorn cifs backups cannot find credentials HOT 9
- [DOC] Incorrect and invalid links HOT 1
- Expanding the volume through UI but not reflecting it in backend. HOT 1
- [TEST][BUG] system restore stuck because of the volume/PV/PVC restoration
- [BACKPORT][v1.6.3][IMPROVEMENT] Improve and simplify chart values.yaml HOT 1
- [BACKPORT][v1.5.6][IMPROVEMENT] Improve and simplify chart values.yaml HOT 1
- Longhorn 1.6.2 - pvc is not ready for workloads HOT 1
- [BUG] Failed to delete a v2 orphan replica
- [FEATURE] Automatically attach the volumes for trimming filesystem HOT 1
- [TEST][FEATURE] Automatically attach the volumes for trimming filesystem
- [BUG] Fresh RWX volume on a fresh cluster install fails to ever mount (dual stack, IPv6-first cluster)
- [UI][IMPROVEMENT] Tweak some minor UI issues
- [UI][FEATURE] Multiple backup stores support
- [BUG] Request for a guide to the longhorn metric
- [BUG] System backup failed because backup creation failed. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from longhorn.