Ideal configuration is vhost6 + IP address.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Fri, Apr 3
-ipaddress
$ salt-call --local state.apply roles/core/network/ipv6 local: ---------- ID: /etc/rc.conf.d/netif/ipv6_igb0 Function: file.managed Result: True Comment: File /etc/rc.conf.d/netif/ipv6_igb0 updated Started: 18:02:28.820428 Duration: 14.352 ms Changes: ---------- diff: --- +++ @@ -14,5 +14,5 @@ # </auto-generated>
$ salt-call --local state.apply roles/core/network/ipv6 local: ---------- ID: /etc/rc.conf.d/netif/ipv6_igb0 Function: file.managed Result: True Comment: File /etc/rc.conf.d/netif/ipv6_igb0 is in the correct state Started: 17:54:13.510501 Duration: 19.632 ms Changes: ---------- ID: /etc/rc.conf.d/routing/ipv6 Function: file.managed Result: True Comment: File /etc/rc.conf.d/routing/ipv6 updated Started: 17:54:13.530295 Duration: 11.486 ms Changes: ---------- diff: --- +++ @@ -14,6 +14,4 @@ # </auto-generated>
I've started a list of the points to check at https://agora.nasqueron.org/WindRiver#To_check_after_reboot
- NetBox ✅
- IP address exists: https://netbox.nasqueron.org/ipam/ip-addresses/112/
- IP address correctly assigned to igb0 interface: https://netbox.nasqueron.org/dcim/interfaces/12/
- Salt
- utils/netbox/pillarize.py windriver returns correctly 2001:bc8:2e84:700:0:dead:c0de:b07 alias
- Address added to pillar by 8202a28a
- /etc/rc.conf.d/netif/ipv6_igb0 contains the alias
Server was rebooted without .35 IP.
Tue, Mar 31
In D4035#63113, @dereckson wrote:OK with pillarize too?
OK with pillarize too?
If we're going to flood /var/log/messages with carp debug information, perhaps should we create a separate log topic, but that can be another change. I've created T2292.
Mon, Mar 30
Sun, Mar 29
Wed, Mar 25
Two actions to fix:
The nginx configuration doesn't seem the same for the Docker container and the development site:
Tue, Mar 24
Mon, Mar 23
I've asked upstream for advice how to resolve pillar for another server than the current node @ https://groups.google.com/g/salt-tower/c/XEKg2CEiZrU
The output is really useful to avoid to manually repeat the ports.
Rebased. Fixed pillar handling.
In D4026#62889, @dereckson wrote:Note: we're deploying a third secret for CARP routers scripts. If we've already that code merged, we'll need to append a line to deploy that state too.
Note: we're deploying a third secret for CARP routers scripts. If we've already that code merged, we'll need to append a line to deploy that state too.
Next: try salt web-001 paas_docker.get_upstreams
Rebased against current main for Alkane.
This change is interesting and should be rebased.